Open kevintsq opened 3 months ago
I have a similar problem with the viewer, have you found a solution?
Unfortunately not yet.
I have the same issue under Windows
Hi,
thanks for bringing it up. We will try to look into it. I can think of two possible reasons that are not yet caught by error handling:
1) OpenGL/CUDA Interop is not working. Do these issues happen on a multi-GPU machine, or a laptop?
2) The memory budget set for the GPU is too high. If your GPU has less than 24 GB of RAM, you can try setting -budget
to, e.g. 70% of your total VRAM memory (in MB, e.g., for 6 GB budget, use --budget 6000
).
Thank you very much for your reply, here are some of the issues I've had, I'd appreciate it if you could take a look:
Hi,
thanks for bringing it up. We will try to look into it. I can think of two possible reasons that are not yet caught by error handling:
- OpenGL/CUDA Interop is not working. Do these issues happen on a multi-GPU machine, or a laptop?
- The memory budget set for the GPU is too high. If your GPU has less than 24 GB of RAM, you can try setting
-budget
to, e.g. 70% of your total VRAM memory (in MB, e.g., for 6 GB budget, use--budget 6000
).
Adding --budget 6000
works! Thanks!
I'm using a laptop that has been configured in the BIOS to use the dedicated GPU only. If I use the mix mode (integrated GPU + dedicated GPU), it will show a segmentation fault. After attaching a gdb
to it, it shows that the error comes from something like libcuda
.
Thanks for the responses. Regarding the issues on some systems: CUDA/OpenGL interop is required for high performance, and not all systems support it, unfortunately. We will try to add some guidance to the program to ensure it's as easy to activate as possible and provide a slower fallback on systems where it absolutely can't run, just like we did for the original 3DGS.
Thanks for the responses. Regarding the issues on some systems: CUDA/OpenGL interop is required for high performance, and not all systems support it, unfortunately. We will try to add some guidance to the program to ensure it's as easy to activate as possible and provide a slower fallback on systems where it absolutely can't run, just like we did for the original 3DGS.
Thank you very much for your hard work and look forward to your updates
same problem here, docker env: colmap/colmap unbuntu 22.04, pytorch 2.3.0+cu121, nvcc 12.1, GTX3080 10GB.
--budget not work.
Is there any other method can solve this problem ? for example, change a docker env, etc...
Thank you very much for your reply, here are some of the issues I've had, I'd appreciate it if you could take a look:
- I think it may be the first reason you said, but if it's this problem, I don't know how to solve it, because I tested it on a single graphics card, and I used 4090.
- Here are some of my screenshots in Interp. mode, most of the time it's all black, sometimes these spots appear.
- When I turn on "show sfm", I can see the point cloud, so the gaussian is not rendered.
- I don't have two small windows related to top viewe in my SIBR
Hello, I have encountered the same problem as you, may I ask if you have solved these problems
Thank you very much for your reply, here are some of the issues I've had, I'd appreciate it if you could take a look:
- I think it may be the first reason you said, but if it's this problem, I don't know how to solve it, because I tested it on a single graphics card, and I used 4090.
- Here are some of my screenshots in Interp. mode, most of the time it's all black, sometimes these spots appear.
- When I turn on "show sfm", I can see the point cloud, so the gaussian is not rendered.
- I don't have two small windows related to top viewe in my SIBR
Hello, I have encountered the same problem as you, may I ask if you have solved these problems
Sorry I didn't. I still could not render the scene.
Ubuntu 20.04, CUDA 12.1
The directory is as follows: