G940, can any confirm?

[Codex]

Originally Posted by Kankkis

Codex is it flyable that way?

Yeah it is. It is annoying but I can live with it for now, I'm sure the devs will activate FF soon.

I wouldn't want to dog fight for hours on end in its current state though.

[Kankkis]

and you tested that picture yellow method, put thick and lowered strenght.

100% with it.

Maybe we must test RoF without FF and check is there 100% centering in G940 too with game FF off.

[cato_larsen]

For me it does not work to tick the option on and adjust.
Now, I have not fiddled a lot with the settings, as there is no FFB to fiddle with.
I love my G940

[Kankkis]

Cato can you fly CoD with 100% nicely?

Kankkis

[chappy]

I have G940 also, i see no way to remove the massive centering spring pressure that occurrs due to this 'sim' not supporting FFB, aside from turning the stick off completely and dealing with a limp wobbly stick as the alternative.
Now I could have lived with no FFB for a period of time (i would expect it to be addressed eventually cause in this day and age its ridiculous that there is NONE in a new title)
but what i find absolutely DISGUSTING is that the developers havent even bothered to address the issue of the spring centreing force of the G940 and the fact it makes it effectively unplayable. This is, i would think, a fairly popular joystick these days, and to not have tested this and either addressed it or made it quite clear it doesnt work on release is really quite pathetic.

[kimosabi]

How does all the axis assigns work for everybody? Seems like every time I start up the game, it reports different axis/buttons and I have to set it up again. It's not a save issue, the inputs gets different names from time to time, for example: Previously assigned 1Y Ailerons don't work anymore and when I re-assign the same axis then it's suddenly called 2Y. etc. etc.

[Kikuchiyo]

Originally Posted by chappy

I have G940 also, i see no way to remove the massive centering spring pressure that occurrs due to this 'sim' not supporting FFB, aside from turning the stick off completely and dealing with a limp wobbly stick as the alternative.
Now I could have lived with no FFB for a period of time (i would expect it to be addressed eventually cause in this day and age its ridiculous that there is NONE in a new title)
but what i find absolutely DISGUSTING is that the developers havent even bothered to address the issue of the spring centreing force of the G940 and the fact it makes it effectively unplayable. This is, i would think, a fairly popular joystick these days, and to not have tested this and either addressed it or made it quite clear it doesnt work on release is really quite pathetic.

I find it odd so many of you with G940s think 100% centering spring is too tight and unplayable....I had to bump it up personally as I found, with non-FFB games, that 100% was too limp. I also had to turn up FFB for games that support it to 115% to get satisfactory resistance. That kind of limp wristed stick is why I always avoided Saitek. I hope they get FFB in soon, but if it uses centering spring I will be okay with it for a short stint, but then I get to wait till 4/19 and hopefully it will be implemented by then.

[chappy]

@kiku all i can say is ,it must vary from person to person. The default stiffness of the G940 (we're talking how it is when u boot up the computer, not in games where it actually works) is very very stiff and would give most people RSI if they tried to use it for more than 30mins in one go.

having said that, simhq users have found one bypass to this now:
Adjust your centering spring to desired %, start any other game that does actually support FFB/G940s (DCS A10/KA50, IL2 previous titles etc etc), do a quick mission/flight, exit soon as u like, then close that and start COD. the previous setttings should be left on the stick from the other game u started playing.

@KIMO, that problem is probably G940 profiler related make sure u have settings such that the currently designated controller doesnt become the default controller, that in effect re-designates the controllers 0,1,2 depending on which one uve been fiddling with in the profiler. There should be an option to stop that happening somehwere in the profiler from memory.