This issue started with the latest BME firmware update and it only happens when I first open the ITM screen. The current speed does NOT display until I scroll to the second ITM panel. Then I must scroll forward through all the panels back to legacy mode and then to the first ITM screen again for current speed to be displayed. If I try to scroll backwards to the first panel, current speed is not displayed even though it is displaying on all the other ITM panels.
I have not tried going back to previous driver/firmware.
Thank you for sharing! I tested for a bit today and so far looks promising. I will also test this further over time and report back if the problem continues, but this could be a good workaround for now.
We'll take a look, I'm not sure why the game sending rev LED commands should make it lag/drop fps with a new driver but not an older one as the base is just listening to the commands the game sends. But we'll have a look to find out more.
What are your PC specs? Then we try to test with a similar PC
What was the previous driver/firmware version it worked fine with?
Regarding the FFB it seems nothing wrong, the base does was the game asks it to do and in real life driving on/off track and so on would als create some amount of force in the wheel and car.
I hear some of the bottons on the wheel rattle, do you mean this noise?
Or do you think the QR has play? In this case, is it tightened completely? If the QR is making noises because of play -> contact support.
A game might apply a special FFB preset int their controls settings for the base, but this is not too common I would say. If in this case COMP is used, the FFB might be a bit different because the preset of the game for the ClubSport V2.5 might be different from the CSL DD preset. I don't think the difference would be dramatic but if you want to be sure you can give PC mode a try in each game and find out yourself.
Another thing is Auto Setup, it offers games to change FFB settings on the base side while the user has chosen Auto Setup in the tuning menu. Race Room is from today on the only game to support it and will change to recommended settings on game start, so here indeed now I would suggest to use PC mode in case you want to give this function a try.
I fully agree that this should not happen, the issue has high priority, we've already found a fix which works on our end. I've posted the firmware a comment above. We are currently doing some tests to make sure its fixing it all the time and is also not creating a new issue before it will get merged for the next firmware release.
Is this test firmware something that’s included in the official 4.36? Or put differently, if I use the Podium F1 on PS5, will I run into any issues with 4.36 without the file you linked?
I just installed 4.36 and tested briefly on PC without issues (coming from 4.34 which worked perfectly on PC and PS5 for me).
As described by Marcel it's a Test Export Firmware NOT included in any driver yet. After Feedback from the Community if the freezing issue on PS is fixed it will get merged into the Main Branch of the firmware and then it will be included into the driver in the future.
Comments
how?
since Maurice Böschen told to turn off my ITM mine base has been running flawless
hope this can somehow help you
DD2, Podium Hub, Fanalab 1.61.3
This issue started with the latest BME firmware update and it only happens when I first open the ITM screen. The current speed does NOT display until I scroll to the second ITM panel. Then I must scroll forward through all the panels back to legacy mode and then to the first ITM screen again for current speed to be displayed. If I try to scroll backwards to the first panel, current speed is not displayed even though it is displaying on all the other ITM panels.
I have not tried going back to previous driver/firmware.
Thank you for sharing! I tested for a bit today and so far looks promising. I will also test this further over time and report back if the problem continues, but this could be a good workaround for now.
Yep I have it turned off as I am in VR exclusively. Thanks!
I have a firmware which should solve the issue, let me know if it works for you.
Try if it happens as well with an older driver and version which previously worked for you.
If it still happens -> contact support
If it doesn't happen anymore with old firmware -> let me know then we have to look into a possible firmware issue
If the wheel is properly attached, but not recognized you should contact support.
Are other wheels working fine if you have available?
Are the QR pins all there?
Does it make a difference when you wiggle the wheel while attached, indicating a loose contact?
Thanks, we've also recognized that the test export provided is not optimal and not a proper solution. Currently further looking into both issues.
Thanks, it is definitely a software issue we have to fix in the firmware.
We'll take a look, I'm not sure why the game sending rev LED commands should make it lag/drop fps with a new driver but not an older one as the base is just listening to the commands the game sends. But we'll have a look to find out more.
What are your PC specs? Then we try to test with a similar PC
What was the previous driver/firmware version it worked fine with?
Regarding the FFB it seems nothing wrong, the base does was the game asks it to do and in real life driving on/off track and so on would als create some amount of force in the wheel and car.
I hear some of the bottons on the wheel rattle, do you mean this noise?
Or do you think the QR has play? In this case, is it tightened completely? If the QR is making noises because of play -> contact support.
A game might apply a special FFB preset int their controls settings for the base, but this is not too common I would say. If in this case COMP is used, the FFB might be a bit different because the preset of the game for the ClubSport V2.5 might be different from the CSL DD preset. I don't think the difference would be dramatic but if you want to be sure you can give PC mode a try in each game and find out yourself.
Another thing is Auto Setup, it offers games to change FFB settings on the base side while the user has chosen Auto Setup in the tuning menu. Race Room is from today on the only game to support it and will change to recommended settings on game start, so here indeed now I would suggest to use PC mode in case you want to give this function a try.
If ITM seems to cause BME freezes, is it maybe happening in specific situations which are affecting whats shown on ITM?
Is it happening on a specific page?
Is it for example when there is a new best lap time, a position change, lap change, fuel change or else?
Please try this test firmware, it should fix the issue on PlayStation
actually you can apply for a job as a full time tester if you consider to move to our location in Landshut, Germany 😉
Home EN - Endor AG - Jobs & Karriere
I fully agree that this should not happen, the issue has high priority, we've already found a fix which works on our end. I've posted the firmware a comment above. We are currently doing some tests to make sure its fixing it all the time and is also not creating a new issue before it will get merged for the next firmware release.
Thank You Marcel, will do it arriving at home tonight...
So i just need to update the DD base firmware with this .hex file?
No need of unninstal or install drivers?
Can i install this .hex over the 434 driver/firmwares?
Use driver 436 (which is now official btw) and manually update the base firmware as described by Marcel with this TestExport hex file.
Thank you!!! Will do it today
Installed Driver 436 today - [edit] correction, anything is fine!
Have done some testing. Weird changes of ffb & ffb intact when pausing/sinishing race - gone.
Unfortunately, now jolts/clanks are there much more often. Like, 2-4 times per 3min rally stages in dr2.0.
My profile for dr2 (also FWs)
Also turning the wheel now feels very grainy. To the extent that I hear the noise/vibrations going through the righ when wiggle the wheel.
p.s. DD2 here
p.p.s. No fanalabs installed or itm enabled. No bases display mode touched.
Wow didn't expect that😮
Is this test firmware something that’s included in the official 4.36? Or put differently, if I use the Podium F1 on PS5, will I run into any issues with 4.36 without the file you linked?
I just installed 4.36 and tested briefly on PC without issues (coming from 4.34 which worked perfectly on PC and PS5 for me).
Thank you
As described by Marcel it's a Test Export Firmware NOT included in any driver yet. After Feedback from the Community if the freezing issue on PS is fixed it will get merged into the Main Branch of the firmware and then it will be included into the driver in the future.
Sorry for late reply.
Working fine in games just no show in the UI.
Working in 434 but not in 435 or 436 so 435 broke it ( just tested all 3 )
Sorry - erledigt.
New driver 437 available
Same firmware as before, but separate firmware for CSL DD available below to solve shifter calibration issue
Control Panel
Download
CSL DD firmware to solve shifter calibration issue
I've also uploaded a new FanaLab version here
https://forum.fanatec.com/discussion/25033/fanalab-1-62-3-download-post-your-feedback-here/p1
marcel yesterday I get late at home and didnt do the procedure in the podium wheel.
Will be okay to put the hex file for the podium freeze problem with this 437 driver???
Hi Marcel 😊
Did You get any time frame from devs?
yes
They told me its too hard to estimate at the moment