I’ve written a script that will convert 2020 control profiles XML to the 2024 format. However I see in the SDK documentation it specifically says we should NOT be generating our own XML inputprofiles:
Is there anything specific that prevents us from doing so/will it cause any issues beyond messing with the controls a bit? I found by dragging the new input profiles into the correct folder and then starting/restarting the sim they showed up and appear to be working.
Not sure if anyone from the MSFS team might be able to weigh in here. Would be happy to publish the tool for the community if there’s no critical issues I’m overlooking. Don’t want to cause issues for anyone else!
PS. Absolutely loving the new sim, I’m addicted to career mode!
I suppose ‘script’ maybe isn’t the best term here - because of the differences between 2020 and 2024 format it does require some user inputs so I’ve currently got it setup as a small webapp - but yeah, I suppose I could put together some instructions and toss it up on a public domain as a sort of ‘beta’ test
My only concern is if doing this causes any further issues for users since it’s specifically warned against in the SDK (which I did not read until I was almost finished haha)
When I finally found the controller profile files under the cryptic path
“c:\Users\USERNAME\AppData\Local\Packages\Microsoft.Limitless_8wekyb3d8bbwe\SystemAppData\wgs\00090000088D1313_000000000000000000000000604CC91B\several_subfolders”
I was thinking, there should be a way to display these files in a spreadsheet, manipulate and then write back to xml.
Sorry, life got in the way today - finally had a chance to toss it up on public domain haha, feel free to give it a try.
The one trouble I had was generating ‘General’ profiles - for some reason the game won’t recognize the files. But it does work for ‘Aircraft’ profiles so things like Flight Control Surfaces, Power Management, Switches/Buttons, etc. I’ll keep chipping away at figuring out the General files so we can bring over camera controls and such.
The whole thing is held together with Javascript, duct tape, and a little bit of hope - but it seems to be working…
Hey, thank you very much for your work! I’ll try it out later today (GMT+1 here) IF I technically have a chance to get into FS2024 in a reasonable amount of time.
Edit 1120z: Ok, this may work for steam users, but the MS Store controller configs are stored in cryptic folders inside of
C:\Users\XXX\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\000901FEAA09A279_00000000000000000000000069F80140.
I did not find the remotecache.vdf anywhere; unfortunately I don’t see any capacity to evaluate things here further.
Hmmm… that’s vexing - are you able to see an files beginning with ‘inputprofile_’ in any of those directories?
ETA: I played around with it a bit, if you find all the ‘inputprofile_’ files, you can just drag all of them directly into the dropbox on the site, doesn’t need to be the whole ‘remote’ folder anymore. However, I’m not familiar with the MS store structure so if you can’t see the ‘inputprofile_’ files or they are not all located together then I’m not exactly sure what the next step would be…
I’m glad to hear it worked for you! Does that filepath in the screenshot lead to the ‘inputprofile_’ files? If so I can update the instructions on the site to point there!
The key bindings settings files are saved by default in: C:\Users\Username\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\SystemAppData\wgs\random_numbers
Inside this folder, there are subfolders where the key bindings settings are stored.
Sorry, can you clarify which area you’re talking about? Is this pulling the old controller profiles or adding the new ones?
If you open up any of the inputprofiles_ in Notepad or another text editor you’ll be able to view the XML, one of the first elements will be ‘FriendlyName’ which is the name you’ll see in the game.
Dooh I didn’t notice. Thank you very much!
FYI although you probably know already…
I see that only two files are encrypted/encoded, I imagine they are needed.
I have listed the folders and file names and their details in a spreadsheet and checked relevant names/categoriesI to save my checking each one in turn in-sim. I learned if you edit anything in the profile file (e.g. to normalise profile categories across the controllers) it may create a new file name, alongside the old one.That’s not a definite, it happened once but a simple Save on another file kept the same file number - I don’t know why it made a new file first time I edited it and I deleted the old one but I write it for info. I have deleted all the empty folders without ill effect. I do have one in-sim profile for the Warthog, named as such, but I can’t delete it in-sim, it has the same attributes as the default profile. Perhaps I duplicated it somehow but I can’t get rid of it and it isn’t named in any of the profile files (all of which now match in-sim). Any idea how I get rid of it. I restarted the sim but it’s still there even though there’s no profile file for it?
Thanks again for your help.
It’s very likely that the profile you’re referring to is stored exclusively in the MSFS 2020 settings cloud, and for some reason, it doesn’t physically exist on your disk. If the profile you can’t find on the disk isn’t needed, you’ll need to trick the MSFS 2020 settings cloud. Here’s how:
Start MSFS 2020 without an internet connection. Disconnect your PC from the internet before launching MSFS 2020.
Once in MSFS 2020, proceed to the main screen (BE PATIENT )
Perform a short flight - set up and complete a quick 30-minute route.
After the flight, exit MSFS by selecting “Quit to Desktop” This step is crucial.
Restart your PC and reconnect to the internet.
Launch MSFS again. You should see an option to select a profile. Choose the profile that physically exists on your disk, not the one in the cloud.
This process should resolve the issue by effectively replacing the cloud-stored profile with the one you’ve selected locally. Let me know how it goes.
.
)