Jump to content

Recommended Posts

Posted

Recently I bought Saitek combat rudder pedals. It was my first time use of foot rudder inputs. In the past I was using my HOTAS to control plane rudders.

 

My problem is that when I apply brake I notice that if I leave my foot of the brakes quickly, brakes don't come back to zero position and plane still continue to decelerate.

 

In the beginning I used Saitek drivers. Then I uninstalled them and used Microsoft default rudder drivers but problem seems to exist. I noticed that when I test drivers in windows environment they respond normal. Problem exists only when I use in game brakes (A-10C).

 

Is there any solution to this problem or something else I need to change in game to work properly. I would happily hear any suggestion or something. Else I have to leave my feet slowly to control the plane right!:huh:

System specs below

Case - Antec Three Hundred

PSU - Corsair AX750watt

Board - MSI Z170A GAMING PRO

CPU - Intel i5 6600K 3900MHz

Cooler - CoolerMaster Hyper 212 Plus

Memory - Kingston HYPERX 16G DDR4 2400Mhz CL15

Graphics - MSI GEFORCE GTX 980 GAMING 4G

SSD - Samsung 950 PRO 256GB M.2 NVMe

Monitor - Philips 277E 27" 1920x1080 60Hz

OS - Windows 10 Home 64bit

Flight Controllers - Thrustmaster HOTAS WARTHOG, Saitek COMBAT RUDDER PEDALS, TrackIR 4, Track Clip Pro

 

[sIGPIC][/sIGPIC]

Posted (edited)

A) You can try to re-calibrate them by using one of these tools:

 

corrupt calibration? crazy joystick response? Use this tools Fix it:

 

B) Set them up like described here: http://forums.eagle.ru/showthread.php?p=1583020#post1583020

 

 

Pay special attention on the small dead-zone I put at both ends of the wheel-brake axis.

Mower,

Just for you.

(But I think it will come handy to show it others too)

 

This is how I set-up my Saitek rudder:

 

 

I set the Deadzones also at the Toe-brakes So there is no input when they snap not back to absolute zero.

And I add also some at the upper end , so I don't have to press with 100% strength to get them to send 100%. - just a security measure to not overstress them by daily use.

 

 

And here is another useful tip:

Maybe not such a big problem for fixed wing aircraft but very helpful when using the rudders with Helicopters.

 

>>> How To: Remove centre detend from Saitek Pro Flight Rudder

Edited by PeterP

Posted

Brake seems to work much better but if I leave my foot extremely fast won’t zero. In the state I am now I think it responds much better. I don't have time to do all the steps you mention now. Will check later. Thank you for the fast response and the help you gave me!

System specs below

Case - Antec Three Hundred

PSU - Corsair AX750watt

Board - MSI Z170A GAMING PRO

CPU - Intel i5 6600K 3900MHz

Cooler - CoolerMaster Hyper 212 Plus

Memory - Kingston HYPERX 16G DDR4 2400Mhz CL15

Graphics - MSI GEFORCE GTX 980 GAMING 4G

SSD - Samsung 950 PRO 256GB M.2 NVMe

Monitor - Philips 277E 27" 1920x1080 60Hz

OS - Windows 10 Home 64bit

Flight Controllers - Thrustmaster HOTAS WARTHOG, Saitek COMBAT RUDDER PEDALS, TrackIR 4, Track Clip Pro

 

[sIGPIC][/sIGPIC]

Posted
Brake seems to work much better but if I leave my foot extremely fast won’t zero.

 

Please have a look what I wrote in the quote above (under the video):

 

 

I set the Deadzones also at the Toe-brakes So there is no input when they snap not back to absolute zero.

And I add also some at the upper end , so I don't have to press with 100% strength to get them to send 100%. - just a security measure to not overstress them by daily use.

Posted

Post #27

The full fix, for those finding this thread:

 

1) Unplug pedals

 

2) Open the registry editor (all the usual warnings apply - don't go mucking about as you can break your windows installation)

 

3) Find the key VID _06A3&PID_0763, search for it or look under

 

HKEY_CURRENT_USER\System\CurrentControlSet\Control \MediaProperties\PrivateProperties\DirectInput

 

The path may depend on your windows version so a search is probably your best bet.

 

(For Saitek Combat Pedals, the key is probably VID _06A3&PID_0764)

 

4) Delete that key

 

5) Plug pedals back in and depress them fully a couple of times

 

6) You should be good to go.

 

Good luck!

/Fred

is the instruction to do manually what the

Clear Calibration Utility does automatically -that is posted in this thread:

>>>

A) You can try to re-calibrate them by using one of these tools:

 

corrupt calibration? crazy joystick response? Use this tools Fix it:

Posted

First I run DXTtweak to analyze the left and right brake axis. Every brake axe responds normal in there.

 

Secondly I run regedit and erased VID _06A3&PID_0764.

 

I also did what you saw me on the video (dead zone saturation slider etcetera) this helps a lot cause even if brake axis won't return buck fully deadzone cover it.

 

But issue still exist. any other recommendations?

 

Strange thing is outside game brakes work fine. So I am sure hardware is ok farther more my pedals are brand new.

System specs below

Case - Antec Three Hundred

PSU - Corsair AX750watt

Board - MSI Z170A GAMING PRO

CPU - Intel i5 6600K 3900MHz

Cooler - CoolerMaster Hyper 212 Plus

Memory - Kingston HYPERX 16G DDR4 2400Mhz CL15

Graphics - MSI GEFORCE GTX 980 GAMING 4G

SSD - Samsung 950 PRO 256GB M.2 NVMe

Monitor - Philips 277E 27" 1920x1080 60Hz

OS - Windows 10 Home 64bit

Flight Controllers - Thrustmaster HOTAS WARTHOG, Saitek COMBAT RUDDER PEDALS, TrackIR 4, Track Clip Pro

 

[sIGPIC][/sIGPIC]

Posted (edited)

Strange...

-is this happens only in the 'axis-tune' screen ?

I have seen similar things there too, but this was caused of the internal refresh rate of the Graphical output for the GUI.

Inside the simulation it is working fluently and I never had a "stuck" toe-brake.

 

Things you should check:

Connected via a USB 1.0 HUB ?

>Try another USB connection preferable 2.0

 

Tell us also a little more about your system - especially what is connected besides the Rudder.

A DxDiag.txt would be perfect to have the whole picture. ( Windows Start > and type "Dxdiag" > run it and attach the created TXT to your next posting)

Edited by PeterP

Posted
Strange...

-is this happens only in the 'axis-tune' screen ?

I have seen similar things there too, but this was caused of the internal refresh rate of the Graphical output for the GUI.

Inside the simulation it is working fluently and I never had a "stuck" toe-brake.

 

Things you should check:

Connected via a USB 1.0 HUB ?

>Try another USB connection preferable 2.0

 

Tell us also a little more about your system - especially what is connected besides the Rudder.

A DxDiag.txt would be perfect to have the whole picture. ( Windows Start > and type "Dxdiag" > run it and attach the created TXT to your next posting)

 

It happens in the axis tune screen and also in game but only if I leave my feet fast. If I travel through the axis slowly it works fine. As I told you again outside game axis respond fine from zero to max. Double checked it in the windows control panel and also in DXTweak2.

 

I use a free USB2 connection. I Have changed USB port as you proposed but no change!

 

Here is my DxDiag

 

Anyway thank you for taking the time to help me out:smilewink:

DxDiag.txt

  • Like 1

System specs below

Case - Antec Three Hundred

PSU - Corsair AX750watt

Board - MSI Z170A GAMING PRO

CPU - Intel i5 6600K 3900MHz

Cooler - CoolerMaster Hyper 212 Plus

Memory - Kingston HYPERX 16G DDR4 2400Mhz CL15

Graphics - MSI GEFORCE GTX 980 GAMING 4G

SSD - Samsung 950 PRO 256GB M.2 NVMe

Monitor - Philips 277E 27" 1920x1080 60Hz

OS - Windows 10 Home 64bit

Flight Controllers - Thrustmaster HOTAS WARTHOG, Saitek COMBAT RUDDER PEDALS, TrackIR 4, Track Clip Pro

 

[sIGPIC][/sIGPIC]

Posted (edited)

Looked trough it and didn't found something suspicious in your USB configuration....

I for instance have right now 9 different USB DX controller attached and don't have this kind of problem - and one of my controllers is also a HOTAS-Cougar like you use too.

 

But one thing seems odd and you should have a look at it:

 

Current Setting: {5C67A112-A4C9-483F-B4A7-1D473BECAFDC} (Quality)

Quality Flags: 2576

Enabled:

Force throttling

Allow half deinterlace

Allow scaling

Decode Power Usage: 100

Balanced Flags: 1424

Enabled:

Force throttling

Allow batching

Force half deinterlace

Force scaling

Decode Power Usage: 50

PowerFlags: 1424

Enabled:

Force throttling

Allow batching

Force half deinterlace

Force scaling

Decode Power Usage: 0

You have set the CPU to throttle down even if your system is running in "Quality/Power mode" at least the Power mode set to use all resources - and you should create a profile that power-mode is used whenever the DCS.exe is running.

 

You should change this so DCS gets all resources that are a available.

- there where some posts in the past with stutter issues and so on.

Some of the problems could get fixed after disabling Throttling and Power-save options.

 

Back to topic:

Did you go already through this for debugging ?

>>> TROUBLESHOOTING - Help us helping you.

 

..I know... these seems not to be much related at the first glance because everything else runs fine, but updating DX may do some miracles some times.

 

You should also try to disconnect everything else (beside the mouse/keyboard) from the PC and see if the rudder still have problems.

 

That's all I can say - now I'm also out of guesses :)

Edited by PeterP

Posted
You have set the CPU to throttle down even if your system is running in "Quality/Power mode" at least the Power mode set to use all resources - and you should create a profile that power-mode is used whenever the DCS.exe is running.

 

You should change this so DCS gets all resources that are a available.

- there where some posts in the past with stutter issues and so on.

Some of the problems could get fixed after disabling Throttling and Power-save options.

 

How do I change this option? I tried to change Power option in the control panel. Changed it to high performance from balance but then when I looked at the dxdiag.txt nothing has changed. More detailed steps would be appreciated!

System specs below

Case - Antec Three Hundred

PSU - Corsair AX750watt

Board - MSI Z170A GAMING PRO

CPU - Intel i5 6600K 3900MHz

Cooler - CoolerMaster Hyper 212 Plus

Memory - Kingston HYPERX 16G DDR4 2400Mhz CL15

Graphics - MSI GEFORCE GTX 980 GAMING 4G

SSD - Samsung 950 PRO 256GB M.2 NVMe

Monitor - Philips 277E 27" 1920x1080 60Hz

OS - Windows 10 Home 64bit

Flight Controllers - Thrustmaster HOTAS WARTHOG, Saitek COMBAT RUDDER PEDALS, TrackIR 4, Track Clip Pro

 

[sIGPIC][/sIGPIC]

Posted (edited)

Freefall we have exactly the same issue! But as I said earlier only if I work brakes normal or fast. If I use them slowly they work fine in game. This exists only in game out in windows they work perfect fast or slow move them.

I' think it's something I have to do with game to solve my problem but what?

Edited by sotosev

System specs below

Case - Antec Three Hundred

PSU - Corsair AX750watt

Board - MSI Z170A GAMING PRO

CPU - Intel i5 6600K 3900MHz

Cooler - CoolerMaster Hyper 212 Plus

Memory - Kingston HYPERX 16G DDR4 2400Mhz CL15

Graphics - MSI GEFORCE GTX 980 GAMING 4G

SSD - Samsung 950 PRO 256GB M.2 NVMe

Monitor - Philips 277E 27" 1920x1080 60Hz

OS - Windows 10 Home 64bit

Flight Controllers - Thrustmaster HOTAS WARTHOG, Saitek COMBAT RUDDER PEDALS, TrackIR 4, Track Clip Pro

 

[sIGPIC][/sIGPIC]

  • 3 weeks later...
Posted

I have a question. Hitting right CTRL + Return axis movement display appears in my monitor. Why when I push right wheel brake only red line goes up? I notice that when I push left wheel brake red line goes up also white bar both left and right goes up. Can someone explain this?

System specs below

Case - Antec Three Hundred

PSU - Corsair AX750watt

Board - MSI Z170A GAMING PRO

CPU - Intel i5 6600K 3900MHz

Cooler - CoolerMaster Hyper 212 Plus

Memory - Kingston HYPERX 16G DDR4 2400Mhz CL15

Graphics - MSI GEFORCE GTX 980 GAMING 4G

SSD - Samsung 950 PRO 256GB M.2 NVMe

Monitor - Philips 277E 27" 1920x1080 60Hz

OS - Windows 10 Home 64bit

Flight Controllers - Thrustmaster HOTAS WARTHOG, Saitek COMBAT RUDDER PEDALS, TrackIR 4, Track Clip Pro

 

[sIGPIC][/sIGPIC]

  • 1 year later...
Posted (edited)

Just wanted to add a huge thanks! Just upgraded to 1.2.7 et all and this was driving me nuts. Now I can spool up to 90% and not move again.

 

Setup my pedals as per the youtube link and problems solved... at least for when on the ground and not moving very fast.

 

---

 

Now the issue is when landing or moving more than a snails pace. If I hit the brakes in these cases, the red percentage bar goes up nicely to 100% in the controls window for each brake but the flat gray bar (no idea what it means) bounces up and down like crazy.

 

If I'm going very slow and press brakes, the gray bar stays at the position of the brakes.

 

Any ideas on this one?

 

Cheers

Tim

 

Note: I suspect it's the anti-skid system, never used to behave this "realistic" that I recall in 1.1.1.1 but is different in 1.2.7, if I disable the anti the grey bar does not bounce all over (anti lock I bet).

 

Did some more testing and laughing my butt off now. Using the external view you can clearly see that this is design as intended. Turn off anti skid and rip down the runway, lock up brakes and watch her skid to the side... love it lol.

 

B) Set them up like described here: http://forums.eagle.ru/showthread.php?p=1583020#post1583020

 

 

Pay special attention on the small dead-zone I put at both ends of the wheel-brake axis.

Edited by Thorvald

System: Win10 Pro 64bit, Gigabyte Z370 AORUS Gaming 7 MB, Intel i& 8700K, Corsair H150i Pro Cooler, Corsair Vengeance LED DDR4 16GB, PNY NVidia 1070 GTX, Corsair MP500 & MP600 SSD, Soundblaster Audigy Rx, CM Mastercase H500P, Oculus Rift S, TM Warthogs.

  • Recently Browsing   0 members

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