-
Notifications
You must be signed in to change notification settings - Fork 15
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
Gaussian instantiation out of memory #11
Comments
Thanks for raising the issue. The reason is that each Gaussian needs to be initialized for each tile they appear in, so the theoretical maximum memory needed is (number of Gaussians * ceil(width / 16) * ceil(height / 16)). The renderer doesn't handle dynamic memory allocation right now, so everything is preallocated. You can try increasing the number here. |
Thanks for the reply. Btw, key control now have 2 translation (left/right and front/near), maybe there could be one more pair for up/down?
in
in And also, mouse control is not easy at some time (hard to rotate to the angle wanted). |
Hey these are great suggestions. Controls are a bit wonky right now. How I envisioned it is that the window would capture the mouse on click using |
Also the latest commit should add dynamic memory management. Feel free to give it a try. |
The latest commit worked with the 2nd model I used yesterday. About camera control, |
I added a few things that should bring better controls. The scene is not aligned right now and it's usually loaded up-side-down, so that's why it might feel a bit weird. I'll add some form of calibration in the future. |
Mouse click and ESC release makes control feel better. But I tried to move mouse left/right, and after some times, still the target model looks like rotating in roll direction. And I found it hard to change the camera to the other side of the model. |
There isn't really a good way to place the camera at the right position unless we read the training dataset as well. I might add that as an option. |
I thought the rotation vector should not just be like x or y axis.
(Btw, add a option for on/off showing origin point (0, 0, 0) and xyz axes direction may help debugging, if possible.) |
Good catch! I'll fix that. |
Hi, I have find some problem with
Gaussian instantiation out of memory
.First time, I run a ply file ~2.1GB, and it worked well.
GPU memory usage went to ~8.5GB at first, then went to 9.4GB when the render result showed.
The next time, I run a ply file ~500MB, which is an edited version of the first file, by deleting some 'fog' points.
GPU memory usage also went to ~8.5GB at first, but then it came out
Gaussian instantiation out of memory
.Why an edited small ply file causes out of memory?
The graphic card is Geforce RTX 2080 Ti 11GB.
Thanks.
The text was updated successfully, but these errors were encountered: