Blender addon "Group by Collections" - Rescan button

Version: ALL

Frequency: Consistently

Severity: High

Context: You already have collections set with LOD values entered, then you want to add collection to make another object within the same blender file.

Bug description: In order to get the gltf exporter to recognize another collection that you’ve added you have to uncheck and recheck "grouped by collections, which erases all your entered data for the previous collections. If its possible can we get a rescan button that would recognize new collections while keeping the data for the existing collections?

2 Likes

@Yasmine :wink:

@Yasmine Lets say i already did these LODs


Now let say i decide i need to add another LOD to 1 of them. Or lets say i want to make a new object in this same Blender File. This means i must press the Reload LODs button. Which does this

All the previously entered data is gone.

Is it possible to have a button where it just scans for New Lod Collections instead of reloading them all and forgetting the data.

1 Like

Hello,

Which version of the blender addon are you using ?

1 Like

Addon Version 3.6
with blender version 3.6.17

1 Like

You can find the addon version in Edit>Preferences>Addons :
Capture d’écran 2024-12-10 155626

Yes, Its 0.3.6

You should update your Core SDK 2024 then, the latest version of the addon is 1.3.2.

Thank you

It does the same thing in the most recent add-ons. Reload LODS deletes all the data of other collections

1 Like

Hello @SLH,
Can you confirm this is fixed using the last Blender Plugin (2.3.1) ?

Regards,
Boris

The latest version I have is 1.3.2 and reloading LODS still deletes the MIN size values and Export paths of all the other collections. @Yasmine @Boris I just realized it works fine when you don’t have “Group by collections” ticked. But I feel most of us mostly use “Group by collections” and when you press Reload LODs it deletes all the data once you have that ticked.

where in Exporter 2.3.1? I can’t find it?

1 Like

@Boris yes it is fixed in 2.3.1

1 Like