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 }}
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.
Since the bug that made export function export objects from the entire Blender file instead of just the current scene was fixed, it makes sense to make import function import segment into a new scene instead of just the current scene.
I also see this as an opportunity to teach beginner modders how to use scenes, or at least push them to that. So you could also rename the new scene to SHATTER_IMPORT in caps so they could notice this, click some buttons, and be interested. I think this actually improves the UX. :P
The text was updated successfully, but these errors were encountered:
I'd probably just name the scene after the name of the file, since that's probably what most people want and I think they would be forced to explore to find out where the default cube went anyway. :P
Not sure how to help people to realise you can keep many scenes in one file while also being somewhat consistent, honestly.
Since the bug that made export function export objects from the entire Blender file instead of just the current scene was fixed, it makes sense to make import function import segment into a new scene instead of just the current scene.
I also see this as an opportunity to teach beginner modders how to use scenes, or at least push them to that. So you could also rename the new scene to
SHATTER_IMPORT
in caps so they could notice this, click some buttons, and be interested. I think this actually improves the UX. :PThe text was updated successfully, but these errors were encountered: