![]() ![]() Absolutely no clear workaround offered, no support from actual Logitech employees, etc. Logitech are an absolute disgrace, they release new versions of ♥♥♥♥-Hub and LGS that simply break/remove a major selling point of their product (force feedback). NOTE: Even after installed LGS will report it cannot detect the wheel but this is deceptive, because the G29 tab is visible under settings, and with this version of LGS running games such as Euro Truck Sim 2, Mudrunner, Dirt 2 all now actual full force feedback. The ONLY way I have been able to get force feedback across games is by uninstalling all Logitech software, then downloading and installing an old version of LGS from 2018! gaming world by storm, offering players an exhilarating. It is 1000% an issue with the disgraceful Logitech software quality. 2 BROKKEN mchte ich euch zeiThe software version is not available and was updated on. This is across all games, not just specific games. First, you need to connect the pedals to the steering wheel. Setting up your G29 shouldn’t take you more than 15 minutes. BOTH the latest GHub and LGS simply do not work after multiple re-installs. Setting up the G29 involves physically connecting all the components and installing the necessary software. Doubt anyone would be hooking these types of devices to a production system, but none the less.Bought a new G29 recently and what a nightmare getting force feedback working on Windows 10 64bit. You should try your best to never disable memory integrity on a production system hosting important VM's, just a warning. Have a feeling this may also effect a lot of other devices that may fall under the Logitech device line, so have a peek at this setting if you're experiencing similar issues. Scenarios\HypervisorEnforcedCodeIntegrity and reboot. I was unable to turn the Memory Integrity setting off via Windows Defender, so the easiest fix was to just flip the DWORD value called Enabled at HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\ I'd installed Hyper-V to run some VM's and it looks like it enabled HVCI (Hypervisor-protected code integrity). ![]() Follow the calibration instructions then test the shifter afterwards. Press CTRL + SHIFT while clicking Properties. Type joy.cpl to open the Windows Game Controller Settings. I checked the solution in that thread and found the issue was the problem I was also having. Press Windows + R key to open the run command box. Upon looking into the error more, I found this thread Simple way to fix your connection issues with Logitech G Hub software.In the video I'm using G Hub version 2046 (download link below)You can also t. I'd assumed this would be fixed once LGS picked up the wheel and had just brushed past it previously. Just a few moments ago I noticed in device manager that that the Logitech Driving Force Wheel USB (HID) had an error on it and it wasn't loading the driver for that part of the device. I'd been using the built-in USB 3 ports on the connected keyboard of the Surface Book 3, but decided to try a USB-c to USB-A hub. I'd nearly given up and decided to try 1 more thing. I thought this had to do with Windows 10 possibly preferring to use whatever driver from Win Updates, but I eventually ruled that out too. I had kept trying to change the USB driver from Logitech Driving Force to a generic USB device as explained in many YouTube videos, but it kept falling back to the Driving Force driver. I tried all the usual things of using wheel cleaner, removing LGS, rebooting, installing the driver with the wheel connected, and every combination of that in existence. I tried for hours trying to get it detected, but LGS either seen no wheel, or just a Driving Force wheel with no pedals or shifter. I decided I'd like to game in my living room using my Surface Book 3 and thought to get my wheel hooked up. I know the regular install LGS 510 stuff, changing device driver fixes, wheel cleaner, etc. I've used this wheel for years and have had very little issues before this. *explaining backstory directly below this, just skip to the bottom for a potential fix. I thought I'd share in case anyone else runs into this issue. I'd like to share how I got this wheel fixed and recognized by the OS properly. I've just wrapped up a very long troubleshooting session of trying to get a Logitech G27 wheel going on Windvia Surface Book 3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |