Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
The support for this wheel must be delivered by the simracing games instead.
Looks like Crew 2 doesn't have official native support for your wheel
https://steamcommunity.com/app/646910/discussions/1/3017941618733395609/
One option is to use a third party tool like x360ce for the Xinput emulation rather than Steam (or maybe even run it through x360ce then through Steam if you like Steam's config options...), but could see if these other stuff get wheel and game to work or get Steam to acknowledge the wheel as the OP request. :D
STUFF 1
Saw something on Reddit but first I'd say disable Steam Input via the per-game setting.
(Right-click C2 in your Steam Library > Properties > Controller > select 'Disable Steam Input')
Then start the game and try the Reddit reply (OP was asking about the PS version of the wheel, don't know about the reply):
https://www.reddit.com/r/The_Crew/comments/18rbnvz/comment/kf3tli6/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
STUFF 2
Let's see if this gets Steam to stop ignoring the wheel.
1. find the Vendor ID (VID) and Product ID (PID) of the wheel:
- run dxdiag (Press Windows key + R, type: dxdiag, choose OK)
- go to Input tab and find the device and you'll see the IDs.
Don't know if you'll see multiple listings for the wheel or just one
(From what I saw online, Thrustmaster VID is 0x044F)
2. place the SDL hint SDL_JOYSTICK_WHEEL_DEVICES_EXCLUDED as a system environment variable:
- Press Windows key + R, type: SystemPropertiesAdvanced, choose OK.
(That should open System Properties on the Advanced tab.)
- Click 'Environment Variables...'
- Under System variables, click 'New...' and use this info
variable name: SDL_JOYSTICK_WHEEL_DEVICES_EXCLUDED
variable value is to be formatted as VID/PID e.g. 0xAAAA/0xBBBB
Use the ID's you got from dxdiag.
- Start/restart Steam.
If that's successful, see if you can map the wheel in Steam. Perhaps you know how to do this.
If no wheel detected, or it doesn't seem to operate in the mapping stage, maybe this:
I see in SDL code that some wheels use one PID in 'initial mode' and another in 'active mode'.
So might want to connect the wheel and run dxdiag for the VID/PID. Then use the wheel somewhere (don't know if the Thrustmaster software would count or if it would have to be other software) and re-run dxdiag for the ID's (while the other software is running??? after the wheel has been used is OK??? Describing it as 'Initial mode' rather than 'In-active mode' implies to me the mode at first connection, and once activated it stays 'Active mode' but dunno, maybe it falls back to 'Initial mode'. I've never owned a wheel so perhaps you have better insight into what the modes could mean, if they do even apply to the T128x...)
Thinking 'Active mode' ID would be the important one but if multiple PIDs format the variable value as VID/PID,VID/PID e.g. 0xAAAA/0xBBBB,0xCCCC/0xDDDD