I have a Ferrari 458 non-ffb wheel. I've put the x64 files into the PCars steam game folder where the 64 bit executable is. I have xinput disabled and Dinput change ID enabled. I've set my usb port to 5 in the .ini because that's what the xbox360 driver for the wheel said it was connected to. My problem is there's no input now when I go to configure settings or drive in the game. The part where you enter GUIDs into the .ini is a bit confusing because I'm not sure what line I'm supposed to change to have the GUIDInstance from the log file, I think the readme might be speaking of an older version of the .ini file because it says changeguidproduct and not GUIDproducttochange. Anyway, it's highly confusing why there's no input but it probably has something to do with the port number or me not entering the GUID correctly. Help?
I may not even need to change the GUID because I have a wireless controller and it's turned off so the PC doesn't recognize it, but I do have a wireless receiver that's always on. Anyway. I've tried not faking the device by GUID but the wheel still gives no input in-game.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the year late reply :/ (comments needed aproval and I didn't login since last release a year ago so I didn't read your question).
But for anyone that might encounter similar trouble:
Change only the USB port if you have another device/controller connected so the utility knows which one to filter, and this setting is for xinput API only. The GUID is for the same purpose but for the dinput API.
If you have only one device connected it should be automatic. If you don't get any input, enable the log file and see if a log is created and what it contains if it's created (if there's no file log created you probably don't have the correct dll(s) installed). If the log is created I would need to see it in order to check what the problem might be. Note that my test devices were a Xbox 360 controller and a Logitech driving force GT wheel so it should work with any device, but who knows ;)
Cheers,
Dwayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
View and moderate all "Help and support" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
I have a Ferrari 458 non-ffb wheel. I've put the x64 files into the PCars steam game folder where the 64 bit executable is. I have xinput disabled and Dinput change ID enabled. I've set my usb port to 5 in the .ini because that's what the xbox360 driver for the wheel said it was connected to. My problem is there's no input now when I go to configure settings or drive in the game. The part where you enter GUIDs into the .ini is a bit confusing because I'm not sure what line I'm supposed to change to have the GUIDInstance from the log file, I think the readme might be speaking of an older version of the .ini file because it says changeguidproduct and not GUIDproducttochange. Anyway, it's highly confusing why there's no input but it probably has something to do with the port number or me not entering the GUID correctly. Help?
I may not even need to change the GUID because I have a wireless controller and it's turned off so the PC doesn't recognize it, but I do have a wireless receiver that's always on. Anyway. I've tried not faking the device by GUID but the wheel still gives no input in-game.
View and moderate all "Help and support" comments posted by this user
Mark all as spam, and block user from posting to "Discussion"
Sorry for the year late reply :/ (comments needed aproval and I didn't login since last release a year ago so I didn't read your question).
But for anyone that might encounter similar trouble:
Change only the USB port if you have another device/controller connected so the utility knows which one to filter, and this setting is for xinput API only. The GUID is for the same purpose but for the dinput API.
If you have only one device connected it should be automatic. If you don't get any input, enable the log file and see if a log is created and what it contains if it's created (if there's no file log created you probably don't have the correct dll(s) installed). If the log is created I would need to see it in order to check what the problem might be. Note that my test devices were a Xbox 360 controller and a Logitech driving force GT wheel so it should work with any device, but who knows ;)
Cheers,
Dwayne