If FanaLab doesn't start this can be fixed by deleting the Fanalab folder in C:\users\[username]\AppData\Local\PodiumControl and then restarting Fanalab. Please send me the log files after solving the issue, it's described at the end of this post how to collect logs
This same identical problem was reported many versions ago by many people here and there was absolutely no help. When they couldn't fix something, they just ignored it, it seemed? Is this how Fanatec works?
Their best recommendations that I know by heart here:
- delete the podium folder and try again; There was no podium folder.
- generate a log and send it to them; Fanalab did not run so log cannot be generated.
If devices are not shown by FanaLab, check if they shown in the normal driver, quite often that's the root cause. If they are not, open the driver installer and run the repair function, then re-boot.
Not to be rude, I work as a software engineer for 30+ years and I know what it involves. As a software engineer I cannot tolerate a single bug in my software as I consider it an insult to me. When a piece of software cannot even launch, that's more than inconsiderate. Is anybody tracking bug report at Fanatec? Is anybody trying to debug it?
Thing is, what you can not reproduce you cant fix.
But of course the issue is on the known issue list and "anybody" is looking into it and trying to debug it but its just one of these rare issues which nobody internally can reproduce at all so its hard to find the root cause.
Agreed that you cannot fix what you can't reproduce. On the other hands, it also didn't mean that if it did not happen in your pristine Fanatec environment then it cannot happen. When more than 1 person encountered the same problem, it cannot be "oh it's that idiot user". As I pointed out previoulsy, Windows event logged several application exceptions when fanalab launched. Of course I can't decode it myself but nobody ever asked to see those.
If you can't reproduce it yourself and if you take it seriously, then work with the users who did.
Hello everyone, I have already read a bit through the forum, but have not really found what I was looking for. Is there a way in Fanalab to change the color of the LED, with own values and not only the default colors? I own the Formula V2
yes i am aware of that, i am interested in more colors than just the ones provided by Fanalab. my eyes have problems with some color tones, so i would like to use a different red and a more yellowish green. maybe there is a possibility to implement that in a future version
In the future there will be more colors, yes definitely!
However it's unclear if we can that advanced to let the user code it's own color to his liking or if just more default colors will be added. But it's definitely on the list :)
Can you provide windows event logs about the FanaLab crashes? Got them from some other crashes already but more probably helps to nail it down. You can also send them to me via personal message, then it's a bit quicker that I see them.
If I want to use fanalab with F1 2020, what is the best telemetry port forwarding software to use? Simhub? or Fanatec one? or other? I was looking for the dedicated Fanatec one but couldn't find it. The best would be if the telemetry was port forwarded in Fanalab. Hope you will build this in soon!
Sur le Porsche GT3 podium hub boutron l'ITM est normalement programmable comme les leds mais fanlab ne fonctionne pas.... Toujours pas....encore pas.... On envoie les fichiers journaux et ...? Pas de réponse
I own a csl elite PS4 wheel base and fanalab 1.53 freezes a few minutes after I start a session in ACC. The fanatec LEDs are disabled in game. Usually the result is all LED on the wheel base stay on until I shutdown the wheel and the P1 wheel gets the blue limit RPM led on. This happens everytime. Didn't try with other games as I don't play anything else at the moment. This is the first version of the app as I bought the wheel on black Friday. Firmware and driver are on the latest version. Driver 381. Firmware 680
Comments
Try this... as mentioned in the initial post
Known Issues / Workaround:
I got the same thing. Searching this forum and found that this same problem existed from many versions ago from many people. No solution.
with driver 380 same way stop after 5 secondes
i have not local dossier podium
in file fw error log my systel is vista is not good i have windows10 64bits
y copy file error log and device information
Endor FW Forcefeedback Driver
Build: Apr 1 2020 13:58:50
Call : 12/14/2020 13:8:1
SystemInfo PROCESSOR_ARCHITECTURE_AMD64 (x64 - AMD or Intel)
OSVersionInfo Version Number = 6.0
OSVersionInfo Operating System = Windows Vista
OSVersionInfo CSD Version =
** FW-FFB Error tracing for C:\Windows\System32\MsiExec.exe **
[START TRACE]
Date: Oct 28 2020 17:12:58
OS: Windows 10
OS Version Info: 10.0
OS Build: 18363
PC Driver: 380
Device Connected...
Wheel Base:
- ClubSport Wheel Base V2.5
- FW: 680
Steering Wheel:
- CSW Universal Hub (Xbox One)
- FW: Not Supported
Motor Firmware:
- FW: 22
Shifter:
- ClubSport H-Shifter
Pedal:
- ClubSport Pedal V3
Note: Shifter and Pedals should be connected in the Wheel Base for it to be detected.
Current Tuning Menu Setting:
-TM #2
SEN: 910
FF: 101
LIN: 0
NDP: 100
NFR: 0
NIN: 0
INT: 0
FEI: 100
FOR: 100
SPR: 100
DPR: 100
BLI: 101
SHO: 100
DRI: -5
MPS: 0
APM: 1
BRF: 50
BRG: 60
it is still painful to pay a good price and have to tinker
we are € 2000 betatesteurs
I am not born grumpy but given the messages about fanlab we can wonder if we regret his purchase
This same identical problem was reported many versions ago by many people here and there was absolutely no help. When they couldn't fix something, they just ignored it, it seemed? Is this how Fanatec works?
Their best recommendations that I know by heart here:
- delete the podium folder and try again; There was no podium folder.
- generate a log and send it to them; Fanalab did not run so log cannot be generated.
Now what else?
Logs are stored in C:\users\Public\FanaLab Logs
Send it to Marcel via DM if you followed the troubleshooting workaround and if you have FanaLab to its default install path without changing anything.
If devices are not shown by FanaLab, check if they shown in the normal driver, quite often that's the root cause. If they are not, open the driver installer and run the repair function, then re-boot.
Yes, fanalab was installed in its default path. Yes, it did not start.
A quick search for "fanalab did not start" showed :
Since 2019, the same exact problem and you gave the same suggestions back then but there was never any solutions?
Not to be rude, I work as a software engineer for 30+ years and I know what it involves. As a software engineer I cannot tolerate a single bug in my software as I consider it an insult to me. When a piece of software cannot even launch, that's more than inconsiderate. Is anybody tracking bug report at Fanatec? Is anybody trying to debug it?
Thing is, what you can not reproduce you cant fix.
But of course the issue is on the known issue list and "anybody" is looking into it and trying to debug it but its just one of these rare issues which nobody internally can reproduce at all so its hard to find the root cause.
What you said is different that the 1st post you pointed to. I did not know the log is in c:\users\public\Fanalab\logs. I'll look.
The 1st post you pointed to said:
"In case of a FanaLab crash, use the "Collect Logs" feature under "Settings" and upload them here."
I could not launch Fanalab so I couldn't select "Collect Logs".
Thanks.
Agreed that you cannot fix what you can't reproduce. On the other hands, it also didn't mean that if it did not happen in your pristine Fanatec environment then it cannot happen. When more than 1 person encountered the same problem, it cannot be "oh it's that idiot user". As I pointed out previoulsy, Windows event logged several application exceptions when fanalab launched. Of course I can't decode it myself but nobody ever asked to see those.
If you can't reproduce it yourself and if you take it seriously, then work with the users who did.
Thanks again.
nobody ever said "oh it's that idiot user".
Its being investigated with the help of the users logs and hopefully fixed sometime.
I saw my own share in my career and we call it "operator error" :-)
Thank you. We all sincerely appreciate your help. Have a great day.
FanaLab log folder is here
C:\Users\Public\FanaLab Logs
It should still collect logs on crash, or at least that's the point of it.
Hello everyone, I have already read a bit through the forum, but have not really found what I was looking for. Is there a way in Fanalab to change the color of the LED, with own values and not only the default colors? I own the Formula V2
No. You are limited to the colors provided in Fanalab.
too bad to read this, but thanks for your quick reply.
Define the default colors you mean.
I think your question might be misunderstood.
There is an option in fanalab but it is only basis the combination of the color pallet that fanalab allows you in the flag colors, pit limiters etc.
So basically you cannot create your own color code if I understood maurice's reply but you have to use the colors only provided in fanalab.
https://www.youtube.com/watch?v=HrO6j8HzhEM&t=970s
Around the 9th minute.
yes i am aware of that, i am interested in more colors than just the ones provided by Fanalab. my eyes have problems with some color tones, so i would like to use a different red and a more yellowish green. maybe there is a possibility to implement that in a future version
In the future there will be more colors, yes definitely!
However it's unclear if we can that advanced to let the user code it's own color to his liking or if just more default colors will be added. But it's definitely on the list :)
Can you provide windows event logs about the FanaLab crashes? Got them from some other crashes already but more probably helps to nail it down. You can also send them to me via personal message, then it's a bit quicker that I see them.
Thanks Marcel, will do it in a little bit. It's on my other gaming computer. Appreciate your help.
mike-
Marcel, PM sent. Thanks!
If I want to use fanalab with F1 2020, what is the best telemetry port forwarding software to use? Simhub? or Fanatec one? or other? I was looking for the dedicated Fanatec one but couldn't find it. The best would be if the telemetry was port forwarded in Fanalab. Hope you will build this in soon!
How to remove Fanalab from PC?
Thnx
uninstall it?
Sur le Porsche GT3 podium hub boutron l'ITM est normalement programmable comme les leds mais fanlab ne fonctionne pas.... Toujours pas....encore pas.... On envoie les fichiers journaux et ...? Pas de réponse
I own a csl elite PS4 wheel base and fanalab 1.53 freezes a few minutes after I start a session in ACC. The fanatec LEDs are disabled in game. Usually the result is all LED on the wheel base stay on until I shutdown the wheel and the P1 wheel gets the blue limit RPM led on. This happens everytime. Didn't try with other games as I don't play anything else at the moment. This is the first version of the app as I bought the wheel on black Friday. Firmware and driver are on the latest version. Driver 381. Firmware 680
Thanks.
Ça fait moyennement rire entre le fait de ne pas obtenir de solutions sauf envoyer les fichiers journaux d'erreurs
Je crois que fanatec collectionne les journaux sans les lires...
On s'en fiche le client à déjà payé....
Ou alors c'est de l'incompétence..
Ou alors les deux.
It is moderately laughing between not getting any solutions except sending the error log files
I believe that fanatec collects newspapers without reading them ...
We don't care the customer has already paid ....
Or it is incompetence.
Or both.