No. The LEDs in the base are not RGB.
oohh what a pity :(
Thanks to everyone providing feedback and log files.
Have you seen my log files above, Marcel?
Marcel asked you on the previous page. Maybe answer that question first :)
Seems to work now, I drove with it in iracing for 30 min, no crash. Before it crashed after 1 minute or so ;)
Marcel what's the status on pedal vibration ocasionally getting stuck?
Fanalab Keeps crashing after +- 4 minutes of use.
I am using a CSL elite+ (ps4 compatible) with clubsport v3 peddals. PC driver 400 wheel Base Firmware 684, Wheel base motor firmware 22. Fanalab V1.54.3
I activated the telementry both out of the game and while in the game and also enabled the led lights
This crash occurs with multiple games. I've tried it on assetto corsa and assetto corsa competizione.
I can reproduce this problem every time i want by just starting up fanalabs and then the game. drive a bit and suddenly the rev lights stay on all the time and dont change. then when i click on fanalabs, it crashes
If you need any more information please contact me I will provide everything. I hope we can figure this out otherwise my wheel base its rev lights will be off all the time.
1.54.3 can crash, yes. Try the new FanaLab (without s) version 1.54.5 which was posted today (5 posts above your message).
Also when you click the Enable Telemetry Button you always have to restart the game so the changes take ffect, therefore never click this when you are actively running a game.
Also best to use driver 402 and not 400.
Not the first time I've posted this:
Fanalab should not be showing up in the alt-tab menu when it is minimized to the system tray.
1.54.5 also crashing for me ... Either crashes, or the leds remain all lit up.
402 driver package. This is really unplayable ...
Which game? Please always provide your Fanalab Logs and more importantly your Windows Event Logs when you report crashes. Otherwise nobody can help you...
Wheelbase: fanatec DD2
Rim: Formula V2
Driver package: 402
Firmware: wb 684, motor 40, wheel 40, qr 6
Additional sofware: racelabs, heusinkveld smart control, tradingpaints, crewchief
It does not matter if it is practice, qualifying or race, but after a few minutes (usually less than 3) when everything seems to be working fine the led lights simply freeze on the wheel, the oled display aswell. They simply remain lit.
It may be worth mentioning that the info on the wheelbase display freezes aswell. Sometimes fanalab software is still running, but no matter what changes i do nothing happens in game, other times (mostly) it simply crashes. Another thing, i thought that it might have something to do with ITM, so i put it on "default"/ legacy", but it really doesnt count, as it randomly jumps to one of those 5 pages.
I am attaching the fanalab logs and i kindly ask you how to get the windows event logs in order to post them aswell.
windows event log
win event log
I am no developer but I had a look at the logs and saw you get a LOT of error messages, not only FanaLab but also TradingPaints and some part of your Gigabyte software is crashing which more leads to a general problem with your Windows installation or a specific other program I would say.
Anyway I am sure the Fanatec Devs will have a look at this as this iRacing crash issue has quite high priority and IF its an issue of FanaLab (which is a bit unlikely as explained) I am sure this logs will help!
Thank you, Maurice ! I will try to shape up my Windows !
Just had a quick look into the win event log. First of all, thanks for providing.
What I can see is that there are a lot of IO-Errors and a lot of OutOfMemory errors.
You might want to do a HDD test and / or RAM test.
If you are using an SSD, try to trigger the TRIM command of your SSD.
Thanks a bunch ! Will do !
I also have raised this in the past. Is it still the case with 1.54.5 ?
I am on old version (1.54.2). If alt-tab issue or minimize to tray have been fixed, I will upgrade.
As it's not listed in any Changelog, no it's not fixed.
@Maurice and @Ensi
Guys, i have cleaned up my windows quite a bit, tested the ram and hdd, until the only event log errors are related to fanalab (attaching the freshest log here)
Crash occurs though.
I cannot think about anyhing more than maybe fresh reinstalling the 402 driver package, but im unsure if this would help much ...
Thank you so much for the support
Thanks again for the logs.
Don't think that a new installation of the driver will cure the Fanalab Crash, but you can try.
Is the crash only occuring in iRacing?
yeah, its the only racing game im playing
Hi I have downloaded Fanalab Ver 1.54.4
Running Windows 10 64 Bits
From Fanatec Firmware Manager
Club Sport Wheel Base V2 Firmware 684
ClubSport Formula V2 Firmware 40
ClubSport Pedal V3 1.31
Game Profile F1 2020
I Enable telemetry, confirm port then I get this message F1 2019 : I get either access to the path denied or could not find access to the path depending if I add the files back after I deleted them. (trying to figure things out here).
Same for hardware settings but the message starts with F1 2020 instead of F1 2019 as mentioned for telemetry.
Fanalab 1.54.4 working properly.
Thanks to the support ! 💪
1.54.4 still might have a chance of crashing in iRacing, better update to 1.54.5 ;)
My Fanalab keeps crashing and my Formula V2 wheel LEDs just go solid blue in the middle of driving in ACC. Here are my logs.
Please provide Windows Event Logs as that are the important Logs and not the Fanalab Logs when it crashes.
i am seeing the same error playing f1 2020 leds work great for a lap and half before locking red and fanalab becomes unresponsive. I can restart fanalab re enable telemtry and led/hardware and it will work again for a lap or so and repeat. vibration, FFB and pedal vibrations continue just no leds. I can get the same thing to happen in PC 2 as well.
Wheel Base : ClubSport Wheel Base V2.5 latest firmware
ClubSport Steering Wheel Formula V2 latest firmware
: ClubSport Pedals V3 fw 1.31
Windows 10 pro
os build: 18363.1316
thank you for all of your hard work on this project. its beautiful when it is working
i recreated and got more error logs