Skip to main content
Participating Frequently
October 23, 2023

Substance 3D Painter 4K Viewport Textures using excessive VRAM? 7900 XTX

  • October 23, 2023
  • 10 replies
  • 1618 views

My scene is 3x UDIMS - quite small I thought. However when I switch my viewport Textures to 4K, my VRAM usage spikes and continues to climb over the next 1-2min until it uses all 24GB of my 7900 XTX - sometimes this doesn't take long at all though (less then 1min). Once VRAM is full, obviously Substance breaks and viewport becomes corrupted - substance slows down to a craw, is unresponsive and I have to restart. Lowering textures to 2k fixes it but I didn't think it should be using the whole 24GB of VRAM for my scene at 4k viewport?

 

I'm running Substance 3D Painter 9.0.1 on a 7900 XTX with up to date drivers. I have 64GB of system Ram.

Is this expected behavior or is something broken?

    10 replies

    Participant
    January 9, 2024

    Thanks for getting back to me.

    I have updated my Intel graphics driver and I have set Substance Painter to use my 7900XTX via windows graphics settings (I believe this should be the same as the nvidia control panel method? If not I can install nvidia control panel and repeat the steps). I have also checked my painter settings and Sparse virtual texture is off by default. I also have none of the programs known to conflict.

    Once piece of information that might help is that I now believe the reason my PC freezes due to this issue is because I have 32GB RAM compared to OPs 64GB. Once my VRAM is full my system memory also appears to start clogging up.


    Cyril Dellenbach
    Community Manager
    Community Manager
    January 9, 2024

    Thanks for all the details, it really helps troubleshooting. I can see from your log an outdated GPU, which I think is the Intel UHD Graphics. You can always try to update it, but to be honest, I doubt this is related.

     

    That being said, Substance 3D Painter could run with the Intel GPU instead of the NVIDIA for some reason. Therefore, I advise you to set the preferred GPU with the NVIDIA control panel.

     

    • Open the NVIDIA Control Panel application
    • Navigate to Manage 3D settings
    • Select the Program Settings tab
     
    • Under Select a program to customize option locate Adobe Substance 3D Painter in the list
    • Select the high performance NVIDIA processor as the option for preferred graphics program for Painter

     

    If this doesn't help, make sure to deactivate the hardwer support acceleration in Edit > Setting > Sparse virtual texture which could be a source of problem for AMD.

     

    Lastely, it's always worth to check the list of Software Conflicts. The issue could come from somewhere else.

     

    Keep me updated on the matter, I'll share your dataset with the team, and we'll try to reproduce the problem on our end.

     

    Cyril Dellenbach (Micro) | QA Support Artist | Adobe
    Participant
    January 9, 2024

    Just an update, I saw that there was an update which I hadn't installed (9.1.1). However after installing this the issue still happens. 

    I am easily able to trigger the crashes on all the substance versions I have tried by changing a mesh map in either of the projects I had opened (Normal, AO or Curvature. Curvature seems to be more consistent). And again lowering the texture resolution partially mitigates the issue, I have had it happen a few times on 2048 but not at all when running at 1024. Here is a video of the issue and here is my 9.1.1 log file.

    Participant
    January 8, 2024

    Hello,


    My issue seems to be the same/similar as OP. What happens is substance uses a large amount of VRAM (System runs at 20-24gb with a substance project open) and then when I do any action (replacing mesh maps, turning on/off materials etc) it will get extremely laggy as it tries to compute. The difference for me is that there is a high chance that my PC will just freeze forcing me to power it off.

    This issue happens to me on Painter 8.1.3, 9.0.0 and 9.1.0, I am currently using AMD driver version 23.12.1 (There doesnt appear to be a newer one) but it has also happened on the previous driver version. This issue has only started happening since I upgraded my GPU from a 3070TI to a 7900XTX.


    I am able to partially mitigate the issue by lowering the texture resolution to 1024 or 2048 however it will still happen if I have another program open that uses a decent chunk of VRAM (like an unreal engine project).

    I have attached my Log file here, I'm unsure if its saving the more recent info due to the crash. 

    Cyril Dellenbach
    Community Manager
    Community Manager
    January 8, 2024

    Hi Nathan,

     

     

    As far as I know, the AMD issue was solved. Therefore, if you're using the latest update, you shouldn't face the issue. Is your GPU updated?

     

    If so, I'd like to have your description of the problem (with screenshots if possible) and your log (help > export log...), so I can take a closer look.

     

    Let me know.

    Cyril Dellenbach (Micro) | QA Support Artist | Adobe
    Participant
    January 4, 2024

    Hello Cyril,

    I am also encountering the same issue as OP and I was just wondering if you have any updates regarding a fix?

    Cyril Dellenbach
    Community Manager
    Community Manager
    October 30, 2023

    Thanks for the log.

     

    The issue seems to be due to latest AMD drivers. We are currently working with them in order to find a solution.

     

    Best regards,

     

    Cyril Dellenbach (Micro) | QA Support Artist | Adobe
    Participating Frequently
    October 30, 2023

    Hey Man!
    I have the log file here 🙂

    thanks for the heads up, I'll deactivate the stuff you said 😊
    Is there an eta on a fix? Is it a substance problem or AMD problem?

    Cyril Dellenbach
    Community Manager
    Community Manager
    October 24, 2023

    Hello Jake,

     

    Thanks for the report and the details.

     

    There are currently issues with AMD GPUs, so I advise you to deactivate the hardwer support acceleration in Edit > Setting > Sparse virtual texture, and if this doesn't help, you can rollback the GPU driver for a version prior to April.

     

    Considering your problem, I'd also love to have a look at your log (help > export log).

     

    Best regards,

     

    Cyril Dellenbach (Micro) | QA Support Artist | Adobe
    Participating Frequently
    October 24, 2023

    To further refine the issue, I found a repeatable example in my scene. I have a recording here of this issue.

    It appears to be unpredictable tasks which cause memory spikes. These only occur when working with 4K viewport textures and not 2K.

     

    This recording example shows the scenario working at 2K viewport textures and then the same thing breaking at 4K viewport texture resolution. 

    Watch On Vimeo