Almost 20 years on, the Logitech Wingman Formula Force still works in windows. Released around the time USB was just arriving on the market, these robust wheels date from back in 1998.
Logitech discontinued driver development in 2006, however Saitek did release a 64bit driver based on the Immersion SDK. A primitive Force feedback design by today's standards, but it still works with most modern games.
This driver was adapted by Sly_North from the below Saitek source.
To breath a new bit of life into the Logitech Wingman Formula Force, here is a Windows 10 Driver (signed) that will permit installation into Win10 x64 bit without the need to disable driver signing.
UPDATE [August 2022] - Ken830 has kindly provided the PIN outs for the DB9 to USB adapter
I measured all the pins of the DB9-to-USB cable... I did not find any connections between pins on the DB9 side -- all were open-circuit, and I checked it twice.Here's the pinout:
- DB9.1 <=> USB.1 (Vcc)
- DB9.5 <=> USB.4 (GND)
- DB9.8 <=> USB.3 (D+)
- DB9.9 <=> USB.2 (D-)
- DB9.Shield <=> USB.Shield
UPDATE [Jan 2020] - This driver no longer installs on fresh Windows 10 OS. This is due to MS changing signing requirements under fresh installs in Windows 10. The below driver is signed with SHA-1, which is no longer trusted, thus not supported in newer releases of Windows 10. I'm looking for a volunteer to re-sign these driver with SHA256 as per Practical Windows Code and Driver Signing
Enjoy!
Logitech Formula Force E-UA2 Windows7 8 10 64bits signed (updated 23/9/21)
SHA256 C132B429B25D1AC0186C65A699FE6AC3131827E3E13297E8F507325B2B31B047
Saitek Source (updated 9/5/19)
SHA256 ECC4B98757FFBF53501A7D239CE3FA3B4D05B9543F091CA156D9EDE1ED44DB6F
Last version of Logitech Gaming Software (LGS) to support the wheel (Windows XP 32bit)
lgs460enu.exe
lgs460enu.exe
Credits: Leshcat of leshcatlabs.net for signing the drivers to make this happen and to Sly_North for the original Saitek driver mod. (http://web.archive.org/web/20160102083612/http://forums.logitech.com/t5/Logitech-G-Controllers/Wingman-Formula-Force-and-Windows-7-x64/td-p/428223?nobounce)
Many thanks !!!
ReplyDeleteYou're Welcome
DeleteHi,
ReplyDeleteCould you make the file available please.
I'm searching drivers for th E-UA2 logitech.
Thank you very much
Unfortunately this post is about this specific model, that shared a driver/tech with other Immersion SDK wheels.
Deletethank you, sorry for the inconvenience you could make a video with the steps to perform the installation for more extensive help to the community thanks
ReplyDeleteYou might want to look at https://www.youtube.com/watch?v=jyKrxxXOvQY
Deletehello there. I have the formula force wheel and notice this is working for others. I do not have the native gameport on my mobo yet have the rockfire gameport to usb adapter. will this program work in tandum with the rockfire drivers?
ReplyDeletealso how does everyone else connect these serial gameport wheels? I was told the rockfire would be the converter between analog to digital but it does not pick up my wheel
DeleteThis Wheel is USB (+Serial RS232/DB9). These Drivers are for USB only. I suspect you might have a different wheel.
DeleteThe Wingman Formula Force (original) came as a Serial (not "gameport") cable device, with an included serial-to-usb extension.
DeleteI thought I'd lost my extension, and had to build a replacement. I later found my extension, thankfully... but not before I'd built the new extension (so I now have a spare, I guess!)
The wiring schematic for the cable is something I had to do a bunch of searching to find. It's a "straight pass-through" cable extension, so getting a USB cable and a "build it yourself" serial connection allows you to build your own converter extension.
Anyone with an extension in their inventory already... who has a complete Formula Force, in other words... can do the job, too. It's just a matter of tapping for continuity across the four contacts inside the USB connector, and the nine pins in the DB9 serial connector.
My memory is a BIT hazy, but I THINK that you also had to short between several pins on the DB9 side, to instruct the wheel's hardware that it is a USB connection rather than a serial one. So, in other words, you need to use a multimeter and check for continuity between EVERY contact on the 9-pin side and every other contact on that side, not merely between the four contacts in the USB connector and the nine pins of the DB9 connector.
I did all this, but I simply can't recall the details anymore. In fact, I was just coming online to see if anyone had improved the "hacky" work-around to get this wheel to work on "modern" OS installations... thanks to the site author, by the way, and those who helped him! Last time I played with this, I had to take the Saitek driver itself and make my own mods to it (though I had instructions on what to do). Having it "pre-packaged" sure is nice!
Anyway, NO... this wheel can work nicely on a modern OS using the driver package provided here and the serial-to-usb connector I described here.
Site owner - it would be helpful, if someone (besides me... my wheel set is packed away right now and inaccessible, though that'll change in a few months!) were to do the "tap-out" on the connector, and perhaps you could publish that diagram here, as well? I'd do it if I could, but it's not possible at the moment, and my old documents are also in sealed boxes awaiting my upcoming relocation, soooo...
If someone has the Serial to USB Pinouts I'm happy to post these here too.
DeleteI dug out my old Formula Force a few months ago but I just could not get the drivers to install on my Windows 10 x 64 machine and gave up... But since I still have the wheel out I measured all the pins of the DB9-to-USB cable... I did not find any connections between pins on the DB9 side -- all were open-circuit, and I checked it twice. Here's the pinout:
DeleteDB9.1 <=> USB.1 (Vcc)
DB9.5 <=> USB.4 (GND)
DB9.8 <=> USB.3 (D+)
DB9.9 <=> USB.2 (D-)
DB9.Shield <=> USB.Shield
Thanks Ken for taking the time to share that.
DeleteThanks, Rob!
DeleteI've done a ton of home-made wire-harness work over the years, and would have SWORN that this was one of those which required "shorting between pins" to detect the alternative connection, but it does seem that in this case it's my memory which is "crossing its wires." :)
So... all anyone needs to do, now, is get a "disposable" USB 1.x or 2.x cable (NOT a 3.x cable, though!) and one of THESE...
https://www.amazon.com/Connector-Adapters-Adapter-Terminal-Screwdriver/dp/B093PFX62L/ref=asc_df_B093PFX62L?tag=bingshoppinga-20&linkCode=df0&hvadid=80539352774065&hvnetw=o&hvqmt=e&hvbmt=be&hvdev=c&hvlocint=&hvlocphy=&hvtargid=pla-4584138876405609&th=1
... and voila! Instant "adapter cable."
As others have mentioned, this only works on the "red rubber" original Formula Force wheel, not on the yellow-rubber version, or on any later version. But given how many of the original red-rubber versions are out there for sale... CHEAP... due to people thinking that they can't be used anymore... and how expensive current-generation wheels are... this is a great option for those of us who are even marginally electronically-competent! :)
This comment has been removed by the author.
DeleteThis comment has been removed by the author.
ReplyDeleteWhat files will I use on this repository for Windows 10 64 bit?
ReplyDeleteThe Zip file is the signed driver. The other files are provided for reference, should someone want to compare to the originals.
DeleteUnfortunately this post is about this specific model, that shared a driver/tech with other Immersion SDK wheels.
ReplyDeleteCorrect. If your wheel looks like the one pictured and you connect via USB it will work.
DeleteI wish 😕
DeleteMy Wheel looks exactly the same, just in Yellow. But the native Port isn't USB. I hava a USB-Adapter tho. Will this work? I can't seem to get the installation done. The .exe doesn't find me device.
ReplyDeleteBTW the Model Number is E-ZA1
DeleteNo this driver is strictly for the red wheel.
DeleteThis driver seems to no longer work on the latest build of Windows 10?
ReplyDeleteWhat error are you getting? And what version build /release of Windows are you running?
Delete1903/1909?
The calling of Force Feedback effects by various x64 applications causes Access Violation crashes on Windows 10 x64 1909.
DeleteManaged to get it working by disabling driver signing.
ReplyDeleteHELP!
ReplyDeleteplease give the driver link. yui on which windows does the steering wheel work?
HELP!!!please give the driver link. yui on which windows does the steering wheel work?
ReplyDeleteA little complicated method can be if you install VMWare or other virtual machine software and you install Windows XP over that. On installed virtual machine you can install the drivers of the Logitech Wingman Formula Force without any problem. You install your wheel-based games to Win XP virtual machine and you play on it. :)
ReplyDeleteYes this is an alternative to these drivers. However 3D games do not run as well under VMware IMO.
DeleteI tested with Need For Speed Underground 2 and Most Wanted. They run a lit bit slower like on host and there is some flashing, but it works with the original Logitech Wingman drivers. I used integrated video card. Maybe the performance can be better with native video card.
Deletemy pc runs windows 8.1 and i have the exact same wheel but yellow instead of red. when i plug in the game port to usb adaptor to my pc only the left led lights up and neither this or the logitech software detects the wheel. someone help?
ReplyDeleteThis driver isn't for the yellow wheel. This is only for the red wheel. They may look the same, but have different internals.
DeleteBeen trying to make this work for years, but cannot make it work. The files everybody points to are always the same. I get "The hash for the file is not present in the specified cataloque file. The file is likely corrupt or the victim of tampering." :(
ReplyDeleteYou need to use the zip file. Logitech_FormulaForce_E-UA2_Windows7_64bits.zip This is the modified Saitek R440 Force Wheel drivers.
DeleteTry https://www.7-zip.org/download.html if you are having issue unzipping.
This comment has been removed by the author.
DeleteThe SHA values of the files do not correspond with the ones in Security Catalog
DeleteNot sure how that could be. The drivers haven't been modified. The only change as per the link above was the Device ID in the inf. The drivers and catalogue have been re-signed. Check the signature on the drivers. If they're invalid, I'd be suspicious something is modifying the files on your PC.
DeleteNot had any one else report this issue.
Nothing wrong with my W10, it works when disabling driver signing. QED :)
DeleteAre the signatures valid on the .sys files?
DeleteI note they're signed with SHA1, so if you are on a modern OS windows may not accept the SHA1 signature. MS has dropped support for SHA1 signed drivers.
https://support.microsoft.com/en-gb/help/4472027/2019-sha-2-code-signing-support-requirement-for-windows-and-wsus
I suspect if the driver was installed in an earlier Win10 Build, it will continue to honor the install. However if it's a fresh install, then the SHA1 policy is enforced during install of the driver.
Nice to see you are still around and posting!!
ReplyDeleteI did use the zip file, no issues with unzipping.
This comment has been removed by the author.
ReplyDeleteSaved my wheel, installed successfully,great job!
ReplyDeleteOne question, how do I calibrate the wheel? I remember in old days windows has a game controller app in control panel to do it. In win10, it disappears.
In NFS game, my accelarator padal keeps the arrow key down like beheavour, not function in the game.
To further dig out the root cause of my problem, I finally find that in my old XP system, the game controller setting has one checkbox option:combined axis. But in Win10, in the game controller panel, I can't find the similar setting, which cause the gas and brake pedal doesn't work in the game, how to solve it?
ReplyDeleteC:\Windows\System32\joy.cpl
ReplyDelete@bARt, what is the use of this file? I tried another logitech driving force pro installation, seems only after installed logitech's driver, game software etc, the HW setting can have more parameter configuation. The worst case for my Formula force wheel is:the gas pedal is always at 100% when it is untouched.
ReplyDelete@bARt, googled the function of joy.cpl. Thanks and yes I already find the access to it. Can't upload the picture, let me explain in detail. In property's test tab, I got a square with a cross in it, labeled:X Axis/Bra.. the cross is always at center bottom, once step on brake pedal, the cross go up to center top. On square's top right there is a red to blue color bar,labeled Gas. Without touch, it is full color, once touch gas pedal, the color bar reduce to 0.That is, the gas is at 100% when untouched. There are also 6 buttons below. The wheel steering and the buttons are working fine, just the pedals seems not right.
ReplyDeletehaving the same issue as bArt: "The SHA values of the files do not correspond with the ones in Security Catalog"
ReplyDeleteProblem:Also the disabling of the drivers check does not work.
Zip Files are unzipped, Driver install results in: "Hash for file not in catalog.File is probably damaged or was changed without permission". Any idea how to get the good old wheel back to work?
Is this a fresh install of Windows 10? I suspect MS doesn't support SHA1 hashes with fresh installs.
ReplyDeleteI am having the same issue as mcmichael, Windows version 1903, trying to install for first time on new system. I receive the Hash error and attempting to use the .exe stops when prompted to connect the device.
ReplyDeleteup date, I was able to use the drivers and get things working by disabling driver signing enforcement and manually installing the driver from device manager. Thanks for the links. I used a version of this driver years ago.
ReplyDeleteNo Prob.
ReplyDeleteThanks Rob for posting this up. I have had my Wingman Forumla Force working with Windows 7 64 for years using the Saitek drivers. I just updated to Windows 10 and the wheel now won't work properly. The driver was installed/installs and the wheel is recognized and can be calibrated, but Force Feedback appears to cause games to crash. Strangely, the wheel will work fine if i force Assetto Corsa to 32bit mode, but is no good under windows 10 when running in 64 bit mode. ForceTest also won't work. Stumped as to what the problem is. Appreciate any suggestions.
ReplyDeleteEvent viewer says...
ReplyDeleteFaulting application name: rundll32.exe_shell32.dll, version: 10.0.18362.1, time stamp: 0x8ceb427f
Faulting module name: SaiQFF04.dll, version: 6.0.4.1, time stamp: 0x46372b3b
Exception code: 0xc000041d
Fault offset: 0x0000000000005a80
Faulting process id: 0x13e8
Faulting application start time: 0x01d5d76e4432ac06
Faulting application path: C:\Windows\system32\rundll32.exe
Faulting module path: C:\Windows\system32\SaiQFF04.dll
Report Id: db1a9aca-87ba-4863-a2a0-376b8760d167
Faulting package full name:
Faulting package-relative application ID:
Hey bro, can you give me original CD driver ? Cause this driver make program crash everytime using ffb in win10 and my CD driver is gone, can you give me that ?
ReplyDeleteSee the original post. I've linked to it.
Delete32 bit only and only Windows XP and older.
This comment has been removed by the author.
ReplyDeleteAre thats LG software waorking and detected perfectly on win XP 32 bit ? Cause when i try to use this in compability mode at win 10 64 bit thats software not detect my wheel
ReplyDeleteThanks for the Saitek drivers, I am trying on Win 10 1809. It does not really work well as the paddles are not detected and there are some difficulties with the brake pedal being activated when gas is pressed. Have some trouble getting Steam to detect it as a actual wheel instead of xbox controller as well. FFB worked once for me in Dirt Rally and it is very strong.
ReplyDeleteAlso no Logitech Gaming Software (lgs) works anymore on 64-bit that supports the wheel. Even with lgs460 software which is the last to support this wheel is on Windows 98/ME only, per the list in the supplied readme. It does not support this wheel on Win XP, only USB HID devices listed in section 1.3.1 is supported on XP with lgs460.
1.3.1 USB HID DEVICES
WingMan Formula GP USB
WingMan Formula Force GP
WingMan Formula (yellow wheel)
Logitech Driving Force
Logitech MOMO Force
Logitech Racing Force
Logitech Racing Wheel
Logitech Driving Force Pro
Logitech Force 3D Pro
Logitech Formula Force RX
1.3.2 LEGACY USB DEVICES
These products are supported under Win98/ME only.
WingMan Force
WingMan Formula Force
1.3.3 GAMEPORT DEVICES
These products are supported under Win98/ME only.
WingMan Formula (black wheel)
WingMan Formula (yellow wheel)
1.3.4 SERIAL PORT DEVICES
These products are supported under Win98/ME only.
WingMan Force
WingMan Formula Force
Two Questions:
ReplyDelete- Is this also working for Wingman Formula Force GP?
- Which node (under the Device Manager) stands for the Wheel? Iam asking this, because I wanted to install the Driver manually but did not find the correct node.
Checkout the .inf file for the HWID and then run powershell and use the command
Delete##ALL USB DEVICES##
Get-PnpDevice -PresentOnly | ?{$_.Class -eq 'USB'} | fl
##WHEEL VID/PID##
Get-PnpDevice -PresentOnly | ?{$_.InstanceId -like 'USB\VID_046D&PID_C291*'} | fl
Which .inf file do you mean (this one: ".\Logitech_FormulaForce_E-UA2_Windows7_64bits\FF04_x64\SaiFF04.inf")?
DeleteOr from the driver of my wheel (Wingman Formula Force GP), that supports only WinXP?
When I use 'Get-PnpDevice -PresentOnly | ?{$_.Class -eq 'USB'} | fl', I can not really see, which device the Wheel is. Should the output contain 'USB\VID_046D&PID_C291' (that it does not contain on my system)?
Sorry for the additional questions.
Wingman Formula Force GP is a different wheel.
ReplyDeleteThe .inf in the provided download.
https://drive.google.com/open?id=1GSBy4NowuRJyDknjNG4h1lGCa_ysnA4r
Only the .inf in the FF04 directly is modified. The others aren't used.
USB\VID_046D&PID_C291 is the HWID from the modified .inf
If you do not see this ID, then your wheel is either not conencted or a different model (as above, GP is different to this wheel).
Just try searching for USB\VID_046D
That is the Logitech Vendor/manufacturer ID they use in many of their products. https://devicehunt.com/view/type/usb/vendor/046D
Thank you for your help.
ReplyDeleteI also realized that my Wheel is a different one. For it (Wingman Formula Force GP) the "old" logitech Software LSG 5.10 is working under Win10. So, I could solve it.
Again, thank you for your support.
ciao a tutti, novità per i nuovi Win10?
ReplyDeleteplease, no news ?? :-(
DeleteThis is a english forum. If you want help , you are best to post in English and specific details.
DeleteWhat are you asking?
Hello,
ReplyDeleteI recover a logitech wingman formula force and I want to use it to play ETS2 but in my periphery manager, my wheel don't have the driver up to date. I search on internet but I don't find the good driver.
So I would like to know if you have the driver or where can I find it. I'm in Windows 10 x64
1st step is to confirm the wheel you have.
DeleteRight click the start menu and select Windows Powershell (Admin)
Then paste in this command. It will list all Logitech wheels connected to the system (whether a drive exists or not).
Get-PnpDevice -PresentOnly | ?{$_.InstanceId -like 'USB\VID_046D*'} | fl
With any luck you'll see "USB\VID_046D&PID_C291".
If not, copy the output and post back here.
Note: This Blog post is only for the wheel pictured in the blog. If it's different, then you'll need another driver.
I did the 1st step and I see "USB\VID_046D&PID_C291\5&39CEA24A&0&1" many time so I don't know if it's the good wheel or not. But it's the same that the picture.
DeleteIf you see that USB ID, then this drive will work. However if you'll need to disable driver signing in Windows 10.
Deletehttps://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/
But when I go on device manager and I check the pilot for my steering wheel, it says that the pilot is not installed. So I don't know what can I do for resolve this.
DeletePilot?
DeleteIf you run this command in powershell
Get-PnpDevice -PresentOnly -Class USB | ft -AutoSize
What is shown against the USB\VID_046D&PID_C291?
What is the friendlyName?
Search for that in Device Manager.
I don't have USB\VID_046D&PID_C291 in powershell when a run the command but I have
DeleteUSB\VID_046D&PID_C52B\5&39CEA24A&0&5, I don't if it's the same thing. The friendly
name of this is composite USB periphery.
That's a Logitech Unifying receiver for mouse /keyboard. Unless you see the USB\VID_046D&PID_C291, the driver will not work.
DeleteWhat do I need to do for it toi work ?
DeleteThis comment has been removed by the author.
DeleteUnfortunately it could be many things? Without physically inspecting it just guesses.
DeleteI presume you have the power supply connected for the wheel? Are you seeign a green LED on the whee at all?
To see if it's being detected at all.
In Powershell:
1.
Disconnect the from the computer and run this command
$d1 = Get-PnpDevice -PresentOnly -Class USB
2. Plug in the wheel, wait 30 seconds
3. Run this command
$d2 = Get-PnpDevice -PresentOnly -Class USB
4. Then run this command
Compare-Object $d1 $d2
If you see output, then this is the wheel USB ID. Please post it.
If you see no output, then the wheel is not being detected by the PC/OS and there is a fundamental electrical issue, which you'll need someone local to diagnose.
I see the green light on my wheel.
DeleteBut when I use the command compare I don't see an output.
Can the problem come from the generation of my pc ? Too recent ?
Not a generation problem. USB is a standard. There is some fault with the wheel.
DeleteConfirm the command is working with another known working USB device.
Do you see a green light without it connected?
The command is working with a mouse plug.
DeleteI see a green light without it connected on my pc
I would say there is an electrical fault with the wheel. If it has power and another USB device registers with the command and the Wheel doesn't, then that rules out any PC issue.
DeleteSo there is nothing to do to resolve this ?
DeleteFundamentally, software cannot fix physical hardware issues. You could take it somewhere to get looked at, but I'd suggest it would be cheaper to buy a new wheel. You can pickup G25/G27's pretty cheap secondhand.
DeleteThis comment has been removed by the author.
DeleteOk I try to see that. Thanks a lot for your help and your patience.
DeleteI get the following:
DeleteWin32_PnPEntity: USB Serial Converter (DeviceID = "USB\VID_0403&PID_6001\FTAPH9IA") =>
Am trying to install the driver on this but it seems not to work - and the wheel is not recognised by the lgs software
If I understand right, you are using a regular USB Serial converter with the wheel. Unfortunately the driver doesn't support Serial (RS232) connections. Only native USB.
DeleteAs the wheel design dates back to platforms where USB wasn't a standard, Logitech/Saitech offered serial (RS232) option to connect the wheel, but that was quickly phased out.
Only USB connection is support and that must be via the propriety adapter. The Adapter AFAIK, is passive. Simple pin plug conversion. I don't have the PIN outs, but someone maybe able to assist with that.
See this image. You need that USB to DB9 Adapter in the picture
Deletehttps://pc.watch.impress.co.jp/docs/article/981109/logi_1.jpg
Siome references to the PIN out.
https://www.eevblog.com/forum/chat/logitech-wingman-formula-force/
Linux Support
https://github.com/torvalds/linux/blob/master/Documentation/input/joydev/joystick.rst#i-force-devices
HI i neeed help i have everything and downloaded the saitek one but the app is not detecting any controllers for me
DeleteYes i have the exact code for the power shell
DeleteThis comment has been removed by the author.
ReplyDeleteHi there. I've been using this driver for many years on my Windows 7 64 bit. Been working great. I'm trying to get it to work in Automobilista 2 but it crashes to desktop more often than not. When it works it's only luck. The wheel works in Project Cars 2 which is the same game engine as AMS2. Any thoughts?
ReplyDeleteTry disabling FF in game
ReplyDeleteDisabling FF basically defeats the purpose of having a wheel. FF works fine in Project Cars 2.
DeleteThere was a version of this wheel (Yellow) that didn't have FF, so I'm not sure I agree with that statement.
DeleteIn short, it's not a driver thing, rather you need to take it up with the game developer. In my experience, they won't care as they're only interested in supporting current wheels, that they can actually still purchase.
Does this still work. I have the Formula Force and the Logitech software hasn't recognized I have anything plugged in.
ReplyDeleteYes. You need to disable driver signing if you are not using Windows 10, that was previously upgraded (inplace upgrade).
DeleteThis driver doesn't integrate with the Logitech Wingman Software. It's standalone.
I have disabled the signing but neither the lgs or saitek are recognizing the wheel. Which file in the google drive do I need to install? Thanks for your help
Deletewas able to get it installed, now a different problem Assetto Corsa crashes when I start the track. Doubt you know of that fix. Thanks for the driver!
DeleteMaybe try disabling FF in the AC. That has worked in some games.
DeleteAs this wheel uses a old implementation of FF SDK, some games well tested and crash.
Can I ask how did you get it working?
DeleteThanks to this post and to entering Win10 Test Mode I could install the Saitek drivers for my Wingman Formula Force... But I can't get the Logitech Monitor to work correctly (lgs460_x64.exe package), its main window is not shown when I double-click.
ReplyDelete@Joandreu, none of the LGS software work for LWFF in Win 10. I tried ws365enu.exe, it can install on Win 10 but Profiler won't work, but with this and the Saitek drivers the wheel at least works with some games on Win 10.
ReplyDeleteWorking games on Win 10 (with FFB):
Project Cars 2
Dirt Rally
Crash:
ETS 2 (FFB must be disabled in game to make it work, otherwise crash, you can temporarily delete SaiQFF04.Dll* then untick FFB in game.)
*To totally disable force feedback delete/move SaiQFF04.Dll in Windows/system32 folder. This is for some games like ETS2 where you can't disable FFB because the game crashes on load.
Also the contents of my SaiFF04.inf is a little different, I have the China version of LWFF wheel so maybe my hardware ID is different:
[SAITEK_MODELS.NTamd64]
%HID_NAME%= SAI_HID_Inst, HID\VID_046D&PID_C291
%USB_NAME%= SAI_USB_Inst, USB\VID_046D&PID_C291&REV_0100
Overall it does the job for some games if you are not picky and can settle for 180 degrees turning, the force feedback is still strong and can be adjusted in these games. It's not a loud wheel either. I could not get my paddle shifters to work, and the pedals do feel clunky.
For an older system on Win98 it would be better because you can use the Logitech profiler and adjust combined/separate pedals for old games.
Alison has a trove of information here: http://alison.hine.net/gpl/controls/logiiff.htm
And here's a ball bearing conversion / teardown: https://youtu.be/r9Ob4xQ93yY
Agreed. I note...
DeleteLWFF and Assetto Corsa x32 works with Windows 10 x64
LWFF and Assetto Corsa x64 crashes with Windows 10 x64.
It's strange as LWFF and Assetto Corsa works fine with Windows 7 32 and 64 bit. Force feedback effects are created via the DInput8 API which as far as i can tell was ported as is to Windows 10. For those interested i've written up what i know here: https://answers.microsoft.com/en-us/windows/forum/windows_10-hardware/windows-10-x64-directinput8-related-device/8c9eba3a-33ff-4358-a41d-7f99d48ad34c?tm=1581511813447
Many thanks! "Assetto Corsa" recognizes the wheel in 32bit mode, I will try this setup by now.
ReplyDeleteThanks Rob!
ReplyDeleteI initially had trouble installing the driver, but once I found the wheel in the device manager under Human Interface Devices, it worked.
Nice work
DeleteThank you ! the drivers for win 32 work well with win vista . I'm using old PC for playing Rfactor 1, and no need more ! I found the red wheels (for only 5€) with db9 port. i make au adapter to usb and IT'S RUN !!! (force feed back too). I have lots of old wheels and this Red one and the yellow to, are the most precise. The FFB is quiet compare to the logitech Force GT (GT4 wheel). And the pedals base is very stable !
ReplyDeleteWith win10, i must start with the advanced boot options & F7, to install 64 bit driver. The wheels works , but no FFB. not matter.
Glad it worked out for you
ReplyDeleteI'm trying to ask logitech for a proper win 10 64bit driver, but their helpdesk in Asia somewhere are finding it really hard to understand the problem. "Sir - all of our joysticks are plug and play" is the reply i get.
ReplyDeleteAn update: I have installed LGS460 on my win 10 32bit pc without problem and both the C291 Formula force and C281 Force both work when booting andvanced boot with pressing F7 for allowing non-signed drivers.
ReplyDeleteThis comment has been removed by the author.
ReplyDeleteI'm desperatly searching for Logitech Wingman Formula(1998) black color steering wheel for windows 7 64bits, I already have them for 32 bits but i guess the 64 bit version of them does not exist. Can anyone suggest anything?
ReplyDeletecan you make a driver for 2020?
ReplyDeleteI didn't write the driver. As per the post I just arranged to get it signed, however MS deprecated SHA1 signed drivers in the newest releases of Win10, which stopped the driver working without disabling driver signing.
DeleteSo far only this method is working for Windows 10 2004 update, the week however is detecting in device manger but not in logitech profiler therefore unable to calibrate the wheel (anyone know how?). As for SaiQFF04.dll ya it's causing some games to crash like Euro Truck Simulator 2 and the crew. Not to sure is it due to Windows 10 but will try on windows 7
ReplyDeleteYeah the Logitech Profiler software does not work on 64-bit OS I guess. You can still calibrate it with Game Controller setting in Control Panel for Win 10, but the gear paddles does not work for me.
DeleteIf you disable FFB in ETS2, you can play without crashing as long as FFB is unticked, but yeah no FFB lol.
Thanks very much for this! :-)
ReplyDeleteInstalled fine from device manager after disabling signing check.
how can i calibrate?
ReplyDeleteUse joy.cpl
ReplyDeleteUse joy.cpl
ReplyDeletehey i have trouble connecting the cable to the paddles to the pc. the paddles are not usb. Do u have any tips?
ReplyDeleteIf the wheel is the one pictured then it should come with the USB cable. Under Win98 the driver supported Serial connection (DB9) for systems that didn't support USB. However new operating systems dropped serail support. If you cable is missing the DB9 to USB portion of the cable, it will not work with this driver unfortunately.
DeletePlease, I'm a bit new to this and have seen the thread but I'm not sure what drivers work with the Wingman Formula steering wheel. Please can you tell me what they are if you would be so kind, thank you very much.
ReplyDeleteHi, i have the Logitech WingMan Formula Force and i want to use it. I changed my PC and in the older one it works. I had installed the driver from the folder and all worked well. But the new PC i can't install the drivers. It say "The Hash for the file isn't avaible in the specified catalog. The file is probably damged". What does it mean? Thanks (and sorry for my bad enlgish)
ReplyDeletehttps://sanghayo.tistory.com/1050
DeleteDisable window signature verification
Reboot
Reinstall Driver
time to buy new
ReplyDeletebonjour esque il y a le pilote pour le volant logitech wingman formula force?
ReplyDeletehi i have the wingman formula force wheel. same as this, but when i install the driver it wont recognize the wheel. i am on wwindow 10 64bit.
ReplyDeleteWell done Rob! I was wondering if sent to trash my wheelie, but this post save my from doing it! It's about 10 years i can't use it, but i tried to download your drivers and install on my W10 20H1 machine. Unfortunately it says me that can't find a right driver, cause it's not signed.
ReplyDeleteSo you still haven't resolve with the new version of driver-signin of Windows? many many thanks for your work!
Disable the windows divers signing in the startup settings. You can do that by the menues or by the console (just google for it). Then install the x64 driver from this page. After doing this the wheel driver can be installed properly. The wheel will appear as as Saitek wheel not Logitech. For calibration you can use joy.cpl in the Windows\SysWOW64 or Windows\System32 folder. I was successful with this method yesterday on a Windows10 x64 "21H1" home version. My Wingman formula force from the late 90ies is doing a great job again. (fist I soldered an extra RS232 2 USB Adapter). So have fun...
DeletePlease the new version of 64 drver..bob.
ReplyDeleteAt least my wheel still function..
Hello there!
ReplyDeleteI was able to install the wheel, but the throttle value seems is inverted. When the throttle is fully pressed th caplibration utility reads zero, and when I release the throttle pedal, the value goes tot he max. The brake works fine.
There is a wasy to invert the throttle value?
Regards!
Hello do you have some driver for the Yellow version ? Thanks !
ReplyDeleteI don't sorry. But if someone has I'm happy to post/host here.
ReplyDeleteFrom my understanding the yellow version doesn't have Force feedback of and thus was not immersion SDK based, thus the drivers will be totally different.
Any info for mod it to 720/ 900°
ReplyDeleteHi,
ReplyDeleteI successfully installed the driver for my formula force wheel. But when I try to start Dirt 2.0 the game crashes and it worked just fine before istalling the driver. What am I doing wrong here?
This message pops up: "Access violation at address 0x10006b0c in module 'SaiQFF04.Dll' + 0x6b0c.
DeleteSaiQFF04.Dll"
I can start the game with the wheel unpluged but as soon as I
plug it back in Dirt crashes :(
Greetings. I recently installed the drivers on Windows 11 pro and it works perfectly. I've only had to disable driver signing temporarily. The problem is that when you open Steam it recognizes the steering wheel as a controller, and when you start configuring it, the right light starts flashing. This does not prevent you from mapping the steering wheel and playing with it, but the force feedback does not work. Does anyone know how to get force feedback to work on Steam? And how can I make Steam recognize the steering wheel as a steering wheel?
ReplyDeleteGenerally the wheel is configure in game and not in steam.
ReplyDeleteI have seen similar reports that the FF doesn't work in some games and I don't know of a fix unfortunately.
Hi,
ReplyDeleteit is not possible to install the Driver on a Windows 11 23H2. The Wheel is found in the Device Manager without a Driver, but if you say "Use this INF-File" there is the following Error Message: " Der Hashwert für die Datei ist in der angegebenen Katalogdatei nicht vorhanden. Die Datei ist wahrscheinlich beschädigt oder wurde unterlaubt verändert." - in English: "The hash value for the file does not exist in the specified catalog file. The file is likely corrupted or has been altered without permission."
Drivers of this era are signed with the deprecated SHA1 algorithm.
DeleteThe driver would need to be resigned. Unfortunately signing drivers in Windows is now much more involved and costly.
Not sure why I haven't thought of this earlier... Before I go through the hassle of digging out my wheel again: Has anyone tried plugging in the wheel to the Steam Deck? SteamOS is Linux based which should have support (no need for signed drivers) and many Windows games run in SteamOS just fine. (I also have a refreshed Model X which runs SteamOS, but I don't think it'll be worth trying there).
ReplyDelete