That happened to me with the upgrade to WQR v7 as I mentioned above, try disconnecting all usb devices, except the steering wheel. It worked for me (in the log logs there were conflicts with other usb devices); after esi let me update wlWQR and steering wheel
I do have quite a few usb devices (handbrake, button box, etc.). But they didn't cause any problems with the base firmware upgrade so I didn't think that they would affect the WQR upgrade. Turns out I was wrong, after unplugging them the WQR firmware upgrade went without a hitch!
Please upload the Log files from C:\Users\Public\Fanatec Logs and list all the Fanatec devices you are using, otherwise it is basically impossible to investigate as you are the first to report this kind of issue.
Also any kind of Windows Event Logs would certainly help as well, for that open Windows Event Viewer, go to Applications and select every entry with a red exclamation mark which is related to the FanatecControlPanel.exe file and upload everything here.
When i look under public user there is no fanatec logs. using csldd 5nm wheelbase clubsport v3 pedals trying to figure out how to get the window log errors uploaded
Yep, on the podium f1. It said everything updated, including the wheels, so I went in game to bind buttons and none worked. So, I went back in and saw the wheel needed an update from V47. Odd, but I attempted to update and it froze. Rebooted the dd1 and went back into the updater and it said it was updated. I've also rebooted my PC twice since 454 was installed and all the wheels were updated. I did have other USB devices plugged in, and everything else updated. I've power cycled the base probably 4 or 5 times during all that.
Marcel /Maurice Hello guys my DD2 came Today.At first it wasn't recognized at all in driver 454. I got it to work with the old driver 336, then driver 447. Then that's it. If I update from 447 to 454, the DD2 is no longer recognized. Is there a solution?
And what happens when you leave the base powered-on, uninstall the driver 447, then install driver 454 (still with the base powered-on), then restart the PC? Does the Control Panel open after the restart and showing "No Fanatec Device found" or what exactly is not working?
If thats the case then you. can look into the Windows Device Manager if there is a device with a yellow exclamation mark which is disabled. If thats the case, enable the device manually via right-click, then the Base should be recognized again by the Control Panel.
If the base is still not recognized in 454 please use the "Collect Logs" feature in the driver and upload them here.
PS: That is btw the way to go moving forward on the next driver installation: The base should always be powered-on when you install the driver. Thats the best way to ensure the USB device driver gets properly installed.
Fanatec has read your comment but with so little information it is not possible to help.
You only said "errored out twice" without explaining what this could mean...
It could mean anything, from a simple issue where the installer fails or an issue that the base is not recognized or an issue that the Control Panel does not open etc etc etc etc etc etc etc. Could literally mean anything...
Please explain in more detail what your issue is. As a software developer you should know that devs need as much information as possible regarding issues as troubleshooting is otherwise hard, if not completely impossible ;)
Vince Lee then go to Simucube .I have a Simucube Pro .Good luck with running the Simucube with Forza Horizon with Emuwheel and the other Emu shit Software for different Games .But you as a Developer will have no Problems with it .But when you only play Iracing it’s perfect to spend 1400€ for a Simucube .
And yea I only play iRacing and ACC anyway. Forza is absolute shit on a wheel too due to their FFB issues so I prefer controller.
I was originally keeping options open due to PS5 and GT7, but I have Heusinkveld Sprints which invalidate this already lol
EDIT: Also not sure if your dev thing is a backhanded comment or not but no, I am not going to spend time reverse engineering assembly to write a driver. I do my job for a living, I do not do it for fun anymore =P
I asked for a detailed issue report as requested in the first post of this thread, not just "it errored out twice".
Logs are great and important but they are not everything, they help our Dev to investigate but he first needs to understand what exactly the issue is and this is still totally unclear.
Then it errors out (there was no descriptive message or I'd be typing it), which starts a rollback. Reboot necessary.
DD1 is unrecognizable after until I open Fanatec Control Panel which will repair the DD1.
I did the above twice before giving up and sticking with 453 which works fine with iRacing.
If your logs are not storing what I mentioned above...as i said, I am a dev and now I am concerned.
In addition, if you have access to your CRM: 000000700469512. This is unrelated to the driver issue but it will explain why, in addition to the driver problem, my impression of Fanatec has gone from "wow you guys are great!" to "...did I just make a $1700 CAD mistake?" within a week.
Comments
in here it worked fine. also driver self if it have issues can be always uninstalled and add older one
That is just bad luck.
Had no problems installing the 454 driver and upgrading firmware (DD1, Button Module Endurance).
I can't help that you are a fanboy and you like to let yourself be fooled ... the power of one, needs the stupidity of the other ...
That happened to me with the upgrade to WQR v7 as I mentioned above, try disconnecting all usb devices, except the steering wheel. It worked for me (in the log logs there were conflicts with other usb devices); after esi let me update wlWQR and steering wheel
Thanks, that worked!
I do have quite a few usb devices (handbrake, button box, etc.). But they didn't cause any problems with the base firmware upgrade so I didn't think that they would affect the WQR upgrade. Turns out I was wrong, after unplugging them the WQR firmware upgrade went without a hitch!
I went from 452 to 453 and then back to 452 and then to 454 with absolutely no problem.
It's faulty. Cannot update the DD1.
Close to refunding because management won't refund me the difference w/ the DD2 sale and I bought the DD1 when it was $899 USD
I can't get my control panel to open at all. with driver 452 453 or 454. I can install it fine but will not open at all once installed?
Please upload the Log files from C:\Users\Public\Fanatec Logs and list all the Fanatec devices you are using, otherwise it is basically impossible to investigate as you are the first to report this kind of issue.
Also any kind of Windows Event Logs would certainly help as well, for that open Windows Event Viewer, go to Applications and select every entry with a red exclamation mark which is related to the FanatecControlPanel.exe file and upload everything here.
is anyone feel that 454 driver is allot better than previous releases? or i just start go nut?
When i look under public user there is no fanatec logs. using csldd 5nm wheelbase clubsport v3 pedals trying to figure out how to get the window log errors uploaded
Yep, on the podium f1. It said everything updated, including the wheels, so I went in game to bind buttons and none worked. So, I went back in and saw the wheel needed an update from V47. Odd, but I attempted to update and it froze. Rebooted the dd1 and went back into the updater and it said it was updated. I've also rebooted my PC twice since 454 was installed and all the wheels were updated. I did have other USB devices plugged in, and everything else updated. I've power cycled the base probably 4 or 5 times during all that.
i think fanatec does use a .net framework, to you have latest .net framework installed for you windows? or what windows version you are using?
Marcel /Maurice Hello guys my DD2 came Today.At first it wasn't recognized at all in driver 454. I got it to work with the old driver 336, then driver 447. Then that's it. If I update from 447 to 454, the DD2 is no longer recognized. Is there a solution?
What are your Firmware versions?
I am now 447 it is impossible To Go To 454 .454 dont shows the Wheelsbase
I have twice To Go from 447 To 454 .The DD2 is not displayed on 454 nothing
And what happens when you leave the base powered-on, uninstall the driver 447, then install driver 454 (still with the base powered-on), then restart the PC? Does the Control Panel open after the restart and showing "No Fanatec Device found" or what exactly is not working?
If thats the case then you. can look into the Windows Device Manager if there is a device with a yellow exclamation mark which is disabled. If thats the case, enable the device manually via right-click, then the Base should be recognized again by the Control Panel.
If the base is still not recognized in 454 please use the "Collect Logs" feature in the driver and upload them here.
Maurice thanks .It works To install 454 and let the Base on Power .Everything Perfect .Good Evening
Nice!
PS: That is btw the way to go moving forward on the next driver installation: The base should always be powered-on when you install the driver. Thats the best way to ensure the USB device driver gets properly installed.
I dont Know this Way with my DD1 F1 there was no Problem from 447 To 454 but many Thanks for the Great and fast Help.
Hey, Fanatec,
Read this please.
I'm nearly deadset on swapping to Simcube :')
Didn't get the hate against Fanatec riddled all over Reddit and even here. I am, very sadly, starting to understand it now.
Fanatec has read your comment but with so little information it is not possible to help.
You only said "errored out twice" without explaining what this could mean...
It could mean anything, from a simple issue where the installer fails or an issue that the base is not recognized or an issue that the Control Panel does not open etc etc etc etc etc etc etc. Could literally mean anything...
Please explain in more detail what your issue is. As a software developer you should know that devs need as much information as possible regarding issues as troubleshooting is otherwise hard, if not completely impossible ;)
Logs are in the zip file.
EDIT: Not gonna lie, your post is only adding to the negative impression I have due to lack of attention to detail.
EDITEDIT: Also, before anyone calls me entitled: if I asked a user to read log files and debug at my job, I would get fired.
Vince Lee then go to Simucube .I have a Simucube Pro .Good luck with running the Simucube with Forza Horizon with Emuwheel and the other Emu shit Software for different Games .But you as a Developer will have no Problems with it .But when you only play Iracing it’s perfect to spend 1400€ for a Simucube .
Waiting for refund with RMA number.
And yea I only play iRacing and ACC anyway. Forza is absolute shit on a wheel too due to their FFB issues so I prefer controller.
I was originally keeping options open due to PS5 and GT7, but I have Heusinkveld Sprints which invalidate this already lol
EDIT: Also not sure if your dev thing is a backhanded comment or not but no, I am not going to spend time reverse engineering assembly to write a driver. I do my job for a living, I do not do it for fun anymore =P
I did not asked you to read log files and debug.
I asked for a detailed issue report as requested in the first post of this thread, not just "it errored out twice".
Logs are great and important but they are not everything, they help our Dev to investigate but he first needs to understand what exactly the issue is and this is still totally unclear.
Made a post but I think it got deleted somehow.
The whole story would be:
I downloaded the driver.
I double clicked.
I hit "Okay" twice at the warning screens.
Then it errors out (there was no descriptive message or I'd be typing it), which starts a rollback. Reboot necessary.
DD1 is unrecognizable after until I open Fanatec Control Panel which will repair the DD1.
I did the above twice before giving up and sticking with 453 which works fine with iRacing.
If your logs are not storing what I mentioned above...as i said, I am a dev and now I am concerned.
In addition, if you have access to your CRM: 000000700469512. This is unrelated to the driver issue but it will explain why, in addition to the driver problem, my impression of Fanatec has gone from "wow you guys are great!" to "...did I just make a $1700 CAD mistake?" within a week.