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
I've put a lot of work into developing my own brand new voxel model file format and I'd really like Vengi tools to be made capable of reading and writing it.
It's actually two formats: one JSON based and one binary.
This is all brand new stuff and may still get changes if anyone has any better ideas to suggest but I think I've come up with a really good standard for the purpose which is also extensible (via properties) without people's extensions breaking interoperability. So for instance, data that Vengi editor might need which isn't meaningful for other programs might go in properties with names prefixed with _VENGI. or something like that. The palettes and voxels would all still work for other programs no matter what's in those properties.
The text was updated successfully, but these errors were encountered:
I've put a lot of work into developing my own brand new voxel model file format and I'd really like Vengi tools to be made capable of reading and writing it.
It's actually two formats: one JSON based and one binary.
This is all brand new stuff and may still get changes if anyone has any better ideas to suggest but I think I've come up with a really good standard for the purpose which is also extensible (via properties) without people's extensions breaking interoperability. So for instance, data that Vengi editor might need which isn't meaningful for other programs might go in properties with names prefixed with
_VENGI.
or something like that. The palettes and voxels would all still work for other programs no matter what's in those properties.The text was updated successfully, but these errors were encountered: