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
Which commit/version of NanoVDB should I use? #125
Comments
Hi bobluoluo! The NanoVDB API probably changed slightly; I think the solution here is to fix the gNanoVDB sample. Give me about an hour or two, and a new version should be up! The previous checked version was about 10 months ago, so likely something went out of sync. |
Okay! Looks like the changes needed are a bit larger than I expected - NanoVDB now uses pointer offsets rather than child indices, and added new average and standard deviation fields which gNanoVDB doesn't write yet, so it'll take a bit longer for me to update the sample. In the meantime, I think commit AcademySoftwareFoundation/openvdb@cc79c0a might work - looks like version 8.1 included most of the breaking changes! |
Hi, Neil -- I'd like to bump this. I've tested the above branch and a few others without success. I tried a few older commits and get some CUDA asserts. Can you confirm which specific commit you used to get the Nano export working? Thanks! |
Hi digbeta! Apologies for the delay - I managed to get a new version about half-working (compiling and running but not yet exporting the volume correctly), but then had to switch to some high-priority tasks. Going historically, the last changes to gNanoVDB were in c2609c5, so that would probably correspond to AcademySoftwareFoundation/openvdb@d31daaf - maybe that would work? Thanks! |
I hit this as well with inability to use nanovdb. AFAIK nanovdb got added to the openvdb repo recently. With these older commits of openvdb, where are the nanovdb include files? |
Which specific commit/version of NanoVDB should I use. The latest one under feature/nanovdb branch is missing some members.
The text was updated successfully, but these errors were encountered: