Suicide Squad: Kill the Franchise DLC
(media.kotakuinaction2.win)
You're viewing a single comment thread. View all comments, or full comment thread.
Comments (46)
sorted by:
Nah, that's letting them off lightly. It's clearly a bespoke mesh. Someone has to own making that. Someone without creativity, skill or the decency to rethink their career choice before completing it.
I wouldn't be surprised if you're right about the photogrammetry on the head though. I saw this posted over on NeoGAF. Another SBI self-insert?
Topology doesn't really have a noticeable impact on performance outside of polycount. Everything is triangulated, vertex cache optimisation is applied, etc. Uneven edge lengths and tri sizes can cause issues since they don't play nice with the clustered nature of rasterization (overshading), or more recently, the spatial indices used in raytracing, but outside of that your GPU isn't too concerned with how your topology looks.
The issue, assuming you wanted it watertight (which you might not), would be the resulting normals/tangents. But let's face it, shading artifacts would be a kindness.
Probably not unlike other studios tbh. Outside of specific requirements, like character creation or certain art styles, game character pipelines usually don't differ a great deal. I also doubt the characters are to blame for the performance problems. Open world in engines not tailored to it isn't an easy optimisation target.
No hard maths, unfortunately. There's simply too much variability between renderers, RHI's, target architectures, hardware configurations and scenes themselves.
The only advice I can really give is that game optimisation is a bit like software optimisation. Always profile and avoid premature optimisation (primarily micro-optimisation, like obsessing over topology). Dev time is finite, after all. Structural changes usually yield the greatest returns, but can become impractical in late development.
In practice, any number of things can introduce performance issues. That said, unless you have severely sub-optimal game systems or tricky requirements (eg. obscene NPC counts will require specific approaches to character animation, rendering and AI), environments are the most likely cause of poor performance in simpler projects.
Design your environments with your renderer in mind, starting with known limitations and general assumptions based on the rendering pipeline (forward, forward+, deferred all have "general" performance do's and don'ts). Starting in blocking, identify problematic sight lines and areas with poor occlusion or requiring a large number of dynamic and/or shadow casting lights. If you can't resolve these outright, you'll have to compensate with lesser fidelity in those areas. That should at least prevent you painting yourself into a corner/incurring significant rework.
Beyond that, efficient texture use, reasonable shader complexity, good use of instancing, good use of LODs and mesh aggregation, and a lot of care in regards to lighting and shadowing will be your primary means of producing something reasonably performant.