Skip to main content
Participating Frequently
January 19, 2023
Answered

SubstancePainter 8.3.0 update crashes, impossible to open file in 8.2.

  • January 19, 2023
  • 1 reply
  • 648 views

Updated from 8.2 to 8.3
Crash at export. Reopening file, impossible to apply new Shaders, or change layer hierarchie.
Installing back 8.2= impossible to open this file, please upgrade your software. 

Rent mode on !
Tired of nowadays buggy apps!
Everyday ther are problems, I am not beta tester ! Just right now I'm pissed off !
Tell your Hierarchie please, it is a mess to work, everyday is getting  worse (even so every day, softawres are better and better). (And yes I know, never update software while on a project, but I'm everyday on a project !!!)
To be honest it was a 15mn work file, not the end of the world, but still. Pissed off, tired !



This topic has been closed for replies.
Correct answer GeoffroySC

Have you tried canceling your export? 

We found a bug when files are written down to disk... 

1 reply

Participating Frequently
January 19, 2023

Just to let know the readers that after re-upgrading to 8.3, and re-trying to work on the same file, everything finaly work OK.

Also crash might comes from USD export, since it did export Bitmaps just before crashing… 

GeoffroySC
Community Manager
GeoffroySCCommunity ManagerCorrect answer
Community Manager
January 25, 2023

Have you tried canceling your export? 

We found a bug when files are written down to disk... 

Participating Frequently
January 27, 2023

Hello,
And thanks for feedback. And yes, indeed, I ran the bitmpa export and ticked  "USD file format" (for the first time) to see if I could import it in c4d. But after 10mn of Substance Painter freeze, I forced quit the software, re-launched and use recent file command to try re-export.  Then the file was temporarly corrupted, blocking all commands. Then I realised the bitmaps did export correctly. After re-installing 8.3 and re-opening the file, everything was running fine again. Did work this file and others and no crash so long, just avoiding USD export for now.

So, in short, this must be this same bug you're reporting.

Thank you. (and sorry for the fury rent 😉 )