I think it is because if you cannot get it compiled, there is not much you can expect from the converted planes either… Should be much more simple to compile the plane than it is to get aomething else working in the converted planes.
HJave you tried ELEVATOR TRIM PCT - I haven’t but its a simulation variable, so potentially worth a go.
Because someone could mess with the code and do nasty things with your computer. This way we can see what the program is going to do.
Did you have to reference those files somewhere else, or did you just copy them from say the CJ4 and paste them?
That is what I tried, but I still have no functional engine.
Aircraft loading as invisible usually means the MDL is FS9 or P3D format. Since you say you exported it as FSX Format, I am stumped. Will think on it further
I copied and pasted the runway.flt from the CJ4 and then copied and pasted the engine section from the 747, reduced the number of engines listed to two as per the model itself. I then added the runway.flt to the manifest.json file so that MSFS knows the runway.flt file exists.
1 Like
thank you, i had not updated the manifest file. Now my bird can take off 
Much appreciated.
IMPORTANT INFO
If you plan to share your aircraft publicly or fly with friends, PLEASE make sure to read the other thread on how this can cause immediate CTDs for anyone with the aircraft installed. You need to structure the files in a specific way to allow them to be used in multiplayer. If you don’t use a workaround (mine or another way you might find) you are burying a landmine in their system!
Looking good! I should’ve said update the layout.json not manifest.json - sorry! I get them confused!
1 Like
So do I. But you gave me the nudge I needed and now I am experimenting with which engine cfg I like the most. It doesn’t to be perfect just yet, but it is good to tinker.
I have seen a recent release on an addon freeware site. The user seemed to have followed this thread but of course it has issues such as gauges, handling and bugged gears etc.
The user remained anonymous probably because they never asked the original creator for permission to release it.
I really do hope you guys refrain from following the same path, redistributing without permission is unethical and I really do not want to see bugged aircraft flooding the community. Just gives a bad look.
3 Likes
Yeah I saw that today and laughed.
I’ll give that a try later and see if adding spaces or using all upper case works, thanks. I was able to find the mixture control by copying it from the King Air .FLT files and manually pasting it.
I’m okay because the files I’m modding are my own payware products 
But I agree, people shouldn’t mod anything without the creators consent. I have aicraft models I made years ago that are in circulation on freeware sites with no credit - over the years the credit has been lost and now others are taking the credit for my work!
1 Like
There is a python script that will create the layout.json file. I found this on Avsim.
This is how I do it, (instructions found on the web)
“first go here and download the build.py file: https://github.com/wpine215/msfs-a320neo
then make sure you have python 3.6 or newer to run that .py file
then go into your MSFS Community folder and make a new folder for the plane you want to bring over from FSX, something like manfredjahn-c47 for example
then drop all the FSX add-on files inside this new folder as if it was FSX’s main directory, make sure the folders look something like SimObjects/Airplanes/your plane, then drop the build.py and some random manifest.json from another default plane in the main folder
run the build.py to create the layout.json file
edit the manifest.json file to match the plane”
Best results are from pure-FSX models that work well in P3Dv4, have 3D gauges and don’t rely on any DLLs.
4 Likes
@JanMarHH re: your model and others regarding the overall process, if you’re having trouble with the model not showing, and it is an FSX model, you may have dependencies in the panels, texture, sound or model folders, in their respective cfg files. These dependencies need to be removed. Or your layout.json file might not be right.
When converting, I recommend making the conversion as simple as possible to start. Make a copy of the original simobject folder so you leave the original in tact, strip out any 2D gauges (they’re not supported anyhow), strip out sounds to start and strip out all but one texture and clean up the aircraft.cfg to only have the first texture. Check each of the remaining cfg files for any dependencies on other folders. Once that’s all done, use the converter tool to move the files and create the JSON files, or if you’re so inclined manually build the folder structure and the manifest.json file and then use build.py to make the layout.json file, or do it all manually.
Once you’ve got your model showing in the library, only then get to work on textures, sounds, etc. Textures all need to be converted to DDS (though I’ve been told BMP32’s work, but I haven’t tested myself). The best way to convert texture BMPs to DDSs is to use the imagetool.exe tool that is included in the P3D SDK, but there are other ways. There are threads on fsdeveloper talking about how to make these conversions, but if they’re done incorrectly, textures won’t show. Then, you can work on sounds and the panel. Do them one at a time so you can see what breaks it.
To be extra clear, while it is possible to get ‘lucky’ and just run the conversion tool and have it work, 99% of the time it will not ‘just work’. These conversion tools are not actually conversion tools right now, they simply help you format the folders and files so that MSFS knows how to insert them into the virtual file system.
@JanMarHH if you join the discord listed at the top of this thread, others can probably help you troubleshoot your specific model.
2 Likes
thanks this is useful. saves some manual editing.
hmm after some tinkering it seems my birds always start in the ground with that script. It appears it has a few hundred lines less code than the other method. I wonder what it is missing specifically.
I would like to second this. Not just because it may save you some legal headaches, but because it’s the right thing to do. I have chosen the Manfred Jahn/Jan Visser C-47 to experiment with myself, but I will not be uploading or distributing it. (Don’t Ask!) It was just a convenient candidate to practice on. I have learned quite a bit from both here and the Discord Discord The most important thing that I’ve learned is how complex this new sim is and how little we actually know about this conversion process., especially about creating or using MSFS gauges. I would like to echo SlinkyMate’s warning about any uploads: If you download something, it will be buggy and incomplete.
1 Like
this happens in many mod communities.
ensure no praise goes to the “ripper” and that sites holding content like this are made known.
some wont care as theyre just after clicks.
its not always done maliciously rather thoughtlessly so dont witch hunt without cause.
1 Like