Appearance
3D can't start in this browser
The 3D workbench is drawn with your computer's graphics hardware, through a browser feature called WebGL 2. On most computers it just works. On some (an office PC with hardware acceleration switched off, a remote-desktop session, a very old graphics driver, a browser that has fallen behind) the browser refuses to start it. When that happens LED.FYI does not break: the app opens on the 2D Mapping workbench instead, every other tab works exactly as usual, and the 3D tab shows a card that says "3D can't start in this browser" with the fixes below.
Your project is not affected in any way. It is the same design; only the 3D picture of it is missing until the browser can draw it.
Fix it
Work through these in order. Each one is a common cause on its own.
| Fix | How |
|---|---|
| Turn on hardware acceleration | Chrome and Edge: Settings → System → Use graphics acceleration when available. Firefox: Settings → General → Performance, untick Use recommended performance settings, then tick Use hardware acceleration when available. Restart the browser after. |
| Update your graphics driver | The most common cause on Windows. Get the driver from your GPU maker (NVIDIA, AMD, Intel) or run Windows Update, then restart. |
| Leave the remote session | Many remote-desktop and virtual-machine sessions have no 3D graphics at all. Sit at the computer directly, or use a remote tool that passes the GPU through. |
| Update or change the browser | LED.FYI needs a current Chrome, Edge, Firefox or Safari. If yours is up to date and still refuses, try one of the others. A driver blocklist in one browser rarely applies to all of them. |
| Check the browser's own 3D diagnostic | In Chrome or Edge, open chrome://gpu (edge://gpu) and look for WebGL2 under Graphics Feature Status. Anything other than Hardware accelerated names the blocker. Firefox: about:support → Graphics. |
After any of these, click Try again on the card (or reload the page). The app re-checks and, if 3D can start now, the 3D workbench appears in place of the card.
No rush
Everything except the 3D picture works without it: arranging panels and wiring in 2D Mapping, paperwork in Sheets, content in Video, the whole-project board in 2D Overview, and every Export. If you are on a borrowed machine, finish the job in 2D and look at the 3D on your own later; the project is the same.
What the card tells you
The card lists the fixes above and, when the browser gave a reason, repeats it in small print (Browser reported: …), and has a Read the troubleshooting guide button that brings you back to this page. That line is worth including if you report a problem: disabled by enterprise policy or commandline switch, for example, means your IT department has switched 3D off for the browser, and no driver update will change that. Ask them, or use another browser.
Shared links too
A client preview link is a read-only 3D view, so on a browser without 3D it shows the same card instead of the wall. Your client can still open the project's PDF drawings or PNGs if you send those alongside the link.
When a view hits a problem
Separately from 3D, any workbench that runs into an unexpected error shows a card reading "This view hit a problem" in its own area. The rest of the app keeps working: switch to another tab with the tabs above, or click Try again to reload just that view. Reload restarts the whole page. Technical details unfolds the exact error message; copy it into a problem report.
If the whole app hits a problem, you see a single full-page card, LED.FYI hit a problem, with a Reload button, a Troubleshooting guide link and a Technical details fold-out. Your project is autosaved as you work, so reloading brings it back.