^
by user 534547469992853534
Hello, do you have a stacktrace and some example where it happens (which file and line) / information about when it happens? E.g. on export or at runtime at a what moment?
hi @marcel 
this happens in this screen recording
by user 534547469992853534
by user 534547469992853534
does that mean the file is too big?
by user 534547469992853534
i downloaded toktx but its still showing the rangeError 
by user 534547469992853534
this is from the console log
by user 534547469992853534
It sounds like something is calling itself. can you figure out where the original call is made?
I mean who makes the “get component in parent” call.
it seems like it’s from Three JS?
by user 534547469992853534
So it’s not from Needle Engine
by user 534547469992853534
How did you come to that conclusion? Does it always happen in that scene?
I only have 1 scene
by user 534547469992853534
So far
by user 534547469992853534
give me a second to verify
by user 534547469992853534
i will try this solution when i get back
by user 534547469992853534
This will not help here tho since youre not using unity’s webgl build but you directly export to Threejs. Unity is not involved in errors at runtime (like the range error exception). So we must figure out whats causing the recursive calls (at least i assume thats the bug).
Some things to try:
-
You can try looking at the stacktrace of the error in chrome (the arrow to the left of the error message to open it) and see if it contains any other info than this one method call
-
try disabling parts of your scene and re export to figure out which object or part of the hierarchy is causing the error (when you disable one object and the error is gone it might be that the disabled object / a component on the object or its children is the cause - ideally find the component that causes it)
-
if above fails please run “Help/Needle Engine/Zip Scene” and send me the zip in a DM. I can try having a look at it after the holidays