GPU memory issue

[iuliia_bogdan]

I have a scene that I have already rendered well in Vantage, but now I get the error that I don't have enough GPU memory. Although everything was fine before and I didn't have any problems. Now almost all the scenes tell me that the GPU memory I have is not enough to render.
I use the Nvidia Geforce RTX 4070 TI super graphics card, it has 16 GB of memory. And I have the last Vantage 2.5.1 version.
How do you think it can be fixed? What can be a problem?

[iuliia_bogdan]

I also get this message. I've tried uninstalling and reinstalling Vantage, but it's still the same

[Alexander.Atanasov]

Hi iuliia_bogdan,

What version have you used previously that rendered out without a problem? If you switch back to it does the issue persist?

Best regards,
Alexander

[npg]

We fixed some errors in the estimated required memory in the render dialog with version 2.5.0. It could be that the usage is the same and it just wasn't properly calculated before, at least if we're talking about this red colored text. Or maybe it really is using more memory now, it's hard to tell.

The screenshot shows a negative value on the right side, which is the currently available memory. So it seems you've already used more memory than the GPU has on board (Windows does some magic to allow that). Have you disabled the "Safe GPU allocations" option in Preferences?

You can find older builds by checking the "Show all versions" box here: https://download.chaos.com/?platform=47&product=63

[iuliia_bogdan]

Thanks for your replies. I installed the previous version, Vantage 2.4.0, and disabled the "Safe GPU Allocations" option, but that didn't resolve the issue.

What’s weird for me is that I had worked with this scene before, and it rendered successfully several times. The scene and the objects in it haven't changed in weight or complexity. However, when I opened the scene yesterday to make a minor adjustment and tried rendering again, it failed to work entirely.

[vladimir.nedev]

Can you send us the scene for testing ? Does it fail only when rendering at 4k resolution ?

Greetings,
Vladimir Nedev

[iuliia_bogdan]

Thanks for your reply again.
I can share the scene with you later.
Today, I tried rendering a different scene, and it rendered correctly, it was a really simple scene. However, another scene that I previously managed to render successfully isn't working now. This scene is also simple but includes some animations. It appears to be okay for rendering, but when I press the render button, nothing happens. Disabling the "Safe GPU Allocations" doesn’t seem to help; the scene still won’t render. Any ideas on what might be going wrong?
It just seems that Vantage stopped working properly overnight. It didn't use to give me so many problems before.

[Luma3d]

Did you try clearing your Temp folder. I've been able to fix allocated memory issues with deleting files in my Temp folder. Seems to clear the cache some how.

[ugo_ledru]

Hello, I did have this issue in the past and solved it by making sure all my maps and geometries were properly linked in the asset editor. I work on Sketchup/Vray/Vantage and Sketchup comes up with 'embedded' files which can be seen on the File Path Editor (appearing in yellow). These 'embedded' files are not properly linked and therefore created the same memory issue for me. Perhaps a single added material map might tilt Vantage toward the side where it is too much to handle, hence your issue appearing one day out of the blue. Once I updated all the correct paths, I solved the memory issue of Vantage. I am not sure if this is valid for all Softwares though.

[michal_baurycza]

Hey guys!

Same issue here. I have one scene and 2.5.2 eats all the ram on GPU (RTX 3090) so I'm not even able to see the Live link but 2.5.1 works perfectly and keeps the ram usage at around 12GB.

[npg]

Are you getting a specific error? Can you try monitoring the video memory usage with GPU-Z and compare the new and old version?

[mat_olszowy]

scene that worked before and rendered in 6k, now even Vantage can't open. The version of 3ds Max (2024) or Vantage (2.5) hasn't changed.

After removing all scatters it opened with surprisingly high RAM usage considering that there were only a few houses in the scene.

After updating Vantage to 2.5.2 the same scene (original and cleaned) no longer opened, consuming all ram.

Something is wrong with memory allocation.

[npg]

Hi mat_olszowy, do you have TWO 4090 cards or just one?

Is this log from the scene you managed to open without scatters "with surprisingly high RAM usage"? The log file is from October 4th. It shows LOW usage of VRAM.

[mat_olszowy]

Hi, I have only one RTX 4090 but I don't know why vantage shows me in setting two devices while windows only one.
This day I have multiple crashes becuase of "low memory", and i thought that I will find multiple logs from this day.- but I can find only one and only for version 2.5.2.
it looks that it could wrong log, but i don't have different one. (or I don't know where to find)

I

[npg]

OK, there are several things related to this:
- Apparently the virtual display adapter is causing DirectX to list the 4090 twice (it is a microsoft bug) and it is difficult to recognize that it is not a real second GPU. We've seen this issue before and we will try to find a way to reject this fake second device.
- There is a new bug that exists only in 2.5.2 and is already fixed for the next update -- the device selection is not restored properly when you restart Vantage so it will use up to two devices automatically, as if you never selected any. You can either use 2.5.1 until we release an update (in a few weeks) or create a shortcut that calls "vantage.exe -d 0" to force the first device to be used every time.
- Our log file is "debug_log.txt" by default and it gets overwritten every time you start Vantage. The file you have has a "_pidXXXXX" suffix because you ran a second instance of vantage.exe while another one was already running, so it created a separate log file.

Finally, because of these bugs you end up running Vantage in multi-gpu mode, even though the second gpu is not real. It still operates as if there are two and the scene contents are uploaded twice to the same physical gpu. If you run 2.5.1 with a single device selected (or 2.5.2 with the shortcut trick), it should work like before. By the way if you can disable this Parsec virtual display it should also prevent Vantage from detecting a second device. You can verify if Vantage is rendering on one or two devices by looking at the status bar at the bottom right. If there are two, it will say "2x 4090".