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
249: Convert Workflows #381
Comments
See here for more details as we research: Workflow Translations |
Converting and unit testing! |
If you have multiple scenes, the naming works differently in regular mode. With one scene, it is the file name. With multiple it is the Scene name. We'll need multiple 249_NEW_ROOT empties with different names for this. |
Closes with dbb5971 |
Currently the API is not consistent, some sub converters take all the objects in a scene, some take new root objects which get searched (which breaks SKIP work flows), some take all objects period. In addition, some return a list of objects created, a list of objects touched, true or false if there was problem. (Could be messing up my memory, but just look at it). SKIP needs to work, and I think there should be some consistency or more thought into what these return. There is the principle of "You aren't going to need it", but, something sensible should be done |
Since the ability to SKIP has been decided to remove, we are ready to close this. |
2.49 had 2 distinct workflows (we care about) and used Blender Objects in certain ways to achieve their means, we have something similar (but not a 1:1). We're going to need to convert the workflow so this works and ask users what they meant (if we can't guess ourselves) whether they used Bulk Export or Regular.
The text was updated successfully, but these errors were encountered: