Please upload ypour Logs, otherwise it is hard to investigate.
Also please list what Base and wheel you use.
I just tried ACC with the CSP V3 connected via USB and the vibration works fine with FanaLab 2.01.18 for me...
EDIT: Ok, got the issue reproduced. Let me guess, you do not have a Fanatec Base? Because when I power-off my Base and only use the CSP v3 on its own then I can indeed reproduce the issue. Vibrations only work when a Fanatec Base is detected.
Hi there, any news regarding adding EA WRC 23 to Fanalab?A new update came recently in the game. I would like to changes my revs colours for my CSL Steering Wheel P1 V2. Thanks
(Limited) support for EA WRC is currently in development.
However, even the recent game updates did not changed anything regarding the lack of the basic functionality to disable the native LED and Display support from the game so you will not be able to change the LEDs or Display through FanaLab. In fact, the Display setting will be completely disabled in the Lab and the LEDs need to be disabled manually by the user to not interfere with the native support.
So your plan to change the revs colours for your CSL Steering Wheel P1 V2 wont work, you will still be limited to what the game uses for the revs colours and the Display.
No, he doesn't have a Fanatec Base any that is exactly the scenario where the issue happens, so when someone only has Fanatec USB Pedals but no Fanatec Base, then the vibrations are not working.
Hey so i just notice i been using my CSL DD 8nm since last monday and didnt know it was a thing as fanalab lol been using the control panel so my guestion is im on PC driver: 454 and 2.00.09 in fanalab is that correct? sorry if dumb guestion but im new to all this
Thanks so i did update and now i opened Controlpanel and got this should i update it or not? sorry if im asking dumb guestions but im new to this and i dont really wanna mess anything up
Driver update and firmware update (although included in the driver) are two different things. Installing 455 only updated the driver and related software like Fanatec control panel. If a driver includes a newer firmware it does not push it to the hardware (base, wheel, pedals etc) without user intervention so you need to do it yourself. Updating software is safe. Updating firmware is potentially risky if you do not follow the rules.
Today just installed older Fanalab 1.69.7, and after hours of playing, no freeze. So now testing this for days if i got freeze or not. I will let you know if there is any change.
I get the profiles to work in iracing and for acc, but it's completely impossible to get them to load automatically in AMS2, I think I've tried everything. Anyone had a similar problem and solved it?
Try 2.01.19 and RC driver 455 and then adjust the LED values to match the in-game ones.
If its still not working, then please upload Logs and Screenshots of your settings, best also a video of the flashing LEDs as the dev has fixed the issue on his end and could not reproduce any further issue with the Wheel Base LEDs anymore.
Thx, I was able to reproduce the issue and it is because of a wrong APM attribute in the pws file which the old FanaLab v2.01.18 has written into the pws when saving the profile.
The issue, that this wrong attribute gets written into the pws, was fixed with v2.01.19, but unfortunately that means that old profiles, which were saved with 2.01.18, need to be manually changed as there is no way for a converter to know which wheels was attached to the base when the profile was originally created.
To do that, open the pws file which lets the Lab crash (so basically every profile which you might have saved in the past days with FanaLab v2.01.18) and then change the APM="0" attribute to either APM="True" or APM="False" depending on if you use a APM or not (or if your wheel has Clutch Paddles like the McLaren GT3 or BMW M4 GT3 as the APM="True" attribute is also valid for the Clutch-Paddle-only-wheels). All my profiles always use the "True" attribute as all my profiles are saved with either Formula v2 + APM or P Hub + APM so always with Clutch Paddles where the "True" attribute applies.
So just change the "0" to "True" or "False" and it wont crash anymore.
Sorry for the inconvenience this might cause but as explained it is not possible for a converter to fix this "correctly" ...
Comments
Yes. Installed today.
2.01.18
I've returned to 1.69 and works again.
I don't have iracing or F1-23 to try.
It Could be a ACC problem?
Please upload ypour Logs, otherwise it is hard to investigate.
Also please list what Base and wheel you use.
I just tried ACC with the CSP V3 connected via USB and the vibration works fine with FanaLab 2.01.18 for me...
EDIT: Ok, got the issue reproduced. Let me guess, you do not have a Fanatec Base? Because when I power-off my Base and only use the CSP v3 on its own then I can indeed reproduce the issue. Vibrations only work when a Fanatec Base is detected.
Forwarded to the dev for a hotfix next week!
Hi there, any news regarding adding EA WRC 23 to Fanalab?A new update came recently in the game. I would like to changes my revs colours for my CSL Steering Wheel P1 V2. Thanks
(Limited) support for EA WRC is currently in development.
However, even the recent game updates did not changed anything regarding the lack of the basic functionality to disable the native LED and Display support from the game so you will not be able to change the LEDs or Display through FanaLab. In fact, the Display setting will be completely disabled in the Lab and the LEDs need to be disabled manually by the user to not interfere with the native support.
So your plan to change the revs colours for your CSL Steering Wheel P1 V2 wont work, you will still be limited to what the game uses for the revs colours and the Display.
Yes. I not have a Fanatec base with Fanatec V3 pedals.
Every item on their USB connection.
Thanks !!
But you have a Fanatec base? If so you should connect your pedals to it, it's better than USB
No, he doesn't have a Fanatec Base any that is exactly the scenario where the issue happens, so when someone only has Fanatec USB Pedals but no Fanatec Base, then the vibrations are not working.
The last message from him, what I understood is that he has it, but he plugs everything to USB...
I understood the issue, but my answer was based on his last post.
"Yes. I not have a Fanatec base"
I understood this sentence that he does not have any Fanatec Base.
Because without a Fanatec Base I can reproduce the issue. However, with a Fanatec Base (and pedals connected via USB) I can not reproduce the issue.
Hey so i just notice i been using my CSL DD 8nm since last monday and didnt know it was a thing as fanalab lol been using the control panel so my guestion is im on PC driver: 454 and 2.00.09 in fanalab is that correct? sorry if dumb guestion but im new to all this
No, that is not correct.
You should use driver 455 (much more stable than 454) and latest FanaLab version is 2.01.18, which is also better than 2.00.09.....
okey where do i find driver 455?
It is linked in the first post of this thread.
https://forum.fanatec.com/discussion/29180/fanatec-driver-455-beta-for-csl-cs-and-podium-all-wheels/p1
Thanks so i did update and now i opened Controlpanel and got this should i update it or not? sorry if im asking dumb guestions but im new to this and i dont really wanna mess anything up
Yes, it tells you that your firmware is outdated so yes, it tells you you should update
Okey yea thanks was unsured when i updated to 455! Appriacte the fast answers!
That behaviour that after a while of use, the LEDs would freeze as well as the screen.
That was under investigation as to whether it was a SW or HW problem.
Yesterday I drove more than two hours and it did not happen.
Yeah it was under investigation and could not be reproduced.
So no change in this version, apparently its either way more a hardware or firmware issue but not a FanaLab issue.
But for now the investigations are on hold due to the fact that nobody internally has the issue, so it can not be investigated.
Driver update and firmware update (although included in the driver) are two different things. Installing 455 only updated the driver and related software like Fanatec control panel. If a driver includes a newer firmware it does not push it to the hardware (base, wheel, pedals etc) without user intervention so you need to do it yourself. Updating software is safe. Updating firmware is potentially risky if you do not follow the rules.
Today just installed older Fanalab 1.69.7, and after hours of playing, no freeze. So now testing this for days if i got freeze or not. I will let you know if there is any change.
Hello!
I get the profiles to work in iracing and for acc, but it's completely impossible to get them to load automatically in AMS2, I think I've tried everything. Anyone had a similar problem and solved it?
FanaLab 2.01.19 available
FanaLab 2.01.19 available
YEAH !!
Tested & Confirmed. THANKS !!!!!
All the profiles I have made the last few days close FanaLab when I try to load them.
Please upload Logs and also the profiles which let the Lab crash.
I downloaded 2.01.18 and the beta drivers, but my base lights still flash blue, is there something I'm missing here?
Try 2.01.19 and RC driver 455 and then adjust the LED values to match the in-game ones.
If its still not working, then please upload Logs and Screenshots of your settings, best also a video of the flashing LEDs as the dev has fixed the issue on his end and could not reproduce any further issue with the Wheel Base LEDs anymore.
Which Wheel is that?! Damn... o.O
Thx, I was able to reproduce the issue and it is because of a wrong APM attribute in the pws file which the old FanaLab v2.01.18 has written into the pws when saving the profile.
The issue, that this wrong attribute gets written into the pws, was fixed with v2.01.19, but unfortunately that means that old profiles, which were saved with 2.01.18, need to be manually changed as there is no way for a converter to know which wheels was attached to the base when the profile was originally created.
To do that, open the pws file which lets the Lab crash (so basically every profile which you might have saved in the past days with FanaLab v2.01.18) and then change the APM="0" attribute to either APM="True" or APM="False" depending on if you use a APM or not (or if your wheel has Clutch Paddles like the McLaren GT3 or BMW M4 GT3 as the APM="True" attribute is also valid for the Clutch-Paddle-only-wheels). All my profiles always use the "True" attribute as all my profiles are saved with either Formula v2 + APM or P Hub + APM so always with Clutch Paddles where the "True" attribute applies.
So just change the "0" to "True" or "False" and it wont crash anymore.
Sorry for the inconvenience this might cause but as explained it is not possible for a converter to fix this "correctly" ...
That is a Cube Controls GT Zero Rubber rim.
But today they launched a new Leather version which I think looks even more stunning 🤩
(unfortunately its also double the price of the rubber version though)... 🙈
Thats definitely some kind of rim style which Fanatec also needs as it fits the BMR absolutely perfect!