Substance Painter 1.x

Substance Painter 1.x

The problem with my Substance Painter......
Substance Painter will not stay 5 seconds on my screen and then it crashes. What to do ?
< >
3145/46 megjegyzés mutatása
CeNedra1320 eredeti hozzászólása:
When Substance Painter crashes, I get a textbox that allows me to send in an error report. I did that a time or two, but it doesn't display anything that I could post here - where does the application print its logs?

southpawami, you lost me at step b), typing even viewer into the search box only yields a few random documents, no Windows Logs folder...

You may have mispelled event viewer. You may also type eventvwr.msc if typing event viewer doesn't work.

You may be using Windows Home or Windows Home Premium version if typing event viewer didn't work, you should check. I'd guess that none of the developers here test on a Home or Home Premium version of Windows, so program reliability may be questionable. The developers are probably using Windows 7 Professional or Ultimate on the machines they test on.
Legutóbb szerkesztette: xyzt; 2014. márc. 24., 6:57
My Windows is Home Premium, but typing eventvwr lead me to the right place. Unfortunately the program does not list any errors related to Allegorithmic or the Substance Painter. In fact there are no entries within an hour of when the crash occured... am I looking in the wrong place?

But seriously, the application has to print a crash log for it to be able to send one in, so why can't the developers just tell me where it is so I can copy it here? This is kind of frustrating.
CeNedra1320 eredeti hozzászólása:
My Windows is Home Premium, but typing eventvwr lead me to the right place. Unfortunately the program does not list any errors related to Allegorithmic or the Substance Painter. In fact there are no entries within an hour of when the crash occured... am I looking in the wrong place?

But seriously, the application has to print a crash log for it to be able to send one in, so why can't the developers just tell me where it is so I can copy it here? This is kind of frustrating.

If you have nothing in Event Viewer, it can be a bit more complicated. Substance Painter doesn't seem to register all crashes that occur. If you right click the taskbar and click taskbar manager, then click on the performance tab, then start substance painter, you can watch for spikes. Also, try clicking on the processes tab and starting substance painter to see what is happening. It's common to spike out on memory or processor. Instead of watching substance painter, watch the taskbar manager all the way up to the crash.

Now it is possible to log a problem program on a run, but the advice above is usually the first thing to do... even before looking at the event viewer.
Substance Painter isn't really open long enough for me to see anything in the processes tab (it crashes a split second after showing up there), but I do get a pretty high CPU spike on one of my kernels (I have 4 virtual, 2 physical). The processor is an Intel i5 760, so not that fast. Might that be the problem? It's strange though that the application ran perfectly fine the first time around, if my CPU is too slow for it...
Jerc  [Fejlesztő] 2014. márc. 25., 10:53 
You should find a log file in there:
C:\Users\...\AppData\Local\Allegorithmic\Substance Painter\
Hah, found it:

[INFO] <RunTimeInfo> build-number: 285 [INFO] <RunTimeInfo> cpu-model: Intel(R) Core(TM) i5 CPU 760 @ 2.80GHz [INFO] <RunTimeInfo> memory: 8190MB [INFO] <RunTimeInfo> os-version: Windows 7 [INFO] <RunTimeInfo> software-version: 0.3.0 [INFO] <RunTimeInfo> sources-version: 1ec5e7f9df5a904c28b669d9af99f18656ed60a7 [INFO] <Qt> "[DBG INFO][SHELF AGENT]" Resources crawling started [WARN] <Qt> QMetaObject::connectSlotsByName: No matching signal for on_currentLayerChanged(Alg::LayerInfo) [INFO] <Library> Library loaded [INFO] <Qt> "[DBG INFO][SHELF AGENT]" Resources crawling duration: 1493 ms [INFO] <Qt> "[DBG INFO][OpenGL Helpers]" Version 4.4.0 [INFO] <Qt> "[DBG INFO][OpenGL Helpers]" GLSL 4.40 NVIDIA via Cg compiler [INFO] <Qt> "[DBG INFO][OpenGL Helpers]" Max texture units 4 [INFO] <RunTimeInfo> gl-renderer: GeForce GTX 660 Ti/PCIe/SSE2 [INFO] <RunTimeInfo> gl-vendor: NVIDIA Corporation [INFO] <RunTimeInfo> gl-version: 4.4.0 [INFO] <RunTimeInfo> glsl-version: 4.40 NVIDIA via Cg compiler [WARN] <Qt> QGLShader::link[ ":/cubeMap" ]: "Fragment info ------------- 0(8) : warning C7555: 'varying' is deprecated, use 'in/out' instead 0(29) : warning C7533: global function texture2DLod is deprecated after version 120 0(30) : warning C7533: global variable gl_FragColor is deprecated after version 120 " [INFO] <Application> Loading default mesh and mesh normal [WARN] <Qt> QGLShader::link[ ":/pbr-view" ]: "Vertex info ----------- 0(5) : warning C7555: 'attribute' is deprecated, use 'in/out' instead 0(6) : warning C7555: 'attribute' is deprecated, use 'in/out' instead 0(7) : warning C7555: 'attribute' is deprecated, use 'in/out' instead 0(8) : warning C7555: 'attribute' is deprecated, use 'in/out' instead 0(9) : warning C7555: 'attribute' is deprecated, use 'in/out' instead 0(11) : warning C7555: 'varying' is deprecated, use 'in/out' instead 0(12) : warning C7555: 'varying' is deprecated, use 'in/out' instead 0(13) : warning C7555: 'varying' is deprecated, use 'in/out' instead 0(14) : warning C7555: 'varying' is deprecated, use 'in/out' instead 0(15) : warning C7555: 'varying' is deprecated, use 'in/out' instead Fragment info ------------- 0(56) : warning C7555: 'varying' is deprecated, use 'in/out' instead 0(57) : warning C7555: 'varying' is deprecated, use 'in/out' instead 0(58) : warning C7555: 'varying' is deprecated, use 'in/out' instead 0(59) : warning C7555: 'varying' is deprecated, use 'in/out' instead 0(60) : warning C7555: 'varying' is deprecated, use 'in/out' instead 0(196) : warning C7533: global function texture2DLod is deprecated after version 120 0(311) : warning C7533: global variable gl_FragColor is deprecated after version 120 " [INFO] <Qt> "[DBG INFO][EngineIntegration]" "VRAM Results" 2019 MB [INFO] <Qt> "[DBG INFO][EngineIntegration]" "VRAM Sources" 256 MB [INFO] <Qt> "[DBG INFO][EngineIntegration]" "VRAM Stamps" 128 MB [INFO] <Qt> "[DBG INFO][EngineIntegration]" "RAM Stamps" 64 MB [ ERR] <Qt> "[DBG ERROR][MaterialPreview]" ..\..\..\src\painteditor\src\matpreview.cpp 352 Null object access

Seems like there's a null-pointer being accessed somewhere...
CeNedra1320 eredeti hozzászólása:
Hah, found it:

[ ERR] <Qt> "[DBG ERROR][MaterialPreview]" ..\..\..\src\painteditor\src\matpreview.cpp 352 Null object access

Seems like there's a null-pointer being accessed somewhere...

I hope the developers get this fixed for you soon.


My log happily says:
[ ERR] <Qt> "[DBG ERROR][Tool Preview]" ..\..\..\src\painteditor\src\toolpreview.cpp 148 The member 'brush' in 'DataActionDecal' doesn't exist [ ERR] <Qt> "[DBG ERROR][Tool Preview]" ..\..\..\src\painteditor\src\toolpreview.cpp 177 The member 'brush' in 'DataActionDecal' doesn't exist
These errors with Numbers 148 and 177 repeat many times over.


I have a mobile Firepro myself, and after AMD merged mobile Radeons and mobile Firepros into the same driver, then started telling programs that you're running a Radeon instead of a Firepro, well, who knows what kind of oddness that causes. Last real mobile Firepro driver for my 7000 series was in 2012.
Legutóbb szerkesztette: xyzt; 2014. márc. 26., 8:42
I'm having this same problem. After running the software without any crashes for about 4hours in a row, it started doing this. Now i cannot launch it without a crash.

This is the crashlog:


[INFO] <RunTimeInfo> build-number: 285
[INFO] <RunTimeInfo> cpu-model: Intel(R) Core(TM) i5-2500K CPU @ 3.30GHz
[INFO] <RunTimeInfo> memory: 8159MB
[INFO] <RunTimeInfo> os-version: Windows 7
[INFO] <RunTimeInfo> software-version: 0.3.0
[INFO] <RunTimeInfo> sources-version: 1ec5e7f9df5a904c28b669d9af99f18656ed60a7
[INFO] <Qt> "[DBG INFO][SHELF AGENT]" Resources crawling started
[WARN] <Qt> QMetaObject::connectSlotsByName: No matching signal for on_currentLayerChanged(Alg::LayerInfo)
[INFO] <Library> Library loaded
[INFO] <Qt> "[DBG INFO][SHELF AGENT]" Resources crawling duration: 1579 ms
[INFO] <Qt> "[DBG INFO][OpenGL Helpers]" Version 4.3.12618 Compatibility Profile Context 13.251.0.0
[INFO] <Qt> "[DBG INFO][OpenGL Helpers]" GLSL 4.30
[INFO] <Qt> "[DBG INFO][OpenGL Helpers]" Max texture units 8
[INFO] <RunTimeInfo> gl-renderer: AMD Radeon HD 7700 Series
[INFO] <RunTimeInfo> gl-vendor: ATI Technologies Inc.
[INFO] <RunTimeInfo> gl-version: 4.3.12618 Compatibility Profile Context 13.251.0.0
[INFO] <RunTimeInfo> glsl-version: 4.30
[INFO] <Application> Loading default mesh and mesh normal
[INFO] <Qt> "[DBG INFO][EngineIntegration]" "VRAM Results" 2414 MB
[INFO] <Qt> "[DBG INFO][EngineIntegration]" "VRAM Sources" 256 MB
[INFO] <Qt> "[DBG INFO][EngineIntegration]" "VRAM Stamps" 128 MB
[INFO] <Qt> "[DBG INFO][EngineIntegration]" "RAM Stamps" 64 MB
[ ERR] <Qt> "[DBG ERROR][MaterialPreview]" ..\..\..\src\painteditor\src\matpreview.cpp 352 Null object access
My log file looks very different. There are about 300 Errors saying: "Declaration must include a precision qualifier or the default precision must have been previously declared.". At the end there is a line which says: "ERROR: compilation errors. No code generated." Can anyone help me? Is there any way to fix it? thx in advance
I'm going to post a new discussion for crash log posting. Maybe we can organize all of this into that discussion so the developers can fix our issues with Substance Painter faster.
Jerc  [Fejlesztő] 2014. márc. 28., 7:34 
Thank you! We gathered all your reports and are looking into the issues, I'll keep you posted.
Legutóbb szerkesztette: Jerc; 2014. márc. 28., 7:34
Shona  [Fejlesztő] 2014. ápr. 4., 9:06 
D3TONAT0R eredeti hozzászólása:
My log file looks very different. There are about 300 Errors saying: "Declaration must include a precision qualifier or the default precision must have been previously declared.". At the end there is a line which says: "ERROR: compilation errors. No code generated." Can anyone help me? Is there any way to fix it? thx in advance

Hi, this issue is related to outdated (bugged) ATI drivers. Can you either post here your Substance painter log located in C:\Users\YourUser\AppData\local\Allegorithmic\Substance Painter\log.txt or Report it attached to a bug here: http://support.allegorithmic.com/

Thx :)
How can it? One of your Youtubers said he uses SP on his Surface tablet and on his Mac PC.
Thank you for your respone.
Here is my log file:
https://www.dropbox.com/s/yqn2mgaa1520zxr/log.txt

You said, this issue is related to outdated ATI Drivers. Would it solve the problem if I would update my Grapics Driver?
Hey guys.
I tried to update my Graphics Driver and NOW IT'S WORKING!!! thank you for your help, now I can finally start painting my Models

PS: My Games are running smoother now, I did not update my Driver since 2009, :D
< >
3145/46 megjegyzés mutatása
Laponként: 1530 50

Közzétéve: 2014. márc. 18., 6:27
Hozzászólások: 46