![]() |
#1
|
||||
|
||||
![]()
has anyone figured out a way to look back using freetrack the same way as the mouse does, without using X axis?
|
#2
|
|||
|
|||
![]()
Track Ir for me.
![]() |
#3
|
|||
|
|||
![]()
There is something like "relative axis"... you can find it in the advanced settings. If i find the time, ´i´ll look it up for you today...
__________________
AMD Penom ll 6x 1055T Processor 2.8 GHz // 8GB Ram // XFX Radeon HD 7870 Black Edition DD (2048 MB Memory DDR5, GPU 1055MHz) // Windows 7 Professional 64 Bit Version Saitek x52 // Saitek Throttle Quadrant // Saitek Pro Flight Rudder Pedals // Track IR 5 |
#4
|
|||
|
|||
![]() Quote:
![]() Before: ![]() After: ![]() |
#5
|
|||
|
|||
![]()
The controls there give you the option of choosing between yaw/pitch/roll as inputs and applying those inputs to X/Y/Z.
So, what does it do? The more you turn to the side (yaw), it adds some X movement to help you look around the fuselage? |
#6
|
|||
|
|||
![]()
I think the point in the whole thing is to simulate the natural movement by your own body.
You don´t move your eyes in only one axis when you make normal headmovements... So movement in one axis does influence another axis which has to be simulated by the programm...
__________________
AMD Penom ll 6x 1055T Processor 2.8 GHz // 8GB Ram // XFX Radeon HD 7870 Black Edition DD (2048 MB Memory DDR5, GPU 1055MHz) // Windows 7 Professional 64 Bit Version Saitek x52 // Saitek Throttle Quadrant // Saitek Pro Flight Rudder Pedals // Track IR 5 |
#7
|
|||
|
|||
![]()
Is there a similar setting for Track IR? I have to lean left/right then look back to get a good view.
|
#8
|
||||
|
||||
![]()
Jimbop, could you share a screenshot of your sensitivity settings, global, profile, curves. I've been trying to get this to work but no matter what I do it's way to sensitive and hard to keep the gunsight in proper view, thanks
|
#9
|
|||
|
|||
![]() |
#10
|
|||
|
|||
![]()
Ok, i've got to ask.
Seems that total movement is what it gets from the profile settings multiplied by what it gets from the global settings. The thing is, you've got so much smoothing enabled (200 in profile and 100 in global) that i can't help but wonder, doesn't it end up being somewhat slow to react? I mean, i have struggled for quite a while to find a balance between smooth movement and quick movement, but i have finally settled for a situation where the view only "jitters" when i'm zoomed in. I also use a deadzone (the stock curve but slightly modified) so i don't need to use that much smoothing (the gunsight stays centered thanks to the deadzone). The thing i found out just yesterday however is the smoothing percentage setting. That one governs how much % of the captured frames will be smoothed. In your settings, only 1% is smoothed out (that was the same for me too, it's the default setting). The more you use, the slower the response, but setting it between 15% and 25% has given me a good trade off. This way maybe you won't need to have that much smoothing on each axis because you'll actually have a meaningful percentage of frames that it applies to. Then i'll probably experiment with the other things on the advanced tab, like the dynamic smoothing reduction. Maybe it automatically reduces smoothing when it detects a large and fast motion (like when checking six in a hurry, you need it to be responsive), while keeping it where you set it for slower, more deliberate movements (like when trying to look at the engine mounted instruments in a 110). |
![]() |
|
|