Describe the bug
I initialised the system loading Open track 2023.3.0 and also 2023.3.1 separately after the octopus failed to move once all the set up steps had been carried out and the game that I wished to use it on was turned on.
Steps to reproduce the behaviour:
- Loaded the open track version (tried 2 separate versions) selected input UDP over network.
- Click on hammer symbol and selected the port 4242
- selected profile default.ini
- Loaded Aitrack ( again tried with 2 separate versions) and entered the configuration screen
- the system changed the Camera FOV to 56 when it is 60 and added a width and height in the number range that a few other uses had reported issues with. I changed it to 640 width and 480 height and altered the PPS to 30.
I then used the options in open track and on the output side inverted the pitch and disabled the roll.
went into mapping and modified the yaw and pitch graphs whilst moving my head around the screen surround until I had a profile that I expected to work in the game.
At this stage the octopus was moving in the manner that I expected and I saved the profiles and opened the game. Condor 3.
Initially the head movements didn't happen and there were some twisted shadow images on the screen.
I closed the game and reopened opentrack and altered the output settings to disable TrackIR when used with freetrack 2.0 enhanced option
I restarted the game and the image on the screen was clear with no ghost duplication however it wasn't moving with any head movement.
I cleared both AiTrack and opentrack and reloaded the programmes using earlier versions of each and followed through the set ups again with the new yaw and pitch instructions
Each time I restart the game I have no movement of the octopus. I change the versions 1 at a time with both opentrack and Aitrack
- Operating system version (Windows 11 Pro Version 24H2 build 26100.6584):
- Webcam model: Papalook PA452
- AITrack version: v0.7.0 and also v0.7.1
Additional context
I have moved now to v0.7.0 Each time I have opened the AiTrack there is a windows message
the option to start tracking causes AiTrack to crash and opentrack reports no video feed.
6.If I change the input on opentrack to neuralnet tracker the video activates and the octopus starts to move as expected.
Describe the bug
I initialised the system loading Open track 2023.3.0 and also 2023.3.1 separately after the octopus failed to move once all the set up steps had been carried out and the game that I wished to use it on was turned on.
Steps to reproduce the behaviour:
I then used the options in open track and on the output side inverted the pitch and disabled the roll.
went into mapping and modified the yaw and pitch graphs whilst moving my head around the screen surround until I had a profile that I expected to work in the game.
At this stage the octopus was moving in the manner that I expected and I saved the profiles and opened the game. Condor 3.
Initially the head movements didn't happen and there were some twisted shadow images on the screen.
I closed the game and reopened opentrack and altered the output settings to disable TrackIR when used with freetrack 2.0 enhanced option
I restarted the game and the image on the screen was clear with no ghost duplication however it wasn't moving with any head movement.
I cleared both AiTrack and opentrack and reloaded the programmes using earlier versions of each and followed through the set ups again with the new yaw and pitch instructions
Each time I restart the game I have no movement of the octopus. I change the versions 1 at a time with both opentrack and Aitrack
Additional context
I have moved now to v0.7.0 Each time I have opened the AiTrack there is a windows message
the option to start tracking causes AiTrack to crash and opentrack reports no video feed.
6.If I change the input on opentrack to neuralnet tracker the video activates and the octopus starts to move as expected.