Your projects list normally, but opening one shows 3D cannot start in this browser instead of the model, with a Back to projects button. Starting a New Tileset project upload reports the same problem in different words, under Heads up!: uploading a tileset needs 3D graphics, and your browser could not start them. The wizard tells you before you choose any files, because it shows you your model before it sends anything.
This is a problem with the browser on your computer, not with your project. Everything you uploaded is intact and nothing needs to be uploaded again.
Twinsity draws the 3D model using a graphics capability your browser provides, and your browser could not start that capability for this session. The failure happens before any of the 3D model is downloaded.
That is why the rest of the portal looks completely normal. Ordinary pages do not need the graphics layer and the 3D view is the only thing that does, so a browser in this state signs you in, lists your projects and opens your reports exactly as it always did.
A browser can also lose access to the graphics layer partway through a session while continuing to run perfectly well in every other respect. If the 3D view worked yesterday on the same machine and the same browser, that is the likely situation, and the first fix below is the one that addresses it.
Three situations cannot be resolved from your own settings, so they are worth recognising before you spend time on them.
| What you see | What it means |
| You are working over remote desktop, Citrix or a virtual machine | The session has no graphics hardware available to it. Your IT team can enable GPU passthrough, or you can run Twinsity on a physical computer. |
| The graphics acceleration setting is greyed out or switched back on its own | Your organization controls that setting centrally. Your IT team has to change the policy. |
| Everything looks correct, but the browser still refuses to use your graphics card | Your graphics driver is one the browser will not use. Your IT team can update it. |
Send support a screenshot of the Graphics Feature Status block, which sits at the top of the page. Type chrome://gpu into the address bar in Chrome, or edge://gpu in Edge.
That single image shows which parts of your graphics stack the browser has switched off, which is usually enough to identify the cause without further questions.
Restart your browser on the day it shows an update as pending, and after any graphics driver or operating system update.
A browser session left running across an update is the usual setup for this failure. Restarting takes a few seconds and keeps the graphics layer in step with the rest of your computer.