Check the connection in this order
Enter the track
Start ApexTrace, then enter a race or driving session in GT7 on your PS5. Remaining in the game menus is not a useful live-data test. Hover over the sidebar connection indicator to read its status.
Check the complete application
Use the Windows installer or launch ApexTrace.exe from the extracted App folder. In 0.6.0 the backend is built into the application; no separate backend executable is needed.
Use the same local network
Connect the PC and PS5 to your home network. Guest Wi-Fi isolation, different subnets or VLANs, VPN routing and multiple adapters can prevent discovery or packet delivery. Ethernet is a useful stability check.
Check Windows firewall access
Allow the installed ApexTrace (app.exe) on your trusted private home network. An old rule for a Python telemetry server may not cover this executable. Keep Windows protection enabled.
Close another telemetry receiver
Close other known GT7 receiver applications or development servers that may be using the same UDP port. Do not terminate unfamiliar processes. After the run, restart ApexTrace and retry.
Verify live data, then record
Check that speed, RPM and pedals change while driving. To test recording, observe a complete lap between two start/finish crossings. Connecting midway through a lap can require another full lap.
The app will not open, or its local service fails
Check Windows 10/11 x64, WebView2 and the complete application package. If files are missing, reinstall from the official ApexTrace download. Review Windows protection history without disabling protection or restoring an untrusted executable.
Do not delete the session archive to troubleshoot a connection. Back up important data before reinstalling or moving folders.
Live values work, but the archive has no new lap
This is a recording check rather than a console-discovery check. Start before the lap begins, cross the line to start a full lap and cross it again to finish. Then inspect Sessions and its filters.
A completed lap and complete telemetry are different things. Connection gaps can leave incomplete data; the application cannot reconstruct channels that were never received.
Local ports and discovery
ApexTrace discovers the PS5 automatically. There is no separate field for manually entering its IP address. It receives UDP on port 33740 and sends heartbeat packets to console port 33739.
Router port forwarding is unnecessary. Keep the telemetry service and these ports within your local network.
Still no live data?
Contact Support with the ApexTrace, Windows and GT7 versions, your connection type, VPN or other receiver details, the checks you tried and the result. Attach a screenshot or logs/application.log from %LOCALAPPDATA%\ApexTrace\Data when relevant. Remove private details before sharing.