You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I fixed some bugs in the Tools/commands by changing the Ressource-Limit-constants in "tools/utils/GeomUtils.as".
As it is right now, it is working for all tools i tested, but i made a lot of tests and think we could set the ressource-Limits higher if we use different LIMIT-constants for verticles and indicies.
Right now the LIMIT for indicies is 3*0xffff (=196605), but the indexBuffer can have a length of 983038 before throwing a error.
The correct LIMIT for the verticle-count seams to be 0xffff (65505).
By using this new LIMITS, tools like mirror or explode, will split into fewer subGeometrys as before.
I thought using fewer Subgeometrys would be a good thing, but the fewer (bigger) subgeometrys are consuming more memory than a lot more (but smaller) subGeometrys.
See this Pic:
I am not shure if i should add this changed LIMIT-values to my commit #503
Any suggestions ?
The text was updated successfully, but these errors were encountered:
As you can see in the pic i put in #496, with the new ressource-limits, we can create ca 4 times as much triangles that have SubSurfaceScattering applied, than with the old limits (before the "Ressource-Limit-reached-Error" is thrown).
I fixed some bugs in the Tools/commands by changing the Ressource-Limit-constants in "tools/utils/GeomUtils.as".
As it is right now, it is working for all tools i tested, but i made a lot of tests and think we could set the ressource-Limits higher if we use different LIMIT-constants for verticles and indicies.
Right now the LIMIT for indicies is 3*0xffff (=196605), but the indexBuffer can have a length of 983038 before throwing a error.
The correct LIMIT for the verticle-count seams to be 0xffff (65505).
By using this new LIMITS, tools like mirror or explode, will split into fewer subGeometrys as before.
I thought using fewer Subgeometrys would be a good thing, but the fewer (bigger) subgeometrys are consuming more memory than a lot more (but smaller) subGeometrys.
See this Pic:
![limit_ressourcest](https://camo.githubusercontent.com/b618e58f888cf8a4b5bd61aac0d0baaa558d44b29aa181046f4d09ad04b6991a/68747470733a2f2f662e636c6f75642e6769746875622e636f6d2f6173736574732f313134333936392f3337353738362f63613533316564302d613363662d313165322d393766312d3365326134626636656531662e6a7067)
I am not shure if i should add this changed LIMIT-values to my commit #503
Any suggestions ?
The text was updated successfully, but these errors were encountered: