Skip to main content
R
Rikev
Participating Frequently
June 24, 2021
Answered

Crash When I Paint

  • June 24, 2021
  • 1 reply
  • 3810 views

OK program starts now, that's a good sign I guess?

 

But as soon as I start painting the tutorial model that appears the program freezes and stops responding. I did the registry key thing it tells you to do so I don't get why it is freezing? It sits in Task Manager on 0% CPU and 2GB RAM used (I have 16).

 

The program is completely unusable and unreliable. 😞

    Correct answer Rahul005

    Any updates on the matter?


    you can go within the installation folder and rename the .exe "Substance Painter", this should solve all issues you are having 🙂

    I tried it and after that My painter stop crashing... It's works for me... You can try it too.

    1 reply

    R
    RikevAuthor
    Participating Frequently
    June 24, 2021

    It seems to happen if I move the mouse anything but a slow crawl???

     

    I've enclosed the log. It says it has a plugin called iray using nVidia but I don't have an nVidia card? I use AMD on the newest drivers.

    N
    N1warhead
    Participating Frequently
    June 24, 2021

    I'm having the same issue as well.

    Lets see if I can figure it out.

     

    Already figured out a workaround for Sampler not installing. Now that i've had some sleep after being up for 30+ hours, now maybe I can try and help figure this out as well.

    N
    N1warhead
    Participating Frequently
    June 24, 2021

    I don't believe the iRay errors are the problem, that's only for iRay rendering, saying since we don't have Cuda Cores it won't use them essentially and go back to handling it on the CPU instead of GPU.

     

    Scanning down (my) log, lets see what all I can find.

     

    [WARN] <Qt> QMetaProperty::read: Unable to handle unregistered datatype 'Alg::PaintData::Float3' for property 'Alg::ColorButton::value'

     

    That's really all I can find in my log, it's the only warning, the only errors were the iRay stuff, but I mentioned above I don't think that's even the problem as it's going to CPU instead to handle iRay rendering.

     

     

     

     

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices