Design & previz software · software
CAST Software wysiwyg troubleshooting
The CAST Software wysiwyg problems live-event techs bring to Ask Roadie most (also called WYG, wysi, wysiwyg R50). Pick your symptom, or describe your own in plain words, and get the likeliest fix first, with the manual page when there is one.
Common wysiwyg errors & problems
What techs run into most, and what's usually behind it. The step-by-step fix for your exact software is in Ask Roadie.
- Step-by-step fixGet the fix →
A legacy .wyg file crashes wysiwyg when I try to open it
Likely cause: The newer visualization engine chokes on certain legacy Boolean geometry; mesh-consolidating flattens it to stable geometry the current build can load.
- Step-by-step fixGet the fix →
Can't print to PDF or export Shaded View to JPEG (fails silently or errors)
Likely cause: The print/export path maps filenames through the active code page; characters outside it can't be encoded, so the operation fails until the name/path or system language is compatible.
- Step-by-step fixGet the fix →
Console is connected but fixtures in the model don't respond correctly to Art-Net / sACN
Likely cause: Visualization only tracks if protocol, universe mapping, fixture personality, and start address all agree end-to-end; a mismatch at any link leaves fixtures dark or wrong.
- Step-by-step fixGet the fix →
Deleted presentation items keep reappearing in Layouts / adding a 'new view' crashes wysiwyg
Likely cause: Undo removes the object but not its Layout-insertion registry entry; the dangling entry has no valid backing view, so inserting it dereferences bad state and crashes.
- Step-by-step fixGet the fix →
My .wyg file became corrupted / won't open after saving to a shared or USB drive
Likely cause: wysiwyg's file I/O assumes low-latency local storage; saving live over network/removable media can leave the .wyg in an inconsistent, corrupt state.
- Step-by-step fixGet the fix →
Shaded View is black, blank, or unusable / poor quality on this machine
Likely cause: The shaded engine leans on OpenGL feature support the IGP simply lacks; a discrete card + current drivers provides the features, and trimming visualization load/geometry restores performance.
- Step-by-step fixGet the fix →
Which wysiwyg edition do I need — console/DMX previz vs. just drawings and paperwork?
Likely cause: Console visualization is a PERFORM-only feature; Report and Design have no DMX/Art-Net input at all, so no amount of patching will make them respond.
- Step-by-step fixGet the fix →
wysiwyg crashes the moment I switch to Shaded View
Likely cause: Deferred Rendering/Alpha Beam Shadows requires OpenGL 4.3; disabling Deferred Rendering removes the unsupported code path that triggers the crash on entry to Shaded View.
Not on the list? Describe it your way, or paste the error code off the display. Ask Roadie works the problem with you until it's fixed or you have a clear next move.
How Ask Roadie helps with the wysiwyg
- 1. Pick the CAST Software wysiwyg. It's already in the list.
- 2. Describe what you're seeing. In your own words, or the error code off the screen.
- 3. Get the likeliest fix first. Steps in order, the manual page when there is one, and a note when other techs have confirmed it.
- 4. Still broken? Tap 👎 and it keeps going from where you left off.