Jump to content

Recommended Posts

Posted

I've been digging around for another report of this, but I haven't been able to find a topic yet that mentions it. Since the last open beta update, the acceleration on the HSD cursor's y-axis and the acceleration on both of the HAD cursor's axes are super high, with odd "jerkiness."

I'm on DCS (Steam) 2.7.17.29493 Open Beta

In order to generate the track file I created a test mission in which the aircraft was loaded for SEAD: 4 HARMS + HTS (and some AA missiles). Map is Caucasus, but the map does not affect whether the behavior occurs.

I have ruled out hardware issues because I've tested this with three individual hardware devices, and replicated the behavior. To further test the HSD, I also bound the "normally-behaving" x-axis to the y-axis to see if it was hardware causing it, but the y-axis still had that acceleration even with the x-axis hardware controlling it.

The FCR cursor behaves as expected, moving in a predictable way given the axis inputs.

I have observed this behavior in both single player and multiplayer.

 

f16_hsd_yaxis_accel.trk

  • Like 3
Posted

I checked on today's patch (DCS 2.7.18.30348 Open Beta), and it's still occurring across multiple hardware input devices with joysticks.

  • 1 month later...
Posted

Man, the HAD sensitivity thing really is a nuisance. It's really challenging to use with the cursor jumping all over the place 😞

  • 2 weeks later...
Posted

I find on the HAD and HSD they work fine when i just use the X or Y axis sepperatly but when you combine both of them they suddenly go super fast. If you try BMS its perfect, would like it to be that good.

  • Like 2

Varzat_signatur.png

  • 4 months later...
Posted

Alright so the only device which does not exhibit this behavior is my old X56. The mini-sticks seem to be supplying very low-resolution data for the rX and rY axes, but beyond that, I cannot figure out why the X56 mini-sticks work as expected, but every other joystick I've tried does not, including virtual axes, which are controlled purely by software and have no hardware connection.

Posted

I have the same issues with the virpil CM3. Doesnt happen in other modules or other games, it would be really nice if this gets fixed. Using the slew like it is now is incredibly annoying

Posted

Issue stille here, i have noticed that on my Warthog trottle it appears to be normal, however when i use my VKB Gunfighter pro it gets jumpy.
 

If i am only moving left to right it behaves itsself, but when adding in movement for the other axis the cursor jumps all over the place.

When i use unly up/down its normal again, adding in left/right i gets jumpy.

  • 9 months later...
Posted

I think I know what the problem is:

My theory is that if the precision reported for the axis is greater than 8 bits (0-255), then the cursor jumps around. I tested this on a USB device that I know sends 8 bits-per-axis (because I set it up) and it did not have an issue with the cursor slew. I assume the x56 HOTAS also does that.

The mini-sticks on my Virpil gear and the XBox controller I tried are sending in more bits of resolution, probably 11 or 12. I'm going to try re-configuring my custom hardware to send 12 bits to see if that replicates the behavior.

 

Posted

I increased the output resolution on my custom device and I'm still not seeing it occur, so I'm going to reach out to Virpil to see if they can replicate this. I do find it suspicious, though, that multiple other aircraft and even the FCR screen in the F16 do not have this problem, and this problem occurs with more than one manufacturer's hardware.

  • 2 months later...
Posted

I use a mini-joystick on my throttle, with two axes, to control the RDR CURSOR.

  • In the FCR, this works fine -- the slew rate is normal. 
  • However, for other sensors (like HARM and the HSD), the slew rate is much too high when the movement is diagonal. 
  • In other words: when moving the cursor along either single axis, it moves as intended. When movement is diagonal, it moves many times too fast. 

This is shown in this short video. https://youtu.be/GwBM-HUgdBU

First, I move the cursor on the FCR. Speed is normal. Diagonal is a bit faster (probably sqrt(2) times faster). Next, I make the HSD SOI and slew the cursor there, using the exact same joystick. Now, the slew rate is normal when moving only on one axis, but much too high when moving diagonally. 

This issue does not occur (on any sensor/page) when buttons are used to slew instead of joystick axes. 

 

It seems to have been known for many years (https://forum.dcs.world/topic/281024-can-i-adjust-harm-page-curser-speeds) although it seems that the connection to diagonal movement was not made before. This really deserves a fix. 

 

  • Like 1

Win10 x64 | SSDs | i5 2500K @ 4.4 GHz | 16 GB RAM | GTX 970 | TM Warthog HOTAS | Saitek pedals | TIR5

  • 2 weeks later...
Posted

there is tuning of axis in the DCS controls section.  You can put a dead zone (5 or so) on both axises  and adjust the other parameters to control speed and curser movement extremes.   I had issues with drift, and making the dead zone 5 worked.

 

Mike

Posted
On 4/28/2024 at 11:15 PM, Aronis said:

there is tuning of axis in the DCS controls section.  You can put a dead zone (5 or so) on both axises  and adjust the other parameters to control speed and curser movement extremes.   I had issues with drift, and making the dead zone 5 worked.

 

Mike

It's unrelated to axis curves. My controller works perfectly in all other aircraft and, as you can see in my original post, in half the sensors in this aircraft. It's just a bug. 

  • Like 2

Win10 x64 | SSDs | i5 2500K @ 4.4 GHz | 16 GB RAM | GTX 970 | TM Warthog HOTAS | Saitek pedals | TIR5

  • 2 months later...
Posted (edited)

Same, definitely an issue. On many pages it applies both axis acceleration and axis value accumulated. It doesn't just happen when slewing diagonally, although the issue is exacerbated diagonally because it also seems to sum acceleration of both X and Y axes. So far I've identified the issue on the following pages:

  • HSD
  • HAD
  • HAS
  • FCR GM and all submodes

It doesn't affect the following pages:

  • TGP
  • FCR ACM or CRM and all submodes

 

Here is a graph with what I think happens:

Spoiler

image.png

 

Other threads with the same issue and more details:

 

@BIGNEWY Could you perhaps take a look? It seems to be an issue going back multiple years.

Edited by LordMustang
  • Like 1
  • Thanks 1
  • 1 month later...
  • 1 month later...
Posted (edited)

same problem:
in FCR mode, cursor was able to set up the movements to be slow through the settings in dcs, but when switchin , we laugh at HSDagain, movements are insanely fast.

I make FCR active again - it works again as I set it up.
vpc cdt-vmax throttle
version 2.9.9.2280 MT

Спойлер

 

MT

 

Edited by pjbunnyru
  • Thanks 1

 

IMG_2572 (1) (1).jpg

  • 3 months later...
Posted (edited)

Just flew a HARM/HAD mission on the Kola map...I have the same issue.  FCR slew is fine, but the HAD cursor is extremely fast, causing me to oversteer to hover and lock a threat.  The HSD cursor also moves faster than the FCR but slower than the HAD.

I don't fly any other DCS aircraft except the Viper, so I can't compare it to others.  

I am using the VKB STECS' X/Y coolie hat axis for my cursor controls.    

@BIGNEWY @GCRev @Corrigan @pjbunnyru

Edited by Dawgboy
Added controller detail.
  • Like 1

The only time you have too much fuel is when you're on fire.
=============================
Intel Core i7 5930K 3.5GHz, 32Gb RAM// Radeon RX Vega // SSD only // VKB STECS Mini Plus Throttle / TM Warthog FCS / Saitek Combat Rudder Pedals / Physical Cockpit // TrackIR or VR (HP R-G2)// Win10Pro 64bit //

  • 2 weeks later...
Posted (edited)

@BIGNEWY @NineLine Would you please move this to the "Bugs and Problems" section and track?  TIA

null

image.png

Edited by Dawgboy
typo

The only time you have too much fuel is when you're on fire.
=============================
Intel Core i7 5930K 3.5GHz, 32Gb RAM// Radeon RX Vega // SSD only // VKB STECS Mini Plus Throttle / TM Warthog FCS / Saitek Combat Rudder Pedals / Physical Cockpit // TrackIR or VR (HP R-G2)// Win10Pro 64bit //

  • 1 month later...
Posted (edited)

I'm having this same issue with VKB STECS firmware v2.196 with the ministick. FCR and TGP cursors are fine. HSD cursor is almost unusable due to the diagonal acceleration. Any news on a bug fix? It's very frustrating to deal with.

Edited by ThisWillHurtU
  • Thanks 1
  • 3 weeks later...
Posted (edited)
В 17.04.2025 в 22:58, ThisWillHurtU сказал:

Can anyone else confirm that the new patch just fixed the problem with the HSD? The HAD and HAS pages are still experiencing this problem.

 

В 30.10.2024 в 12:07, pjbunnyru сказал:

same problem:
in FCR mode, cursor was able to set up the movements to be slow through the settings in dcs, but when switchin , we laugh at HSDagain, movements are insanely fast.

I make FCR active again - it works again as I set it up.
vpc cdt-vmax throttle
version 2.9.9.2280 MT

  Показать контент

 

MT

 


it still doesnt work for me.

Edited by pjbunnyru

 

IMG_2572 (1) (1).jpg

  • Recently Browsing   0 members

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