VKB Gunfighter Ultimate Mk4 + Flaming Cliffs

[TheBiggerBass]

I recntly upgraded from a TurtleBeach VelocityOne Flight deck to VKB Gunfighter Ultimate Mk4 + STECS. After the usual setup mania everything performs nice and smooth now. The VKB just plays in another league and blows the VelocityOne out of the water.

But - wait a minute.

All other moduls F-4E, F-16, F-18 perform fine with no issues, but there's a strange Gunfighter Ultimate stick behaviour when flying with any aircraft from Flaming Cliffs. Moving the main axis X and Y from Gunfighter Ultimate stick the roll and pitch axis in all FC aircrafts follow the stick action only very slowly and incremental. Cross checking with VelocityOne Flight Deck showed normal roll and pitch response to the stick. Also cross checking reflashing + recalibration of Gunfighter Ultimate stick with configuration tool VKBDevCfg-C didn't change anything.

How can I fix that?

[MAXsenna]

I recntly upgraded from a TurtleBeach VelocityOne Flight deck to VKB Gunfighter Ultimate Mk4 + STECS. After the usual setup mania everything performs nice and smooth now. The VKB just plays in another league and blows the VelocityOne out of the water.
But - wait a minute.
All other moduls F-4E, F-16, F-18 perform fine with no issues, but there's a strange Gunfighter Ultimate stick behaviour when flying with any aircraft from Flaming Cliffs. Moving the main axis X and Y from Gunfighter Ultimate stick the roll and pitch axis in all FC aircrafts follow the stick action only very slowly and incremental. Cross checking with VelocityOne Flight Deck showed normal roll and pitch response to the stick. Also cross checking reflashing + recalibration of Gunfighter Ultimate stick with configuration tool VKBDevCfg-C didn't change anything.
How can I fix that?

In the Controls Indicator or the virtual stick in the cockpit? In other words, does the module behave erratically when you fly? Do you have any axis conflicts? If the stick works in one module, it should work the same in all modules on the hardware level.
Cheers!

Sent from my SM-A536B using Tapatalk

[TheBiggerBass]

vor 15 Minuten schrieb MAXsenna:

 

 

In the Controls Indicator or the virtual stick in the cockpit? In other words, does the module behave erratically when you fly? Do you have any axis conflicts? If the stick works in one module, it should work the same in all modules on the hardware level.
Cheers!

Sent from my SM-A536B using Tapatalk
 

 

I did not check the controls indicator but roll and pitch behave erratically e.g. the just follow in very small step-by-step movements faster stick action. I deleted all other pitch/roll bindings than the Gunfighter axis bindings - no change.

But it get's even weirder: i checked every aircraft in the FC module again. Now the strange behaviour just applies to SU-27. All other aircrafts work fine.

Something strange is going on here ...

[MAXsenna]

I did not check the controls indicator but roll and pitch behave erratically e.g. the just follow in very small step-by-step movements faster stick action. I deleted all other pitch/roll bindings than the Gunfighter axis bindings - no change.
But it get's even weirder: i checked every aircraft in the FC module again. Now the strange behaviour just applies to SU-27. All other aircrafts work fine.
Something strange is going on here ...

Gremlins perhaps?
Try the Controls Indicator, and see how it behaves. Then open axis and select x/y and click axis tuning, and see if its smooth in the test window. I'm sure VBK has an app too, and if they don't Virpil's is excellent, and I use it for all my peripherals.


Sent from my SM-A536B using Tapatalk

[TheBiggerBass]

vor 22 Minuten schrieb MAXsenna:

Gremlins perhaps?
Try the Controls Indicator, and see how it behaves. Then open axis and select x/y and click axis tuning, and see if its smooth in the test window. I'm sure VBK has an app too, and if they don't Virpil's is excellent, and I use it for all my peripherals.


Sent from my SM-A536B using Tapatalk
 

The controls indicator shows this strange behaviour too. The VKB joytester app displays a perfect readout signal from Gunfighter stick. The error must be somewhere at the DCS input interface. And it just applies selectively to FC module for SU-27, all other FC modules and other flight modules are fine.

I am sure it's Gremlins.

[MAXsenna]

The controls indicator shows this strange behaviour too. The VKB joytester app displays a perfect readout signal from Gunfighter stick. The error must be somewhere at the DCS input interface. And it just applies selectively to FC module for SU-27, all other FC modules and other flight modules are fine.
I am sure it's Gremlins.

Rename the Su-27 folder under Saved Games\DCS\Input, or is there something under the special settings I've forgotten about? You might also try to turn off FFB, which is enabled by default, under the General settings.

Sent from my SM-A536B using Tapatalk

[TheBiggerBass]

vor 9 Stunden schrieb MAXsenna:

Rename the Su-27 folder under Saved Games\DCS\Input, or is there something under the special settings I've forgotten about? You might also try to turn off FFB, which is enabled by default, under the General settings.

Sent from my SM-A536B using Tapatalk
 

There is no Su-27 folder under Saved Games\DCS\Input. There is even no Saved Games\DCS\Input folder, just a folder Saved Games\DCS\InputUserprofiles without any subfolders.

Edited April 5 by TheBiggerBass

[MAXsenna]

There is no Su-27 folder under Saved Games\DCS\Input. There is even no Saved Games\DCS\Input folder, just a folder Saved Games\DCS\InputUserprofiles without any subfolders.

My bad! Remembered the old path. Correct path is DCS\Config\input I think

Sent from my SM-A536B using Tapatalk

[TheBiggerBass]

vor 5 Stunden schrieb MAXsenna:

My bad! Remembered the old path. Correct path is DCS\Config\input I think

Sent from my SM-A536B using Tapatalk
 

Unfortunately no aircraft specific folders under DCS\Config\input\Aircrafts either, only Common and Default. But also there I could not find any files where DCS might store any aircraft specific input bindings.

Well, as long as only SU-27 from FC is affected, it's just a minor problem for me. I mainly use F-16C and F-4E anyway. However I would like to understand what's going on. I am also considering to reinstall Flaming Cliffs, but I guess this will reset all joystick/keyboard bindings.

[MAXsenna]

Unfortunately no aircraft specific folders under DCS\Config\input\Aircrafts either, only Common and Default. But also there I could not find any files where DCS might store any aircraft specific input bindings.
Well, as long as only SU-27 from FC is affected, it's just a minor problem for me. I mainly use F-16C and F-4E anyway. However I would like to understand what's going on. I am also considering to reinstall Flaming Cliffs, but I guess this will reset all joystick/keyboard bindings.

My computer is in storage, (haven't been flying for two months and I'm going crazy!!! ), or I would have posted a screenshot. You do find the folders for other modules there though? I'm just checking I remember the correct path.
You are in Saved Games right? And the correct Saved Games folder if you've ever had multiple installs.
No need to reinstall, perform a repair. And no, neither a re-installation nor a repair touches Saved Games. Even if you manually wipe DCS from your disk, all settings will stay in Saved Games until you delete them!
Cheers!

Sent from my SM-A536B using Tapatalk

[TheBiggerBass]

Update: I found some kind of a work around. When reseting pitch/roll trim settings, the pitch/roll axis react like normal. However some controls commands seem to force it back to the strange pitch/roll reaction but I could not identify yet which ones.

[MAXsenna]

Update: I found some kind of a work around. When reseting pitch/roll trim settings, the pitch/roll axis react like normal. However some controls commands seem to force it back to the strange pitch/roll reaction but I could not identify yet which ones.

You haven't bound any of the autopilot modes to some switch or button?

Sent from my SM-A536B using Tapatalk

[TheBiggerBass]

Gerade eben schrieb MAXsenna:

You haven't bound any of the autopilot modes to some switch or button?

Sent from my SM-A536B using Tapatalk
 

No. And I also cleared all other bindings than main pitch/roll axis, which might potentially control pitch or roll. I just made a joystick button binding for the trim reset.

[MAXsenna]

No. And I also cleared all other bindings than main pitch/roll axis, which might potentially control pitch or roll. I just made a joystick button binding for the trim reset.

Post a short track? Maybe someone can take a look.

Sent from my SM-A536B using Tapatalk

[TheBiggerBass]

vor 1 Stunde schrieb MAXsenna:

Post a short track? Maybe someone can take a look.

Sent from my SM-A536B using Tapatalk
 

Ok, here's a track file from SU-27 FC module (landing training). 1st the module starts with the described strange pitch/roll behaviour. At 00:35 secs I reset trim and pitch/roll react normal. I hope that helps.

SU-27 - pitch and roll error.trk

[MAXsenna]

Ok, here's a track file from SU-27 FC module (landing training). 1st the module starts with the described strange pitch/roll behaviour. At 00:35 secs I reset trim and pitch/roll react normal. I hope that helps.
SU-27 - pitch and roll error.trk

I re-read through the posts. Did you try to disable FFB?

Sent from my SM-A536B using Tapatalk

[TheBiggerBass]

vor 4 Stunden schrieb MAXsenna:

I re-read through the posts. Did you try to disable FFB?

Sent from my SM-A536B using Tapatalk
 

Yes. No change.

The root cause must be located somewhere in the input settings which are only used by SU-27. All other FC moduls react fine. And it's repeatable. It always occurs when I start to fly SU-27. After Trim reset it's gone.

Edited April 6 by TheBiggerBass