Prove that the source works without a project
Open the Computer Vision panel and select the source that matches your test. ConsoleTuner’s release notes describe device, stream, display and window sources. Check the live preview before starting Python. If it is blank or frozen, investigate the source selection, the computer’s ability to see the source and any relevant capture permissions first.
For a capture device, confirm that the source is providing a signal and that the capture device can be selected on the computer. For a window source, check that the preview contains the intended window. The project cannot process frames it never receives.
Verify the Python environment used by Gtuner IV
Use the Computer Vision preferences to check the Python location and the availability of the files the application expects. The official changelog documents Python and OpenCV integration, and an individual project can have its own dependencies. Compare those requirements with the specific environment selected inside Gtuner IV.
Start with a trusted local test that can demonstrate frames are reaching Python without sending controller actions. A preview that works but a project that fails to start usually calls for checking the environment, required project assets and the reported Python error.
Test feedback to the device on its own
If a project also includes a companion GPC file, confirm it is built, installed and active. ConsoleTuner documents GCV feedback functions for the device-side script and also records a later feature for sending a string from GPC to Python. A working preview and a running Python project are useful milestones. Check the expected controller-side result separately in a permitted offline test.
Sources
Titan Two AI publishes these guides independently. ConsoleTuner makes the Titan Two device and Gtuner IV.