I wonder why every other brands are able to tell windows what the wheelbase is and what the wheel is. It might be "normal" for the fanatec people since the csl dd release but it's not normal in the meaning of the word normal if fanatec is the only product that shows this behavior.
We are also able to tell Windows the exact name.of the base but we intentionally dont want to as it's better to name every device "Fanatec Wheel" for Universal compatibility. More deep down in the code there are still the proper strings for the bases so the game can differentiate between the different bases which might all be named "Fanatec Wheel" but have different strength capabilities etc.
So it's not that we couldnt, we just simply dont want to name the bases individually to keep it more simple for the game devs.
Hello. I have just updated my system to Windows 11 following some guidance of an issue I was having in EVO where the screens were black however the game was running.
So updated my GPU and upgraded to Windows 11. I was advised that there was a Fanatec Driver update so I tried to update it (prior to reading Maurice's comment ref' a server issue).
So now I have bit of an an issue where my base and Bentley and Porsche GT3 wheel's aren't recognised.
Download and Install all of the Microsoft Visual C++ 2015 - 2022 (X86) and (X64) redistributable packages.
Turn off Fanatec wheelbase and uninstall all Fanatec software drivers and Fanalab if installed and start from scratch.
Reboot computer and re-install Fanatec Driver v451, v455 or v464 depending on you equipment and needs for compatibility with your model of Wheelbase (Probably recommend v451 or v455 in general, as v464 seems to be problematic with some configurations of computer and Fanatec Wheelbase/Wheels) .
Reboot computer again.
Then turn on your Fanatec Wheelbase and see if windows detects the USB connection and identifies the Wheelbase.
If not detecting after this, try plugging Fanatec Wheelbase USB cable directly into another USB port on Motherboard.
If wheelbase now detects, continue to use as per usual.
Hi Maurice, tell me, has the problem with the short-term departure of the base in the games (gt7 cs dd+) been solved?I have a 457 driver version, which is the most stable?
I respectfully disagree and am aware of Maurice's comments on the matter, however in years of computing I have never installed software drivers for any USB based hardware including Fanatec devices by having the hardware connected and turned on whilst installing said device drivers, uninstalling software it make no difference if hardware is on or off.
In the past with other hardware installs I have seen windows auto install rudementry Microsoft default drivers for the hardware enabled on USB port which has caused problems with the hardware working correctly and even when loading the proper drivers from the manufacturer windows preferred to keep using its default driver instead.
Secondly, in past such as installing USB cameras, joysticks the drivers have insisted that the device is not plugged in during software install or asks for the device to be plugged in when the driver is parshialy loaded up, if the device was already plugged in it would ask you to remove it and re-plug in for the software to detect it correctly.
So my conclusion, I have done it this way for as long as USB devices have been available on computers and I have never had any issues with the hardware / Drivers installations, others may have different experience.
if some core isolation feature or any other software blocks install, then it does not matter if hardware turned on or not.
there was even issues run the Evo game self, because some protections pop up and not allowed run the game. hardware drivers install is not much different
Thanks for taking the time to reply. I have a DD1. I have done what you have suggested and still no luck. I was running v.464 without any issues. Downloaded EVO worked okay then had some know EVO related issues. Then like I say saw the update available available even though running 464.... since then this is when the issues started to happen. Went back to v.462. Still having the issue.
This dialogue keeps popping up about 10x during driver installation. I have to just keep pressing yes. Not sure if this is related.
seen this problem before, i think it goes away one point, or i was reinstalled the drivers, but yeah if you click no, then it not install the driver and device may not work
Hmm, very interesting that you have a DD1 but is showing as a CSW2.5 with FW version 0, is this because DD1 is in compatibility mode or more like hardware issue (Looks like Hardware failure at this stage as Allan suggests)?
The UAC screen is normal to ask for permission to install Fanatec drivers as it needs admin priv (However 10x seems excessive, it usually only asks 1 or 2 times on my Windows 10 system, My main User account is Admin Priv, is Your User account Admin Priv or just User Priv).
Was the DD1 in normal PC mode when you installed all of your Fanatec drivers ?
Has the DD1 ever been detected as a DD1 with all the correct FW Motor / Base revisions starting with 3.x.x.x. in Fanatec Config or is it just not detecting the DD1 at all on the Window 11 system ?
Posting a copy of you FanatecLogs archives on here for more analysis might give more information into what has been happening, but might not also.
Picture of Fanatec Control Panel showing all detected hardware / FW revisions, Driver Version, etc would also be useful, if not detecting in Windows, you may be able to get FW revision numbers and other info directly from the DD1 Oled Screen if you can swap screens to HW info, I think that only can be done with the Tuning button on Steering Wheel so all gear would probably be need to functional for it to work
with CSL Elite V2, SQ 1.5 and Handbrake 1.5 connected to base
driver 464 (was the first I ever used)
latest firmware of all devices (updated directly after first connection of wheelbase)
It's more like a cosmetic issue (except from this I think everything works as expected):
After opening the tuning menu (no matter if standard or advanced or what set is selected) it says "Selected Tuning Hans Setup" instead of "Selected Tuning Menu Setup"
Jup, this is known. The whole Tuning Menu texts on the GT SW X wheel are actually wrong and can show nonsense, this will be corrected with a future firmware update at some point in the future.
This is not a wndows or fanatec issue. Its a bug which is happening with anyone that uses triple screens, nvidia surround...etc. The temporary trick to fix this it to go in and start as if you was going to drive. Pause the game which brings up the menu. Now in the menu go to video setting and change something.... hit apply... change it back and hit apply. Now you can see everything! Note: You might have to do this everytime until a patch is released.
Comments
DD+ is shown as "FANATEC Wheel" in Assetto Corsa Evo. It would be great to have a Wheelbase and a Wheel instead of two "FANATEC Wheel"s.
Maybe sometimes in a future update or is it one of those "the gamedevs have to fix it.."?
Other brands name the wheel and base seperatly as it has to be.
That's normal and cant be "fixed" from our aidem every wheel base since the CSL DD is seen by Windows as "Fanatec Wheel" with 2 USB entries.
The Fanatec Control Panel shows me that there is a new driver available. Guess thats wrong
Same.
Its a known sever issue atm.
I wonder why every other brands are able to tell windows what the wheelbase is and what the wheel is. It might be "normal" for the fanatec people since the csl dd release but it's not normal in the meaning of the word normal if fanatec is the only product that shows this behavior.
As always: Es sind halt immer die anderen..
just ignore second message like i been todo at day one when i get my fanatec stuff,
if comes to game devs, they can change name if they want
We are also able to tell Windows the exact name.of the base but we intentionally dont want to as it's better to name every device "Fanatec Wheel" for Universal compatibility. More deep down in the code there are still the proper strings for the bases so the game can differentiate between the different bases which might all be named "Fanatec Wheel" but have different strength capabilities etc.
So it's not that we couldnt, we just simply dont want to name the bases individually to keep it more simple for the game devs.
Hello. I have just updated my system to Windows 11 following some guidance of an issue I was having in EVO where the screens were black however the game was running.
So updated my GPU and upgraded to Windows 11. I was advised that there was a Fanatec Driver update so I tried to update it (prior to reading Maurice's comment ref' a server issue).
So now I have bit of an an issue where my base and Bentley and Porsche GT3 wheel's aren't recognised.
Appreciate any kind of help please.
👍️
@Andrew McKillop
Which Base and driver versions you have ?
At this stage I could only recommend:
Download and Install all of the Microsoft Visual C++ 2015 - 2022 (X86) and (X64) redistributable packages.
Turn off Fanatec wheelbase and uninstall all Fanatec software drivers and Fanalab if installed and start from scratch.
Reboot computer and re-install Fanatec Driver v451, v455 or v464 depending on you equipment and needs for compatibility with your model of Wheelbase (Probably recommend v451 or v455 in general, as v464 seems to be problematic with some configurations of computer and Fanatec Wheelbase/Wheels) .
Reboot computer again.
Then turn on your Fanatec Wheelbase and see if windows detects the USB connection and identifies the Wheelbase.
If not detecting after this, try plugging Fanatec Wheelbase USB cable directly into another USB port on Motherboard.
If wheelbase now detects, continue to use as per usual.
As mentioned several times you should install and uninstall drivers with base on.
Hi Maurice, tell me, has the problem with the short-term departure of the base in the games (gt7 cs dd+) been solved?I have a 457 driver version, which is the most stable?
I respectfully disagree and am aware of Maurice's comments on the matter, however in years of computing I have never installed software drivers for any USB based hardware including Fanatec devices by having the hardware connected and turned on whilst installing said device drivers, uninstalling software it make no difference if hardware is on or off.
In the past with other hardware installs I have seen windows auto install rudementry Microsoft default drivers for the hardware enabled on USB port which has caused problems with the hardware working correctly and even when loading the proper drivers from the manufacturer windows preferred to keep using its default driver instead.
Secondly, in past such as installing USB cameras, joysticks the drivers have insisted that the device is not plugged in during software install or asks for the device to be plugged in when the driver is parshialy loaded up, if the device was already plugged in it would ask you to remove it and re-plug in for the software to detect it correctly.
So my conclusion, I have done it this way for as long as USB devices have been available on computers and I have never had any issues with the hardware / Drivers installations, others may have different experience.
if some core isolation feature or any other software blocks install, then it does not matter if hardware turned on or not.
there was even issues run the Evo game self, because some protections pop up and not allowed run the game. hardware drivers install is not much different
when something uses the dynamic link library (dll) , you are not able uninstall that,
that's where is better when fanalab and hardware is disabled
Maurice is been also tell before that user needs uninstall drivers first, but users sometimes installs right away new driver instead
and that also may cause problems if something goes wrong
Thanks for taking the time to reply. I have a DD1. I have done what you have suggested and still no luck. I was running v.464 without any issues. Downloaded EVO worked okay then had some know EVO related issues. Then like I say saw the update available available even though running 464.... since then this is when the issues started to happen. Went back to v.462. Still having the issue.
This dialogue keeps popping up about 10x during driver installation. I have to just keep pressing yes. Not sure if this is related.
seen this problem before, i think it goes away one point, or i was reinstalled the drivers, but yeah if you click no, then it not install the driver and device may not work
Yes you are right it does not install the driver. Either way by pressing yes or no my DD1 is not working.
Appreciate any help please
restart the pc and then try install again
Lost count Alan how many times i've tried that
This is also showing,,,
base Firmware should not show 0
try restart the base self, if it not goes away then you out off luck and you need repair or something
or try even more older driver
isnt 464 the newest driver...?
Yes. Their server is broken again or something like that. Nothing works like it should anymore for a long time now. Don't wory about it.
its something todo with Sunday, what ever issue that is
Hmm, very interesting that you have a DD1 but is showing as a CSW2.5 with FW version 0, is this because DD1 is in compatibility mode or more like hardware issue (Looks like Hardware failure at this stage as Allan suggests)?
The UAC screen is normal to ask for permission to install Fanatec drivers as it needs admin priv (However 10x seems excessive, it usually only asks 1 or 2 times on my Windows 10 system, My main User account is Admin Priv, is Your User account Admin Priv or just User Priv).
Was the DD1 in normal PC mode when you installed all of your Fanatec drivers ?
Has the DD1 ever been detected as a DD1 with all the correct FW Motor / Base revisions starting with 3.x.x.x. in Fanatec Config or is it just not detecting the DD1 at all on the Window 11 system ?
Posting a copy of you FanatecLogs archives on here for more analysis might give more information into what has been happening, but might not also.
Picture of Fanatec Control Panel showing all detected hardware / FW revisions, Driver Version, etc would also be useful, if not detecting in Windows, you may be able to get FW revision numbers and other info directly from the DD1 Oled Screen if you can swap screens to HW info, I think that only can be done with the Tuning button on Steering Wheel so all gear would probably be need to functional for it to work
Gran Turismo DD Extreme
with CSL Elite V2, SQ 1.5 and Handbrake 1.5 connected to base
driver 464 (was the first I ever used)
latest firmware of all devices (updated directly after first connection of wheelbase)
It's more like a cosmetic issue (except from this I think everything works as expected):
After opening the tuning menu (no matter if standard or advanced or what set is selected) it says "Selected Tuning Hans Setup" instead of "Selected Tuning Menu Setup"
Jup, this is known. The whole Tuning Menu texts on the GT SW X wheel are actually wrong and can show nonsense, this will be corrected with a future firmware update at some point in the future.
This is not a wndows or fanatec issue. Its a bug which is happening with anyone that uses triple screens, nvidia surround...etc. The temporary trick to fix this it to go in and start as if you was going to drive. Pause the game which brings up the menu. Now in the menu go to video setting and change something.... hit apply... change it back and hit apply. Now you can see everything! Note: You might have to do this everytime until a patch is released.