Marmoset Viewer could not initialize

Discussion started by aronimandikromo

Hello everyone,

I got a question/problem here. i really like tho showcase my 3D models and i have been learning how to use the Marmo toolbag so people could interact with my models.

But after uploading the file the viewer works fine for 5-10 min. but then it would just give an error when loading the model. "Marmoset viewer could not inatialize"

anyone knows why this happens? and how i can fix this?

on the desktop app the file works just fine.

Answers

Posted 6 months ago
2

Same problem on a couple of my models, but interestingly only in certain browsers.
Edge is fine, while Chrome (Which except for branding is the same) won't load. Chrome on Android works, but internet explorer does not. Seems random to me.

neilmoore-2000 wrote
You're right pbr3d, Marmoset Viewer using Edge as the browser works fine! I cannot over state how useful this is for me in accessing the graphics of models I've purchased the licenses for, thanks champ you're a legend! I know this doesn't fix the issue for modellers wanting their models displayed across all browsers, but hopefully once CGT know it's a browser issue, they can sort out a fix... I'll let em know.
pbr3d wrote
pbr3d
Great to hear that works for you nielmoore :) fingers crossed it will get fixed too, it's also not a problem I have with any of my models on turbosquid so it definitely seems to be browser and site related, possibly even something as simple as an outdated backend.
Posted 16 days ago
2

I noticed something. In the error message, there is an URI for the file the viewer tried to load. Example:

https://cgtfiles.s3.amazonaws.com/uploads/files/2047441/Corporate%20Man.mview?X-Amz-Expires=300&X-Amz-Date=20210103T162207Z&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJAIWBP4YJ3PPYJKA/20210103/us-east-1/s3/aws4_request&X-Amz-SignedHeaders=host&X-Amz-Signature=a8c650e40361856ad2724256af458f556a3df093d05517731843e5e41a82f79a

If you use this request, you get an xml with the error "AccessDenied" and the message "Request has expired". So I removed the whole query part and now this works:

https://cgtfiles.s3.amazonaws.com/uploads/files/2047441/Corporate%20Man.mview

You can then download this file and view it in the standalone marmoset viewer.
I don't know if you have control over this URI. If you have, make sure it does not expire.

Posted 8 months ago
1

same problem -___-''

Posted 7 months ago
1

The same problem

Posted 7 months ago
1

Marmoset Viewer isn't working on the majority of models I've purchased the license for on the CGTrader site, yet it works fine elsewhere. I reported this to CGT a couple of weeks ago (with five examples, screen shots etc) but am yet to see a fix. As someone working predominantly in 2D the MV is a great tool for me, when it works (screen capturing what I want). In fact this preview is more valuable to me than the model itself! I'd really like to see a fix to this problem. :(

Posted 7 months ago
1

Permanent problem. Interesting when it will be solved...

Posted 4 months ago
1

I've contacted CGT support to let them know it's a browser issue (thanks again pbr3d!) I'd imagine the tech heads at firefox, chrome, IE etc will be able to sort out where the conflict lies once they're alerted to it. If CGT don't do it, I'll contact the tech folk for the above browsers directly myself. A solution it seems isn't far away!

Slayver wrote
Slayver
Eah. Several years more :)
pbr3d wrote
pbr3d
Lets hope so :) Thanks for going the extra mile
Posted 2 months ago
1

https://marmoset.co/support/viewer/
Read this guys there is a line under troubleshooting.

pbr3d wrote
pbr3d
Thanks for the link, I'll paste the contents here for anyone else to read.
Posted about 2 months ago
1

Good day to you, gentlemen!

Joined CGTrader a couple of days ago, now facing the very same issue. Which is worrying, since the discussion is over half a year old and the problem is still in it's original state and quite persistent.

I sincerely believe this is an issue with CGTrader's servers (or those that are responsible for storing Marmoset previews for the website) and not with browsers we use or any of our local stuff.

Here's why I believe that: after re-uploading both .HTML and .MVIEW files (that Marmoset Toolbag generates when exporting a Viewer file) to CGTrader, everything loaded perfectly on all browsers on multiple laptops and smartphones, which weren't connected to each other by any means (asked a friend from another country to help XD). However, as it was previously stated, after a couple of minutes (5, maybe 10), it all goes black everywhere with the same error, which I'm sure we've all seen too many times now :) PACKAGE FILE COULD NOT BE RETRIEVED and all that jazz. After a couple of hours the Viewer file randomly succeeded to load on one phone with Samsung's internal browser (nowhere else) and then went dark again.

Maybe I'm not a 100% accurate with my little experiment, but to me it's convincing enough that it is CGTrader's side that's causing the trouble. No matter the details why it really happens, the sad truth is: *CGTrader's Marmoset Viewer feature is basically unusable because of it's inconsistency.*

Pity it's like that, I was really excited to join CGTrader partly because of the ability to embed Marmoset previews (cause Marmoset Toolbag is awesome for real-time PBR rendering). Since CGTrader's tech support hasn't solved the issue yet, I'm guessing it's either extremely complex or it's not a priority for them at the moment.

In any case, I guess a semi-reasonable thing to do at the moment would be to render-out videos of turntables in Marmoset and then upload to YouTube or Vimeo and use those as a temporary substitute. It sucks, but it's something, right? :) If anyone has a better understanding of the situation or a better alternative, please do not hesitate to share your thoughts, I believe all of CGTrader's PBR folks would be extremely grateful, myself included ;)

pbr3d wrote
pbr3d
That was a good experiment, I'm also certain that it's a server side issue as I can upload the same Mview to both Turbosquid and CGtrader, and it will work fine on Turbosquid. It's a shame no Cgtrader staff have noticed or replied to this thread to help clear things up, or give us an ETA on when it will be fixed. All we can do is keep talking about it, as more and more members reply to this thread it will become more obvious that it's definitely not a localised issue.
PeppermintGraphics wrote
PeppermintGraphics
User neilmoore-2000 in this thread has claimed to have contacted CGTrader support staff directly about this issue, and something tells me he isn't the only one to do that over the course of 6 months, maybe more. And yet nothing transpired. It's not really possible for them to have no clue about this discussion's existence, is it? Probably the server trouble goes much deeper than just a simple fix. I'll give a go writing CGTrader support a letter, maybe they'll give somewhat of an comprehensive answer. I'll report back if I catch something :)
Posted about 2 months ago
1

Try opening your model in incognito view in your crome. This works for other onky u can't see it i also don't get why this happens

pbr3d wrote
pbr3d
I'll give that a try when I come across the next one that doesn't work. It's strange how randomly it happens.
Posted 7 months ago
0

reuploaded several times but having the same problem here as well :‑(

Posted 3 months ago
0

same problem

Posted 3 months ago
0

same problem.

Posted 3 months ago
0

Same problem, browser gchrome

Posted 2 months ago
0

From https://marmoset.co/support/viewer/ (thanks to urisaki for the link)

----------------------------------------------------------------------------------------------------
This message will be displayed when a variety of errors occur, such as:

“PACKAGE FILE (SCENE.MVIEW) COULD NOT BE RETRIEVED.”
This means that the file could not be found, or that there was a server-side problem loading the file. To troubleshoot:

Make sure you have uploaded both the .mview file and the .html file to your server.
Make sure the path to the .mview file in the .html file is correct. If you’ve moved the .mview file to a different directory, you will need to update the path.
If you’ve done the two steps above and continue to have problems loading your file you may need to enable cross-origin resource sharing on your web server. Many servers have CORS disabled by default. If you do not have access to server-side settings, try contacting support for your web host.

If there is no way to enable CORS on your web host, the easiest way to share your art will be via ArtStation.

“PLEASE CHECK TO ENSURE YOUR BROWSER HAS SUPPORT FOR WEBGL.”
This means that your device and/or browser do not support WebGL. To troubleshoot:

Make sure you’re using a web browser that supports WebGL. Most modern browsers such as Chrome, Firefox, Internet Explorer and Safari support WebGL.
Check that you have the latest version of your browser installed.
Confirm that you have the latest version of your video card drivers installed.
If you’re using a beta version or special build of your web browser, try the latest public release instead.
Make sure WebGL is enabled in your browser’s settings. Some browsers such as Safari may have WebGL disabled by default. For more details visit https://get.webgl.org/.
“THIS .MVIEW FILE IS FROM AN OUT-OF-DATE BETA VERSION OF TOOLBAG. PLEASE RE-EXPORT IT WITH THE NEW VERSION. THANKS!”
This error means that something major has changed with Marmoset Viewer’s code, which has broken backwards compatibility. Re-exporting your scene should fix the problem. This error will only be seen with content exported from the early beta version.

“PACKAGE FILE COULD NOT BE READ OR IS INVALID.”
This means that there was some sort of problem reading the file. The file may be corrupt, in which case:

Re-upload the file, or if your upload is still in progress, wait for it to finish and refresh the page.
Re-export and re-upload the file.
If that doesn’t fix it, it may simply be a file not found error (depending on how your web host handles 404s). Try the steps listed above in the “Package file could not be retrieved.” section.

urisaki wrote
So if i understood correctly its CGT problem because its most likely server side right ?
pbr3d wrote
pbr3d
Yeah, that seems to be the case. I get the "PACKAGE FILE (SCENE.MVIEW) COULD NOT BE RETRIEVED." Error on mine which would be server side.

Your answer

In order to post an answer, you need to sign in.

Help