Recommended test
Learn the non-destructive recovery controls before you need them on an important project.
- Save a small test project, then navigate far away from it and use Fit model.
- Hide and restore a group to distinguish missing visibility from a renderer problem.
- If the recovery state is shown, choose Retry Viewport and wait for the scene to reinitialize.
- Reopen the saved .strek only if the viewport remains unreliable, then verify a known dimension.
Rule out a camera issue
Choose Fit model and a standard isometric view. A valid model can appear blank when the camera is far away, inside geometry or pointed in an unexpected direction. Switch between 3D and a standard 2D view to confirm.
Check visibility and display
Use Unhide all, restore disabled Object Groups and return opacity to full. Turn off Solar Shade and highly detailed covering if performance is poor. A line-only or transparent view can also make geometry difficult to recognize against the background.
Retry the viewport
Match the recovery action to the message on screen:
| State | Next step |
|---|---|
| The toolbar works but the model is out of view | Try Fit model, a standard direction and restored visibility first. |
| WebGL required | Follow the message about hardware acceleration or use a browser/device with WebGL support. Preserve unsaved work before restarting a browser. |
| Renderer could not be created | Close other graphics-heavy browser tabs, then use Retry Viewport. |
| Context lost or viewport reinitializing | Allow the automatic recovery to finish; use Retry Viewport if the recovery state remains. |
Autostrek exposes Retry Viewport when its render boundary catches a problem. Use it once and allow the scene to initialize. Avoid repeatedly clicking while a large model or texture set is still loading. Refreshing the whole page is a separate action and can lose temporary measurements or quote work.
Return to a known file
If the view remains unstable, save only when you trust the project state. Otherwise reopen the last verified .strek and check a known dimension and object group. Record the browser, action and model feature that preceded the failure before contacting support.
If the file itself fails to load, use save/load troubleshooting rather than treating every file error as a renderer issue. When possible, compare a small known-good model with the failing project and include the exact recovery message in the report.