ozzieblr

Yes that would work too. I believe it is to do with long filenames errors, and you can change where you install by selecting the new location (either a Kodiak folder on the desktop, or an xboxgames folder on the C drive) and entering it during the install process. Creating a Community folder in C:\XboxGames\Microsoft Flight simulator 2024\content\ and using that as your install folder is easy - it automatically places the files where they should be and avoids having to manually copy the files to the old Community folder. That certainly worked for the Kodiak.

You might like to explore where the installer is trying to install. I had similar issues with the latest Kodiak installer until I discovered that MSFS 2024 now wants Community content installed via an xboxgames folder rather than the old location. When I pointed it to that folder, it installed without errors.

I had to reinstall MSFS 2024 a couple of weeks ago, and in the process it established the xboxgames set of folders which I don't think had been there before. I then created the Community and Community2024 folders inside the Contents folder, and set up the correct pointers before reinstalling my software. Instructions came from Microsoft Copilot. I have never had a problem with installers since, nor have I ever had a long filename error since. My (possibly limited!!) understanding is that the system seems to automatically place the installed files in the original folder locations, but uses this 'virtual file' system to do installations without errors, no matter how long the file names are.

By the way: these Community folders are now supposed to be in the xbox / Content folder too, I have discovered ... my sim is the Microsoft Store version, so this might vary for Steam users, but my new location for Community folders is here: C:\XboxGames\Microsoft Flight Simulator 2024\Content I found this when updating the newest Kodiak with the current installer, which spat out multiple error messages when trying to install in the Community folder/s in the old location. When I pointed it to the new location, it worked perfectly without any errors. I have since ensured that all pointers go to this location now and my system is working perfectly well. I suspect this is to help us avoid problems we have had in the past with fairly common long filename errors.

No, SWS has not got any bugs in the latest version. I too had the same problem with errors and thought it was faulty until I discovered that MSFS now requires all non-default aircraft to be installed in an xbox games Community folder now instead of the location used in earlier versions. Once I located the correct place to install to, it went perfectly right through to the completion, and the aircraft performs as expected. The location of the Community folder for 2024 is now in this Contents folder as follows: C:\XboxGames\Microsoft Flight Simulator 2024\Content Asobo and Microsoft have clearly failed to advertise this change as effectively as they should.

My setup permits the aircraft to wear the painted tail number on the rear fuselage in whatever style and size you want, and then have MSFS2024 place the tail number (the same as the painted tail number entered manually in the Identification field) on the lower left wing and on the cockpit placard. I'll see if I can send some screen shots in a DM.

I have some custom liveries working just fine on the Reims Rocket without over-writing the painted tail number. I used a panel folder with entries to reduce the size of the dynamic tail number to zero. Do you know how to do that? If not, I could send you an example.

UPDATE - yes it was indeed the long file pathway that was the problem. However, the installation worked properly when installed to the desktop then copied into the Community folder. The aircraft is outstanding, flies beautifully, and is once again one of my favourite GA aircraft. All the older liveries worked perfectly when converted to ktx2 format, and the file structure altered to suit the MSFS2024 model.

Thanks guys - I have now gone right through installation and have the same outcome. Hopefully SWS will quickly solve the problems (many files did not install) and update the installer for us. I'm pretty annoyed, as I had purchased the original aircraft from JustFlight as well as SWS (my mistake of course!), and when I experienced this problem with one 2024 installer I went to the other and bought the update again as well. Its an awesome aircraft, but not happy about double the price it could have been. I'm sure that in the end, the fun will be worth it!

I'm wondering if anyone else is having trouble installing their new upgraded Kodiak 100 Wheels for MSFS2024? And if so, is there a workaround? I am getting "Error opening file for writing" message for the file AlternatorShrouded_LOD0.gltf, and many others - resulting in having to abort the installation. The installer downloaded normally and was extracted in the normal way, and commences the installation process as expected, but hangs with this message about one quarter of the way through. TIA for any help!

You may need to go to Content Manager and enable them.

Hi Ray I have used ModelConverter frequently (though mainly for converting aircraft models to use in Blender) and would love for you to provide a brief tutorial outlining the steps required to achieve this outcome for my own copy of YBCS, if you are able to do that. I am a dual UK/Australian and fly the Aussie airspaces regularly - this adaptation would make for much greater depth of realism for the airport. If you are able to help without breaching T&C I would be very grateful! TIA, Brian

Yes its an awesome small turbo prop - there are times when the jetstream of approx 100-120kts across southern Australia gives even greater ground speed when heading east! Not so much fun when heading west, of course!!

Have you checked to see if they are installed in MSFS2024 but are listed separately (not with your PMDG liveries)? I have seen some liveries online that are incorrectly located directly into the Community folder rather than in with the PMDG liveries. Therefore they cannot be seen listed with the PMDG liveries for a particular airframe type. I had the opposite problem for a while - the liveries showed up and worked in MSFS2024 after I manually installed them but did not show up in OC3. The problem was in the structure of the file name and the contents of the config files - they have to be consistent and matching, or the livery is not recognised by OC3. If the files you are installing are correctly named and formatted, and set up correctly to install in the same folder as the PMDG liveries, OC3 should recognise them and they should work when they have been installed.

Thanks Jonathan - that was the solution! It didn't like Edge, but worked just fine with Chrome!