FOR ALL OF YOU STILL HAVING PROBLEMS WITH FANALAB NOT STARTING
I upgraded to the 410 drivers and latest Fanalab today and had exactly the same issue with splash screen showing for 2 seconds then no cigar.
Did what we have been advised "Delete Podiumcontrol under user/appdata/local" -this didn't work. Reinstalling driver and Fanalab didn't work. This is what worked for me.... I found a folder c:/users/[username]/appdata/local/Fanatec (not PodiumControl). In there I found my old profiles, deleted the folder (after backing up just encase) and Fanalab started first time!
To double-check the issue, I imported one of the backed-up profiles and Fanalab closed immediately, and wouldn't restart. Found the offending profile in that same folder, deleted it, and Fanalab started.
It seems the installation process doesn't always clean up the old profiles- this was definitely the issue for me and Fanalab now works fine.
I've been using Maurice's ACC profiles, and I like them a lot. However, even on the DD1 I feel they're a bit stronger than I'd like. In this case, is it better to lower the Fanalab FFB setting, or the ACC in-game FFB gain? Which should I adjust to preserve the most detail? Thanks!
It is as intended that during new install FanaLab never ever just deletes this folder with the profiles, they always stay in that folder. That was always the case and will always be the case so users dont lose their profiles during an update...😅
So in this case it's intended that the installation process does not clean up that folder, however old profiles should still be compatible and get converted to a new Format automatically. Maybe for some this conversion is not working then, maybe because of older incompatible profiles or so... From what version did you updated?
Maybe other people who are affected can test this as well (please also with a Backup of your profiles of course!).
This explains the issue. We could reproduce the Crash of 1.55 now with old 1.53 profiles so that is indeed the root cause.
1.53 is a very old version. 1.54 got a SIGNIFICANT update to the whole pws file structure. Old 1.53 were converted automatically in 1.54 structure on first boot of 1.54 but when you never installed 1.54 but you went straight from 1.53 to 1.55 and your pws file structure is still on the old 1.53 code this leads to incompatibility to 1.55 now because the profiles are missing the important re-structure of 1.54.
That are actually good news because I think Chances are good that a converter for 1.53 profiles to 1.55 profiles can be created.
Workaround would be to uninstall 1.55.3 again, then install 1.54.5, start 1.54.5, go to the Profile Overview Tabs and select each game once to trigger conversion process for game profiles, then uninstall 1.54.5 again and re-install 1.55.3 again. That way the 1.53 profiles should get converted first to 1.54.5 structure and after that then to 1.55.3 structure.
My DD1 is 3 weeks old, so no problem to start with fresh installation. I was using "official" recommended settings for iracing, so no hassle to start over and try the latest profiles.
Confirmed! On my Laptop there was still 1.53 installed, as I've used this long time ago for FW installation and playing with profiles. Same issue here, but with 1.53 --> 1.54 --> 1.57 it works with at least the iRacing profiles.
Thanks for your response. I upgraded from 1.52, so I believe there is the problem! Seems people upgrading from older versions need to delete the profiles (after backing up). I understand the need to retain and convert profiles during an upgrade of course, but in this instance users could always open the backed up profiles via notepad or similar and replicate the profile in the new version if really necessary. Alternatively, if a hotfix comes out that could cope with converting the older profiles that would sort the issue for all.
This worked for me, but I needed to go one step further.
"I found a folder c:/users/[username]/appdata/local/Fanatec (not PodiumControl). In there I found my old profiles, deleted the folder (after backing up just encase) and Fanalab started first time!
I deleted this folder - still didnt work.
Found another 2 folders named Endor_Fanatec in the same location as above. One is for the 4.10 drivers, and the other has a Folder inside related to Fanalab. I deleted that folder and now Fanalab is back to working properly.
In fairness to Fanatec, its so difficult to cater for an almost unlimited number of PC specifications and combination of wheels/bases/pedals out there. Then, we all have different software installed! So, not an easy job. Personally I think they do a good job of pre-testing their drivers and software- much better than Microsoft!!
We've found the cause of the crash now, its profiles from 1.54 and older which 1.57 tries to convert and fail. If everything goes right we have an update for the weekend with some further improvements to other known issues.
Thanks for the help of everyone with trying different things and providing log files.
Had the same issue with the previous version of Fanalab (1.54) and 1440p triples as well, as soon as I've installed SimHub (don't know the version). Only way to access Fanalab fully and with an correct rendering was minimizing it to the task bar and re-open it, then it was all there as desired.
With the latest versions of Fanalab, SimHub and Nvidia driver it didn't occured so far....
Comments
FOR ALL OF YOU STILL HAVING PROBLEMS WITH FANALAB NOT STARTING
I upgraded to the 410 drivers and latest Fanalab today and had exactly the same issue with splash screen showing for 2 seconds then no cigar.
Did what we have been advised "Delete Podiumcontrol under user/appdata/local" -this didn't work. Reinstalling driver and Fanalab didn't work. This is what worked for me.... I found a folder c:/users/[username]/appdata/local/Fanatec (not PodiumControl). In there I found my old profiles, deleted the folder (after backing up just encase) and Fanalab started first time!
To double-check the issue, I imported one of the backed-up profiles and Fanalab closed immediately, and wouldn't restart. Found the offending profile in that same folder, deleted it, and Fanalab started.
It seems the installation process doesn't always clean up the old profiles- this was definitely the issue for me and Fanalab now works fine.
I hope this helps some of you 😉
Happy racing.
Gray
I've been using Maurice's ACC profiles, and I like them a lot. However, even on the DD1 I feel they're a bit stronger than I'd like. In this case, is it better to lower the Fanalab FFB setting, or the ACC in-game FFB gain? Which should I adjust to preserve the most detail? Thanks!
Hehe, yes I drive more on the stronger end of FFB strength, that's true...😅
Just lower the FFB in the Tuning Menu then :)
VERY interesting!
It is as intended that during new install FanaLab never ever just deletes this folder with the profiles, they always stay in that folder. That was always the case and will always be the case so users dont lose their profiles during an update...😅
So in this case it's intended that the installation process does not clean up that folder, however old profiles should still be compatible and get converted to a new Format automatically. Maybe for some this conversion is not working then, maybe because of older incompatible profiles or so... From what version did you updated?
Maybe other people who are affected can test this as well (please also with a Backup of your profiles of course!).
Thank you!
That's the solution, I deleted fanatec folder (and previously the podium one) and now it starts as it should.
So, guys with this problem, delete podium AND fanatec folder in user/appdata/local (enable hidden files and folders in file explorer).
Now it's time to try Maurice profiles in Iracing. THANK YOU!
From which version did you updated? Were you on 1.53 or 1.54.5 before or maybe an even older version?
From 1.53.
Thanks. That's good!
This explains the issue. We could reproduce the Crash of 1.55 now with old 1.53 profiles so that is indeed the root cause.
1.53 is a very old version. 1.54 got a SIGNIFICANT update to the whole pws file structure. Old 1.53 were converted automatically in 1.54 structure on first boot of 1.54 but when you never installed 1.54 but you went straight from 1.53 to 1.55 and your pws file structure is still on the old 1.53 code this leads to incompatibility to 1.55 now because the profiles are missing the important re-structure of 1.54.
That are actually good news because I think Chances are good that a converter for 1.53 profiles to 1.55 profiles can be created.
Workaround would be to uninstall 1.55.3 again, then install 1.54.5, start 1.54.5, go to the Profile Overview Tabs and select each game once to trigger conversion process for game profiles, then uninstall 1.54.5 again and re-install 1.55.3 again. That way the 1.53 profiles should get converted first to 1.54.5 structure and after that then to 1.55.3 structure.
Great to know what happened.
My DD1 is 3 weeks old, so no problem to start with fresh installation. I was using "official" recommended settings for iracing, so no hassle to start over and try the latest profiles.
Confirmed! On my Laptop there was still 1.53 installed, as I've used this long time ago for FW installation and playing with profiles. Same issue here, but with 1.53 --> 1.54 --> 1.57 it works with at least the iRacing profiles.
BTW: Guess you've meant 1.57.3 instead 1.55?!?!
Ah, this versioning is so confusing...🙈
Yes I meant 1.57, hehe..😅
If FanaLab doesn't launch for you
Please zip this folder and forward it.
C:\Users\Windows 10\AppData\Local\Fanatec\FanaLab\settings.
Hi Maurice,
Thanks for your response. I upgraded from 1.52, so I believe there is the problem! Seems people upgrading from older versions need to delete the profiles (after backing up). I understand the need to retain and convert profiles during an upgrade of course, but in this instance users could always open the backed up profiles via notepad or similar and replicate the profile in the new version if really necessary. Alternatively, if a hotfix comes out that could cope with converting the older profiles that would sort the issue for all.
Glad to hear the issue is getting understood 😉
All the best,
Gray
Thank you Graham,
This worked for me, but I needed to go one step further.
"I found a folder c:/users/[username]/appdata/local/Fanatec (not PodiumControl). In there I found my old profiles, deleted the folder (after backing up just encase) and Fanalab started first time!
Thanks for the help!
You're welcome Ryan,
I'm glad you got it working.
In fairness to Fanatec, its so difficult to cater for an almost unlimited number of PC specifications and combination of wheels/bases/pedals out there. Then, we all have different software installed! So, not an easy job. Personally I think they do a good job of pre-testing their drivers and software- much better than Microsoft!!
Enjoy your racing
Gray
Issue resolved by updating firmware!
Actually this brings up a good point. What are your in game settings Maurice?
Explained in the readme Text files
We've found the cause of the crash now, its profiles from 1.54 and older which 1.57 tries to convert and fail. If everything goes right we have an update for the weekend with some further improvements to other known issues.
Thanks for the help of everyone with trying different things and providing log files.
Do you have 4k resolution?
Thanks Graham, this worked for me too
I have 1440p and also have this glitches since forever on fanalab, now I've got them on the new UI too...
nope. Triples 1440p
Yes, 1440p triples.. what could be happenig...
Worked for me as well. Thank you to all!
That's no problem Marcel,
We're here to learn, and to help when we can. That's what a community is about, right?
Regards,
Gray
Maurice any chance of whipping up a quick profile for the Formula Vee's please?
1440p tripples like the others or single?
Do you maybe have overclocked systems and give it a try if the UI glitches go away without OC.
Do you have SImHub installed?
Had the same issue with the previous version of Fanalab (1.54) and 1440p triples as well, as soon as I've installed SimHub (don't know the version). Only way to access Fanalab fully and with an correct rendering was minimizing it to the task bar and re-open it, then it was all there as desired.
With the latest versions of Fanalab, SimHub and Nvidia driver it didn't occured so far....