you can try but it sounds like a different issue than discussed here if your LEDs are also affected. Is the QR still inserted well and the clamp tight? Because it might be a brief disconnect of the complete wheel if all functions of it are affected at once.
i already had a look at the QR and clamp as i thought i might be more of an hardware than a software issue but it doesn´t explain the not being able to upshift on the straight aswell. I bought the wheel back in April and due to the QR1 shortage it arrived in May. Should i do an RMA rather than trying to change the firmware? I have to say everything worked fine till the update. I´ve been training Watkins for some time now and i had no issues before!
I have observed that with the Formula 2.5X wheel, the miss shift issue occurs much more frequently compared to the BMW GT2 V1 wheel, where it was less common. I also experience this problem less often with the ClubSport Universal Hub V2.
Reporting similar issue here since I updated to 462. Was on 455 before. My setup is:
CSL DD 8Nm
Formula V2.5 with APM module
QR2 connection (don't think it's going to make much of a difference, but just in case)
CSL Elite V2 (connected to wheelbase)
The wheelbase is connected directly to one of the USB headers on my desktop, no passthrough or hubs.
From time to time, up and downshifts just stop registering all of a sudden for a short period of time, up to 5 seconds, and afterwards, they start working again. I have not been able to determine any specific trigger as to why it happens, but it happens on at least two games (iRacing and F1 24).
RMA makes sense in case you can't get it to work well with any firmware. So if you already tried multiple drivers and also each time updated the firmware, then it makes sense to open an RMA because it might be a hardware issue.
EDIT: I see you were successful by using driver 455, then it's best to stay there for now and not open an RMA. We have the issue with critical priority in our system and I'm pushing regularly with updated information from here.
When I check the other steering wheel(mclaren gt3 v2, ps dd1 formula wheel, bmw m4 gt3) without fanalab, I can not see the miss up shifting issue.
To define the problem accurately,
1. with Fanalab
This issue occurs All my steering wheel. However, issues occur more frequently with Bentley wheels.
2. without Fanalab
This issue occurs only with Bentley wheels. I have not observed this issue with other wheels.
I conducted reproduction tests over several days, so I believe the results are reliable. Furthermore, as this issue seems to be affecting other users as well, I think it should not be difficult to reproduce. Of course, I understand that debugging can be challenging if the issue cannot be reproduced directly by the dev team.
One peculiar aspect is that the issue differs depending on whether Fanalab is running or not. Initially, I assumed it was purely a firmware problem, as reverting the wheelbase firmware to a previous version resolved the issue. However, the fact that the problem also varies with Fanalab's operation makes it difficult to pinpoint the exact cause. (That said, I believe defining and debugging the problem is the responsibility of the dev team.) It may be worth checking whether the issue lies in the control interface between the wheel and the base, or in the interface between the base and the PC.
Lastly, it is unfortunate that this issue occurs more frequently with the newly released (and expensive) wheels.
Comments
you can try but it sounds like a different issue than discussed here if your LEDs are also affected. Is the QR still inserted well and the clamp tight? Because it might be a brief disconnect of the complete wheel if all functions of it are affected at once.
Hello Manuel,
i already had a look at the QR and clamp as i thought i might be more of an hardware than a software issue but it doesn´t explain the not being able to upshift on the straight aswell. I bought the wheel back in April and due to the QR1 shortage it arrived in May. Should i do an RMA rather than trying to change the firmware? I have to say everything worked fine till the update. I´ve been training Watkins for some time now and i had no issues before!
I have observed that with the Formula 2.5X wheel, the miss shift issue occurs much more frequently compared to the BMW GT2 V1 wheel, where it was less common. I also experience this problem less often with the ClubSport Universal Hub V2.
Follow up post
I deleted driver 462 and installed 455. No more shifting or rev light issues with the Formula V2.5
Reporting similar issue here since I updated to 462. Was on 455 before. My setup is:
The wheelbase is connected directly to one of the USB headers on my desktop, no passthrough or hubs.
From time to time, up and downshifts just stop registering all of a sudden for a short period of time, up to 5 seconds, and afterwards, they start working again. I have not been able to determine any specific trigger as to why it happens, but it happens on at least two games (iRacing and F1 24).
its a stupid bug, because even developer would have hard time for figure out what cause it exactly.
but because it not happen constantly, it may have something todo with timers.
RMA makes sense in case you can't get it to work well with any firmware. So if you already tried multiple drivers and also each time updated the firmware, then it makes sense to open an RMA because it might be a hardware issue.
EDIT: I see you were successful by using driver 455, then it's best to stay there for now and not open an RMA. We have the issue with critical priority in our system and I'm pushing regularly with updated information from here.
it's probaply not helps at all but
when i reinstalled everything in 9 November the 462, in the first day i not saw a single miss shift when i play the ACC
we are maybe up to something in here about miss shift. not tested yet
https://forum.fanatec.com/discussion/31916/need-help-with-shifting-problem-v2-5x#latest
When I check the other steering wheel(mclaren gt3 v2, ps dd1 formula wheel, bmw m4 gt3) without fanalab, I can not see the miss up shifting issue.
To define the problem accurately,
1. with Fanalab
2. without Fanalab
I conducted reproduction tests over several days, so I believe the results are reliable. Furthermore, as this issue seems to be affecting other users as well, I think it should not be difficult to reproduce. Of course, I understand that debugging can be challenging if the issue cannot be reproduced directly by the dev team.
One peculiar aspect is that the issue differs depending on whether Fanalab is running or not. Initially, I assumed it was purely a firmware problem, as reverting the wheelbase firmware to a previous version resolved the issue. However, the fact that the problem also varies with Fanalab's operation makes it difficult to pinpoint the exact cause. (That said, I believe defining and debugging the problem is the responsibility of the dev team.) It may be worth checking whether the issue lies in the control interface between the wheel and the base, or in the interface between the base and the PC.
Lastly, it is unfortunate that this issue occurs more frequently with the newly released (and expensive) wheels.