Hello, I want to use this program to convert my xinput wheel to dinput so it's not recognized as a controller and can be configured as a wheel (project cars 2). Because my xinput device is a racing wheel, I do not want any special effects/deadzone/filtering/etc. I only want the raw data converted from xinput to dinput. Are the default values from the root INI file essentially this? Or do I need to go to Axis > Filter > and uncheck all? I am not using the pcars preset, as I understand it's for a gamepad, so it has filters applied to it. I know how to disable xinput and change dinput device ID and everything works (thank you so much for this program), I just want to make sure I'm getting the raw data from my wheel and no other special effects are being applied from your program. Thank yo so much! - Cory
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
Anonymous
-
2020-07-31
If you tested it and got no input lag (immediate response from your device) then u probably already have raw input :p
Anyway, aside the instructions from the readme.txt, there's the presets folders where you can test the one that fits your device. In your case try the x360 preset for pcars2 as it should work for any xinput device.
But... it seems that there's a new trend in newer games, like the ones from codemasters (Dirt (Rally), F1...), or the very nice game DAKAR 18 in that they don't use the dinput API to query for existing devices but instead use the HID route, which is harder to intercept, so in those games you CAN'T get raw using this utility ;(
But to every problem there's usually some solution xD, in this case: installing the very nice VJOY utility and create a virtual device.
The "problem" I had with vJoy is that none of the feeders I found handled FFB/rumble effects... I'm using a xobx gamepad so playing without any effect felt very flat and not enjoyable at all, although being able to drive without the crappy steering limitations was already worth it).
So I decided to code a feeder in my utility and implement support for vJoy rumble/FFB effects, which was not very hard since I already had a dinput->xinput FFB translation (at least an attempt, I don't have a xbox wheel so I can't test how good or bad the FFB emulation works for those devices). But with my xbox gamepad it makes a huge difference, and also think that it does a better job than most of in-games xinput effects, maybe I'm biased xD, but it's no surprise since the data I use for the effects comes from the game's FFB wheel feed which is usually much more detailed than their xinput effects implementation.
Thing is that I have done this almost a year ago but for diverse reasons I have yet to release an updated version with this feature. Main problem being that I gradually changed many things in the code, implemented new features (macros and other things), inserted some testing portions which I have to clean up, and since it's been about nine months last time I touched it, now I can't quite remember all the things I updated and the bugs I fixed xD, so my main "problem", aside from a quick cleanup of the code is mainly updating the readme.txt which is the biggest and most annoying work to do :p
Meanwhile for the ppl who have a xinput device and would like to test the vJoy method to get raw input (without FFB/rumble) you still can do it but you'll need to disable xinput using my utility or even better only "block" the steering axis by setting a 99% deadzone without having to disable xinput altogether, so in game you'll only have to remap the steering axis to the vJoy axis, and still being able to navigate in the game(s) without any trouble. Yoy'll need to find a feeder tho, can't remember the one I used but it's not hard to find one.
Note that for Dakar 18 only enable 3 axes in vJoy (not sure, can't quite remember) or , for whatever reason, the game won't correctly detect the vJoy device. Anyway, if I finally release the new version I'll put detailed instructions for the tricky games I tested/played...
Funny thing is that the vJoy "trick" doesn't work for pCars1/2 as I was thinking on going full vJoy route, as it would significantly simplify the things. Let's see how pcars3 (arcadish it seems xD) will handle the devices as the trend from developers seems to not use the dinput route anymore...
Dwayne
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello, I want to use this program to convert my xinput wheel to dinput so it's not recognized as a controller and can be configured as a wheel (project cars 2). Because my xinput device is a racing wheel, I do not want any special effects/deadzone/filtering/etc. I only want the raw data converted from xinput to dinput. Are the default values from the root INI file essentially this? Or do I need to go to Axis > Filter > and uncheck all? I am not using the pcars preset, as I understand it's for a gamepad, so it has filters applied to it. I know how to disable xinput and change dinput device ID and everything works (thank you so much for this program), I just want to make sure I'm getting the raw data from my wheel and no other special effects are being applied from your program. Thank yo so much! - Cory
If you tested it and got no input lag (immediate response from your device) then u probably already have raw input :p
Anyway, aside the instructions from the readme.txt, there's the presets folders where you can test the one that fits your device. In your case try the x360 preset for pcars2 as it should work for any xinput device.
But... it seems that there's a new trend in newer games, like the ones from codemasters (Dirt (Rally), F1...), or the very nice game DAKAR 18 in that they don't use the dinput API to query for existing devices but instead use the HID route, which is harder to intercept, so in those games you CAN'T get raw using this utility ;(
But to every problem there's usually some solution xD, in this case: installing the very nice VJOY utility and create a virtual device.
The "problem" I had with vJoy is that none of the feeders I found handled FFB/rumble effects... I'm using a xobx gamepad so playing without any effect felt very flat and not enjoyable at all, although being able to drive without the crappy steering limitations was already worth it).
So I decided to code a feeder in my utility and implement support for vJoy rumble/FFB effects, which was not very hard since I already had a dinput->xinput FFB translation (at least an attempt, I don't have a xbox wheel so I can't test how good or bad the FFB emulation works for those devices). But with my xbox gamepad it makes a huge difference, and also think that it does a better job than most of in-games xinput effects, maybe I'm biased xD, but it's no surprise since the data I use for the effects comes from the game's FFB wheel feed which is usually much more detailed than their xinput effects implementation.
Thing is that I have done this almost a year ago but for diverse reasons I have yet to release an updated version with this feature. Main problem being that I gradually changed many things in the code, implemented new features (macros and other things), inserted some testing portions which I have to clean up, and since it's been about nine months last time I touched it, now I can't quite remember all the things I updated and the bugs I fixed xD, so my main "problem", aside from a quick cleanup of the code is mainly updating the readme.txt which is the biggest and most annoying work to do :p
Meanwhile for the ppl who have a xinput device and would like to test the vJoy method to get raw input (without FFB/rumble) you still can do it but you'll need to disable xinput using my utility or even better only "block" the steering axis by setting a 99% deadzone without having to disable xinput altogether, so in game you'll only have to remap the steering axis to the vJoy axis, and still being able to navigate in the game(s) without any trouble. Yoy'll need to find a feeder tho, can't remember the one I used but it's not hard to find one.
Note that for Dakar 18 only enable 3 axes in vJoy (not sure, can't quite remember) or , for whatever reason, the game won't correctly detect the vJoy device. Anyway, if I finally release the new version I'll put detailed instructions for the tricky games I tested/played...
Funny thing is that the vJoy "trick" doesn't work for pCars1/2 as I was thinking on going full vJoy route, as it would significantly simplify the things. Let's see how pcars3 (arcadish it seems xD) will handle the devices as the trend from developers seems to not use the dinput route anymore...
Dwayne