Feature #120
Updated by Fredrick Amnehagen almost 4 years ago
According to the documentation, there should be more than one way to store information in blender.
One of which would be to create an "empty" object with a special name that has "custom properties", however the user might accidentally remove this object or misplace it in the hierarchy. Before moving forward with that way of implementation, check if there are other ways. Maybe something like custom properties on the blend-file itself inside blender.
- One button to initiate the blend file as an ecos world file.
becos format:
https://docs.google.com/spreadsheets/d/1gMfOqDk0wxMTHolGAFGY8fNrjggF-oJr15eNS5t0Xgg/edit#gid=203527558
One of which would be to create an "empty" object with a special name that has "custom properties", however the user might accidentally remove this object or misplace it in the hierarchy. Before moving forward with that way of implementation, check if there are other ways. Maybe something like custom properties on the blend-file itself inside blender.
- One button to initiate the blend file as an ecos world file.
becos format:
https://docs.google.com/spreadsheets/d/1gMfOqDk0wxMTHolGAFGY8fNrjggF-oJr15eNS5t0Xgg/edit#gid=203527558