Works fine without LFS open, but as soon as LFS is in focus, it stops changing (the rpm value still goes up and down though).
Both windowed and fullscreen.
Starting the app after, then clicking on LFS does the same...
After some extra investigation I was able to modify the test program and now it's possible it will actually work. However, there are few steps you have to take before testing...
1) Enable OutGauge in cfg.txt (in your LFS directory) and set it like this
OutGauge Mode 1
OutGauge Delay 1
OutGauge IP 127.0.0.1
OutGauge Port 30000
OutGauge ID 0
2) Start LFS, go to Options->Controls->Axes/FF and set Force Feedback to "No" (really, it's necessary right now)
3) Start LedsTest
If you set up everything correctly, you should be able to see the LEDs lighting up at 4000 rpm and reaching redline at 7500.
If something goes wrong, you should still be able to see at least first led lit, the first led should also light up when rpm drops below 100.
Did above; upon launching the exe I get the following;
The First two LEDs light up upon launching the exe; other LEDs don't light up. Closing the app don't turn off the lights. Closing LFS don't turn off the lights; need to remove the USB to turn them off - don't know if that'll help, just thought I might add...
First time I'm trying this out; I have not checked if the previous (i.e. yesterday's release work(yet)).
The app displays the X-axis position as a sort of check that it has access to the device. You should see it changing as you turn the wheel. If the output seems to be frozen, then there is something oddly wrong. Can you try it without LFS running?
Awesome, could it be that we're finally getting somewhere? I suppose I should now make everything configurable and give it a better user interface. I'll deal with the Force Feedback later as it will probably require some wicked hack to make the LEDs play along with it...
Another little update. I pretty much rewrote the whole thing to get rid of tons of unnecessary code and make the code well organized.
There is also a config file which allows you to customize at what RPM the LEDs should light up and reach the redline. The OutGauge connection IP/port is adjustable too. There is still no force feedback workaround though...
I've changed a lot of things internally so if this doesn't work for you, give the old version a try 'cause it's possible I accidentally broke something...
Still works great
Though, the lights flash after it goes over the set redline, so 8000 is a little high for XRT (fuel cutoff is around 7500), or even FZ5 (just under 8000).. so it only flashes if the engine gets over-revved :P
All the cars are too high
edit: It seems any port higher then 32767 gets this: "Cannot parse port number, check your config file."
Other ports work though....
Hi, I tried to turn the program but then nothing had happened when I went in the pit stop and after a while, then showed up on the error screen, visible in the photograph that I send. can anyone help?
My operating system is Windows 7 64 bit
LFS stops sending OutGauge packets when the car in view is not moving or if you're not in race. There is a timeout set in this app which triggers this error when no OutGauge packet is received for 30 seconds. Not a good idea for general use, but this app was more of a proof of concept thing...