![]() You're CPU limited anyway: It can be well worth doing some extra work on the application side to reduce the workload of the software renderer. Reduce overdraw: One of the most effective approaches is to first render the scene to the z-buffer only, then perform a second pass with color calculations enabled. Everything else needs to be converted anyway and it's often not worth the bandwidth savings. Use data formats 'native' to the CPU: 8-bit, 16-bit, 32-bit data elements are typically faster. ![]() ![]() It won't speed up hardware rendering but it will affect software rendering. For instance to render a 2D menu, disable bilinear filtering and mipmapping. Nothing comes for free: Any feature you use translates to extra code. Anyway, here are a few basic guidelines (off the top of my head): Currently we have a whitepaper explaining the overall architecture, but we exchange optimization details on a per-customer/application basis. Click to expand.That might become a good idea in the near future.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |