-
-
Notifications
You must be signed in to change notification settings - Fork 35.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ColladaLoader instance nodes imported with names like 'instance_0' #13365
Comments
👍 |
alright i am super close, i just need a way of referencing the previous version of i have logging in the console to show the part of the scene that has the you can find my dae at https://raw.githubusercontent.com/shelbyspeegle/threejs-13365/master/source-model.dae. |
Can you please check what happens if you change the following line of code to: if ( object.name === '' ) object.name = ( type === 'JOINT' ) ? data.sid : data.name; Does this change improve the names of your scene graph elements? |
yes! thanks for the line number too! passing all my tests now without special lookup against library nodes 👍 |
Do you wanna make a PR with the change? I think we can put this in |
sure! |
…ciated library nodes name, vs 'instance_#'.
Description of the problem
After the replacement of
ColladaLoader
withColladaLoader2
(now named justColladaLoader
), it looks like the imported information has changed a little bit.heres a (condensed) snippet of my dae.
the behavior that i used to see was that the imported dae object would look like this:
now it is looking like this:
is this the expected output? on one hand i see at as incorrect because of how
ColladaLoader
used to work, but on the other hand i see it as correct because it matches how the dae is represented.i am able to achieve what i need by doing a search through
library.nodes
and marrying the 'instance' up with its original definition and getting that name.would you accept a PR if i ensure that instance nodes are coming through with their definitions name rather than
'instance_0'
,'instance_1'
etc?i'll work on putting together a jsfiddle and updating this issue once complete.
Three.js version
Browser
OS
Hardware Requirements (graphics card, VR Device, ...)
The text was updated successfully, but these errors were encountered: