Does this version of Fanalab is compatible with 455 or only 462? I wait until the driver/firmware in 462 will published as stable, as I don't have any issues with 455 on my CSDD, but I'd like to upgrade FanaLab if it's possible.
Two weeks ago I wrote to you that Fanalab simply crashed after 10-20 minutes of F1 23. This has never happened to me before in years. The button assignment still works, but the ITM data can no longer be seen on the display of the base and the steering wheel.
The current update FanaLab 2.01.54 has not solved the problem.
The driver does not allow the computer to sleep. Windows 11 24h2 has just been freshly installed. Windows 23h2 had the same problems. When you close fanalab, the function recovers with sleep.
This was investigated some time ago but could not get reproduced. I just tried this myself once again and the PC goes into Sleep Mode just fine with the Lab running. So it is not a general FanaLab issue but more a special setting in your Windows installation (like power saving options etc) which causes this issue.
There are currently no plans to investigate this again.
Yes, it is a problem only for some. But it exists. I installed windows a couple of hours ago. Therefore, I can no longer understand where to look for an answer.
Ok. As I said, we wont investigate this issue atm as it is not reproducible and therefore not a general FanaLab issue but more some Windows setting issue.
I suggest you do some trial and error testing. Leave only one USB device connected and put the PC to sleep. If it stays asleep wake it up, connect another device and repeat. Eventually you will find the one that wakes up the PC. But likely it's a windows 11 thing. I used to have W10, and my simrig could stay connected with the PC in sleep. Once upgrading to W11 it started waking up. Since the upgrade coincided with fanatec driver update I thought it was a fanatec driver issue. Turned out out the third party handbrake started waking the PC up for reasons unknown. It was not generating any input and the option to "allow this device to wake up the PC" in the power savings settings was disabled. Go figure. I had to learn to unplug the handbrake before putting the PC to sleep. After upgrading to fanatec handbrake I do not have any wake up issues.
I've had this issue for a while now, at least on FanaLab 2.01.45. In my case it has to do with the Moza Handbrake. When I have it connected, if FanaLab or Discord is running, the PC doesn't idle and won't go to sleep. If I disconnect the handbrake, it sleeps as normal.
I'd suggest you to disconnect all USB devices and check again if Windows go to sleep, whether it's a similar issue on your end.
What I've done to get around this, is to use a script to start/stop FanaLab and Discord when needed only.
Thanks a lot for the suggestion. It helped me a lot. All the problems arose with the TCA Sidestick X Airbus Edition connected to the usb port, which prevented the computer from going into sleep mode. It's just not clear why the TCA Sidestick X Airbus Edition is somehow tied to the Fanalab drivers. Because when Fanalab is turned off with the TCA Sidestick X Airbus Edition connected to the usb port, the sleep mode works for the computer. As soon as I turn on Fanalab, computer sleep mode no longer works. Either way, it's a win. I am very grateful for the suggestion.
there are this thing like power off sleep times and so on, you may need check this TCA Sidestick X Airbus Edition. and look if it have proper settings for this
fanatec cant be babysitter for the third party company's if they make issues
Sleep mode is allowed for the device by default. When FanaLab is turned off, computer sleep mode works. When unplugging the TCA Sidestick Airbus Edition from usb with FanaLab on, the sleep mode also works. If both are turned on, it does not work. However, there are conflicts between them.
im guessing what happens is that fanalab is searching the own device what is active and what is not, if third party hardware have this wake the computer turned on, and then it not allows go sleep mode
It doesn't help. I have tried before. Maybe there is something else I don't know. But at the moment I am happy with the result. Airbus usb is easier for me to debug. I use it a lot less often since I started simracing. Thanks for the tips.
I'm glad it helped. Too bad that turning all the power saving options off did not work. It happens that I also have the exact same joystick and my PC sleeps well with it connected and Fanalab running, no matter if the base it connected and turned on, connected and turned off or not connected at all. Power savings are finicky to say the least. Different mother boards may behave differently, each user might have different power setting in EUFI and Windows.
Hi. Is work being done to resolve the BMW M4 GT3 light issue and the Rally Button Module screen issue (like wacky numbers instead of gear shifts)? Thanks in advance.
I can see cars have been bound to a profile but can't tell what cars they are. Where can I see which cars are bound a profile? I suppose if I knew this I would also like the ability to unbound a car to a profile as well. Thanks - Stuart
Okay, I've made some progress in figuring-out which cars are bound to a profile. I have 2 profiles with cars bound to them, as evidenced by the small car icon to the left of the profile:
Recommended FFB Settings - CSL DD (rf2)
_My Radical SR3 Profile
I bound 2 cars to my "_My Radical SR3 Profile" and can see those 2 cars bound in the rfactor2 car list as evidenced by the small icon to the left of the car name, indicating it is bound. However, when I load the "Recommended FFS Settings - CSL DD (rf2)" profile, the factor2 car list shows no cars bound to this profile.
Also, when I attempt to bind the car, "1960 Indy Roadster - Lee Sutton" car to "_My Radical SR3 Profile", I get a warning that the car is already assigned to a profile and do I wish to change it. However, neither of the 2 profiles which I have cars bound to them reflect this car being bound to them. Finally, I am unable to bind any cars to the "Recommended FFS Settings - CSL DD (rf2) profile.
At this point, I believe something is corrupted and am inclined to wipe everything clean and start over again. Any suggestions?
You can not bind cars to the recommended profile. Well, you can, but this intentionally does not work as it makes no sense. Recommended profile is meant for a general favorite (aka general) loading, not for CDALP loading. For CDALP loading you should create your own profiles, not the recommended profile. You can load the recommended profile, save it with a different name, and then bind cars to that new profile when you rely on the recommended settings.
"You can not bind cars to the recommended profile. Well, you can, but this intentionally does not work as it makes no sense"
Okay, I understand the logic now. Maybe an error message such as "You cannot bind a profile to the recommended profile" would be helpful. Also, as error message such as "You cannot create a profile called 'New Profile'. Choose a new name" That drove me nuts for a week or so until I figured it out. Also, I may still do a fresh install since I still have some cars "bound" to the recommended profile but it doesn't say which ones they are.
Comments
Does this version of Fanalab is compatible with 455 or only 462? I wait until the driver/firmware in 462 will published as stable, as I don't have any issues with 455 on my CSDD, but I'd like to upgrade FanaLab if it's possible.
Thanks!
Latest FanaLab needs at least driver v453.
Thanks Maurice, I will upgrade it then.
Two weeks ago I wrote to you that Fanalab simply crashed after 10-20 minutes of F1 23. This has never happened to me before in years. The button assignment still works, but the ITM data can no longer be seen on the display of the base and the steering wheel.
The current update FanaLab 2.01.54 has not solved the problem.
Regards
Stefan
The driver does not allow the computer to sleep. Windows 11 24h2 has just been freshly installed. Windows 23h2 had the same problems. When you close fanalab, the function recovers with sleep.
This was investigated some time ago but could not get reproduced. I just tried this myself once again and the PC goes into Sleep Mode just fine with the Lab running. So it is not a general FanaLab issue but more a special setting in your Windows installation (like power saving options etc) which causes this issue.
There are currently no plans to investigate this again.
Thanks for your reply.
Yes, it is a problem only for some. But it exists. I installed windows a couple of hours ago. Therefore, I can no longer understand where to look for an answer.
Ok. As I said, we wont investigate this issue atm as it is not reproducible and therefore not a general FanaLab issue but more some Windows setting issue.
one example what not allows pc go to sleep is when windows update is waiting
I suggest you do some trial and error testing. Leave only one USB device connected and put the PC to sleep. If it stays asleep wake it up, connect another device and repeat. Eventually you will find the one that wakes up the PC. But likely it's a windows 11 thing. I used to have W10, and my simrig could stay connected with the PC in sleep. Once upgrading to W11 it started waking up. Since the upgrade coincided with fanatec driver update I thought it was a fanatec driver issue. Turned out out the third party handbrake started waking the PC up for reasons unknown. It was not generating any input and the option to "allow this device to wake up the PC" in the power savings settings was disabled. Go figure. I had to learn to unplug the handbrake before putting the PC to sleep. After upgrading to fanatec handbrake I do not have any wake up issues.
I've had this issue for a while now, at least on FanaLab 2.01.45. In my case it has to do with the Moza Handbrake. When I have it connected, if FanaLab or Discord is running, the PC doesn't idle and won't go to sleep. If I disconnect the handbrake, it sleeps as normal.
I'd suggest you to disconnect all USB devices and check again if Windows go to sleep, whether it's a similar issue on your end.
What I've done to get around this, is to use a script to start/stop FanaLab and Discord when needed only.
You can also use the following to check whether Windows idle or not (instead of just waiting to see if Windows will sleep)
https://github.com/xaviergmail/DiscordNotificationDebug/
Thanks a lot for the suggestion. It helped me a lot. All the problems arose with the TCA Sidestick X Airbus Edition connected to the usb port, which prevented the computer from going into sleep mode. It's just not clear why the TCA Sidestick X Airbus Edition is somehow tied to the Fanalab drivers. Because when Fanalab is turned off with the TCA Sidestick X Airbus Edition connected to the usb port, the sleep mode works for the computer. As soon as I turn on Fanalab, computer sleep mode no longer works. Either way, it's a win. I am very grateful for the suggestion.
there are this thing like power off sleep times and so on, you may need check this TCA Sidestick X Airbus Edition. and look if it have proper settings for this
fanatec cant be babysitter for the third party company's if they make issues
Sleep mode is allowed for the device by default. When FanaLab is turned off, computer sleep mode works. When unplugging the TCA Sidestick Airbus Edition from usb with FanaLab on, the sleep mode also works. If both are turned on, it does not work. However, there are conflicts between them.
im guessing what happens is that fanalab is searching the own device what is active and what is not, if third party hardware have this wake the computer turned on, and then it not allows go sleep mode
that is a problem right there, you may need disable this allow the computer to turn off,
this features what have there may cause sleep time problems
Unfortunately, no changes.
you could try disable the, USB selective suspend setting,
there are so many different things what could cause this
It doesn't help. I have tried before. Maybe there is something else I don't know. But at the moment I am happy with the result. Airbus usb is easier for me to debug. I use it a lot less often since I started simracing. Thanks for the tips.
I'm glad it helped. Too bad that turning all the power saving options off did not work. It happens that I also have the exact same joystick and my PC sleeps well with it connected and Fanalab running, no matter if the base it connected and turned on, connected and turned off or not connected at all. Power savings are finicky to say the least. Different mother boards may behave differently, each user might have different power setting in EUFI and Windows.
Hi. Is work being done to resolve the BMW M4 GT3 light issue and the Rally Button Module screen issue (like wacky numbers instead of gear shifts)? Thanks in advance.
Button LED issue: no work done at all, no.
BMR OLED showing weird nonsense is internally fixed to be included in an upcoming driver update at some point in the future.
Both issues are not FanaLab related.
Thx.
I can see cars have been bound to a profile but can't tell what cars they are. Where can I see which cars are bound a profile? I suppose if I knew this I would also like the ability to unbound a car to a profile as well. Thanks - Stuart
Okay, I've made some progress in figuring-out which cars are bound to a profile. I have 2 profiles with cars bound to them, as evidenced by the small car icon to the left of the profile:
I bound 2 cars to my "_My Radical SR3 Profile" and can see those 2 cars bound in the rfactor2 car list as evidenced by the small icon to the left of the car name, indicating it is bound. However, when I load the "Recommended FFS Settings - CSL DD (rf2)" profile, the factor2 car list shows no cars bound to this profile.
Also, when I attempt to bind the car, "1960 Indy Roadster - Lee Sutton" car to "_My Radical SR3 Profile", I get a warning that the car is already assigned to a profile and do I wish to change it. However, neither of the 2 profiles which I have cars bound to them reflect this car being bound to them. Finally, I am unable to bind any cars to the "Recommended FFS Settings - CSL DD (rf2) profile.
At this point, I believe something is corrupted and am inclined to wipe everything clean and start over again. Any suggestions?
You can not bind cars to the recommended profile. Well, you can, but this intentionally does not work as it makes no sense. Recommended profile is meant for a general favorite (aka general) loading, not for CDALP loading. For CDALP loading you should create your own profiles, not the recommended profile. You can load the recommended profile, save it with a different name, and then bind cars to that new profile when you rely on the recommended settings.
"You can not bind cars to the recommended profile. Well, you can, but this intentionally does not work as it makes no sense"
Okay, I understand the logic now. Maybe an error message such as "You cannot bind a profile to the recommended profile" would be helpful. Also, as error message such as "You cannot create a profile called 'New Profile'. Choose a new name" That drove me nuts for a week or so until I figured it out. Also, I may still do a fresh install since I still have some cars "bound" to the recommended profile but it doesn't say which ones they are.
Thanks!
Best would be to delete Rhe whole xml folder in AppData as a simple reinstall wont unbind any existing cars from the profiles.
"Best would be to delete Rhe whole xml folder in AppData as a simple reinstall wont unbind any existing cars from the profiles."
Thanks! I will give that a try.