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
{{ message }}
Repository navigation
Moving an entity using appendChild makes the entity disappear as of v0.9.2 #4316
Moving an entity using appendChild makes the entity disappear as of v0.9.2
Expected behavior (which worked with v0.9.0 and before) is for the entity to remain visible although perhaps this behavior was not guaranteed and is related to #2425 ?
A-Frame Version: 0.9.2
Platform / Device: Firefox 70.0.1 on OS X, Macbook Air
i am also getting this behaviour i believe in 1.0.4:
when trying to move an existing visible element child from one parent oldParent to another newParent in the scene, with:
newParent.appendChild(child)
afterwards, the javascript object exists, but the child entity is invisible.
as far as i could tell the child's object3D.parent was correctly set to the newParent's object3d after appending.
i'm also posting other problems around moving elements around scene hierarchy related to transformations to #2425
We recommend reparenting at the THREE.js level Attaching / reattaching and re initializing components is costly and not always reliable (components have to account for a complex costly scenario that is relatively rare)
Activity
damned commentedon Jul 5, 2020
i am also getting this behaviour i believe in 1.0.4:
when trying to move an existing visible element
childfrom one parentoldParentto anothernewParentin the scene, with:afterwards, the javascript object exists, but the
childentity is invisible.as far as i could tell the
child'sobject3D.parentwas correctly set to thenewParent'sobject3dafter appending.i'm also posting other problems around moving elements around scene hierarchy related to transformations to #2425
dmarcos commentedon Oct 23, 2020
We recommend reparenting at the THREE.js level Attaching / reattaching and re initializing components is costly and not always reliable (components have to account for a complex costly scenario that is relatively rare)