Jump to content

Shkval slew control with analog axes


Recommended Posts

Nature of the issue:

Using an analog ministick to control the Shkval slew axes is defective.

 

There's a noticeable default deadzone and the deadzone increases as the axes curvatures are increased.

The resulting axes response does not provide a sufficient control and accuracy.

 

Hardware used:

VKB-Sim Gunfighter + MCG Pro, analog ministick, no deadzone.

8408b05c17d5f43134eeb20e8bc0c07c.jpg

 

Tests:

Axes in the control options:

- Absolute SHKVAL Horizontal Slew

- Absolute SHKVAL Vertical Slew

 

Increasing the curvature of the axes (tested 40 then 70) (trying to achieve slower and precise response for small movements) progressively increases the default deadzone.

On the following picture the Shkval camera just starts to respond. Note the position of the axe (Rot Z) on the analog stick.

The green dots are the center/neutral positions for the ministick axes.

 

6a6632515a3a412b66336792748a0915.jpg

 

Reducing the saturation (Y) for both axes to 20 increases accuracy (less jumpy) and makes the default deadzone less noticeable.

BUT, the max speed for the Shkval axes is greatly reduced.

 

955ec75cb7f8e6a970b8d130c016e603.jpg

 

In the current state binding analog axes to the Shkval slew makes it barely usable and, tracking and locking targets is very uncomfortable.

 

Hopefully this is already fixed for the upcoming Black Shark 3 upgrade.

A fix for the current version would be very welcome.

 

If anyone has a solution, other than binding multiple controls and hats/buttons/mouse to make more precise movements, please do share your tricks ;)


Edited by Bourrinopathe

/// ВКБ: GF Pro MkII+MCG Pro/GF MkII+SCG L/Black Mamba MkIII/Gladiator/T-Rudder MkII | X-55 Rhino throttle/Saitek Throttle Quadrant | OpenTrack+UTC /// ZULU +4 ///

/// "THE T3ASE": i9 9900K | 64 GB DDR4 | RTX 2080ti OC | 2 TB NVMe SSDs, 1 TB SATA SSD, 12 TB HDDs | Gigabyte DESIGNARE mobo ///

Link to post
Share on other sites

I have spent lots of time to tweak the shkval axis. In SU-25T it is easier than in KA-50.

 

And I am about same positions as your finding. Heavy reduction in saturation and apply some curves.

 

But you get good large scale movement, but really lose the fine tune for a tank size targets. Where you start to jump over targets and spend seconds to get gate on target.

 

That deadzone should go!

The ultra high sensitivity should as well go!

 

The default should be close to real sleeving behavior!

i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S.

i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.

Link to post
Share on other sites

This has been bothering me since I got a joystick with analogue TDC cursor 7 or 8 years ago! Funniest thing is some people were calling me crazy, because they couldn't believe how messed up the analogue TDC controls are.

 

There is a built in deadzone you just can't get rid off. If you make it past the deadzone the minimum axis response is way too much. You just can't make tiny adjustments reliably.

The TGP on A-10, F/A-18 or F-16 on the other hand can be controlled perfectly smooth.

 

The only "fix" I found was mapping the Shkval TDC to a spare hat switch and tapping it for small adjustments.

 

This should have been fixed years ago already so please fix it for BS3.

Link to post
Share on other sites

Analog axes really are only usable for large movements with Skhval. Have to use castle switch for small adjustments. Not only because of the deadzone but the Skhval is missing acceleration that the digital control has which is why digital is better in small adjustments. The camera seems to follows the thumbstick with infinite speed. This can be tested with any analog gamepad if not having one on the flight stick.

Link to post
Share on other sites

This should be the most simple of things to fix please ED, that is all.

System Specs: Intel Core i9-9900K 3.6GHz @ 5GHz, Gigabyte Z390 Aorus Master, 32 GB Patriot Viper Steel RAM, GeForce GTX 2080 Ti, Crucial SSD (750 GB), TrackIR 5, TMWH, TM T-Flight Rudder Pedals, Samsung 49” Odyssey G9

Link to post
Share on other sites
Analog axes really are only usable for large movements with Skhval. Have to use castle switch for small adjustments. Not only because of the deadzone but the Skhval is missing acceleration that the digital control has which is why digital is better in small adjustments. The camera seems to follows the thumbstick with infinite speed. This can be tested with any analog gamepad if not having one on the flight stick.

 

 

This should be fixed soon.

System Specs: AMD R5 1600x, Windows 10 64-Bit, 16GB RAM, GTX 1080, X52 Pro Throttle, Tobsen CM Kollektiv, Saitek Rudder Pedals, VPC T-50 CM2 + WarBRD Base, HP Reverb G2

Helis: UH-1H / KA-50 / MI-8 / SA-342   Jets: F-5E / F-14A/B / F/A-18C / MC-2000 / A-10C / A-10C II / AV-8B / AJS 37 / MIG-21bis    WWII: Spitfire

Misc.: Combined Arms / NS430 / Supercarrier   Maps:  Nevada / Persian Gulf / Normandie / Syria   Waiting for: Mi-24 P / OH-58 / AH-64 D / BO-105

Link to post
Share on other sites

I really hope soon is closer than only two more weeks ;)

That's a serious issue imho.

It impairs the efficiency of the targeting that's crucial near threats (even trying to dispatch targets from a safe distance - it makes things much slower and inaccurate due to the clunky controls). Just as mentioned above by other users.

 

Now, we have no idea how the real ministick and Shkval behaves but I'm pretty sure it must have a better efficiency.


Edited by Bourrinopathe

/// ВКБ: GF Pro MkII+MCG Pro/GF MkII+SCG L/Black Mamba MkIII/Gladiator/T-Rudder MkII | X-55 Rhino throttle/Saitek Throttle Quadrant | OpenTrack+UTC /// ZULU +4 ///

/// "THE T3ASE": i9 9900K | 64 GB DDR4 | RTX 2080ti OC | 2 TB NVMe SSDs, 1 TB SATA SSD, 12 TB HDDs | Gigabyte DESIGNARE mobo ///

Link to post
Share on other sites

Yep i agree it needs a tweak and smoothed out.

I use a combo of ch mini joystick then a modifier and hat switch when close, not optimal but works when fine tuning.

i7-7700K OC @ 5Ghz | ASUS IX Hero MB | ASUS GTX 1080 Ti STRIX | 32GB Corsair 3000Mhz | Corsair H100i V2 Radiator | Samsung 960 EVO M.2 NVMe 500G SSD | Samsung 850 EVO 500G SSD | Corsair HX850i Platinum 850W | Oculus Rift | ASUS PG278Q 27-inch, 2560 x 1440, G-SYNC, 144Hz, 1ms | VKB Gunfighter Pro

Chuck's DCS Tutorial Library

Download PDF Tutorial guides to help get up to speed with aircraft quickly and also great for taking a good look at the aircraft available for DCS before purchasing. Link

Link to post
Share on other sites

+1 the sensitivity is unbelievable like in missions I would think twice before touching it, because it jumps to the sky or whatever away instead of moving slowly. spent hours trying to solve it still not easy.

Link to post
Share on other sites

I also have this problem. Like many others I am using the ministick for large movements and a separate hat for fine adjustments.

 

I think the real problem is that the slew rate with the analog stick is the same in terms of degrees per second whether you’re zoomed in or zoomed out. In the A-10 for example, the slew rate is proportionate with zoom level to allow finer adjustments when zoomed in.

Intel Core i7-8700K @ 5.0 GHz // Nvidia GTX 1080Ti // 32 GB DDR4 RAM // 1 TB SSD

Link to post
Share on other sites
  • 2 weeks later...
I also have this problem. Like many others I am using the ministick for large movements and a separate hat for fine adjustments.

 

I think the real problem is that the slew rate with the analog stick is the same in terms of degrees per second whether you’re zoomed in or zoomed out. In the A-10 for example, the slew rate is proportionate with zoom level to allow finer adjustments when zoomed in.

 

This is the same in the Gazelle, the more zoom the finer it adjusts.

HP pro Reverb.

Current settings:

Windows VR setting: IPD is 64.5mm, High image quality, 90Hz refresh rate.

Steam: VR SS set to 100%, motionReprojectionMode set to "motionreproduction" and Locked in at 45 Hz display,

DCS: Pixel Density 1.0, Forced IPD at 55 (perceived world size), 2 X MSAA, 0 X SSAA.

My real IPD is 64.5mm. Prescription VROptition lenses installed.

VR Driver system:

I9-9900KS 5Ghz CPU. XI Hero motherboard and 2080ti graphics card, 32 gigs Ram 3

[code][code][code][code]

[/code][/code][/code][/code]200 Hz. No OC at the mo.

Link to post
Share on other sites

Also have the same problem with skhval

Куплю модули : СУ-7 , СУ-9 , СУ-11,Миг-23,Миг-27 ,Ту-22М3,Ту-95,Ми-24,AH-64,F-16 ,F-4 Phantom,модуль-карту современной западной Европы

I-7 4790k (4.4GHz), GTX980 4GB , Z97, 16Gb DDR3

Link to post
Share on other sites
  • 3 weeks later...

I don't have my settings available but as I recall I have had good luck using "user curve".

 

It should be fixed for sure though. Not sure what's wrong with it and honestly the post up there saying "this should be the easiest thing in the world to fix" is a tad rude ;).

Win-10 x64

 

Nvidia RTX2080 (HP Reverb)

Asus Prime X570P

AMD 3800x

32GB G-Skill RipJaw 3600

 

Saitek X-65F and Fanatec Club-Sport Pedals

Using VJoy and UCR to remap Throttle and Clutch into Rudder axis

Link to post
Share on other sites
  • 3 months later...
  • 2 months later...
  • 4 weeks later...
  • 5 weeks later...

It's waaaay clunky the way it works now. I also have to use 2 separate controls (ministick and hat) to effectively use the Shkval with any precision AND decent slew rate.

 

I'll just join the bandwagon and say I want this fixed at least on BS3.

Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...