Python S3O module and optimizer
Moderator: Moderators
Re: Python S3O module and optimizer
Suggestions to handle these cases? Perhaps a lower limit on the number of vertices before it decides to optimize.
Re: Python S3O module and optimizer
Yeah, don't optimize under 16 vertices. The gain negligible there anyway.
Re: Python S3O module and optimizer
Hm. Is there perhaps any more reliable way of detecting this? Optimizing 16-vertex meshes would still be a performance improvement if they were drawn often.
- Deadnight Warrior
- Posts: 183
- Joined: 08 Jun 2009, 17:59
Re: Python S3O module and optimizer
I tried it on XTA, since it uses Mr D's core vehicle models, and the result was only 2 or 3 files out of ~20 got optimized. When I tested the performance of those optimized units, there was no FPS gain and I was even sure that in case of CORE Cloakable fusion power plant I saw a FPS reduction.
Re: Python S3O module and optimizer
Ask Nemo what he did when fixing the issue in S44, it was something trivial afaik.Muon wrote:Hm. Is there perhaps any more reliable way of detecting this? Optimizing 16-vertex meshes would still be a performance improvement if they were drawn often.
Re: Python S3O module and optimizer
Hm, I should probably make the decision whether or not to save the optimized S3O depending on whether or not the ACMR goes down, rather than file size.Deadnight Warrior wrote:I tried it on XTA, since it uses Mr D's core vehicle models, and the result was only 2 or 3 files out of ~20 got optimized. When I tested the performance of those optimized units, there was no FPS gain and I was even sure that in case of CORE Cloakable fusion power plant I saw a FPS reduction.
EDIT: Okay, updated. Now it commits anyway, because it may have optimized drawing regardless of the change in file size. I should point out that the vertex cache optimizer only works on triangles, but not quads or tri strips.
EDIT EDIT: I've run the optimizer on that model, and the ACMR goes from 2.009901 to 0.982673, which means it *should* yield a performance improvement.
Re: Python S3O module and optimizer
I would say anything under 4 vertices can definitely be left unoptimized.
Btw I use your s3olib extensively. Its super nice and well built!
Btw I use your s3olib extensively. Its super nice and well built!
Re: Python S3O module and optimizer
Anything you could contribute back to the repo?Beherith wrote:I would say anything under 4 vertices can definitely be left unoptimized.
Btw I use your s3olib extensively. Its super nice and well built!
- Forboding Angel
- Evolution RTS Developer
- Posts: 14673
- Joined: 17 Nov 2005, 02:43
Re: Python S3O module and optimizer
Upspring 1.54 is very reliable. It has it's quirks, but it is more or less rock solid. I have far more trouble with spring doing stupid shit to models than upspring.FLOZi wrote:In what quantum reality is Upspring reliable?