Any chance fanalab could implement telemetry forwarding so it could be the first stop for Telemetry data from a simulator game, instead of a last?
Simhub is forwarding it for me now, but I do not like the idea that the game sends data to Simhub, and Simhub sends data to Fanalab that controls the game interfaces.
I think it would be better if Fanalab had the telemetry data first and then forwarded it to less critical apps like simhub.
It's a known issue and on the first page in the first post there is a workaround for that.
Did you tried that workaround? AppData is a secret hidden folder which you first have to make visible according to Google tutorials. You MUST have that folder, otherwise your pc is completely screwed and Fanalab isnt properly installed.
What are you talking about? Just follow the workaround Maurice already mentioned!
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.
In 99% of this kind of issues its a simple user error.
The Workaround worked for EVERYONE who had your issue.
If you dont have the mentioned folder then it could be because the installation of FanaLab went wrong (simply uninstall and re-install would help) or because you dont enabled visibility of hidden folders which you then first have to enable to see the AppData folder where the sub-folder WILL BE included. Simply deleting that folder and re-starting FanaLab will fix the issue.
A simple users error! I have an Origin PC on the way and I decided to give Fanalab one more try. I will no longer be a looser and a sucker for Fanatec's Fanalab software. The Podium 911 GT3 boat anchor will continue to be a home for spiders.
Sascha I do not have access to the AppData but Fanatec did when they created the file named "PodiumControl". Fanatec should be the only software that would access "PodiumControl" and would be the cause of the corruption. Stop casting the blame where it does not belong.
Fanatec is in denial when they can blame the users for a corrupted hidden file named "PodiumControl".
Bill, stop this please and just google how to make the AppData folder visible, then you will see the PodiumControl sub-folder in there as shown in the workaround in the first post. Delete it, restart FanaLab and you can use FanaLab again.
I'm having some issues with Fanalab and the F1 2020. I am using Fanalab to give me wheel lock and wheel spin vibrations in my CS 3 Throttle and Brake pedals.
Since the last F1 2020 update (1.12) when I do larger multiplayer races, with qualifiers, in the middle of my race, the FFB cuts out and the wheel goes limp, or pulls to the right side, and the wheel base needs to be restarted in order to come back to life.
I don't really understand how fanalab (or even the fanatec driver) communicate with f1 2020. Is it all through telemetry data? or does it also have a native transfer of data? Do I need to have both for it to work? I am interested in the wheelbase and FFB data communication, as that is the connection that seems to break. Guessing it comes down to some interruption in the communication between fanalab and f1 2020.
I also do not understand why the disconnect would be specific to larger multiplayer lobbies (especially when it happens with just two same country live players and 16 AI's). I have a very stable wired internet connection (business class service) and never have any lag or weak connection indicators...??
I could really use your help getting this connection solid, as I really would like to use the wheel lock and wheel spin brake and throttle motor feedback that that I get with fanalab.
You can just type in \AppData in windows explorer without changing any settings. That's what I do. I also had this same issue once and solved it by deleting the folder within \PodiumControl.
Not sure why you feel your PC is screwed. Plenty of software has access and content in this folder, not just Fanatec.
So why do you say it will be fixed? (I hope you are right, but this problem has existed ever since F1 2020 1.12 release, and not before then for me. And it only happens while racing, after quali, in multiplayer mode.
I already have the latest driver, don't I - 373? Is there a newer driver you are referring to? My understanding is 380 is not released yet?
Also, I am still hoping someone can explain to me why this "wheelbase freeze" is happening. I never had this with Thrustmaster and am becoming quite frustrated because all the sim hardware/software vendors keep passing responsibility to the other, and all I know is I still have the problem!
Fanatec Support blames Codemasters - (Techinical Support - Fareed - Fanatec Support Team)
Codemasters blames Fanalab
Fanalab blames Fanatec Drivers (above)
... and the best I am getting is to try some Release Candidate Fanatec driver and it will magically fix it? I sure would like some better explanation of what is going on here.
Comments
Any chance fanalab could implement telemetry forwarding so it could be the first stop for Telemetry data from a simulator game, instead of a last?
Simhub is forwarding it for me now, but I do not like the idea that the game sends data to Simhub, and Simhub sends data to Fanalab that controls the game interfaces.
I think it would be better if Fanalab had the telemetry data first and then forwarded it to less critical apps like simhub.
That's on the list for next year AFAIK.
😕
Maurice are your profiles still compatible with the new 380 driver?
Cheers for any info
Yes but there will be new ones with the release of Fanalab 1.51 coming soon. ;)
Perfect, thank you, looking forward to 1.51 and the new profiles.
Today I discovered, after some testing, that Fanalab won't let my PC go to suspension / standby. Is there a way to avoid this? Thanks
Same issue here, brake works fine and can control it with BLI, throttle does not work at all. Only tried ACC
I installed new 380 driver and this is now fixed
Did anyone find a way to solve this issue? (Under Windows 10).
Thanks
Anyone have an MP4-30 Profile for iRacing?
Fanalab quickly displays the FANATAC banner (about two seconds) then disappears. Task Manager does not show it running.
DD1 with Formula V2
PC Driver 373
Wheel Base Firmware 674
Wheel Base Motor 40
Steering Wheel Firmware 35
"C:\Program Files (x86)\Fanatec\FanaLab\Control\" Installation Path
I do not have a "C:\users\[username]\AppData\Local\PodiumControl" folder. I am the only users of this computer.
I do have a "C:\Program Files (x86)\iRacing\iRacingSim64DX11.exe" size 163,344 KB date 10/29/2020 12:33 PM
It's a known issue and on the first page in the first post there is a workaround for that.
Did you tried that workaround? AppData is a secret hidden folder which you first have to make visible according to Google tutorials. You MUST have that folder, otherwise your pc is completely screwed and Fanalab isnt properly installed.
The iRacing exe is irrelevant for this...
So Fanatec modified a file that they can not maintain!
?
What are you talking about? Just follow the workaround Maurice already mentioned!
Thank you Fanatec for completely screwing my PC.
In 99% of this kind of issues its a simple user error.
The Workaround worked for EVERYONE who had your issue.
If you dont have the mentioned folder then it could be because the installation of FanaLab went wrong (simply uninstall and re-install would help) or because you dont enabled visibility of hidden folders which you then first have to enable to see the AppData folder where the sub-folder WILL BE included. Simply deleting that folder and re-starting FanaLab will fix the issue.
Do you have access to the appdata folder?!
A simple users error! I have an Origin PC on the way and I decided to give Fanalab one more try. I will no longer be a looser and a sucker for Fanatec's Fanalab software. The Podium 911 GT3 boat anchor will continue to be a home for spiders.
Sascha I do not have access to the AppData but Fanatec did when they created the file named "PodiumControl". Fanatec should be the only software that would access "PodiumControl" and would be the cause of the corruption. Stop casting the blame where it does not belong.
Fanatec is in denial when they can blame the users for a corrupted hidden file named "PodiumControl".
Bill, stop this please and just google how to make the AppData folder visible, then you will see the PodiumControl sub-folder in there as shown in the workaround in the first post. Delete it, restart FanaLab and you can use FanaLab again.
I'm having some issues with Fanalab and the F1 2020. I am using Fanalab to give me wheel lock and wheel spin vibrations in my CS 3 Throttle and Brake pedals.
Since the last F1 2020 update (1.12) when I do larger multiplayer races, with qualifiers, in the middle of my race, the FFB cuts out and the wheel goes limp, or pulls to the right side, and the wheel base needs to be restarted in order to come back to life.
I don't really understand how fanalab (or even the fanatec driver) communicate with f1 2020. Is it all through telemetry data? or does it also have a native transfer of data? Do I need to have both for it to work? I am interested in the wheelbase and FFB data communication, as that is the connection that seems to break. Guessing it comes down to some interruption in the communication between fanalab and f1 2020.
I also do not understand why the disconnect would be specific to larger multiplayer lobbies (especially when it happens with just two same country live players and 16 AI's). I have a very stable wired internet connection (business class service) and never have any lag or weak connection indicators...??
I could really use your help getting this connection solid, as I really would like to use the wheel lock and wheel spin brake and throttle motor feedback that that I get with fanalab.
Any ideas?
(I've also opened a thread at Codemasters that you can look at for reference, because I think it is the communication between fanalab and F1 2020 that is breaking)
data:image/gif;base64,R0lGODlhAQABAPABAP///wAAACH5BAEKAAAALAAAAAABAAEAAAICRAEAOw==What you mention is a typical Wheel Base Freeze and is more a firmware and not a FanaLab issue.
This specific kind of freeze should be fixed with the latest driver 380 and included firmware. Which driver are you using?
You can just type in \AppData in windows explorer without changing any settings. That's what I do. I also had this same issue once and solved it by deleting the folder within \PodiumControl.
Not sure why you feel your PC is screwed. Plenty of software has access and content in this folder, not just Fanatec.
Yep now I don't have a c:\User\.... Thanks for not suppling a link.
Dude... Windows button + R. Type in %appdata%. Go back to Appdata, then click on the Local folder and delete the folder "PodiumControl"
If you don't understand how to access the Appdata folder, why don't you ask instead of blaming others now?
Please close Fanalab prior to the steps above!
Bill, please.
Follow these steps:
If you don't know how to access the Appdata, why don't you just tell us and stop blaming others now?!
PC Driver: 373
Wheel Base: 674
Motors: 22
Wheel: 35
Fanalab: 1.47b
So why do you say it will be fixed? (I hope you are right, but this problem has existed ever since F1 2020 1.12 release, and not before then for me. And it only happens while racing, after quali, in multiplayer mode.
It should be fixed with the latest driver and included FWs. Please update your driver to see if it fixes the freezes for you.
I already have the latest driver, don't I - 373? Is there a newer driver you are referring to? My understanding is 380 is not released yet?
Also, I am still hoping someone can explain to me why this "wheelbase freeze" is happening. I never had this with Thrustmaster and am becoming quite frustrated because all the sim hardware/software vendors keep passing responsibility to the other, and all I know is I still have the problem!
Fanatec Support blames Codemasters - (Techinical Support - Fareed - Fanatec Support Team)
Codemasters blames Fanalab
Fanalab blames Fanatec Drivers (above)
... and the best I am getting is to try some Release Candidate Fanatec driver and it will magically fix it? I sure would like some better explanation of what is going on here.