Of course everyone has the right to report issues but nobody should complain about issues which were not found because someone didnt helped to test, especially when it comes down to a RC driver which is the very last step before it's going official and where testing from as many people as possible is much appreciated to maybe indeed find an issue which should not be in a stable driver.
Some discrepancy I noticed - in ChangeLog.txt for 399 and 400 firmware version for Podium BME is v16. I have not tried 400, but have tried 399 and there the actual firmware version shown in drivers (update tab) after flash is 17.
Sorry I probably missed that thread. Did you mean keeping everything else on the latest firmware but only leaving WQR on the older version? I did re-flash everything back to 381 and (obviously) it worked...
I really don't agree with this. The right of any user to comment, negatively or positively on any future full release is not dependent on being a beta tester - nor should it be. Purely academic in any case as there has not been a full release since - forever. Even with the help of scores of beta testers long standing issues like jolts aren't even seeing attempted fixes making it into beta releases - never mind being resolved in release version.
Sorry if this question was answered before - the latest firmware manager doesn't seem to offer the option to flash the WQR firmware? (anyway i used 381 to flash the WQR but curious why the new fw manager doesn't have the option...)
You can only flash the WQR automatically through the green Update button (if a new WQR FW is available which is VERY rarely the case), not manually anymore.
Exactly, I also used V381 to reflash. It would be interesting IMO to have the ability to reflash current Firmware in V400, what do you think?
Regarding my case, I did not test again this evening, but will keep the forum posted in case this technique is still working. I think this can help many users experiencing this issue.
new 400 drivers arent working hangs on this screen and wheel shuts off before updating . i got to update the wheelbase and motor firmware but not even sure if it worked or not because it had the please wait screen after i was done and it was hung up there. cant update podium hub or the button module
The issue could not get seen elsewhere yet in that form with the message but I'm also missing some information, please list your complete setup like described on the first page how to report issues.
Come on now, lets get facts straight - Fanatec list for a long time two drivers for every wheelbase - a release version and a test version. This is currently release 346 and test version 381. This is for DD and belt drive.
Regarding the jolts, your speculation that I believe Fanatec does not want to solve the jolt issue is nonsense. I have never suggested such a thing - because the thought has never entered my head. All I have said on the matter is that they remain unresolved and I have seen no official information regarding them being addressed; only some cryptic comments by testers that suggest that to fix them is of a level of complexity similar to putting a man on the moon! I am disappointed that the outcome of this is that many screens that were described as useful features still remain unusable. I would have thought that this merited an official statement. It does not suggest that there is a lack of willingness. But I remain more interested than results than willingness.
Fanatec list two stable release drivers since 2 months. Stable driver 381 and stable driver 346. Both are fully official and stable non-beta and non-test drivers.
Comments
Yeah that's actually true :)
Still bugs and issues can occure on released or "official" software. I don't see the problem here.
Atleast you can rely on the people who aree actuallyy interested in the newest improvements and have no problems with minor bugs or issues.
Yeah no problem, RC on a driver is always a good sign it will eventually be an official one.
Of course everyone has the right to report issues but nobody should complain about issues which were not found because someone didnt helped to test, especially when it comes down to a RC driver which is the very last step before it's going official and where testing from as many people as possible is much appreciated to maybe indeed find an issue which should not be in a stable driver.
Did you try to reflash the WQR on an older driver like David did? Seems like it solved a similar problem he had.
Some discrepancy I noticed - in ChangeLog.txt for 399 and 400 firmware version for Podium BME is v16. I have not tried 400, but have tried 399 and there the actual firmware version shown in drivers (update tab) after flash is 17.
Sorry I probably missed that thread. Did you mean keeping everything else on the latest firmware but only leaving WQR on the older version? I did re-flash everything back to 381 and (obviously) it worked...
Ah thats indeed a typo in the txt file^^ Should be v17 for BME and v32 for McLaren v1 (which is also wrongly listed as v31).
I see the exchange now. I'll reflash all the firmware again with 400 and see if it helps. Thanks.
I really don't agree with this. The right of any user to comment, negatively or positively on any future full release is not dependent on being a beta tester - nor should it be. Purely academic in any case as there has not been a full release since - forever. Even with the help of scores of beta testers long standing issues like jolts aren't even seeing attempted fixes making it into beta releases - never mind being resolved in release version.
The latest full release is driver 381 which is only 2 months old ;)
"Even with the help of scores of beta testers long standing issues like jolts aren't even seeing attempted fixes"
You are very good at assumptions it seems.
And Maurice is right, the latest full releasee driver is 381, and this one isn't old at all.
Sorry if this question was answered before - the latest firmware manager doesn't seem to offer the option to flash the WQR firmware? (anyway i used 381 to flash the WQR but curious why the new fw manager doesn't have the option...)
dd1, wheel formula v2,
like 399 drivers, does not open firmware manager, i use windows 10 64
You can only flash the WQR automatically through the green Update button (if a new WQR FW is available which is VERY rarely the case), not manually anymore.
You get a error message or you click on the "Open Firmware Update Assistant" Button and nothing happens?
Got it. Thanks.
Exactly, I also used V381 to reflash. It would be interesting IMO to have the ability to reflash current Firmware in V400, what do you think?
Regarding my case, I did not test again this evening, but will keep the forum posted in case this technique is still working. I think this can help many users experiencing this issue.
A nice addition would be to have different colored lighting in the OLED screen for each mode(pc, V2.5, xbox).
This way the screen will change color when you switch modes and confusions will be avoided.
With the tiny letters currently displaying the selected mode you could easily forget switching to the correct mode before launching a game.
And this will mess up your in-game settings and you will have to re-tune them.
Not a big deal but Fanatec can consider including this change in an upcoming release if it is technically possible.
You mean release candidate 381 available in the beta forum, the one with the year old jolt issue unresolved? Or a different version. 😂
new 400 drivers arent working hangs on this screen and wheel shuts off before updating . i got to update the wheelbase and motor firmware but not even sure if it worked or not because it had the please wait screen after i was done and it was hung up there. cant update podium hub or the button module
Another 30 min session, No Shuts Down, No freezes.
Only problem is when I turn on the WB, the wheel does not boot up. I need to unplug and plug the wheel again.
But yeah besides reflashing the WQR, I also plugged the usb cable to the back panel (Motherboard IO) instead of on the port of the front of my case.
Everything is working flawlessly on games for the moment.
Hello Maurice. I have a question. but after the upgrade to the new driver ...
what is the best feeling ... with motor sensor calibration or without motor calibration ?
thank you for answer
The new driver/firmware combo feels horrible on my CSL Elite V1.1.
The ffb feels weak and undefined and i can't fix it. I reinstalled the driver and firmware multiple times with the same horrible result.
Switched back to 381/V680 and everything is working as intended.
Im not Maurice, but imo it's still without ACV, because there was no new update for it yet.
Which is the official driver since it was released under "Downloads" for EVERY product on the webshop.
You know, there aren't only DD owners here and the new driver brought great improvements and fixes for CSW and CSL bases ;)
I get the feeling you seriously think Fanatec doesn't want to solve the jolts.
The issue could not get seen elsewhere yet in that form with the message but I'm also missing some information, please list your complete setup like described on the first page how to report issues.
Come on now, lets get facts straight - Fanatec list for a long time two drivers for every wheelbase - a release version and a test version. This is currently release 346 and test version 381. This is for DD and belt drive.
Regarding the jolts, your speculation that I believe Fanatec does not want to solve the jolt issue is nonsense. I have never suggested such a thing - because the thought has never entered my head. All I have said on the matter is that they remain unresolved and I have seen no official information regarding them being addressed; only some cryptic comments by testers that suggest that to fix them is of a level of complexity similar to putting a man on the moon! I am disappointed that the outcome of this is that many screens that were described as useful features still remain unusable. I would have thought that this merited an official statement. It does not suggest that there is a lack of willingness. But I remain more interested than results than willingness.
Fanatec list two stable release drivers since 2 months. Stable driver 381 and stable driver 346. Both are fully official and stable non-beta and non-test drivers.
It will only show the option if there is a reason to update.