Problems reading Logitech G27 steering wheel on Windows 10

Unity Engine
,
1

I’ve got a Logitech G27 steering wheel that I need to get working in at least a basic way (steering wheel, gas, and brake) under Windows 10. This is a pretty fresh installation of Windows, and I did download and run the latest Logitech Gaming Controller installer.

Using just standard Unity inputs, I can read gas and brake fine as the Y axis; buttons also work. But turning the steering wheel results in no input on any axis I can find.

So I tried the Game Controllers control panel, where the device appears (as “G27 Racing Wheel”). Using Properties → Test, I can see the Y axis moving when I press gas/brake, but the X axis doesn’t budge no matter how I turn the wheel.

Then I tried using the Logitech SDK from the App Store. But when I run that, it throws a DllNotFoundException. (Even when I copy LogitechSteeringWheel.DLL out of the SDKs folder and into the Plugins folder.) Maybe it’s a 32- vs 64-bit thing? Or maybe my Windows install is lacking some other DLL that this one depends on?

I’m not very experienced with mucking about with Windows at this level… any suggestions on how I can test this DLL and figure out why it’s not loading? Or, any idea why the X axis (wheel) wouldn’t be working in both the Game Controllers test mode and my Unity app?

2

Are you targeting Standalone player or the UWP player?

In either case, did you try playing with the drivers? If the control panel doesn’t respond to turning the wheel, it’s unlikely Unity will be able to detect it.

Some thoughts on using their specific SDK: I don’t think it’s a good idea. You won’t be able to ship your game and support many different wheels if you have to include their own SDKs for each different wheel. It’s just not feasible.

3

Standalone (PC/Mac build target, set to Windows 64-bit).

Yes, that’s what I spent most of the morning doing. But I’m at an impasse — I’m hoping someone who knows Windows better than me will have some suggestions.

I agree, though, that it’s probably not Unity’s fault. The failure of the control panel to respond to the wheel is very disturbing (and why I decided to try the SDK).

This isn’t a consumer app; it’s a bespoke app for a client setting up a very specific simulation. We don’t need to support any other wheels (though we might have to switch to something else if we can’t get this one to work).[/QUOTE][/QUOTE]

4

If that’s the case, going the native DLL route might be the easiest option, but you’ll have to debug why that DLL fails to load. I’ve explained in another thread on how to do that:

In your case, you’ll want to build a standalone player, enable gflags.exe for that, attach VS native debugger to it (Debug → Attach to Process) and finally trigger the DLL load so that the exception is thrown.

5

OK, I’m trying to follow these directions, but as a Windows noob I’m a bit stuck. First:

I managed to do this, but gflags responds:

This looks like an error to me. Is that normal?

OK, how do I do that? I’m not sure I even have Visual Studio on here, though it’s entirely possible I just installed it as part of this winsdksetup thing. But when I search for Visual Studio in Cortana, the only result is “Visual Studio (Mac)” which I’m pretty sure is not right.

Is there no way to launch my exe with the debugger on the command line (similar to gdb on the Mac)?

6

OK, I think actually this may be just a hardware problem. I checked the same steering wheel on my Mac (which requires no drivers at all), and it’s showing exactly the same behavior: pedals work the Y axis, but steering wheel does nothing.

It’s an odd sort of hardware failure, but given the same results on both platforms, I don’t know what else it could be.

7

No, it should say something like this:

C:\Program Files (x86)\Windows Kits\10\Debuggers\x64>gflags.exe -i InputConfig.exe +sls
Current Registry Settings for InputConfig.exe executable are: 00000002
    sls - Show Loader Snaps

I’d make sure that you ran command line with admin privileges, and that you didn’t accidentally copy/paste invisible characters into the command.

Yeah, Visual Studio needs to be installed explicitly. But read on below.

You can use WinDBG, which definitely got installed as part of debugging tools for windows. Then do File → Open Executable and enter “G” command to continue execution (it will break on the first instruction by default).

1 Like