-
Notifications
You must be signed in to change notification settings - Fork 60
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
SIBR_gaussianViewer_app build and runtime issues - "PyTorch is not linked with support for CUDA devices" #77
Comments
Can you successfully compile with the |
Sorry for the delay in responding, I have been on holiday. Yes, I can successfully compile
It seems that |
Hello,
I'm trying to build the SIBR_gaussianViewer_app from your sources, but I'm having runtime issues. Let me explain what I've done to build it, let's focus on debug configuration:
2.1. On Windows 11
2.2. CMake GUI 3.29.2, I've added
OpenCV_RUNTIME=vc17
entry2.3. With Visual Studio 2022 LTSC 17.8 (17.8.12)
2.4. Python 3.10
2.5. CUDA 11.8
src/core/viewer
folder from original SIBR repositoryextlibs/
directorySIBR_gaussianViewer_app
andsibr_gaussian
project in Visual Studio according to your READMESIBR_gaussianViewer_app
(debug configuration) and copied all missing dlls to install directoryWhat I'm getting with such build is an unhandled exception:
Unhandled exception at 0x00007FFE2FE1FABC in SIBR_gaussianViewer_app_d.exe: Microsoft C++ exception: c10::Error at memory location 0x0000009458EFA7D0.
at line
TORCH_CHECK(p, "PyTorch is not linked with support for ", type, " devices");
From
SIBR_viewers\extlibs\libtorch\debug\include\c10\core\impl\DeviceGuardImplInterface.h:318
It's caused by
p
beingnull
, sodevice_guard_impl_registry[1]
(CUDA
is1
) isnull
.The stacktrace shows that dll being used is
torch_cpu.dll
.I tried using other builds of torch 1.10, but that caused fail on loading data from file, which seems to be a library version compatibility issue:
opacity_mlp_module = torch::jit::load(opacity_mlp_path, _libtorch_device);
Could you help me with this issue?
The text was updated successfully, but these errors were encountered: