I dont know if youre still watching this thread but i did somew googling on the issue and even though i have no programming skills whatsoever this might interest you.
They had the same problem for rfactor and what they had to do was change the force feedback setting to a negative number. Now i dont know if that is possible in lfs. But if so can someone with some basic programming skills atleast have a look at it?
For all I know the rF plugin uses a hacked dinput8.dll to work around DInput limitations, setting FF strength or whatever to a negative number would do squat. (unless it's abusing some bug in DInput that is).
Anyway, thanks for your interest, could you post a link to the info you found?
By a lucky fluke I stumpled upon a template of a proxy dinput8.dll which made me experimenting again. I have no way of testing if this is actually working, all I know is that it's being loaded and used by LFS and that it's receiving correct packets from OutGauge.
It will need a helluva lot of fixing and tweaking, now I just want to know if this approach has any chance to work.
To try it out set OutGauge the "usual" way, port 30000, IP 127.0.0.1, copy the dinput8.dll to your LFS directory and launch LFS. You should hear a short beep upon LFS' startup confirming that the proxy DLL is being used and OutGauge interface has been set up. Get on track, first LEDs should light up at 3000 RPM and you should hit the redline just before 7000.
It should not interfere with force feedback this time.
Launches LFS without issue when the wheel is disconnected.
Plugged it in. Didn't crash.
Althought Controller was selected as Wheel in Options > Controls the G27 was not recognized. Switched to Mouse, LFS beeped and the G27 was recognized - although pedals were set to combined (most of my settings/previous wheel button binds seemed to be lost).
First LED lighted up at 3000. Red ones light up around 5750.
Wheel turn limited to 180 (450ish in-game). 450-ish in profiler. Changing the value in LFS does not make a difference.
No ffb (set yes, and tried at various values)
Alt+tab back into LFS will make it crash again. "Failed to bind socket. G27 LED wont be available".
I'm done for the day, but I think I was able to figure out why it crashed. I managed to mend this on my machine, so you're free to try it out. Do not attempt to Alt+Tab from LFS, there something wrong with releasing the device, the same problem also causes LFS to hang on exit, but I'll deal with this later on when I know this has a chance to work out.
Be sure the OutGauge is configured properly and if you have any trouble, try rebooting your machine. Fixed DLL is attached to the previous post.
I'm sorry for putting you through such a hassle, but there's noone around who could lend me a G27...
Leds are working. No feedback.
Game can't exit(black screen and process stays active, have to CTRL+ALT+DEL)
Not compatible with other DX "plugins"(it didn't work when i was using the DirectX overlay plugin of TeamSpeak3)
A little update. To simplify things for the time being I ditched OutGauge and the modded dll now reads the RPM directly from the memory. This approach has a few setbacks, the worst being that it WILL NOT work at all if you have any other 3rd party dll mod installed (ENBseries etc.)
The hang on exit or Alt+Tab should be fixed. All debugging info is being written to g27dbg file, FFB is next on my TODO list.
It looks like I was finally able to get around the obnoxious no FFB problem. I attached two version of the mod, the NOFFB version uses an old method which is known to light up the LEDs at the expense of messing up FFB, the second one is what I'd like to test.
Could you please try out both versions and report back how they behave? A g27dbg.txt file is created and it doesn't get overwritten so please, don't delete it and, if possible, send it along with your report.
Thanks a lot...
EDIT: Files removed, read on to get the recent version...