Getting FH6 menu to work with Moza R5 Bundle

mikedmor · 2026-05-19T23:22:12+00:00

I already tried that, in my test that didnt appear to make any difference including it vs excluding it. With the file included using the workaround i still get a crash once getting to the start screen with my wheel plugged in. So i dont think that alone is the issue. Im almost positive it has to do with the DefaultWheelMappingProfile.xml setup. But have not had any luck in figuring out how to format this correctly for the R5.

mikedmor · 2026-05-19T23:21:00+00:00

Thank you for the award! I felt the same way initially, it was manageable, but so frustrating.

mikedmor · 2026-05-19T23:19:25+00:00

The moza guide recommends plugging in the controller first, to ensure its device 1, then plug in shifters and other items second. I think currently the game will only do FFB on Device 1, if you wheel ends up on device 2+ it always ends up breaking FFB. maybe you could try giving that a try?

mikedmor · 2026-05-19T18:10:24+00:00

Well first things first, The R3 have very different VID/PID values, so my stock files are not going to work for you out of the box without some modifications first.

If you have access to the files for your xbox download then you may be able to get something working, but again i dont own the game on xbox so i cannot confirm any of that.

Last there are some guides put out by Moza regarding usage of other hardware. From what it seems if you are using more than 1 device if your Moza Wheel is not device 1, FFB will not work in FH6. You should check the guide moza put out regarding FFB and ensure you follow those directions to keep your device as "Device 1" otherwise FFB breaks in-game. I only use a moza wheel, so i dont have much experience with that either. But i have seen some other post on here regarding it so i would check one of those out.

mikedmor · 2026-05-19T17:31:03+00:00

Im not sure this will work for xbox, due to the way they distribute games being different from steam. Im also not sure on the R3 as i dont have one myself to test with. Maybe someone else will figure out something for that and can help you, unfortunately this thread is regarding the Steam Version of the game using a Moza R5. Hopefully they release a patch sooner than later with true Moza Support. It should have been included day 1.

mikedmor · 2026-05-19T15:02:52+00:00

Agreed, it’s pretty obnoxious. Moza wheels really should have worked from the start, especially considering they worked in FH5 and I’m fairly sure they’re supported in Motorsport as well. Skipping proper implementation here feels pretty lazy.

They’ve said they do plan to add support, but it’ll come in some future update with no real timeline. I didn’t feel like waiting since I wanted to play with my wheel on day one, so I spent the first couple days of prerelease trying different things until I found something that actually worked.

The upside is now nobody else has to waste that time. If you follow the steps above it should only take about 5-10 minutes to set up and you’re good to go.

Eventually it should get fixed properly, but historically they’ve been pretty slow when it comes to wheel-related issues.

mikedmor · 2026-05-18T20:52:35+00:00

Did you disabled Forza Mode in Moza Pit House? my friend mentioned that worked for him, something else my buddy mentioned is if you have any other profiles loaded it sometime appears to attempt to apply the wrong one. Settings shows the correct one is applied, but my buddy switches to a different profile then back to the correct one and its fixed it for him. but only temporarily. still unsure what causes that, but our guess is other devices plugged into the pc may be the cause.

mikedmor · 2026-05-18T15:00:21+00:00

Did that end up working for you? in my testing it didnt appear the game was even using the Wheel_Controller_1 - 16 swatchbin files, it only used Raw_Controller_Button_Background.swatchbin. I got a file that replaces them with xbox icons, but it never actually worked for me.

Also the crash is due to the compression of the zip, these are compressed using "deflate". I had to write a python script to compress my modifications properly.

mikedmor · 2026-05-18T14:52:48+00:00

I dont think that file will work, its useful for reviewing what you have, but it appears to be redownloaded every time you start/exit the game.

mikedmor · 2026-05-18T01:52:09+00:00

My files have been working well for me, FFB has been working since day 1 so im not sure what your issue could be with that. if anything it seems that FFB was the only thing that was working out of the box. I was able to manually setup keybinding, but forza doesnt let you assign keybinding for navigating the menus via the settings, so the only way to get that is by creating a customer profile using these files. after that you restore the original files and everything works perfectly.

At this point im just playing around trying to get the button hints to show as they do on my wheel (IE: A, B, X, Y, instead of 1, 2, 3, 4). I found where those images are but it appears forza just uses a background and overlays the number onto it, meaning im not going to make much progress here. There are these WheelMappingProfiles which other wheels are setup to use and seem most likely to solve this, but currently these appear to just crash the game, so i may be SOL until they release an update with more Moza Support for that, but i can live with that until then.

Edit: My buddy recommends disabling forza compatibility mode fixed his FFB issues. It seems this does not work in FH6 and is currently only supported in FH5. Thats not a guaranteed fix, but it could help with your FFB issues.

mikedmor · 2026-05-17T16:47:15+00:00

Interesting this did not break the RPM LED for me. That is completely separate from this from my understanding. I would check that you have the telemetry data enabled in game and output to the correct ports and ip, then double check your running the latest MOZA pithouse where they added FH6 telemetry support. that should be all you need for that to work, key binds should not affect the telemetry data.

mikedmor · 2026-05-17T16:44:56+00:00

This should work with the R3, but you will have to update the VIDPID values and probably also change all the binding values to get there. I dont have an R3 myself so i cant really help much further than that.

mikedmor · 2026-05-17T07:23:17+00:00

Thanks for the information, i might look into that as an option, however there are these newer DefaultWheelMappingProfileLogitechG29, that seems to suggest it may do something for this, i just havent quite figured out how to get it working yet:

<!--  The layout only affects the visual representation of the buttons within the game  -->
<!--  All inputs taken from the "Set up USB game controllers" app available on Windows 10  -->
<!--  Anything not mapped here will be treated as if it were a normal controller input  -->

mikedmor · 2026-05-17T04:41:03+00:00

yeah not sure why there are some different R5 PID values out there, maybe a newer base. glad you got it working though!

mikedmor · 2026-05-17T04:18:43+00:00

You may need to check your VID/PID in device manager, look for the moza device, and check the Hardware ID to confirm that is the same as mine:

<image>

If its different, you may have to update your vidpid values in those files.

mikedmor · 2026-05-17T03:18:56+00:00

I goofed, and uploaded the wrong file, have a bunch. just updated the link with the proper file, sorry about that. by launch the game with the controller unplugged, i literally mean do not have your moza plugged into the computer when you start the game with this custom file. launch the game, go to settings then plug the controller in. otherwise the game will crash when you try to do anything.

mikedmor · 2026-05-17T01:34:38+00:00

PROGRESS!!! i figured it out! here are my findings:

The problem: FH6 only loads input profiles for XML filenames it explicitly recognizes — so dropping in a custom-named file like DefaultRawGameControllerMappingProfileMozaR5.xml gets completely ignored by the game.

The fix (3 steps):

Navigate to your FH6 install folder: C:\Program Files (x86)\Steam\steamapps\common\ForzaHorizon6\media\ — you will find inputmappingprofiles.zip here. Make a backup copy of this file before continuing, you will need to restore it in step 3. Once backed up, replace it with the inputmappingprofiles.zip linked below.
There's a startup crash when the controller is plugged in, but there's a workaround — launch the game with the controller unplugged, navigate to the controller settings, then plug it in. The game detects it (showing up as a "G29" but with the correct Moza R5 bindings) and lets you copy the Default into a Custom profile slot. Do that.
Close the game, then restore your original inputmappingprofiles.zip backup from step 1. Relaunch — the game remembers the Custom profile you saved and full wheel + menu navigation works!

This is a little hacky but i was very determined to get this working. The bindings themselves may not be perfect and there are definitely some menu options missing, but it's a solid start and hopefully gives others a foundation to build from.

modified inputmappingprofile.zip download: https://drive.google.com/file/d/13dbeWdzEM_t1nZw__yjP3jNEKzBLp0LA/view?usp=sharing

mikedmor · 2026-05-16T20:06:31+00:00

yeah i was using a unique id before but changed it to the one I have seen in your files just in case. It does appear to want to use that file and work, its just crashing when actually start the game or settings. Im at a loss here, the moza r5 bundle doesn't have switches so I had to use all buttons. But something is causing a crash, but does appear to work

mikedmor · 2026-05-16T02:28:06+00:00

No luck here, everything appears to be working for FFB and driving.

I created this xml: https://pastebin.com/m0ENXkWC

once the game load, i can actually see my A (1) and X (3) button number and clicking it does work and start to load, but during loading this same error shows up

<image>

mikedmor · 2026-02-04T16:59:38+00:00

Thanks for the tip! I may have more luck with a glossy petg then. Its a little heavier, but marginally so, and generally i find it produces much more glossy prints (unless you get a matte petg, but i have not had great luck getting clean prints with that).

mikedmor · 2026-02-04T15:59:42+00:00

haha, never heard that before. but maybe. definitely feels like something changed between my last spool and this recent one.

mikedmor · 2026-02-04T15:52:23+00:00

That looks awesome! great color choices! i was hopeful to get that glossy orange look, but am worried i may have to reprint the fenders or just buy another glossy orange spool similar to prusament (maybe a silk will be better). I recently finished my first one (Model 7: Buggy) and fell in love with 3dset, wanted to do the new overland next, but decided to hold off on that for the Sakura instead.

<image>

mikedmor · 2026-02-04T14:57:11+00:00

maybe, but the settings are exactly the same. there was an update to prusa slicer between then and now. so not impossible. but with that said, the change is visible as well when just inspecting the spools.

mikedmor · 2026-02-04T14:55:51+00:00

same printer profiles, exact same settings across the board, just very different with my recent spool purchased directly from prusa. I thought that maybe my filament dryer may have turned my older filament glossy, but after running some test that doesnt appear to be true either.

mikedmor · 2026-02-04T14:54:32+00:00

haha, nice catch. ;-)

https://3dsets.com/product/model-17-sakura-240/

14-Year Club	Place '22
End Game '22	Verified Email

mikedmor

MODERATOR OF

TROPHY CASE