 |
Typhoon Wiki v1
Next-gen industrial viewer
|
|
Typhoon Wiki v1
Next-gen industrial viewer
|
This page helps you diagnose and solve issues related to startup, loading, rendering, interaction, performance, and data integrity. For unresolved problems after following the guidance below, email **typhoon@plainconcepts.com** with details (see Reporting section).
| Symptom | Most Likely Cause | What To Do | See Also |
|---|---|---|---|
| Application won't start | Missing .NET 8 runtime | Re-run installer; ensure .NET 8 Desktop Runtime present | System Requirements |
| Blank / black viewport | Outdated / unstable DX11 driver | Update GPU driver and restart | System Requirements |
| Point cloud fails to load | Not enough free VRAM | Close other GPU apps; reduce dataset size | System Requirements |
| Gaussian splat fails to load | Corrupt / unsupported splat file | Re-export splat; test with known working sample | Getting Started |
| Point cloud partially loads | VRAM exhausted mid-transfer | Free VRAM; retry; split dataset | System Requirements |
| Initial sparse point view | Refinement in progress (point clouds) | Wait 1–2 seconds for full detail | Getting Started |
| Export option disabled | No compatible item selected | Select correct model (cloud or splat) | Getting Started |
| Project reopens empty | Source files moved/deleted | Restore paths; re-link then re-save | Projects |
| Selection not working | Tool mismatch / distance too large | Zoom closer or change selection mode | Selection & Tagging |
| Camera rotation locked | Focus lost / wrong mouse button | Click viewport; hold right button | Getting Started |
| Movement too fast/slow | Speed setting not tuned | Adjust Camera Speed | Getting Started |
| Tags not visible | Selected model not a point cloud | Select a point cloud; open Properties | Selection & Tagging |
| Model looks clipped | Clipping planes too tight | Adjust near/far clipping | Getting Started |
| Update check fails | Network issue | Restore connectivity; retry | System Requirements |
| Authorization error | Firewall / proxy blocking | Allow outbound connection; retry | System Requirements |
| Model appears offset or jittery | Origin far from (0,0,0) causing precision loss | Recenter via preprocessing; contact support if persistent | Section 9 |
Possible causes: outdated DX11 driver, remote desktop session without proper GPU forwarding, or third-party overlay conflicts. Actions:
Most often insufficient free VRAM. At ~24 bytes per point, 2 GB free handles about 107M points. Free VRAM by closing other GPU-heavy applications. If a very small test cloud fails, include details and email **typhoon@plainconcepts.com**.
Normal refinement behavior. Interaction is already active—full detail appears within a couple of seconds.
Memory pressure or VRAM exhaustion mid-transfer. Try loading only that file. If it succeeds alone, load others sequentially. If still partial for modest size (<50M points with enough VRAM), contact with us.
Likely a corrupt or incompatible splat file. Verify source export pipeline. Test with a known-good splat sample. If only one file fails, re-export; if many fail, report with file size and tool used for generation.
May indicate missing channel data or precision issues. Compare with point cloud version (if available) to isolate whether original data or splat conversion introduced artifacts.
If silent failure occurs, confirm the extension matches actual contents (e.g., LAS vs LAZ). Attempt opening in a different viewer to validate integrity. Re-export corrupt or truncated datasets.
| Issue | Cause | Resolution |
|---|---|---|
| Rotation not working | Right button not held / focus lost | Click viewport; hold right button while moving mouse |
| Very fast movement | Speed value too high | Lower Speed in Camera panel |
| Hard to judge depth | Projection set to Orthographic | Switch to Perspective in Left Panel |
| Cloud disappears when close | Near plane too large | Reduce near clipping in Camera panel |
| Far portions cut | Far plane too small | Increase far clipping distance |
Tip: Center Camera after selecting an element to reorient quickly.
Common pitfalls:
| Symptom | Cause | Fix |
|---|---|---|
| No points selected | Tool not active | Activate desired selection tool (Bottom Panel) |
| Rectangle selects nothing | Too far zoom / thin density | Zoom closer; try paint or cubic selection |
| Tag field absent | Non-cloud element selected | Select a point cloud in Scene Manager and make sure it has labels |
| Wrong region tagged | Selection overwritten unnoticed | Confirm selection highlight before tagging |
| Parts of the scene are missing when selection brush or measure tool is used | To enhance precision, the far plane is automatically adjusted | Manually adjust the far plane in the Camera panel. |
Best Practice: After tagging, briefly switch to a different color mode (if available) to visually confirm groups.
Exports are model-type specific.
Select a point cloud; choose a supported format (E57, PCD, EPC if available in your build). Ensure there is adequate disk space. Large point counts mean larger export times.
Select a splat model; export to native splat package or a converted point-based format (e.g., compressed PLY) if supported. Some attribute fidelity may reduce when converting to point formats due to compression.
If export stalls or produces an unexpectedly small file send details to **typhoon@plainconcepts.com**.
Contents rely on original relative file paths. If items appear missing:
If persistent failures occur despite correct paths, pack scene and send it to us at **typhoon@plainconcepts.com**.
Expected: Immediate navigation responsiveness; refinement completes in a couple of seconds.
If stutter occurs:
| Cause | Resolution |
|---|---|
| Competing GPU process | Close other GPU-intensive apps |
| Near VRAM limit | Unload a large cloud; try smaller dataset |
| Driver throttling | Update driver; disable battery-saving modes |
Visual artifacts (flickering points, random color blocks):
Requires active connectivity for authorization, telemetry, and automatic updates.
Symptoms & Fixes:
| Symptom | Cause | Fix |
|---|---|---|
| Authorization error | Blocked outbound port | Allow app in firewall; retry |
| Update check fails | Intermittent connection | Test general internet access; retry later |
| Telemetry disabled unexpectedly | Global policy / offline | Re-enable once online if desired |
If connectivity is stable but errors persist, send a brief description + any on-screen messages to **typhoon@plainconcepts.com**.
Indicators: Points or splat patches vanish, jitter, or show z-fighting; distant geometry cuts off; subtle movement causes large visual shifts.
Adjust near/far clipping in the Camera panel. For very large scenes, increase far plane substantially while keeping near plane small (but >0.01 to avoid precision loss). If the scene need a far plane further than 1000 units, modify it by pressing Ctrl+ Left click on the far plane. It will enable the input box to set a custom value.
If your dataset's coordinates are extremely far from (0, 0, 0) (e.g., large real-world geospatial coordinates), floating-point precision can degrade, causing jittering, selection inaccuracies, or visual artifacts.
Mitigations:
If precision artifacts remain after recentering, send a brief description plus approximate coordinate ranges to **typhoon@plainconcepts.com**.
Before reporting:
Report via **typhoon@plainconcepts.com** if:
Email should include: Typhoon version, OS version, GPU model & VRAM, driver version, approximate point count, client id (Help > About), and reproduction steps.
Need more answers? See the FAQ or refer back to the System Requirements. For direct assistance email **typhoon@plainconcepts.com**.