-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Repositioning objects doesn't re-export scene #145
Comments
Hi @DylanRJohnston !
|
Hey @kaosat-dev, the objects in the scene are collection instances i.e. blueprints. Moving them doesn't seem to trigger the change detection code at all. |
Hi @DylanRJohnston :
|
@DylanRJohnston could you please send the information above so I can track down the issue ? :) Thanks ! |
Hey kaosat, apologies for not supplying more information initially, I thought the problem might be easy to reproduce for you since it was happening reliably for me, but since you already have tests covering these cases and given the other problems I've been encountering perhaps something fundamental about my setup is misconfiguration. |
Thanks for the screenshots and information ! |
Ok, tried it out, and still cannot reproduce the issue, change is detected correctly no matter the nesting level of an object ... |
How do Blender plugins handle python dependencies? Maybe I'm ending up with slightly different packages due to something in my environment? |
Is there any way to force the export each time instead of checking for changes? I'm encountering an issue where repositioning objects in the scene does not cause the auto export to properly save. Only deleting the
Scene.glb
properly exports the scene.The text was updated successfully, but these errors were encountered: