kaosat-dev / Blenvy

Bevy Code & Blender addon for a simple workflow to add & edit Bevy components in Blender

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Repositioning objects doesn't re-export scene

DylanRJohnston opened this issue · comments

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.

Screenshot 2024-02-23 at 4 54 49 pm

I can confirm after forking the code that a brute force if True: here and here fixes the issue. Perhaps there could be a setting that just always exports everything? Or would you rather fix up the change detection?

Hi @DylanRJohnston !
Could you tell a bit more about your setup please ?

  • are the objects that you are moving in a main scene, library scene etc ?

  • are the objects blueprints, instances, something else ?

  • I added the ability to force export (really not recommended from my experience, but it can be practical) to this pr: #143

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 :
Very weird, that always worked reliably, and is now also one of the test cases.
thanks for the info, could you please send screenshots of:

  • your export settings
  • your scene with the objects that you are moving, including the outliner ?

@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.

Library Outline

Scene Outline

Export Settings

Thanks for the screenshots and information !
I think I might know where the issue comes from, I need to try it out on my end too to double check : your setup seems similar to what I usually use & have in the tests except that your objects in your main scene are nested inside collections.
I'll get back to you once I checked things out.

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?