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

Split octree file format in some way to allow for better error handling #1251

Open
NotStirred opened this issue Apr 29, 2022 · 3 comments
Open

Comments

@NotStirred
Copy link
Member

Currently if anything in octree loading has any error the state of everything is unknown, and any data that hasn't yet been loaded is completely lost

Perhaps just having a different data stream for every major thing, combined later would solve this.

It concerns me that a single error in any part of loading makes the entire thing unloadable (particularly because I've just edited it in #1225 🤣)

@MadDog443
Copy link

MadDog443 commented Apr 29, 2022

This would save me hours considering I've done a few mega renders that go over 300k chunks. When it comes across an error and I have to start over again it can take up a lot of time going through trial and error.

@NotStirred
Copy link
Member Author

Sorry, by "Octree Loading" I'm referring to loading from save, not loading new chunks into an octree

@MadDog443
Copy link

MadDog443 commented May 4, 2022

Sorry, by "Octree Loading" I'm referring to loading from save, not loading new chunks into an octree

Damn. This is a sad day. Still handy though.

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

2 participants