@Labuzan That is a really ancient driver, a search indicated it was used by Noah when designing the Ark, sorry 2023 but I am glad it works for you.
@adi99 The 577.00 is a relatively new driver can you manage to get back to an earlier version, i.e. will the NVidia software install and earlier driver. Many of my tests indicate that PL9.X is consuming a lot of memory very rapidly.
You could try my “trick”, providing you can get your machine in and out of “Sleep” mode easily and successfully every time. “Sleep” appears to clear the GPU VRAM and so you need to do the following
- Select all the images you are going to export and leave PL9 in that state, i.e. ready for just the export command
- Put the PC to “Sleep”
- When the PC is sound asleep, wake it up and it should return showing the images you selected
- Do nothing, absolutely nothing, except select ‘Export’, changing the location and the suffix doesn’t seem to trigger any GPU VRAM usage increase, in my case.
- Export and see if the export process can now complete successfully.
Yes its a pain but if you are trying to get JPG images to review then you may be successful. I have a 12GB GPU and a 16GB GPU (and a 6GB GPU which has now been retired!?) but not an 8GB GPU and have seen the memory usage under normal use rising to 12,000MB and 15,000MB and wondered how much does PL9 actually need?
Some users are surviving well on 8GB VRAM but …
@adi99 It is as I stated above and I was going to make a Topic entitled “Is PL9 playing fast and loose with GPU VRAM” but users experience are very varied.
The drivers of “choice” appear to be 573.24 and my 3060(12GB) appears to be able to handle my “problem” image successfully on that release but Nvidia won’t load that driver version for the 5060Ti(16GB) at all.
Plus tests I have done with 576.02, 581.29 and 581.42 on the 5060Ti(16GB) are showing 10 second differences from one release to the next!?
@Wlodek But why can I clear NVRAM(with Sleep) and successfully export images with just about 6GB VRAM, i.e. the AI required to render the image for export must be included in that VRAM usage.
But if I make a single edit then that figure will jump, potentially above 8GB.
It would appear that we have AI for export + denoising + AI for screen which will also need to handle denoising for the Loupe etc.
The NVRAM appears to be getting hit twice for AI, possibly even for NR(!?), i.e. is it using two discrete AI models or even the same model twice?




- 
