Fix common issues
Find the cause of upload, Studio connection, material and render problems from what you can see, and fix them.
Find the problem you see below. If none of these fix it, email support@glossi.io with your browser and version, what happened and when, any message Glossi showed, and what you already tried.
Model uploads
Glossi doesn't recognize the format, or the file has no geometry in it.
- Check the format against Supported file types.
- If it isn't listed, export it from your 3D tool in a supported format. See From your 3D tool.
A model can be up to 3 GB when you upload it through the app, the API or a plugin. A model Glossi fetches from a URL can be up to 1 GB.
- Reduce polygons where the detail won't show, and compress large textures.
- See Prepare files for upload.
- Keep the tab open and your connection stable until the upload finishes.
- Check the file for broken geometry or missing textures. See Prepare files for upload.
- Try a small test file to find out whether the problem is in this file or in your connection.
Studio connection
Studio moves through Reserving an engine, Starting it up, Connecting the stream and Loading your scene. Each can take a few minutes, and the screen tells you when one is taking longer than usual.
- Wait while the stage is still changing.
- If it stops changing, refresh the page once. You return to the same project.
- If it still fails, sign out and back in, then open the project again.
- Check that your browser allows WebRTC. Some extensions, VPNs and company firewalls block it.
See Connect to Studio.
Your workspace has used its usage, so Studio won't start. On a paid workspace, an owner or admin can add usage under Settings → Plans & billing.
The stream adapts to your connection, so a weak or busy connection lowers the quality first.
- Use a wired connection if Wi-Fi is busy or unstable.
- Close other tabs and apps that use a lot of bandwidth.
- Turn off VPNs or proxies that may interfere with WebRTC.
- Try another network to see whether the problem is your local network.
Materials and textures
- Export in a format that carries materials and textures, such as GLB or USDZ, with textures embedded or included.
- Assign material slots in your 3D tool before exporting.
- Check the UVs. Without them, textures can't map correctly. See UV unwrapping.
- Bake procedural textures to image textures before export.
- Fix individual finishes in Studio. See Product and materials.
Renders
Render time grows with output size, scene complexity and the options you pick in Export.
- Choose a smaller Size for drafts.
- For video drafts, set Quality to Fast.
- Under Advanced, Path tracing and Render with Cycles take longer than a standard render. Turn them off for drafts.
See Render.
A failed render is listed at the top of Renders with the reason it couldn't finish. Choose Open project and render again from Studio. For an automation run, choose View job; automations retry failed work on their own. If the same render keeps failing, contact support with the project name.
The live view is a preview; the render uses the Size, Format and other options you choose in Export.
- Check the file at the size it will be used, not zoomed in.
- Choose a larger Size if edges look soft.
- If a fine material looks noisy, try Path tracing under Advanced for that render.
The app is unresponsive
- Refresh the page.
- Clear the browser cache and site data, or try a private window to rule out extensions.
- Try another current desktop browser.