Major FFB Issue?

[zlorax]

pffff I have found it, there are presets in game, sim and general, these presets are not working together and that couses a fatal problem to control the plane. I have deleted everything in game, sim, and general and make only in sim a new configuration that solve this problem.

[Dustoff74]

Now grounded for over a month.

I´m not into software development, but I wonder how hard can it be, to fix something, that worked perfectly before?

I bought ALL modules, just to show my support, now please support me :helpsmilie:

 

I would like to take to the skies again, without wondering, what my stick is up to :joystick: (at least, now I know, what this smiley really means!)

[tietze]

Sorry if this has been tried before, but I was just wondering if the "swapaxes" declaration of the forcefeedback section in the device profile could do something to change this?

 

For example the start of my device profile looks like this:

 

C:\Users\[username]\Saved Games\DCS\Config\Input\ka-50\joystick\Thrustmaster Combined {....}.lua

function layout()
return {
forceFeedback = {
	trimmer = 1,
	shake = 0.5,
	swapAxes = false,
},
keyCommands = {
...<snip>

[Rotorhead]

Sorry if this has been tried before, but I was just wondering if the "swapaxes" declaration of the forcefeedback section in the device profile could do something to change this?

 

I suppose it has the same effect as ticking "SWAP AXES" selection box in DCSW menu.

 

It fixes front / aft movement, but left / right movement stays inverted IIRC.

 

 

 

Seriously, I doubt that we'll get fix before Christmas.

[Terrorvogel]

...maybe Santa Claus brings us back a working FFB-Support for Christmas (2012)...

a gift which we already know "whats inside" but in spite of everything a gift which makes us very happy...

 

We all were too well-behaved this year so this should be no problem i think:music_whistling:

 

Regards

Terrorvogel

[Ensi Ferrum]

...maybe Santa Claus brings us back a working FFB-Support for Christmas (2012)...

a gift which we already know "whats inside" but in spite of everything a gift which makes us very happy...

 

We all were too well-behaved this year so this should be no problem i think:music_whistling:

 

Regards

Terrorvogel

 

I hope so, 2 weeks of vacation and being grounded ........

[PeterP]

average_pilot has compiled a new version of his FFBSIM tool.

 

This should be the number one alternative for G940 BlackShark pilots.

 

Download >> http://forums.eagle.ru/showthread.php?p=1628706#post1628706

 

Please give him feedback!

[Terrorvogel]

@PeterP

 

Thank you for that link!

 

I have already seen this link but i can´t use this solution, because i can´t set the trim button (like others) because all of my switches (except the FBB-unit and axis of course) inside the G940 were connected to a seperated Leo Bodnar USB-unit.

 

What we do all simply need is a true solution from ED. It is nice and remarkable that users care about ED´s problems with tools like that but this can not be the right way - that should be clear.

 

What makes me really angry is, that ED meanwhile does not care for so many important things, like in earlier days and it seems the most important thing now, is to make one unfinished one module after other. Fast money at simultanious reduced support and product quality. Sorry to say that but in my sight its the truth. I would rather pay some more and get a particularly finished working high-quality product with adequate framerates.

 

I don´t know when BS1 was exactly released but this must be for some years now and what i´m "running" on my computer is a still not finished product with some elementary bugs!:mad:

 

Nonetheless thank you PeterP for trying helping :)

 

Regards

[Dustoff74]

Update 1.2.3 without fix?

 

Am I missing something, or are we left out in the next update? :cry:

[danilop]

It looks so ... :mad::mad::mad:

 

 

(hope I'm wrong :cry:)

[sobek]

Is this still the status quo on the g940 issue in 7570?

[Kuky]

Hey there!

 

I've updated to 1.2.2 yesterday and did some testing in the last hours. Aside of another few bugs, there's a major problem with my G940 - the FFB axes are swapped. For example, when I trim right, the stick goes aft instead.

 

I tried to fix this by checking the "SWAP AXIS" option, but it cures only pitch axis, roll trim is reversed then - I trim left, stick goes right and vice-versa.

 

Removing "Config" folder in "Saved Games" and then setting the controls from stratch didn't resolved the issue. In 1.2.1, everything worked just fine.

 

Any help appreciated. Thanks.

 

EDIT: Tested with BS2, A-10C and P-51D with same results.

 

Can't you first SWAP the PITCH and ROLL AXIS (that fixes pitch axis), then REVERSE (or is it called INVERSE) the ROLL axis (that should fix the reversing)?

[sobek]

Kuky, that would not only give them inverse feedback behaviour, but also a inverse axis response. :)

 

As far as i have understood, it's the feedback that is the wrong way around, not the response. Besides, this begs the question whether at current implementation that wouldn't also switch the FFB again, so they would get correct FFB but wrong response. It's wrong whichever way you turn it.

[Kuky]

Riiiight... I thought the whole axis was in reverse... never mind then... clearly needs ED's attention and I don't have FFB HOTAS to test

[Dr_Arrow]

Am I missing something, or are we left out in the next update? :cry:

 

As I opened the update log the only thing I was really interested in was fixing the FFB bug - but it is not there ;(

[Dimebag]

I wonder if there is some random registry entry somewhere we can change to affect only the ffb operation.

[-Mop-]

i suppose that modules like a-10 and FC3 just get a higher attention from ed... i think they earned enough with BS2, so why stick to it... maybe, hopefully not... its disappointing...

 

ED told in one or two threads to this topic, that we all should have patience... in my opinion in a very unsympathetic way... dont get me wrong i received a lot of help in this forum from them - and fast as well - but according to the G940-FFB-Problem something is going the wrong way...

 

but maybe it is just a very difficult problem to be solved... if this would be the case i would have understandig for this...im looking forward, hearing something from ed to this case

[sobek]

Again:

 

Is this still the status quo on the g940 issue in 7570?

[Rotorhead]

Is this still the status quo on the g940 issue in 7570?

 

Yes, exactly that, Sobek.

 

FFB axes still messed up, and SWAP AXIS option solves it only partially.

 

I really hope it will get fixed soon. It's about time to get rid of that annoying bug.

[Kuky]

Can you fly without FFB till its fixed? What I mean is, I know it would be nice to use it if you have a HOTAS with FFB, but then again I've been flying DCS with broken HDR and few other things for quite a few months (actually 1-2 years) when using multiple monitors and I don't think it's really a show stopper.. as I can still fly with good settings, but just without HDR etc.

 

So if you CAN fly without FFB it's not really that you can't fly at all.

Edited December 20, 2012 by Kuky

[Rotorhead]

Can you fly without FFB till its fixed?

 

Off course I can. But as I mentioned earlier, using FFB stick without FFB removes all of its advantages and keeps only its flaws.

 

For fixed-wings, it is possible to re-map trim commands (as also mentioned), and for BS, there's a little app from "average pilot" to fix it (brilliant idea, btw:thumbup:)

 

But none of these solutions is ideal. The only right way is to have it finally fixed in-sim.

 

EDIT: I've spent looong time flying without HDR on my old system (it prevented my poor old GPU from melting), and I believe there's a huge difference between flying with HDR off, and flying with not well working stick.

Edited December 20, 2012 by Rotorhead

[danilop]

Who knows, maybe Thrustmaster/Mad Catz insist that G940 (Logitech) FFB bug doesn't get fixed ! :music_whistling:

 

:lol::lol::lol:

Edited December 20, 2012 by danilop

[Terrorvogel]

and I believe there's a huge difference between flying with HDR off, and flying with not well working stick.

 

+1

 

Regards

Terrorvogel

[PeterP]

Can you fly without FFB till its fixed? What I mean is, I know it would be nice to use it if you have a HOTAS with FFB, but then again I've been flying DCS with broken HDR and few other things for quite a few months (actually 1-2 years) when using multiple monitors and I don't think it's really a show stopper.. as I can still fly with good settings, but just without HDR etc.

 

So if you CAN fly without FFB it's not really that you can't fly at all.

Kuky,

believe me - the G940 guys are right when they say it's a mayor issue.

 

Once you have flown the Ka-50 with FFB and Force-Trim you can't simply switch back to the non-ffb trimmer method.

- once you have flown with proper FFB you would fully understand that it is a difference like night and day.

 

Comparing FFB with HDR isn't the right example,

a much better analogy would be to imagine that you cant use your Track-IR properly any more (lets imagine up/down axis is swapped).

 

I'm just so lucky that I use a MSSFFB2 setup and that I'm not affected from this bug.

If FFB would be broken for the MSFFB2 too, I also wouldn't touch the Ka-50 any more - before I'm forced to fly without FFB and to re-learn to move my stick in silly ways, - I would rather Fly MSFSX helicopters.

 

So I can fully understand that the G940 users get angry and express it here in the forum.

These guys don't need a workaround or alternative, they need a fix.

 

Edit:

The Best what ED could do before this fix is ready:

Provide a Upload-link for a 1.2.1 version,

so they have at least the ability to fly without this bug in single-player.

Edited December 20, 2012 by PeterP

[Ensi Ferrum]

Not only that's a big difference between FF enabled and disabled.

I, and many other, paid a lot of money for:

a) the G940

b) DCS World and the different modules

c) some of us hardware to mod the G940 for mainly DCS

Those who modded the G940 also spend a lot of time for doing this, just to enjoy the sim much more.

Then, FF get broken by an update. To make things much more complicated it's not possible to roll back the damned thing to a state the FF was working (another unfinished "Feature" of DCS!)

I'am sick of workarounds for a bug which wasn't in a paid product before. If DCS-World, KA-50, etc would still be officially in beta-status, I could understand.

I could only hope you get this fixed before Christmas!!

2 weeks of vacation and being grounded just because a bad QM ....

If I would work like this, I would have been fired long ago!!

 

Edit:

+1 for Terrorvogel and PeterP