Major FFB Issue?

FFB G940 ISSUE

Hello! I have the G940 and also realized that the same little problem using the trim with SU25T and KA-50.While the old version everything was normal, now the axes are reversed when I use the trim.

THX.:helpsmilie:

I have a regular Logitech FF joystick (Extreme 3D) and it has the same funky issue with trimming the KA-50. Haven't really tested su25T as now all modules take forever and a day to load.

Please try this little program to restore the old FFB behaviour for the KA-50 .

Damper and friction effects in force feedback for Black Shark

 

I'm using a MSFFB2, -I'm not affected of this bug - so I can't really tell that it will work for you.

But logic tells me that using this program with the G940 should be a temporally fix to restore the normal FFB trim behaviour.

 

 

 

Hopefully there will be soon a helpful official response from ED for those that are using the G940 .

... more helpful as the "advises" that are given here:

http://forums.eagle.ru/showpost.php?p=1608354&postcount=25

Hi PeterP!

 

Unfortunately, it does not work as expected (at least for me). Yes, it fixes the swapped axes (which only proves it is DCSW problem, not G940's) but my stick does not stay in the trimmed position (especially when I trim aft).

 

I experimented with slider settings, no avail. Maybe I'm doing something wrong. Any tips?

 

But you have my rep anyway. You're the only one who at least tried to help us. Thanks.

Well I tried too and in my case it basically restored trim functionality for the KA-50 (at the cost of all other FFB effects, but that is a minor inconvenience for flying the Shark compared to DCSWorld 1.2.2).

Rotorhead, the trim button has to be selected in the simFFB program (listbox next to the detected FFB stick, the default #3 is button S1 on the G940). Be sure to unselect "progressive input" in the options of simFFB and also do a "init DirectInput" so that the program can take control of the FFB over from the now parkinsonian DCSWorld executable (alt-tab between the two programs just after entering the cockpit to do that).

SimFFB also has the "progressive trimmer mode" (equivalent to the default behaviour of A-10 and Su-25) in which the neutral position of the stick is controlled by the 8-way hat switch (not the mini-joystick) on the joystick. However, this is hard-coded so you should not assign other functions to this hat switch in DCSWorld.

As SimFFB provides its own FFB/trim control and does not receive ANY data from DCSWorld, you will not get any feedback from rough landings, firing the cannon, being hit by something etc but, on the plus side, you get to adjust separately the centering force (position-dependent resistance), friction and damping (rate-dependent resistance) of the stick to your liking.

[Another benefit (to me) of simFFB is that, because the trim routines of the KA-50 in DCSWorld are completely bypassed, the rudder is not trimmed when you press the trim button (hence those who use it do not neet the autokey z x x z "trick" anymore) EDIT - Not such a good idea after all, as the AP is then left unaware of trim. A better option is to assign the same trim button in DCSWorld and simFFB. Thanks again to PeterP for pointing that out in a post further down this thread].

I would be curious to have look at the source code of this small but neat utility. Maybe ED should ask the author too (forum member "average pilot", latest version of the program here: http://forums.eagle.ru/showpost.php?p=1401669&postcount=25), as it seems to work equally well with the MSFF2 and probably other FFB sticks as well. By the way, as a proof of concept, this also strongly suggests that there is no fundamental flaw in the basic G940 FFB. :music_whistling:

Last but not least, a big thank you to "Average Pilot" :thumbup: for writing this utility which serves as a nice stop gap while ED addresses the bug introduced in 1.2.2 and which should, imho, serve as an inspiration. Thanks also PeterP for digging out this hidden jewel from an old thread.

It is only natural for you to prioritize bugs that affect you especially. However, ED need to work the big picture..

Ranting helps none. But the guy has a point: this is a flight simulator and the control stick is quite important. If you look at a computer a joystick might be periphery. When you look at a flight simulator the joystick is not.

To say that it is only natural to prioritize bugs that effect oneself is not helping anyone. And no I do not use a force feedback joystick. Instead I'm trying to figure out how and where bugfixing is going on.

Rotorhead, the trim button has to be selected in the simFFB program (listbox next to the detected FFB stick, the default #3 is button S1 on the G940). Be sure to unselect "progressive input" in the options of simFFB and also do a "init DirectInput" so that the program can take control of the FFB over from the now parkinsonian DCSWorld executable (alt-tab between the two programs just after entering the cockpit to do that).

Ah, stupid me... didn't select the proper button from the list... :doh:

Now it works like a charm! Well, it has some minor flaws, like the need for Alt-Tabbing, which triggers the black buildings bug (another issue still not fixed... :huh:), but... it really works!

Until ED comes with a fix, this is more than sufficient.

Big thanks mrsylvestre and of course average pilot and PeterP! :thumbup:

Nice you got this workaround running.

Tip: Edit your first post with a link to the solution, so fellow G940 users have it easier to find the fix.

(and maybe add screen-shots with a descriptions of your exact settings).

Well I tried too and in my case it basically restored trim functionality for the KA-50 (at the cost of all other FFB effects, but that is a minor inconvenience for flying the Shark compared to DCSWorld 1.2.2).

 

Rotorhead, the trim button has to be selected in the simFFB program (listbox next to the detected FFB stick, the default #3 is button S1 on the G940). Be sure to unselect "progressive input" in the options of simFFB and also do a "init DirectInput" so that the program can take control of the FFB over from the now parkinsonian DCSWorld executable (alt-tab between the two programs just after entering the cockpit to do that).

 

SimFFB also has the "progressive trimmer mode" (equivalent to the default behaviour of A-10 and Su-25) in which the neutral position of the stick is controlled by the 8-way hat switch (not the mini-joystick) on the joystick. However, this is hard-coded so you should not assign other functions to this hat switch in DCSWorld.

 

As SimFFB provides its own FFB/trim control and does not receive ANY data from DCSWorld, you will not get any feedback from rough landings, firing the cannon, being hit by something etc but, on the plus side, you get to adjust separately the centering force (position-dependent resistance), friction and damping (rate-dependent resistance) of the stick to your liking. Another benefit (to me) of simFFB is that, because the trim routines of the KA-50 in DCSWorld are completely bypassed, the rudder is not trimmed when you press the trim button (hence those who use it do not neet the autokey z x x z "trick" anymore).

 

I would be curious to have look at the source code of this small but neat utility. Maybe ED should ask the author too (forum member "average pilot", latest version of the program here: http://forums.eagle.ru/showpost.php?p=1401669&postcount=25), as it seems to work equally well with the MSFF2 and probably other FFB sticks as well. By the way, as a proof of concept, this also strongly suggests that there is no fundamental flaw in the basic G940 FFB. :music_whistling:

 

Last but not least, a big thank you to "Average Pilot" :thumbup: for writing this utility which serves as a nice stop gap while ED addresses the bug introduced in 1.2.2 and which should, imho, serve as an inspiration. Thanks also PeterP for digging out this hidden jewel from an old thread.

I tried everthing with simffb, but nothing workes... i tried it that way that it was mentioned above... tried different button numbers: my trimbutton is s6(the Thumbbutton)... i dont use any configuration tools-my keyboard and joystick assignment can only be edited ingame...

i changed the presets of simffb (do i have to?) -nothing

maybe i have to change something in the windows preferences... do i have to enable or disable ffb there or even switch on the center-spring?

Help me please

Thx Mop

Another benefit (to me) of simFFB is that, because the trim routines of the KA-50 in DCSWorld are completely bypassed, the rudder is not trimmed when you press the trim button (hence those who use it do not neet the autokey z x x z "trick" anymore).

 

I highly recommend to set the simFFB to the same button as the Ka-50Trimbutton and keep the autokey z x x z "trick" .

(or simply use this mocro-mod that works without the need of AHK: Unchain Rudder from Trim )

When you don't tell the Ka-50 of your set trim you won't set the AP-Channels to your new altitude and this leads to a completely different flight behaviour. - at firts maybe not so noticeable in a level flight, but it sure becomes a big issue when using Hover-hold .

-Mop-,

Maybe you already tried that but just in case : simFFB can (should) be first tested independently of DCSWorld/BS2. Connect your stick to your PC, launch simFFB (it should display your joystick name in the first listbox), move and hold the stick off-center (you should feel some resistance) then press different buttons to find the one that removes the centering force (or, more accurately, that registers the current position as the new center). Once you know that this works, play with the second listbox (button#) to set your desired trim button.

Then repeat with DCSW/BS running (alt-tabbing to set simFFB options). If you launch simFFB before entering the cockpit, you may have to select "init DirectInput" so that simFBB can "steal" the force control from DCSW. Repeat: as DCSW initalises DirectInput and gets force control when you enter cockpit, you have to activate simFFB after that.

Another possible source of trouble (but I am not sure of that) could be that, the G940 appears as 3 different devices to Windows (stick, throttle, pedals). Just to be sure, I set the G940 joystick as the default in the "game controller" options in Windows (this option is there to tell windows which device should be made the default for legacy applications).

Hope this helps.

-Mop-,

 

Maybe you already tried that but just in case : simFFB can (should) be first tested independently of DCSWorld/BS2. Connect your stick to your PC, launch simFFB (it should display your joystick name in the first listbox), move and hold the stick off-center (you should feel some resistance) then press different buttons to find the one that removes the centering force (or, more accurately, that registers the current position as the new center). Once you know that this works, play with the second listbox (button#) to set your desired trim button.

 

Then repeat with DCSW/BS running (alt-tabbing to set simFFB options). If you launch simFFB before entering the cockpit, you may have to select "init DirectInput" so that simFBB can "steal" the force control from DCSW. Repeat: as DCSW initalises DirectInput and gets force control when you enter cockpit, you have to activate simFFB after that.

 

Another possible source of trouble (but I am not sure of that) could be that, the G940 appears as 3 different devices to Windows (stick, throttle, pedals). Just to be sure, I set the G940 joystick as the default in the "game controller" options in Windows (this option is there to tell windows which device should be made the default for legacy applications).

 

Hope this helps.

Thx MRSYLVESTRE...

this was the hint i needed... it works now... thx again

Has it been resolved in the latest update??? It is not listed in the changelog :( . SimFFB is no solution as it only solves trim and all other effects including artificial feel system are gone.

Has it been resolved in the latest update??? It is not listed in the changelog :( . SimFFB is no solution as it only solves trim and all other effects including artificial feel system are gone.

No, not yet.

This is a real bummer that it's not fixed with this update. I was hoping it would be resolved with today's update.

No, not yet.

Short question, and I want a short answer:

WHEN WILL IT BE DONE??!!

Short question, and I want a short answer:

WHEN WILL IT BE DONE??!!

ASARP.

Short enough for you?

ASARP.

 

Short enough for you?

Realy short, but no information content. More precisely please!

1 Week?

2 Weeks?

This year?

Next year?

fixed bugs has a delicate issue, please dont expected a fixed time.

ASARP.

 

Short enough for you?

Thanks a lot for the answer, now at least we know that it has been acknowledged and it will be solved :thumbup:

Any news on this topic?

Nothing new, no.

Hi,

im affected too of this annyoing Logitech G940 trim bug. I also modded my G940 heavyly so i´m not willing to buy a new momentary "compatible" brand like MSFFB2 or to integrate complicated workarround-tools to get it temporarily work. That´s not what i paid for a long time ago.

Force-Feedback support is, without question, absolutely essential for this kind of software, so this bug has to get a much bigger attention, i´m sure.

What makes me a little bit think is, that modules like Combined Arms or Flaming Cliffs 3 were released without bugfixing essential things from the older ones...

I do really expect that this major bugs will recognized as such and get solved soon...

Regards

Terrorvogel

Hi,

 

im affected too of this annyoing Logitech G940 trim bug. I also modded my G940 heavyly so i´m not willing to buy a new momentary "compatible" brand like MSFFB2 or to integrate complicated workarround-tools to get it temporarily work. That´s not what i paid for a long time ago.

 

Force-Feedback support is, without question, absolutely essential for this kind of software, so this bug has to get a much bigger attention, i´m sure.

 

What makes me a little bit think is, that modules like Combined Arms or Flaming Cliffs 3 were released without bugfixing essential things from the older ones...

 

I do really expect that this major bugs will recognized as such and get solved soon...

 

Regards

Terrorvogel

Full Acc.

Getting a little bit angry about it. Would buy FC3, but not with a broken FFB and not being able to use my hardware.

Thinking if I should turn my back to DCS and return to BMS. Also thinking 'bout selling the whole DCS bundle.

Hi,

 

im affected too of this annyoing Logitech G940 trim bug. I also modded my G940 heavyly so i´m not willing to buy a new momentary "compatible" brand like MSFFB2 or to integrate complicated workarround-tools to get it temporarily work. That´s not what i paid for a long time ago.

 

Force-Feedback support is, without question, absolutely essential for this kind of software, so this bug has to get a much bigger attention, i´m sure.

 

What makes me a little bit think is, that modules like Combined Arms or Flaming Cliffs 3 were released without bugfixing essential things from the older ones...

 

I do really expect that this major bugs will recognized as such and get solved soon...

 

Regards

Terrorvogel

+1. This is getting really annoying, especially considering that the bug was not present in the pre-DCS world and early DCS world versions to start with. And it was not as if a major overhaul of the FFB system was introduced that would somehow explain new bugs creeping along with new features.

Please ED, do something. I have bought every single product you released so far and want to continue with FC3 and probably the Mustang, but not before this kind of glaring issues are resolved.

Thanks.

major G940 problem

I have made some bad mistakes with my older version of A10-C (1.1.1.1.) and have to delete the hole program.

Now I have DCS World with the A10 module, then everything goes wrong

My Logitech G940 work fine in the older version but I canᷰt get it to work in dcs world.

I can use the presets in the options menu, but when I start the game nothing works?

the throttle does nothing and the joystick is in revert and a lot of buttons are asigned to somthing throttle, brakes flaps al in to 2 buttons. I have deleted everything on axes nothing in the presets and still when I start the game the plane start to roll and throttle is full and everything is out of control then the plane explode.

What can I do to resolve this?

Same problem here.

G940 does not work in DCS world.