Worked once, now crashes at launch

[Banquillor]

After using it once with no issues, now shows a white screen and just says (not working).
I tried reinstalling several times and even updating nvidia drivers, nothing helps so far.

Any help will be highly appreciated.

[robsanta74]

I can't repeat your problem on my end. Works fine here. You may want to contact them or post here with the specs and driver versions just in case there's a compatibility issue. If the app produced a crash log at any time, giving Adobe that information would also be extremely helpful.

[Thomus]

Same thing is happening to me. Launches once and now it crashes.

[Thomus]

I figured it out.

Basically, you want be sure that you open and close substance 3d paint on the default display. Try turning off your #2 external display and open substance 3d paint. So that it opens on the main display.

This is what was happening:

So I have a laptop with an ultra-wide external monitor and my main laptop display is the default display: ( go to the multiple displays setup in Windows )

> Multiple Displays:
#1 Laptop Display [default]
#2 External Display

Substance 3d paint was loaded and subsequently closed on the #2 external display. It gets stuck as a "white screen app-locked" when opened again.

> Multiple Displays:
#1 Laptop Display
#2 External Display [default]

When the default display = external display, and substance 3d paint was loading on the #1 display it gets does not get stuck.


* I'm sure someone could better explain this than I. It is a strange issue. It seems like a switch in the code for hardware context [device id] gets out of sequence somehow.

I should note the following:

OS = Windows 11.
Laptop = Alienware m17 r4.
External display = 34" Acer Nitros.

[Thomus]

*** Make sure that you turn off your external display when you launch substance 3d paint.

[GoatsOnToast]

This app keeps crashing every time I use the shift key to simply rotate lighting. I only have one display. It's now a very expensive garbage app.

[Lowell]

Originally posted by Thomus:

I figured it out.

Basically, you want be sure that you open and close substance 3d paint on the default display. Try turning off your #2 external display and open substance 3d paint. So that it opens on the main display.

This is what was happening:

So I have a laptop with an ultra-wide external monitor and my main laptop display is the default display: ( go to the multiple displays setup in Windows )

> Multiple Displays:
#1 Laptop Display [default]
#2 External Display

Substance 3d paint was loaded and subsequently closed on the #2 external display. It gets stuck as a "white screen app-locked" when opened again.

> Multiple Displays:
#1 Laptop Display
#2 External Display [default]

When the default display = external display, and substance 3d paint was loading on the #1 display it gets does not get stuck.


* I'm sure someone could better explain this than I. It is a strange issue. It seems like a switch in the code for hardware context [device id] gets out of sequence somehow.

I should note the following:

OS = Windows 11.
Laptop = Alienware m17 r4.
External display = 34" Acer Nitros.

That's what happens and still ocurring... :/

[Local Catdad]

Originally posted by Thomus:

I figured it out.

Basically, you want be sure that you open and close substance 3d paint on the default display. Try turning off your #2 external display and open substance 3d paint. So that it opens on the main display.

This is what was happening:

So I have a laptop with an ultra-wide external monitor and my main laptop display is the default display: ( go to the multiple displays setup in Windows )

> Multiple Displays:
#1 Laptop Display [default]
#2 External Display

Substance 3d paint was loaded and subsequently closed on the #2 external display. It gets stuck as a "white screen app-locked" when opened again.

> Multiple Displays:
#1 Laptop Display
#2 External Display [default]

When the default display = external display, and substance 3d paint was loading on the #1 display it gets does not get stuck.


* I'm sure someone could better explain this than I. It is a strange issue. It seems like a switch in the code for hardware context [device id] gets out of sequence somehow.

I should note the following:

OS = Windows 11.
Laptop = Alienware m17 r4.
External display = 34" Acer Nitros.

Thanks, it helped for me.