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
Discussions Rules and Guidelines
0 
Report this post
Your Steam Client offers a controller interface, it can cause problems if you are using another driver/app/emulator for your device.
There is a switch to turn these setting on/off for each game. Right click on the game in steam library and choose properties. "Steam Input Per-Game Setting" ; “Use your Global Steam Input" for on, "Force Off" to disable. Select Force Off.
.............
Wheel/controller configuration save is located within your encrypted main game save and can be deleted when entering the game.
When you launch the game and it reaches the splash screen that says ‘press start to enter’ you need to use a button on the wheel / controller or the return/enter key (enter with left arrow) on KB. Using the normal enter key or mouse will delete you previous wheel configuration save and will require rebinding the wheel to game.
.................
For wheels, you should find a list of supported devices in the 'read me' file in the main game folder. Non supported can be entered as direct input or a custom input xml can be made, custom file is the best option.
......
Using direct input, this guide should get you started
https://steamcommunity.com/app/310560/discussions/0/451852571445075283/
If you find steering input slow with this option, you may have to adjust the dinput_default input xml file for deadzone and saturation limits. Default deadzone is likely to be '0.2' 20% for gamepads, you want 0% for most wheels.
Long version explained here;
https://steamcommunity.com/app/310560/discussions/0/615085406669620765/
.........
For custom xml for your device, you will need the PID & VID ( product and vendor USB ID ) numbers for your device. You can modify an similar device file, fooling the game to see it as a existing supported device, or create a new file with your device name- this requires more work. If you need help with this let me know.
I set "forced off" on the "per-game setting", and then I enter the game and try to follow the instructions on the link you posted as "direct_input". I cannot follow the instructions on that link, because my wheel are not recognized as wheel... There isn't the "direct input" on preset and so I don't have the possibility to change from gamepad to wheel by pressing F1.
That wheel works perfectly in Grid autosport and is recognized as "speedlink darkfire", so I copied the file "sl_darkfire.xml" from the grid input folder and paste in dirt rally input folder, nothing changed.
If I leave it as gamepad, it works... But is unplayable because there is a big lag between my input and the effect of steering, and the steering angle change with speed. Is not direct input.
If you add or create a new input xml, you need to add a action map path before the game will recognize it. For this game, those are also within the "input" folder - in a file named " paths.xml".
For this file, try opening with 'note pad' as this will be easier to see the commands.
Copy one complete line under "<!-- Action map presets -->" from "<xmlreader" to the end "userdata="presets" /> " and paste it just below that line.
Now edit that new line after " filename="input/ " to match your xml file name " sl_darkfire.xml "
Save before exit. If your xml from grid is a match, the game should now see your wheel in the controller setup menu.
.......................
If you have problems with the way the wheel or buttons respond, you may need to edit that xml from Grid. These files can be opened with word pad or note pad.
If you open one of the existing file from Dirt Rally, you will see categories sections like;
<!-- In Game Actions --> ,
<!-- FE Actions -->,
<!-- Replay/Youtube Actions -->.
Sometimes they may change these names from one game to the next, they need to match the game you are trying to use it in.
The repeated basic command "<Action id=" and "<Axis id=" may be worded differently between the games.
.................
If you ever reopen an edited file with 'explorer', it may appear empty. Close and reopen with notepad or wordpad.
I believe this game offers FFB (directional motor driven force) and vibration motor output for game pads and lower end wheels.
Inside "options & extras", under "choose preset", I have:
- CONTROLLER PRESET 1
- CONTROLLER PRESET 2
- Preset 2
- Keyboard (azerty)
- Keyboard
I compare the two files, "sl_darkfire.xml" that I copied from grid folder, and "sl_strikefx.xml" already in the folder, they are very similar, I think the two games use the same "language".
Between the "ActionMap" tag, first line, the wheel xml have this one added, after "priority":
force_wheels="true"
So, I try to add this line on "xinput_pad_1.xml", because I thought is one of the recognized setup.
Again, nothing changed.
To be sure, I try to reboot steam, play the game without steering wheel connected, now in "choose preset" I see only the two keyboard setup.
Then, I connect the wheel, in "choose preset" appear again the three gamepad preset, I try all of them but nothing changed
Oops, I did not see the SPEEDLINK Strike FX Gamepad support or the xml in this game when I looked the first time.
"I have a generic gamepad and a budget steering wheel."
Would that game pad be the Strike FX, and the Darkfire wheel a separate device?
............
Can you find the PID & VID ( product and vendor USB ID ) numbers for your wheel and the game pad? The game uses these to offer presets.
On Windows; Finding the PID and VID of your USB devices. You will need to have your wheel powered up for your PC to see it in ‘devices’ or ‘device manager’ which ever location is easier for you to find.
Right click on the wheel for the properties page. Select ‘Hardware’ in the top of the box. Click on the HID or USB (it does not matter which one) for a new box and select “details” at the top. Under ‘Property’ is a drop down option- select ‘ Hardware ID ’ (should be near the top of the list). In the value box below are the numbers/letters we need.
You should see something like ‘ USB/VID____&PID------‘ . make a note of the first 4 digits of the VID and PID numbers/letters. If they are more than 4 digits, use only the first 4 and ignore the rest. Do the same for your game pad.
Looking in the existing SPEEDLINK file, the VID should be 0E8F for any of their devices.The PID should be different for each model they offer.
When you put those 8 numbers together (PID & VID), they are the beginning of the string within the xml file for ID. Near the top of the file you should see this
device_type="{________-0000-0000-0000-504944564944}
with that blank space filled with PID VID numbers in that order. Make sure there is no extra spaces between the { } or it will fail.
'device_type=' states it is the primary device or when there is more than one USB for the wheel set (pedals, shifters on separate USB hookups) it would be 'device_type_0='.
When the game launches it scans you USB device IDs that are plugged in and offers any one that matches 'device_type=' or 'device_type_0=' within all of the xml files.
Any match should show by name under "choose preset". It's best to unplug game pads if you are using a wheel, sometimes they can cause interference and the game will show less offers as presets.
Check inside your Grid xml and see if the IDs match your wheel, those first 8 numbers/letters.
........................................
- CONTROLLER PRESET 1
- CONTROLLER PRESET 2
- Preset 2
- Keyboard (azerty)
- Keyboard
Did you have more than your wheel plugged in? If the ID numbers in the Grid file was the same as the pad file, could explain the multiple options.
When you launch the game and it reaches the splash screen that says ‘press start to enter’ you can use the regular enter key or mouse ( not the return/enter key (enter with left arrow) to clear your previous config save. This might help when you are testing the changes you have made to the files.
.......................
" Between the "ActionMap" tag, first line, the wheel xml have this one added, after "priority":
force_wheels="true"
So, I try to add this line on "xinput_pad_1.xml", because I thought is one of the recognized setup. "
I think the "xinput_pad_1.xml" is for the Xbox 360 game pad, not sure what you were doing whit that one.
I don't recall the line force_wheels="true" used in these preset xml's for this game. I don't work for CM, but I have helped a few players getting mismatched wheel sets, DIY, and button boxes into the mix of inputs. You might want to explore other xml files for wheels in Grid and see if that line is used for others.
Does Grid offer advanced wheel settings when you are in the menu? They may have added support for this device deeper within the game files that does not exist within this title.
.......................
Keep in mind if you mess up these files and can not remember where/what you changed, you can always delete the one sub folder and verify the game files through Steam to download a fresh start.
.......................
.......................
What type of wheel is this? FFB or vibration motors only? Degrees of rotation? Does it require a driver software app? Could not find much info when I searched darkfire wheel.
There may be another way, changing the ID within another xml file, and the game would see it as a device that has internal support.
Post your PID / VID info for your devices and the xml from Grid.
I add the paths of sl_darkfire.xml in both files, nothing changed.
The game pad is a chinese bluetooth gamepad for smartphone. I try if it works with these games, but usually I don't use it.
So, if the wheel is connected, the gamepad is not.
In linux, the command to see the properties of the USB hardware is "lsusb" (to be typed in a terminal).
These are the information of the wheel as recognized by the OS:
Bus 001 Device 004: ID 0e8f:0003 GreenAsia Inc. MaxFire Blaze2
If you search on google "maxfire blaze2" you find a joystick... maybe is the same hardware, in a different "box".
So, VID is 0e8f, PID is 0003, and the device_type on the xml file is correct.
I check all the xml files and only "sl_strikefx.xml" have this VID and PID (and sl_darkfire, but i copied it so...).
>Did you have more than your wheel plugged in? If the ID numbers
>in the Grid file was the same as the pad file, could explain the
>multiple options.
No, only the wheel. I don't know why I see multiple options (and all of them are gamepad, not wheel).
I see the same three options before I copied the xml file from grid as well. So nothing changed after I copied that file.
>When you launch the game and it reaches the splash screen that
>says ‘press start to enter’ you can use the regular enter key
>or mouse ( not the return/enter key (enter with left arrow)
>to clear your previous config save. This might help when you
>are testing the changes you have made to the files.
If I start the game by pressing enter in the keyboard, it remain the gamepad configuration... seems like it don't clear the previous setup.
>Does Grid offer advanced wheel settings when you are in the
>menu? They may have added support for this device deeper
>within the game files that does not exist within this title.
No, only the normal settings.
>Keep in mind if you mess up these files and can not remember
>where/what you changed, you can always delete the one sub
>folder and verify the game files through Steam to download
>a fresh start.
I'm sorry I can't understand this sentence, are you telling that if I delete the entire input folder, it was recreated by steam?
>What type of wheel is this? FFB or vibration motors only?
>Degrees of rotation? Does it require a driver software app?
>Could not find much info when I searched darkfire wheel.
The wheel is a "GMB Gaming", but you can find it in amazon or ebay with other names. Is a cheap wheel without FFB, 90° of rotation. I'm using it without specific driver, I've just plugged it on usb port and it works. In it's box there is a CD with driver, but is windows-only.
>There may be another way, changing the ID within another
>xml file, and the game would see it as a device that has
>internal support.
I try, again, nothing changed. Looks like every modify I do is not seen by the game.
Moreover, I don't understand why I don't see "direct input" on the presets.
I don't understand why in grid all works, and in dirt rally not...
How can I add the xml file here? I have to copy/paste?
- dinput_default
- feral_paths
- icons
- keyboard
- keyboard_azerty
-mouse
-paths
-strings
After that, in "choose preset" I have keyboard, keyboard (azerty) and it appear CONTROLLER PRESET 3. In this one, I can change from gamepad, joystick or wheel by pressing F1. I set Wheel, but, again.... nothing changed! Always seen as gamepad
..........
>If I start the game by pressing enter in the keyboard, it remain the gamepad configuration... >seems like it don't clear the previous setup.
The controller config save is in the main encrypted game save file and that is tied to cloud save and could be over write if used. I think it would show a warning of difference between files.
...........
>Keep in mind if you mess up these files and can not remember
>where/what you changed, you can always delete the one sub
>folder and verify the game files through Steam to download
>a fresh start.
>I'm sorry I can't understand this sentence, are you telling that if I delete the entire input folder, >it was recreated by steam?
Only if you needed to start over and you would have to manually command a file check / verify the game files through Steam. It could be quicker than a reinstall of the whole game.
..................
>These are the information of the wheel as recognized by the OS:
>Bus 001 Device 004: ID 0e8f:0003 GreenAsia Inc. MaxFire Blaze2
>If you search on google "maxfire blaze2" you find a joystick...
>So, VID is 0e8f, PID is 0003, and the device_type on the xml file is correct.
>I check all the xml files and only "sl_strikefx.xml" have this VID and PID (and sl_darkfire, but i >copied it so...).
With the SPEEDLINK Strike FX Gamepad support of the "sl_strikefx.xml" using the same PID, there could be something deeper in the game code (encrypted files) that will not let it be seen as a wheel. This could prevent you from using soft lock feature, although a 90* or 180* DOR wheel would not benefit from soft lock, you would likely want full DOR.
Not sure if there is any difference within the Grid xml, looking in the Strike file I see;
<Action id="Steer Left">
<Axis id="di_x_axis" type="biDirLower" deadzone="0.2" saturation="1.0" />
<Axis id="di_slider_0" type="biDirUpper" deadzone="0.0" saturation="1.0" />
</Action>
<Action id="Steer Right">
<Axis id="di_x_axis" type="biDirUpper" deadzone="0.2" saturation="1.0" />
<Axis id="di_slider_0" type="biDirLower" deadzone="0.0" saturation="1.0" />
The dual '<Axis id=' lines offers both inputs of x axis and slider, could be to cover different devices made by this company, and they could be sharing ID's with others. I'm sure they have to register these numbers with some official agency, might be trying to save cost.
*Note the dead zones of "0.2", that is 20% in both directions from center. This might work for a game pad but would create your complaint of delayed steering. Change all 4 of those to "0.0" and see what happens. Raising or lowering the saturation number from "1.0" could change the speed of input response. In the event of a brake pedal that does not always return to zero causing the brakes to drag, you might want to add a touch of dead zone - "0.1" , if the game will not allow it in the setup menu.
Near the top of the file
device_type="{00030E8F-0000-0000-0000-504944564944}" priority="6">
you might want to try a different priority number. I have not checked them all but most of the wheels use "0" , I see game pads using 1,5,6,or 7. Have not tested this option yet to see what it does.
.......................
.......................
>There may be another way, changing the ID within another
>xml file, and the game would see it as a device that has
>internal support.
The old MS Sidewinder wheel is supported in this game and was a 180* DOR without FFB. It might have vibration motors in the rim similar to the Xbox game pads.
If you can't get your wheel to respond properly you might be able to use that xml.
looking in that file, the top part;
<!-- Action map for the Microsoft Sidewinder FFB Wheel -->
<!-- Supported for driving and replay control only - A keyboard is required for all menu controls -->
<ActionMap name="ms_sidewinder_ffb" device_type="{0034045E-0000-0000-0000-504944564944}" priority="0">
Delete some of this down, change the ID number so you have
<!-- Action map for the Microsoft Sidewinder FFB Wheel -->
<ActionMap name="ms_sidewinder_ffb" device_type="{00030e8f-0000-0000-0000-504944564944}" priority="0">
swap out everything under
<!-- In Game Actions -->
with one of the SPEEDLINK files, be sure to change those dead zones too.
You would want to remove the other SPEEDLINK xmls as they would share the sane USB ID's.
The game would then see your wheel as the Sidewinder and should offer that by name for preset device. This might allow you to get advanced wheel settings within the game menu if they offer that for the Sidewinder.
.......................
.......................
Another possibility;
>..I enter the game and try to follow the instructions on the link you posted as "direct_input". I >cannot follow the instructions on that link, because my wheel are not recognized as wheel... >There isn't the "direct input" on preset and so I don't have the possibility to change from >gamepad to wheel by pressing F1.........
This option might allow the advanced wheel option to show.
If there was no xml,s with your device ID numbers, the game should offer it as a un-known device. From there you should be able to select wheel with the F1 key. This should set it up as a direct input device and use the dinput_default.xml . You would need to map each action in the game controller menu, as there is almost no presets (including dead zones) in that xml. Most are just command names.
When you look into that dinput_default.xml file, you will see some menu selection actions presets. If you are not allowed to remap any of those actions in the game controller setup menu, you can manually change / add the <Axis id="di_button_ numbers to your desire ( you can do this in any xml file too).
You will have to set it one digit less than what you PC recognizes, for example - button # '1' on your wheel would need to be '0' within the xml.
..............
..
Note that all of these xml's have category sections to allow multiple actions from one input/button without causing interference in different game operations.
<!-- In Game Actions --> ,
commands in this section can only respond while driving/on track mode.
<!-- FE Actions -->, or <!-- Menu Actions -->
commands in this section can only respond while in the menus.
<!-- Replay/Youtube Actions -->.
commands in this section can only respond while viewing replays. The Youtube reference is leftover from earlier console games that offered direct uploads of replays.
<!-- Spectator Actions -->
......
Each command line for presets should start with
<Action id="......name.......">
<Axis id=".....input type....." />
</Action>
If there is multiple input devices, there can also be ' restricted_device= ' followed by the USB ID if needed to prevent crossing input commands. Something you shouldn't need with your wheel.
In some of the wheel files, command options might not be available for presets, most of the time you cam map them in the setup menu. You can add those action commands from other xml files.
You can find some extra command lines in the key board & dinput xml's, like wipers, headlights..... if you are having troubles mapping them to your wheel when using a dedicated xml file.
.............
Hope you can find something useful out of this wall of text.
These are in reference to the popup on screen display numbered options that can be seen near the bottom of your screen; restart, continue.....
- feral_paths.xml
- icons.xml
- ignore_presets.xml
- keyboard.xml
- keyboard_azerty.xml
- mouse.xml
- ms_sidewinder_ffb.xml
- paths.xml
- sl_darkfire.xml
- strings.xml
And then I modified the first line of ms_sidewinder as:
<ActionMap name="ms_sidewinder_ffb" device_type="{00030e8f-0000-0000-0000-504944564944}" priority="0">
and replace all the in-game actions with that of darkfire file.
So I start the game, press "Enter" from the keyboard, go to the options, choose presets.... again, no change! Now there is:
- keyboard
- keyboard azerty
- CONTROLLER PRESET 3 (Gamepad)
it's strange the third preset, because I delete the file "dinput_default.xml". By pressing F1 I change from "gamepad" to "wheel", so I go back to mapping the behaviour, again remain the advanced option for gamepad, not wheel!!!
I close the game, connect the joystick (only to try), go to preset and select "CONTROLLER PRESET 3 (wheel)".
When I go back, I map the left stick of the joystick as steer left-right, and appear:
- steer left left (and there is an image of the wheel)
- steer right right (and there is an image of the wheel)
And appear the command "advanced wheel setup", where I can setup deadzone, saturation and so on.
This is the joystick, and works (but, again, I delete the file "dinput_default.xml" so for me is strange that works).
I repeat the exhact same operations with the wheel.
Now in "choose preset" there is two times "CONTROLLER PRESET 3 (wheel)", I try both, and with both I can't map the steering wheel left or right (they are light grey and I cannot change), but I try to use the wheel and don't work.
Before to connect the gamepad, I do the same operation with the wheel, I choose "CONTROLLER PRESET 3 (wheel)" and, when I map the steering, appear:
- steer left left (and there is an image of LS)
- steer right right (and there is an image of LS)
but in this case I don't have "advanced wheel setup", I have "advanced gamepad setup".
I really don't know what to think...
Normally, I would say "ok, my wheel don't work"... but this wheel works perfectly on grid, that's why I can't understand.
..........................
Did some testing with the "choose preset" drop down list with the Windows version and with the USB devices i had available.
XBox 360 wireless pad, XBox wireless speed wheel, 2 Fanatec wheels. All were supported devices for this game showing in the preset list by name and the F1 key had no effect on any of them.
The game pad was shown with three options
Xbox 360/One Controller
Preset 1
Preset 2
This would match the 3 xml files xinupt_pad_0, _1, and _2 .
Crawled though the wheel thread, found this post on a HORI Racing Wheel being seen as an Xbox pad, maybe a xinput device?
https://steamcommunity.com/app/310560/discussions/0/451852571445075283/?ctp=4#c1696043263498842854
The other USB's, with ID's in my wheel xml but not as primary devices as described earlier, were listed as "Direct Input Device" . The F1 key would change those names to "Direct Input Device [wheel]", "Direct Input Device [Game Pad]" . With any of them set to wheel, "Advanced Gamepad Settings" was the only option available.
Th MS Speed Wheel is a handheld U shape controller with motion sensor steering with 180 DOR lock to lock. It offered "Advanced Wheel Settings" which is useless for a device like this. The wheel calibration has 2 steps designed for 900 & 1800 DOR wheels. 1. Turn to full lock 2. Turn to 90 degrees from center. There is no difference in a 180 degree wheel !
Soft lock is for 900 & 1800 DOR wheels, automatically reducing to the 4 options; 900, 810, 720, 540 depending on car used.
And that is all the additional adjustment with Advanced wheel. You did say 90 degree wheel, I assumed that was from center to lock = 180 lock to lock.
.......................
The Linux version might not list all devices by name like the Windows version, replacing the option to Controller #. If F1 key works, it should be a un-supported device. Setting it to wheel does not always allow Advanced Wheel setting. There may not be any way to override a xinput beyond Xbox pad which might include the single preset # lines. Advanced Wheel setting does not offer much or any advantage for a 180 DOR wheel.
............
With your main complaint of "unplayable because of the delay with steering", something that Steam Controller" users often say, can be solved by changing the xml steering dead zone from "0.2" to "0.0". That "0.2" remains even with dead zone set to zero in the menu.
Which xml would be hard to guess when it only offers Controller by name. Di_input, xinput, strike FX, custom? You could try to shotgun it and change them all. And this is still on the guess that the Linux version will respond like the Windows version.
.............
Another tip is not to remap the escape pause button in the menu, some have reported a save problem.
................
Feral Interactive has been making the Linux port of these games, their support contact info can be found in the pinned thread above in this forum. Maybe they can give you a answer.
You might check the "read me" file in the main game folder, Feral may have added something different than CM.
>available.
Ok, so you confirm what happen with my steering wheel?
>Advanced Wheel setting does not offer much or any advantage for a 180 DOR wheel.
Right, but the advantage is not on the regulation... if there is "advanced gamepad settings" instead of "advanced wheel settings", the devices is recognized as gamepad... so, there is "soft lock" (in any turn you must steer full left or full right, and the angle of steering change with speed) and the steering is slow, is not direct. This mean that is very difficult to drive (almost impossible to control an oversteer, for exhample).
I try with keyboard... and, compared to the steering wheel recognized as gamepad, is better the keyboard.
>With your main complaint of "unplayable because of the delay with steering",
>something that Steam Controller" users often say, can be solved by changing
>the xml steering dead zone from "0.2" to "0.0". That "0.2" remains even with
>dead zone set to zero in the menu.
It's not a problem of dead zone. If I steer instantaneously, in the game the steer must turn instantaneously. If the wheel is recognized as wheel, this happen. If it is recognized as gamepad, it take some time, it have kind of "damper".
>Which xml would be hard to guess when it only offers Controller by name. Di_input,
>xinput, strike FX, custom? You could try to shotgun it and change them all.
>And this is still on the guess that the Linux version will respond like the
>Windows version.
Sadly, I try to delete all the xml except one, and modify this one. I see only this one on the menu, but remain the problem that the steer is recognized as gamepad.
>Feral Interactive has been making the Linux port of these games, their support
>contact info can be found in the pinned thread above in this forum. Maybe they
>can give you a answer.
>You might check the "read me" file in the main game folder, Feral may have added
>something different than CM.
I try to contact them, the answer was like "it's your s**t" (well, not with these word... but the meaning is the same).
At this point, I think that the only possible way is to remap the wheel using a software like vJoy. Sadly this software is windows-only, and I don't found a linux alternative
I had started to look into Linux when Windows was upgrading to 10, but found it offered almost no wheel support except for Logitech. It would be a downgrade to use older firmware on my Fanatec that offers a Logitech emulator to support Logitech drivers. Plus all the other apps for dashboards, LEDs, shakers and motion rigs.
...............
>It's not a problem of dead zone. If I steer instantaneously, in the game the steer must turn >instantaneously. If the wheel is recognized as wheel, this happen. If it is recognized as >gamepad, it take some time, it have kind of "damper".
What you are describing could be non-linear input. Steam controller users have posted this problem when using it in motion sensor mode. The fix was to remove that 0.2 deadzone in the appropriate xml file.
........
When you had all the original files in the game, you had options of "- Preset 2", this is similar to what I saw with the 360Xbox game pad which is a xinput device. Most wheels are a direct input device as there is not the limitations of button inputs for H-shifters and extra buttons on the wheel face, lower end wheels could be xinput.
..............
Found this for supported wheels, maybe try changing the ID in one thees xmls to match your device.
https://support.feralinteractive.com/en/mac-linux-games/dirtrally/faqs/wheels_linux/
I send a second mail to feral support, as an answer of the first mail they answered me... And their answer is exatly the same of the first one, they did copy/paste.
So, because I'm planning to buy some games that are Windows-only, I decided to bought a second hard drive and install Windows in it.
I will try if in Windows there are the same problem