-
Notifications
You must be signed in to change notification settings - Fork 21
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
can't run the vpt #1
Comments
Yes the file path is hardcoded at main.cpp. Try full path if you are having problems at finding the file. For compilation of cudapp, please refer to https://github.com/NVIDIA/gvdb-voxels |
Could you please upload a vpt.exe, Thanks. |
I can but the exe will still be my file system specific. I will add the vdb file path as an argument later. Could you try a full path to vdb in "gvdb.LoadVDB(scnpath);" replacing scnpath. |
Don't work, it don't failed here. I compile the libgvdb.lib my self now, but it still failed, when call cudaMalloc, it will lead to out of memory, it's strange, because cudaMalloc should alloc memory on GPU. |
Ok. Will look into that. |
The crash is beed fixed, it's a bug of shared_cudpp. But the vdb can't been loaded, becuase when generate the project sln file, the macro "BUILD_OPENVDB" didn't been add to the project. I find the "FindOpenVDB.cmake" in folder thirdparty\gvdb\sample_utils, but in the source\CMakeLists.txt, it didn't use openvdb lib. |
Can you try building this fork https://github.com/sergeneren/gvdb-voxels I've automated cmake a little bit to grab openvdb libraries from vcpkg. |
Thanks. ps, nvidia update some makefile recently, fix the error. |
Win 10, cuda 10.1, vs 2017
GVDB CUDA ERROR:
Launch status: file not found
Kernel status: no error
Caller: VolumeGVDB::LoadFunction
Call: cuModuleLoad
Args: D:/PROJECTS/gvdb-voxels/_output/lib/cuda_gvdb_module.ptx
Error. Application will exit.
i don't compile gvdb-voxels myself, so this is because some hardcode the gvdb path?
ps, how to compile shared_cudpp which in the gvdb-voxels?
use the cmake, can't compile the shared _cudpp.
Thanks.
The text was updated successfully, but these errors were encountered: