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
Hi there, I really appreciate the work you've put in to the road geometry creation logic, it seems to work very well. However I am seeing a large number of draw calls (it appears to be correlated with the # of lengthSegments and "segments" of road)
it is difficult for me to use this inside of a more complicated scene that is already draw call constrained
For example opening this scene in an oculus quest results in dropped frames, ostensibly due to draw call count not total polygon count
Instead:
is it possible to refactor the road creation functions such that only 1 draw call is used for the length of each segment? ie in this demo case there would be 5 draw calls regardless of lengthSegments value
Workaround:
In the meantime I will try testing with much lower values for lengthSegments and curvePoints to see if I can get draw calls to a useable threshold with the existing code base
The text was updated successfully, but these errors were encountered:
Thanks @hofk appreciate the project background info! I have some work to continue that doesn't depend on this but if it becomes a true blocker then I will dig in more and add more requests for help from others.
Hi there, I really appreciate the work you've put in to the road geometry creation logic, it seems to work very well. However I am seeing a large number of draw calls (it appears to be correlated with the # of lengthSegments and "segments" of road)
To reproduce issue:
renderer.info.render
and press entercalls: 5006
(or similar number)Impact:
Instead:
Workaround:
The text was updated successfully, but these errors were encountered: