15-05-2023, 11:43 AM
Hello.
I tried to reproduce the "Benchmark" scene programmatically with my own 32 procedurally generated patches of cloth (no wind though). Everything worked fine! The blueprints, the connections with solvers, updaters, and so on. However, I observed differences in displayed FPS values: My scene always runs at 75% FPS relative to the benchmark scene. Since both are opened in the same project I don't suspect Unity's time/fixed time-settings, or similar things, to interfere here.
I also checked:
- updater cycles
- enabled constraints in solver
I even have no environment geometry, no textures and no wind, as mentioned.
Has anyone an idea what the reason for lower FPS could be in this case?
Thank you.
I tried to reproduce the "Benchmark" scene programmatically with my own 32 procedurally generated patches of cloth (no wind though). Everything worked fine! The blueprints, the connections with solvers, updaters, and so on. However, I observed differences in displayed FPS values: My scene always runs at 75% FPS relative to the benchmark scene. Since both are opened in the same project I don't suspect Unity's time/fixed time-settings, or similar things, to interfere here.
I also checked:
- updater cycles
- enabled constraints in solver
I even have no environment geometry, no textures and no wind, as mentioned.
Has anyone an idea what the reason for lower FPS could be in this case?
Thank you.