Skip to content
Game Action 360 SPORTS
HUB
Menu
Application manual

Production Truck: Commercial event workflow

Operational reference for commercial event workflow in Production Truck.

Updated November 4, 2026 · 2 minute read · Application 1.0.103

Commercial event workflow

  1. On Ubuntu 24.04+ (Intel/AMD 64-bit), run bash ./install-linux.sh as the signed-in desktop user. It installs Python/browser dependencies, native OBS 31.1.1+, Source Record, DistroAV and NDI runtime. Capture-card drivers remain hardware-specific. Flatpak/Snap OBS is separate from this managed native engine.
  2. Run python3 linux_kiosk_setup.py install --autostart, then open Game Action 360 Production Truck. For a portable folder use ./launch-kiosk.sh. Optional --obs-binary /path/to/obs selects a native executable.
  3. OBS starts in its dedicated GA360 workspace. Engineering → Desktop engineering view reopens the controls in a normal window so you can access OBS setup/import dialogs. Use Return to full-screen kiosk afterward. The desktop remains signed in; these modes are not a security boundary or OS account lockdown.
  4. Pair your Hub truck or name a local event. Import the Hub collection into the managed OBS workspace, map/create cameras, configure sound and encoders, then select the installed profile/collection under Production presets. Preset changes require broadcast, recording, replay and virtual-camera outputs to be stopped. Managed OBS remembers the selected preset for later launches.
  5. On Readiness, review engine connectivity, scene/input mappings, decoder plugins, audio inputs, destination and local recording storage. These are configuration checks; they do not certify live camera frames or audible sound. Monitor the program and sign off video, audio and destination before using Go live.
  6. Operate preview/program, transitions, camera/graphics decks, audio, program recording and replay from Live desk. Native Full-motion multiview and Program monitor buttons open OBS projectors in a window or on a selected connected display. An external monitor keeps these beside the touchscreen controls.
  7. End outputs explicitly. Stop OBS for maintenance is permitted only after OBS confirms every output is inactive and ownership is verified. Edit the managed executable/port while OBS is stopped. Start / reconnect OBS resumes supervision.

Need more help with this?

Search a specific symptom, review related guides below, or prepare a report with the app version, operating system and exact error. Guides describe the documented release; installed versions and subscription access can differ.

Prepare a support report

Related guides

Troubleshooting · 2 min

Troubleshooting: start here

A reusable process for finding the failing layer and avoiding unnecessary reinstalls.