Skip to content
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

VOXELFORMAT: BenVoxel #546

Open
BenMcLean opened this issue Nov 17, 2024 · 0 comments
Open

VOXELFORMAT: BenVoxel #546

BenMcLean opened this issue Nov 17, 2024 · 0 comments

Comments

@BenMcLean
Copy link

BenMcLean commented Nov 17, 2024

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.

mgerhardy added a commit that referenced this issue Nov 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant