Ensi Ferrum Posted December 25, 2012 Posted December 25, 2012 Seems linke ED is talking go Logitech about the issue. Whatever that means. Intel Core i7 2600K @ 3.40GHz OC 4.9 GHz 8,00 GB Dual-Channel DDR3 @ 686MHz (9-9-9-24) ASUS SABERTOOTH P67 (LGA1155) GeForce GTX 780 Creative Sound Blaster Z Logitech Proteus Core Mouse Logitech G19S Logitech G940 (heavily modded) Thrustmaster MFCD-Bevels 1 x Samsung T27B300 2 x ASUS VW224
mrsylvestre Posted December 26, 2012 Posted December 26, 2012 Seems linke ED is talking go Logitech about the issue. Whatever that means. Do yo mean "talking TO Logitech" ? Source ? Regards, Mr. S. 5800X3D - 64GB DDR4 - Samsung 990 PRO SSD @ PCI 4.0 x 16 - 7900XTX (6950XT for posts before May 2025) - Pico 4 (VDXR)
Ensi Ferrum Posted December 26, 2012 Author Posted December 26, 2012 Do yo mean "talking TO Logitech" ? Source ? Regards, Mr. S. Sure, meant TO :-) Motherfu**ing typing correction on my new tablet. Source is from ED's Facebook account: Intel Core i7 2600K @ 3.40GHz OC 4.9 GHz 8,00 GB Dual-Channel DDR3 @ 686MHz (9-9-9-24) ASUS SABERTOOTH P67 (LGA1155) GeForce GTX 780 Creative Sound Blaster Z Logitech Proteus Core Mouse Logitech G19S Logitech G940 (heavily modded) Thrustmaster MFCD-Bevels 1 x Samsung T27B300 2 x ASUS VW224
Dimebag Posted December 26, 2012 Posted December 26, 2012 Sure, meant TO :-) Motherfu**ing typing correction on my new tablet. Source is from ED's Facebook account: Oh great, talking to logitech, they will probably deny all connection to the g940 knowing their track record with the hotas. We really are screwed if they can't work it out themselves. [sIGPIC][/sIGPIC] Find us at http://virtual-roulettes.forumotion.com/
danilop Posted December 26, 2012 Posted December 26, 2012 Yep, we are entering blame game ... It's shame, really - G940 could have been the best HOTAS ever, but Logitech ruined it with poor software and horrible support. G940, being abandoned by its maker is perfect scapegoat! ;)
Ovenmit Posted December 26, 2012 Posted December 26, 2012 Logitech has nothing to do with it... no drivers or firmware have changed in like 2 years... Win 10pro x64 | i5 2500 | 16GB RAM | GTX1060 6GB | Logitech G940 | Tir5 + TC [sIGPIC][/sIGPIC]
danilop Posted December 26, 2012 Posted December 26, 2012 (edited) Exactly! Logitech ditched G940 long time ago, and software companies now can easily blame "obsolete" firmware and software. It's easier (cheaper) for them than fixing the code :) Edited December 26, 2012 by danilop 1
Ensi Ferrum Posted December 26, 2012 Author Posted December 26, 2012 Did a quick test with the code below (you might get it here). Since the whole code is to long, I only posted the relevant part of it. Tried it with my G940 and with my Force 3D Pro, both from Logitech. Both behaved as they should. What the code does is fairly simple, it applies a constant force to the stick. Just like trim should do. [font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][size=2][font=Consolas][color=#008000]// Name: CoordToForce()[/color][/font][/size] [size=2][font=Consolas][color=#008000]// Desc: Convert a coordinate 0 <= nCoord <= FEEDBACK_WINDOW_WIDTH [/color][/font][/size] [size=2][font=Consolas][color=#008000]// to a force value in the range -DI_FFNOMINALMAX to +DI_FFNOMINALMAX.[/color][/font][/size] [/color][/size][/font][/color][/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]INT[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] CoordToForce( [/size][/font][/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]INT[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][color=#808080][font=Consolas][size=2][color=#808080][font=Consolas][size=2][color=#808080]nCoord[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )[/size][/font] [size=2][font=Consolas]{[/font][/size] [/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]INT[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] nForce = MulDiv( [/size][/font][/size][/font][font=Consolas][size=2][color=#808080][font=Consolas][size=2][color=#808080][font=Consolas][size=2][color=#808080]nCoord[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2], 2 * [/size][/font][/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DI_FFNOMINALMAX[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2], [/size][/font][/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]FEEDBACK_WINDOW_WIDTH[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )[/size][/font] [size=2][font=Consolas]- [/font][/size][/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DI_FFNOMINALMAX[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2];[/size][/font] [/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000]// Keep force within bounds[/color][/size][/font] [/color][/size][/font][/color][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]if[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]( nForce < -[/size][/font][/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DI_FFNOMINALMAX[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )[/size][/font] [size=2][font=Consolas]nForce = -[/font][/size][/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DI_FFNOMINALMAX[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2];[/size][/font] [/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]if[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]( nForce > +[/size][/font][/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DI_FFNOMINALMAX[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )[/size][/font] [size=2][font=Consolas]nForce = +[/font][/size][/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DI_FFNOMINALMAX[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2];[/size][/font] [/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]return[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] nForce;[/size][/font] [size=2][font=Consolas]}[/font][/size][/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000] [size=2][font=Consolas][color=#008000]// Name: SetDeviceForcesXY()[/color][/font][/size] [size=2][font=Consolas][color=#008000]// Desc: Apply the X and Y forces to the effect we prepared.[/color][/font][/size] [/color][/size][/font][/color][/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]HRESULT[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] SetDeviceForcesXY()[/size][/font] [size=2][font=Consolas]{[/font][/size] [/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000]// Modifying an effect is basically the same as creating a new one, except[/color][/size][/font] [/color][/size][/font][/color][/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000]// you need only specify the parameters you are modifying[/color][/size][/font] [/color][/size][/font][/color][/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]LONG[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] rglDirection[2] = { 0, 0 };[/size][/font] [/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]DICONSTANTFORCE[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] cf;[/size][/font] [/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]if[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]( g_dwNumForceFeedbackAxis == 1 )[/size][/font] [size=2][font=Consolas]{[/font][/size] [/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000]// If only one force feedback axis, then apply only one direction and [/color][/size][/font] [/color][/size][/font][/color][/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000]// keep the direction at zero[/color][/size][/font] [/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]cf.lMagnitude = g_nXForce;[/size][/font] [size=2][font=Consolas]rglDirection[0] = 0;[/font][/size] [size=2][font=Consolas]}[/font][/size] [/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]else[/color][/size][/font] [/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]{[/size][/font] [/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000]// If two force feedback axis, then apply magnitude from both directions [/color][/size][/font] [/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]rglDirection[0] = g_nXForce;[/size][/font] [size=2][font=Consolas]rglDirection[1] = g_nYForce;[/font][/size] [size=2][font=Consolas]cf.lMagnitude = ( [/font][/size][/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]DWORD[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )sqrt( ( [/size][/font][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]double[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )g_nXForce * ( [/size][/font][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]double[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )g_nXForce +[/size][/font] [size=2][font=Consolas]( [/font][/size][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]double[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )g_nYForce * ( [/size][/font][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]double[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )g_nYForce );[/size][/font] [size=2][font=Consolas]}[/font][/size] [/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]DIEFFECT[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] eff;[/size][/font] [/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]ZeroMemory[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]( &eff, [/size][/font][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]sizeof[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]( eff ) );[/size][/font] [size=2][font=Consolas]eff.dwSize = [/font][/size][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]sizeof[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]( [/size][/font][/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]DIEFFECT[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] );[/size][/font] [size=2][font=Consolas]eff.dwFlags = [/font][/size][/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DIEFF_CARTESIAN[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] | [/size][/font][/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DIEFF_OBJECTOFFSETS[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2];[/size][/font] [size=2][font=Consolas]eff.cAxes = g_dwNumForceFeedbackAxis;[/font][/size] [size=2][font=Consolas]eff.rglDirection = rglDirection;[/font][/size] [size=2][font=Consolas]eff.lpEnvelope = 0;[/font][/size] [size=2][font=Consolas]eff.cbTypeSpecificParams = [/font][/size][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]sizeof[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]( [/size][/font][/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]DICONSTANTFORCE[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] );[/size][/font] [size=2][font=Consolas]eff.lpvTypeSpecificParams = &cf;[/font][/size] [size=2][font=Consolas]eff.dwStartDelay = 0;[/font][/size] [/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000]// Now set the new parameters and start the effect immediately.[/color][/size][/font] [/color][/size][/font][/color][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]return[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] g_pEffect->SetParameters( &eff, [/size][/font][/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DIEP_DIRECTION[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] |[/size][/font] [/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DIEP_TYPESPECIFICPARAMS[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] |[/size][/font] [/size][/font][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a][font=Consolas][size=2][color=#6f008a]DIEP_START[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] );[/size][/font] [size=2][font=Consolas]}[/font][/size][/size][/font] Intel Core i7 2600K @ 3.40GHz OC 4.9 GHz 8,00 GB Dual-Channel DDR3 @ 686MHz (9-9-9-24) ASUS SABERTOOTH P67 (LGA1155) GeForce GTX 780 Creative Sound Blaster Z Logitech Proteus Core Mouse Logitech G19S Logitech G940 (heavily modded) Thrustmaster MFCD-Bevels 1 x Samsung T27B300 2 x ASUS VW224
Ensi Ferrum Posted December 26, 2012 Author Posted December 26, 2012 Just stumbled over some old knowing from days I used the Logitech G25 in some racing sims. With this steering wheel we had to use something called "inverted force", because Logitech products react inverted on forces. Did same change to the above code: [font=Consolas][size=2][font=Consolas][size=2] [/size][/font][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]if[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]( g_dwNumForceFeedbackAxis == 1 ) { [/size][/font][/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000]// If only one force feedback axis, then apply only one direction and [/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2][/size][/font][/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000]// keep the direction at zero [/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]cf.lMagnitude = g_nXForce; rglDirection[0] = 0; } [/size][/font][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]else [/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]{ [/size][/font][/size][/font][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000][font=Consolas][size=2][color=#008000]// If two force feedback axis, then apply magnitude from both directions [/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2]rglDirection[0] = g_nXForce[b]* -1[/b]; // edit by me rglDirection[1] = g_nYForce [b]* -1[/b]; // edit by me cf.lMagnitude = ( [/size][/font][/size][/font][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af][font=Consolas][size=2][color=#2b91af]DWORD[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )sqrt( ( [/size][/font][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]double[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )g_nXForce * ( [/size][/font][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]double[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )g_nXForce + ( [/size][/font][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]double[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )g_nYForce * ( [/size][/font][/size][/font][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff][font=Consolas][size=2][color=#0000ff]double[/color][/size][/font][/color][/size][/font][/color][/size][/font][font=Consolas][size=2][font=Consolas][size=2] )g_nYForce ); } [/size][/font][/size][/font] And voila, the sticks move exactly to where they should. Now can you imagine what happens, if in one line my changes are left? The stick behaves as 9it does since 1.2.2. Intel Core i7 2600K @ 3.40GHz OC 4.9 GHz 8,00 GB Dual-Channel DDR3 @ 686MHz (9-9-9-24) ASUS SABERTOOTH P67 (LGA1155) GeForce GTX 780 Creative Sound Blaster Z Logitech Proteus Core Mouse Logitech G19S Logitech G940 (heavily modded) Thrustmaster MFCD-Bevels 1 x Samsung T27B300 2 x ASUS VW224
StoOopiD Posted December 26, 2012 Posted December 26, 2012 http://simhq.com/forum/ubbthreads.php/topics/3007420/4.html http://riseofflight.com/forum/viewtopic.php?f=350&t=25707 how are they going to fix this? [sIGPIC][/sIGPIC] Crosshair VIII hero wifi, 3800x w/ Enermax 360 AIO cooler (push-pull), 32gigs DDR4 Ripjaws 3600, Win 10 home on a Plextor PCI-E x4 3gb/s HD, EVGA 2070 Super FTW3 ultra+, Soundblaster Z Rift S, M$FFB2, CH Pro throttle, Saitek pedals BS2, A10C, P51D, SPITFIRE, FC3, Uh-1H, F86, Mi-8MTV2, SA342, MIG21-bis, AV8BNA, F14, F16, FA-18C, SUPERCARRIER
Ensi Ferrum Posted December 26, 2012 Author Posted December 26, 2012 http://simhq.com/forum/ubbthreads.php/topics/3007420/4.html http://riseofflight.com/forum/viewtopic.php?f=350&t=25707 how are they going to fix this? Don't know exactly what you mean. Both threads are 'bout hardware related problems of the G940, e.g. wires to short, bad potys, etc. How to fix it? Simple. Exchange the to short wires with longer ones, and replace the cheap potys with better ones. Intel Core i7 2600K @ 3.40GHz OC 4.9 GHz 8,00 GB Dual-Channel DDR3 @ 686MHz (9-9-9-24) ASUS SABERTOOTH P67 (LGA1155) GeForce GTX 780 Creative Sound Blaster Z Logitech Proteus Core Mouse Logitech G19S Logitech G940 (heavily modded) Thrustmaster MFCD-Bevels 1 x Samsung T27B300 2 x ASUS VW224
SkateZilla Posted December 26, 2012 Posted December 26, 2012 Last time I checked, Someone pointed to a thread somewhere on a Logitech board saying it was because the G940 doesn't conform to Windows X Input -FFB Standards, the same way the G25/27 Doesnt, and requires their own driver. I know it's a real Issue with KA-50 Owners especially, as it affects the Rotary Wing Trim / Them more than Fixed Wing Pilots. But that being said, it looks like it's more Logitech's Problem to fix. Good Luck with that though, as A LOT of Racing Sim/iRacing Players have been waiting for similar fixes for the G25/G27 for upwards of 8 years. Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
mrsylvestre Posted December 26, 2012 Posted December 26, 2012 Sure, meant TO :-) Motherfu**ing typing correction on my new tablet. Source is from ED's Facebook account: NP, thanks for the info. Despite all the frustration, I remain optimistic about how this will eventually turn out. The DCS Black Shark is (well, *was* until recently) probably the best reason to own a FFB joystick these days. The FFB/trim implementation by ED was so good that once experienced, there is no turning back. The fact that until recently, the G940 FFB was perfectly working in DCS and is also working in numerous other sims (FSX, Condor, RoF...) is IMHO a proof that whatever is causing the stick/code combination to misbehave in DCSW 1.2.2 can be addressed. 5800X3D - 64GB DDR4 - Samsung 990 PRO SSD @ PCI 4.0 x 16 - 7900XTX (6950XT for posts before May 2025) - Pico 4 (VDXR)
4c Hajduk Veljko Posted December 26, 2012 Posted December 26, 2012 It looks like to me Logitech going out of PC Joysticks business. I wish, Saitek makes a FF joystick. Thermaltake Kandalf LCS | Gigabyte GA-X58A-UD3R | Etasis ET750 (850W Max) | i7-920 OC to 4.0 GHz | Gigabyte HD5850 | OCZ Gold 6GB DDR3 2000 | 2 X 30GB OCZ Vertex SSD in RAID 0 | ASUS VW266H 25.5" | LG Blue Ray 10X burner | TIR 5 | Saitek X-52 Pro | Logitech G930 | Saitek Pro flight rudder pedals | Windows 7 Home Premium 64 bit
mrsylvestre Posted December 26, 2012 Posted December 26, 2012 Last time I checked, Someone pointed to a thread somewhere on a Logitech board saying it was because the G940 doesn't conform to Windows X Input -FFB Standards, the same way the G25/27 Doesnt, and requires their own driver. Testing the sample code linked in Ensi Ferrum's post or Average Pilot's nice simFFB program suggests that the G940 is working as it should (at least with that code). Besides, the G940 is also working with FSX, a Microsoft program released in 2007. That is nearly 2 years before Logitech released the G940 so it seems rather unlikely (to say the least) that FSX would include any G940-specific code. And it is not unreasonable to believe that Microsoft probably knows a thing or two about how to implement DirectX / DirectInput functions correctly. ;) I know it's a real Issue with KA-50 Owners especially, as it affects the Rotary Wing Trim / Them more than Fixed Wing Pilots. But that being said, it looks like it's more Logitech's Problem to fix. Good Luck with that though, as A LOT of Racing Sim/iRacing Players have been waiting for similar fixes for the G25/G27 for upwards of 8 years. What is the problem with the G25/G27 with iRacing (and other racing sims) ? Last time I checked, my trusty G25 was working perfectly with all the racing sims I have been throwing at it. 5800X3D - 64GB DDR4 - Samsung 990 PRO SSD @ PCI 4.0 x 16 - 7900XTX (6950XT for posts before May 2025) - Pico 4 (VDXR)
MA_Goblin Posted December 27, 2012 Posted December 27, 2012 +1 My G27 functions perfectly in all racing sims/games out there! [sIGPIC][/sIGPIC] _____________Semper paratus, In hoc signo vinces________________ PC: Intel i7-8700K (4.9 GHz), Aorus Ultra Gaming Z370 MB, Gigabyte RTX 3080, 32 GB DDR3 (3,2 GHz), Samsung EVO 860 M.2 500 GB SSD + Samsung 960 M.2 250 GB SSD Gaming: Virpil T-50 CM2, TM WH Throttle, Crosswind pedals, HP Reverb
Ensi Ferrum Posted December 27, 2012 Author Posted December 27, 2012 Been playing Race, Race07 with all expansions, rFactor, RBR, GP4, F1-2010, F1-2011, F1 2012, Shift unleashed with my G25, never had a problem. But this thread is about the G940, so back to topic please. As we all know, the Force-Feedback is somewhat inverted by Logitech products. Therefore, in some racing titles we have to invert the force. Given the fact that we don't need to do this in DCS World, if I remember right, tells me that there is a function which determins which Joystick is plugged in. A former colleague of mine, software-designer and one of the best mathematics genies I personally know, gave me a little hint yesterday at dinner. What if the joystick is not properly recognized by the software. Could this lead to the malfunction? After thinking about it, I would not say this is the case, it is properly recognized. But this is only a guess, as I don't know the exact code ED has implemented to determine the stick. Let me do some more testing throughout the day. Intel Core i7 2600K @ 3.40GHz OC 4.9 GHz 8,00 GB Dual-Channel DDR3 @ 686MHz (9-9-9-24) ASUS SABERTOOTH P67 (LGA1155) GeForce GTX 780 Creative Sound Blaster Z Logitech Proteus Core Mouse Logitech G19S Logitech G940 (heavily modded) Thrustmaster MFCD-Bevels 1 x Samsung T27B300 2 x ASUS VW224
danilop Posted December 27, 2012 Posted December 27, 2012 Been playing Race, Race07 with all expansions, rFactor, RBR, GP4, F1-2010, F1-2011, F1 2012, Shift unleashed with my G25, never had a problem. ... Same here (+GTR2) ... :thumbup:
Ensi Ferrum Posted December 27, 2012 Author Posted December 27, 2012 Did a quick test with my Force 3D Pro and the A-10C. Wanna know the outcome? The very same behavior as with the G940. Intel Core i7 2600K @ 3.40GHz OC 4.9 GHz 8,00 GB Dual-Channel DDR3 @ 686MHz (9-9-9-24) ASUS SABERTOOTH P67 (LGA1155) GeForce GTX 780 Creative Sound Blaster Z Logitech Proteus Core Mouse Logitech G19S Logitech G940 (heavily modded) Thrustmaster MFCD-Bevels 1 x Samsung T27B300 2 x ASUS VW224
PeterP Posted December 27, 2012 Posted December 27, 2012 Are you so desperate to go a 'unusual' ways? Are you able to dismantle your G940 and put it back together ? Are you able to cut two wires and bring them back together? If yes, here is a hardware fix that will help you waiting for a software fix: Swap the two wires that drives the brush-less motor that move the swapped axis. IMHO: Your time is better spend doing this hardware-fix instead of posting every couple of hours that it still doesn't work.
Ensi Ferrum Posted December 27, 2012 Author Posted December 27, 2012 Came across this idea a few weeks back on my own. BUT: Then I have the wrong FFB in Cliffs of Dover, FS-X, X-Plane 10.0, RoF. Sorry, NoGo. Intel Core i7 2600K @ 3.40GHz OC 4.9 GHz 8,00 GB Dual-Channel DDR3 @ 686MHz (9-9-9-24) ASUS SABERTOOTH P67 (LGA1155) GeForce GTX 780 Creative Sound Blaster Z Logitech Proteus Core Mouse Logitech G19S Logitech G940 (heavily modded) Thrustmaster MFCD-Bevels 1 x Samsung T27B300 2 x ASUS VW224
SkateZilla Posted December 27, 2012 Posted December 27, 2012 Did a quick test with my Force 3D Pro and the A-10C. Wanna know the outcome? The very same behavior as with the G940. Testing the sample code linked in Ensi Ferrum's post or Average Pilot's nice simFFB program suggests that the G940 is working as it should (at least with that code). Besides, the G940 is also working with FSX, a Microsoft program released in 2007. That is nearly 2 years before Logitech released the G940 so it seems rather unlikely (to say the least) that FSX would include any G940-specific code. And it is not unreasonable to believe that Microsoft probably knows a thing or two about how to implement DirectX / DirectInput functions correctly. ;) What is the problem with the G25/G27 with iRacing (and other racing sims) ? Last time I checked, my trusty G25 was working perfectly with all the racing sims I have been throwing at it. Been playing Race, Race07 with all expansions, rFactor, RBR, GP4, F1-2010, F1-2011, F1 2012, Shift unleashed with my G25, never had a problem. But this thread is about the G940, so back to topic please. As we all know, the Force-Feedback is somewhat inverted by Logitech products. Therefore, in some racing titles we have to invert the force. Given the fact that we don't need to do this in DCS World, if I remember right, tells me that there is a function which determins which Joystick is plugged in. A former colleague of mine, software-designer and one of the best mathematics genies I personally know, gave me a little hint yesterday at dinner. What if the joystick is not properly recognized by the software. Could this lead to the malfunction? After thinking about it, I would not say this is the case, it is properly recognized. But this is only a guess, as I don't know the exact code ED has implemented to determine the stick. Let me do some more testing throughout the day. edit, sorry, Had a bit of a brain fart on the note of the G25/27 FFB, Mine Also works fine in iRacing. Interesting note about other FFB Sticks having an issue, so that eliminates FFB Translation from Logitech's Drivers to DirectX X-Input. So... Maybe the Culprit is the DirectX X-Input/ Other Input Code for DCSW 1.2.2, I do notice other things related to Sticks in DCSW 1.2.2 not in 1.2.1 or 1.1.1.1. when dealing with Axes. Windows 10 Pro, Ryzen 2700X @ 4.6Ghz, 32GB DDR4-3200 GSkill (F4-3200C16D-16GTZR x2), ASRock X470 Taichi Ultimate, XFX RX6800XT Merc 310 (RX-68XTALFD9) 3x ASUS VS248HP + Oculus HMD, Thrustmaster Warthog HOTAS + MFDs
Rotorhead Posted December 27, 2012 Posted December 27, 2012 Interesting, so G940 is not the only stick with this problem? Seems like Logitech drivers are really somewhat "special", but... I'll repeat myself right now, but we all saw them working in earlier versions. It means, no matter how much "different" they are, there must be some trick to make them do what they should.
mrsylvestre Posted December 28, 2012 Posted December 28, 2012 (edited) edit, sorry, Had a bit of a brain fart on the note of the G25/27 FFB, Mine Also works fine in iRacing. No harm done :) Interesting note about other FFB Sticks having an issue, so that eliminates FFB Translation from Logitech's Drivers to DirectX X-Input. So... Maybe the Culprit is the DirectX X-Input/ Other Input Code for DCSW 1.2.2, I do notice other things related to Sticks in DCSW 1.2.2 not in 1.2.1 or 1.1.1.1. when dealing with Axes. The Force 3D stick is also made by Logitech so the "blame Logitech" crowd will not be entirely convinced, I suspect :) However, other things seem indeed a bit fishy with the axes. Also MSFF2 users need to tick "swap axis" in the config, and if I read other forums posts right, even after that the on-screen trim visuals do not always mimic the input (and the trim effect) on some (all ?) planes. To me, the two key arguments remain that a) something that was working in 1.2.1 does not work anymore in 1.2.2 so I see no reason why 1.2.1 behaviour could not be restored and b) the G940 works well with about every other flight sim (including older sims developed before the G940 went into production) and even FSX which, coming from Microsoft, can be expected to strictly adhere to the DirectX standards. One should probably not exclude that the problem arises from a combination of "features" from DCS and Logitech's FFB implementation, though. Maybe the easiest way out for the ED coders (but I am not in their shoes...) would be to add a "reverse X force axis" checkbox and a "reverse Y force axis" checkbox to the "swap axis" one in the config screen and implement FFB sign changes accordingly. This brute force solution may not be elegant but would at least restore functionality. Anyway, I am happy to know that ED is talking to Logitech (1st post of this thread). That suggests that they really want to fix the problem for good. Edited December 28, 2012 by mrsylvestre typo. 5800X3D - 64GB DDR4 - Samsung 990 PRO SSD @ PCI 4.0 x 16 - 7900XTX (6950XT for posts before May 2025) - Pico 4 (VDXR)
Ovenmit Posted December 28, 2012 Posted December 28, 2012 Since they are "talking" to logitech... how about getting the button lights working, being the first sim to do so natively :P Win 10pro x64 | i5 2500 | 16GB RAM | GTX1060 6GB | Logitech G940 | Tir5 + TC [sIGPIC][/sIGPIC]
Recommended Posts