Jump to content

Recommended Posts

Posted

When I try to role play as Petrovich and guide the ATGMs, the sight drifts in the direction that I've moved it, it never comes to rest. Is this normal behavior? I've tried aiming with the joystick, the small joystick on my M.16000 throttle, and the mouse. To get the target "locked" (I know it doesn't really lock) I'll wait until the target is under the aiming dot and then quickly hit LAlt+A. Then, if I hit it again the sight will have stopped moving and be where it was previously.

Feature or bug?

 

Chris

 

 

  • Like 1
Posted

Hello, in Control Settings, go to "Mi-24 Aiming Sight" and remove Joystick, mouse, and rudder axes assignation. After that you can assign what you want to move 9k113 sight.

MSI Z97 Gaming 5 - Intel I7 4790K - Artic cooling freezer 7 pro rev 2 - GSKILL 32 Go - SSD Crucial M5 120 go - SSD Crucial 2To - HDD western digital caviar blue 1 TO - Gigabyte GTX 1070 Gaming G1 - Windows 10 home 64 bits

Posted

@clanitho I did all of that, trying one option at a time. The drift still happens; sometimes it moves rapidly and other times very slowly, but it never completely stops moving.

Posted

You probably need to set a deadzone in the aiming station mappings for whichever controller you are using. You will always need to adjust it slightly to compensate for the movement of the helicopter

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted (edited)

I am having the exact same issue - I deleted all bindings in the Aiming station page, and the only two inputs mapped are Aiming Station Left/Right (Joystick) and Aiming Station Up/Down (Joystick) to a POV on my stick and the drift still happens. Setting a deadzone does absolutely nothing to solve the issue (I tried a deadzone of '90').

 

It looks like the motion of the aiming device is based off the velocity of the input, rather than the axis value ; this would make sense to have it working that way when using a mouse as you would calculate the speed of motion based on the displacement of the mouse cursor, but not for a POV. 

Edited by Althar93
  • Like 1
Posted (edited)

Worth noting I am seeing this issue in the Guided missile training mission where the Hind is in a 'perfect' hover so there should be no movement whatsoever to compensate for.

Edited by Althar93
  • Like 1
Posted (edited)
10 hours ago, Althar93 said:

Worth noting I am seeing this issue in the Guided missile training mission where the Hind is in a 'perfect' hover so there should be no movement whatsoever to compensate for.

 

Same here.

Tested with a stick, POV, mouse, even a XBOX controller as a RADUGA only controller, (with d-pad and stick) with the same results.

 

Edit, yes, the sight is based off the velocity of the input, rather than the axis value, but I can´t "stop or control " the drift.

Edited by Tarres
  • Like 1
Posted

HI.

Same here. Deadzone does nothing. At the end, I have two cotrollers: minijoy on the throttle and the mouse. For coarse movements, I use the ministick, and once close to the target and low movement, I switch to mouse control,and then I am able to stop or have a little drift, enough for targeting.

Saludos.

Saca111

  • Like 1
Posted (edited)
On 6/21/2021 at 2:21 PM, hornblower793 said:

You probably need to set a deadzone in the aiming station mappings for whichever controller you are using. You will always need to adjust it slightly to compensate for the movement of the helicopter

I tried adding a substantial amount of deadzone and it had no affect on this problem. Same issue with mouse, joystick, mini-stick. I disabled any of the controllers I wasn't using to eliminate any "cross-talk". So I'm calling it a bug until someone convinces me otherwise.

Edited by Quatapus
removed unrelated screenshot
  • Like 1
Posted (edited)

Interesting - I will try mine again later with the new patch but had the sight rock steady last time I tried

 

UPDATE - I have now tried and can get it steady if I use my joystick without any curves or deadzone (it takes very gentle movements when moving slowly to do this). However, adding curves to it made it easier to get it steady.

 

The same goes for both the mouse and the mini-stick I have (it is the Deltasim mod on my Warthog Throttle). For these I set the curves on each axis to 100 for the mini-stick and 25 for the mouse. The mouse is definitely the trickiest to use for me but then I  haven't spent a lot of time tuning it because I will never use this method of control

Edited by hornblower793
  • Like 1

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted
3 hours ago, hornblower793 said:

Interesting - I will try mine again later with the new patch but had the sight rock steady last time I tried

 

UPDATE - I have now tried and can get it steady if I use my joystick without any curves or deadzone (it takes very gentle movements when moving slowly to do this). However, adding curves to it made it easier to get it steady.

 

The same goes for both the mouse and the mini-stick I have (it is the Deltasim mod on my Warthog Throttle). For these I set the curves on each axis to 100 for the mini-stick and 25 for the mouse. The mouse is definitely the trickiest to use for me but then I  haven't spent a lot of time tuning it because I will never use this method of control

 

 

I have tried setting the curvature to the maximum value & it does help, but the drift does still occur. To me this is definitely a bug / oversight in the implementation of the aiming sight motion/input.

Posted
I am having the exact same issue - I deleted all bindings in the Aiming station page, and the only two inputs mapped are Aiming Station Left/Right (Joystick) and Aiming Station Up/Down (Joystick) to a POV on my stick and the drift still happens. Setting a deadzone does absolutely nothing to solve the issue (I tried a deadzone of '90').
 
It looks like the motion of the aiming device is based off the velocity of the input, rather than the axis value ; this would make sense to have it working that way when using a mouse as you would calculate the speed of motion based on the displacement of the mouse cursor, but not for a POV. 
Why not use the whole stick as the controller? This is why the Aiming Station is a separate set of control bindings so you can use the joystick to do this and it will have more control than a POV

Sent from my SM-T835 using Tapatalk

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted
1 minute ago, hornblower793 said:

Why not use the whole stick as the controller? This is why the Aiming Station is a separate set of control bindings so you can use the joystick to do this and it will have more control than a POV

Sent from my SM-T835 using Tapatalk
 

 

I have tried using the whole stick & the drifting still occurs (I have a VKB Gunfighter MKIII / MCG).

Posted
 
I have tried using the whole stick & the drifting still occurs (I have a VKB Gunfighter MKIII / MCG).
I use a VKB as well on the extension - adding some curves should help

Sent from my SM-T835 using Tapatalk

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted
23 minutes ago, hornblower793 said:

I use a VKB as well on the extension - adding some curves should help

Sent from my SM-T835 using Tapatalk
 

I tried it with the curves maxed out to 100, the drift still occurs.

Posted
I tried it with the curves maxed out to 100, the drift still occurs.
I cannot help much more apart from to check that your joystick calibration is good in the VKB software - I am sure the early access sight will be further tuned during early access.

It would also help if you could post a video showing the degree of drift you are experiencing

Sent from my SM-T835 using Tapatalk

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...