Logitech Driving Force Gt Drivers Windows 11

[Magnhild Lachowicz]

Igot my Logitech G25 working very nicely in Win98se with the Logitech LGS460 drivers. It is seen as a Logitech Driving Force Pro USB but everything

works except the Clutch, which isn't very important, especially as it's hardly used and most old games don't support it anyway.

I tested in Colin Mcrae Rally 1 and it was all good. The force feedback is quite rubbish in this game as it just rattles the wheel to varying

degrees but otherwise it all tested ok. Had to set Pedals to combined axis otherwise I had no acceleration or braking.

Thanks for the info. So, uhm, Colin Mcrae Rally 1 supports vibration only? No real forcefeedback? Right now I'm also looking for a wheel to use it on my retro win98 PC. Especially in Need for Speed 5 Porsche Unleashed. This game has fantastic force feedback (you can really feel the car). Could you please test how G25 works in that title if you have it?

I have a Driving Force GT, which will *probably* work too, but I'd like to try it. Without custom drivers it runs in a basic compatibility mode (auto-center, 180 degrees, combined axis), but this isn't ideal.

... and in my case, this makes things worse. The "Driving Force Pro" drivers are marked with the yellow exclamation mark, and the device doesn't function this way. Guess the Driving Force GT isn't close enough to work this way. Either that, or it's because I'm running 98 first edition. It also gave me some bluescreens on disconnect, which was fun. What's less fun is trying to remove the drivers which are sticking around even after the uninstall ?

What's weirder still, is that after fiddling with all that, manually removing the logitech driver file, and manually telling Windows to use the default HID Joystick driver... it works. The control panel option still (somehow) has the Logitech panel, and the force feedback gimmicks all function correctly there. I had to switch it to combined pedals for it to respond, but respond it did.

After installing NFS Porsche Unleashed, I fired it up and started a quick race. Force feedback.. technically works? But while it seems like vibration is working, the directional effects aren't really happening much at all. I've got the "Road Grip" and "Stick Volume" effects all the way up and zeroed out Engine and Road Effects to prevent them from interfering (both of which work, but just rumble it). It feels like it's trying to do something, but it doesn't end up working at expected.

... and yeah, the effect is there in Win 7, gone in 98. Granted, the road grip effect isn't great; you either have perfect traction, or absolutely zero when you are skidding, without good directional feedback based on the direction of skid. But either way, the difference is not there when running on Windows 98 at all. At least in the (be it somewhat unusual) configuration I ran the game under.

The reason I'm asking about NFS PU is that for the wheel I have this noname monster (AVB something something) which from the electronics side looks like a knock-off from another extremely expensive pro-grade wheel made by some corp the name of which I can't remember. Anyway, I'm using sorta hacked drivers from this corp and damn it works great in NFS PU... All those effects with that - I'm going to rip your hands off - motor inside the wheel... But only under Windows 98. In windows xp and later all I'm getting is vibration and driver-side centering.

I would buy a proper modern wheel but I'm interested in working ff in NFS PU. Could you please confirm it in modern OS again, zerker? Before that topic I believed that such a behaviour is because of the Need for Speed which somehow defaults to simpler ff effects in NT systems. Looks like it is not?

If you are running on Windows 8 or newer, you will also need some way to get back to 60 fps. I just used nGlide and forced the game into GLIDE rendering mode. There may be other solutions; I know I've used a replacement ddraw.dll in some 2D games on Windows 8 when they are throttled by modified backwards "compatibility". I'm sure there's something similar for 3d games.

I will have to set up my Win98 pc maybe tonight and give this a go. It may well be that even though the G25 works in Win98se, but recognised as a Driving force Pro USB, that may not

be enough for proper force feedback effects.

I did spend quite a while trying to get newer drivers to install in Win98se, by modifying ini files and swapping and renaming files here and there, but was unsuccessful. Back in the day I only

had a Wingman Formula Black that had no FFB, so as long as the wheel works I'm happy. Of Course properly working FFB would be nice though.

We recently deployed Teams Rooms devices across our org. We have about 60 devices currently, all Rallybar w/ Tap and Intel Nuc. I've notice that randomly some devices will get stuck at a blank black screen after nightly reboot. I initially thought this was an issue updating from Teams Rooms v. 4.10.10.0 to 4.11.12.0, however today we had 3 devices get stuck that had already updated to the latest version.

We are having the same issue on our end, too. 20 out of our 50 Rallybars with Taps/Intel Nuc's seem to have this issue every single day so far this week. It's become very frustrating and word is starting to get around that our Teams meeting rooms are starting become....unreliable.

The recommendation from @CheetoChester has worked great on a few Logitech Taps that were already on Windows 10, version 20H2 and only installed the Intel Iris Xe Graphics driver version 30.0.101.1191 after the Windows 10 Feature Update. We can just roll back the drivers as recommended.

However, if the drivers were installed before the Feature Update to 20H2, with the Feature Update installed after the drivers, then the button to "Roll Back Driver" is simply greyed out. We have almost 20 endpoints which fall into this category, as they were all deployed in the past 2 weeks.

Something tells me this will require Intel to publish a newer driver version before we see any real relief. They did release 4 newer sets of drivers since version 30.0.101.1191, which can be found on their support website, though this version is still the latest showing for the Intel NUC that was bundled with the Logitech Tap.

We also introduced another problem (static coming through the rally speaker) during our troubleshooting which according to logitech is caused by latest bios on the NUC. Suggested workaround is to disable Intel Platform Trusted Technology setting in the BIOS, which will kill bitlocker in the process.

@hrcc-cg This is so frustrating, we have only two systems but have the same issue on both with a frozen display every morning. I too got the information from Logitech support to upgrade all drivers (through Windows Update) and we have a "crackling" sound in the MIC now and really low volume on the speakers (We have Rally Medium).

We come across a few users reporting that the NUC MTR systems appear to be frozen or unresponsive after the nightly reboot or after displays go into sleep mode. Tap appears dark and unresponsive. The only recovery is to press and hold the NUC power button until the system shuts down and then power it back on. The root cause is an Intel Iris graphics driver update that was pushed via a Microsoft update.

In light of the latest version(30.0.101.1960) of the Graphics driver released by Microsoft on 10/05/2022 and the fact that you already rolled back to 27.20.100.8935 with no improvement, I would suggest updating the Graphics driver to see if that helps. -graphics-windows-dch-drivers.html

It was also reported that Static noise is heard on Rally Bar, Rally Bar Mini or Rally system connected to the MTR NUC when the system is idle and not on a call.

These issues started after the customer recently updated the NUC BIOS to version 0064. Intel is investigating the issue and has paused the BIOS firmware update version 0064. Microsoft MTR Premium has also stopped pushing this BIOS update via their service. The below workaround worked for most of the users.

We did that Firmware update tool awhile ago too and it helped. We haven't had any issues with our HD projectors and displays after running it. Most of our rooms are HD... with one 4K projector. The 4K was giving us issues is my last post. So far, no issues with our 4k projector and the NUC post upgrading the driver to 30.0.101.1960. This driver update seems to be the fix. If I have issues again, I'll be sure to come back and let you all know.

Hi Johan yeah I ended up having an issue a week later after my post. Tried everything that was recommended by Logitech and Microsoft. In the end I had to reset the unit. So to cut a long story short. I gave up with both Logitech and Microsoft, installed a 3rd party software called Deep freeze, that prevents any changes being made to the os, and on restart the system returns to the exact state it was in when the hard drive was "frozen". Been 3 weeks and I haven't had any issue with the system since. I will schedule to push updates this week coming to keep the system complaint.

3a8082e126