Marmoset Viewer could not initialize
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.
same problem -___-''
The same problem
reuploaded several times but having the same problem here as well :‑(
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. :(
Permanent problem. Interesting when it will be solved...
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.
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!
Same problem, browser gchrome
Read this guys there is a line under troubleshooting.
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.
In order to post an answer, you need to sign in.