8.3.1 BUG - [Scene 3D] Failed to load 3D scene. No suitable reader found for the file format of file

[malcomr70091265]

Reading from Substance painter files on a Google Drive mapped drive.

After updating to version 8.3.1 from an earlier version, I can no longer open files saved on GD. I get the error: [Scene 3D] Failed to load 3D scene. No suitable reader found for the file format of file.

It's inconsistent though, sometimes a file will load, sometimes only if I double click from the windows explorer window. 

The issue seems to be related to another bug report, regarding saving files to a NAS drive.  

I've saved files to a mapped Google Drive for many years without issue, it appears to be some new lower level file action that Substance Painter is doing in this newer version, which is the issue.

I can open the files if I copy them to a native drive. So I'm able to continue working, but don't have the added benefits of my previous routine. 

QUESTION: Will this issue be fixed in a future version? 

[Cyril Dellenbach]

Hello @malcomr70091265,

Thanks for the message and all the details.

I'll link your message to the team and we'll have a discussion. I'll get back to you as soon as I have an answer to give you. Would you mind to send me your log (help > export log...), so we can have some data to rely on? Make sure to export the log after the error, so the informations are written in.

Keep me updated,

[malcomr70091265]

Hey Cyril,
I've tried this morning to grab an export log, but I can't repro the issue. Files are loading correctly at the moment.
I've also tried without an internet connection to see if it made a difference (to the local G-Drive files) and they still load.

I'll monitor and if I get the same issue again I'll ensure I get a log file. 

[Jakub33353676komm]

Hi, I have same issue now. I can´t load my substance scene on which I was working for few days in substance painter.... So there can´t be problem with some export or anything else. It seems like a bug that for some reason can´t load the scene.

[Sam34115665e4c5]

I'm having the same issue.

Was there a fix or workaround for this?