Quote:
Originally Posted by stovak
Could this be a problem with your TIR set-up, assuming you use it? I'm using a hat-switch for head movement and have no trouble using the sight, so it doesn't seem to be a limitation on the range of movement.
|
I use FreeTrack with spectrum modified Microsoft VX-1000 webcam. It's not a field of view issue, as I retain full control over rotation (which means all the reflective dots are visible) - the movement range just stops in the game, not letting the camera move further up, down, left, right, front or back. There are no translation limits in place in the software itself, beyond the camera's field of view, so it doesn't seem like I'm hitting any fence there.
I interpreted the issue as the camera "bounding box" kicking in, preventing the movement of the camera to areas that are deemed "inaccessible", either for gameplay purposes, or for preventing the camera from going into places where the cockpit mesh has transparent or otherwise glitchy spots.
Quote:
Originally Posted by [URU]BlackFox
The multiplier factor for head movement is adjustable. The readme has some details about it.
|
If I'm not mistaken, multipliers usually affect the speed at which the movement of your head is translated to the viewpoint's movement in the game; I would expect increasing them would simply mean that you reach the hard limits of the movement range with lesser movement of your head... but I could be completely wrong about this.
I will experiment with them as soon as I find them, but I am unsure whether it is easily possible to extend the range of translation on X/Y/Z axis, especially on plane-specific level.