Legacy Aircraft

"Ending up upside down in a field has become a pretty common way for me to end up when flying these 'Legacy' fighters, this does not happen to me in other sims I promise. "

Nosing over will undoubtedly be caused by contact points, the CoG not relating to the parameters used in the MSFS world. Try moving them forward in the Aircraft CFG of the pre-converted file. This will effectively move the CoG when on the ground. Then port and see what happens. :engel016:
 
"Ending up upside down in a field has become a pretty common way for me to end up when flying these 'Legacy' fighters, this does not happen to me in other sims I promise. "

Nosing over will undoubtedly be caused by contact points, the CoG not relating to the parameters used in the MSFS world. Try moving them forward in the Aircraft CFG of the pre-converted file. This will effectively move the CoG when on the ground. Then port and see what happens. :engel016:

btw. Bazz any news about first official conversion any Your model to MSFS? Maybe as the first MS893, C140 or this new Zlin 50? :wavey:

btw.2 Im not sure but MSFS Store will the one place only to buy addon for MSFS? What will happen with Simmarket, PCAviator, ect.?
 
A few minutes with DXTBMP fixed the tyres and exhaust stack on the AH Spit and Hurricane

Still a few textures to convert though.
Very pleased with these two :)

For the Virtavia Islander it's very easy - just follow the instructions and it works.
I still use the simple python script (no need for virtual studio) but there are good instructions for the converter program here at FSDeveloper
Cheers
Keith
 
btw. Bazz any news about first official conversion any Your model to MSFS? Maybe as the first MS893, C140 or this new Zlin 50? :wavey:

btw.2 Im not sure but MSFS Store will the one place only to buy addon for MSFS? What will happen with Simmarket, PCAviator, ect.?

As part of the "proof of concept" approach we are taking with Ctrl/Ezy, we are currently working on bringing the Pucara to MSFS. Once the workflow is to our liking, we will then be able to publish more detail on other product for MSFS. Zlin Z50LS will definitely be there.

MS has always stated that developers will be able to sell their products themselves. We have heard nothing to the contrary as yet.:engel016:
 
Yes, there are already some companies that have their products released outside of the MSFS Marketplace, like ORBX, FLYT, Gaya Simulations, Sierrasim and Drzewiecki. In Microsoft's own words, as reported in their July 16th development update:

"The Marketplace will operate under an Agency model, which means that you, as the content creator, will set the price for every piece of content you submit. Becoming a partner doesn’t alter your ability to sell your content on your own websites and storefronts. Just like with FSX, you can continue to sell your content outside of our Marketplace. Becoming a Microsoft Flight Simulator Marketplace Partner essentially unlocks another channel for you."

Obviously getting an addon product in the MSFS Marketplace will be of a great benefit especially when the XBox version of the sim is released, as it will open up a whole 'nother sector of potential customers.
 
Another one I've had success with is the Virtavia Islander, again everything except the radios, GPS and A/P display and everything works.
attachment.php


Cheers
Keith
Would love to see this one working. I wonder if there is a way to just distribute the needed files to folks who already have the payware?

Don't know if you've seen this thread at avsim but on page 7 Ernie Alston, developer of the KLN-90 used in the Virtavia/Flight1 Islander, gave us a 64-bit version. Works great in P3Dv4+.
avsim.com/forums/topic/529864-britten-norman-bn-2-islander-for-p3dv4-coming-soon/

:ernaehrung004:
 
Would love to see this one working. I wonder if there is a way to just distribute the needed files to folks who already have the payware?Don't know if you've seen this thread at avsim but on page 7 Ernie Alston, developer of the KLN-90 used in the Virtavia/Flight1 Islander, gave us a 64-bit version. Works great in P3Dv4+.avsim.com/forums/topic/529864-britten-norman-bn-2-islander-for-p3dv4-coming-soon/:ernaehrung004:
I can email you two JSON files, that should be all you need...pm me your email.Create the folder structure \Community\Islander\SimObjects\Airplanes\and copy your "Flight One BN-2 Islander" folder into it from an existing installation.Put the two .JSON files into the Islander folderStart MSFSThe Islander SHOULD be there and flyable, I don't know if anyone has tried this before but it should work....Yes, I had that GPS for P3D, it doesn't help for MSFS as the problem is only 3D gauges in the MDL file are supported for now.CheersKeith
 
Hey folks, FYI I have written up the process for creating port-overs: https://www.fsdeveloper.com/forum/threads/guide-converting-aircraft-from-fsx-to-msfs.448744

Theres a few things that I need to update but that's pretty much the process.
Excellent. I could have used this two days ago when I was mapping airfile tables to .cfg files myself. But thanks for making the effort to codify and share this process.

Have you tried the Python build.py script to build your layout.json files? Seems way easier then the planeconverter.
 
Excellent. I could have used this two days ago when I was mapping airfile tables to .cfg files myself. But thanks for making the effort to codify and share this process.

Have you tried the Python build.py script to build your layout.json files? Seems way easier then the planeconverter.

The each do the same thing and I was using PlaneConverter before the python file was a thing :D (like it's ancient or something LOL)

Have you got a link for that python file? I'll add it to the page. Also, did you want to include anything onto that master list to help?
 
build.py is on github as part of the developer files from the A32NX project, here:

https://github.com/wpine215/msfs-a320neo/tree/master/A32NX

Just install Python 3.8.x for W10 on your pc if you don't have it..
https://www.python.org/ftp/python/3.8.5/python-3.8.5-amd64.exe

Then drop the build.py script in the top folder of you add-on (where your manifest.json is) and click it To run it. Drops A layout.json in the same folder. Done.

Nice one :D I'll update the document now.
 
Back
Top