Screenshots

**RichardLouis** · July 2nd, 2021, 00:13

**ZsoltB** · July 2nd, 2021, 00:36

***noddy*** · July 2nd, 2021, 06:43

**TeiscoDelRay** · July 2nd, 2021, 18:55

**Bookman1960** · July 3rd, 2021, 02:58

***Radioman123*** · July 3rd, 2021, 06:09

Here is a classic. It flies well but I need to work the instruments.

Click image for larger version.

Name: SpofStLouis2.PNG
Views: 102
Size: 2.11 MB
ID: 83481

***Tom Clayton*** · July 3rd, 2021, 14:18

Lake Tahoe

**CG_1976** · July 3rd, 2021, 14:42

Bookman1960, great shots on the 377. Where can I find that one?

**Bookman1960** · July 4th, 2021, 03:02

Originally Posted by CG_1976

Bookman1960, great shots on the 377. Where can I find that one?

Thank you sir. That import is still very much a WIP but its the wonderful KC-97G from Manfred Jahn.

As I've been importing some of my favorite models into MSFS, I keep discovering new challenges and things to try and understand. It seems that for every 5 i successfully bring in to the game, 5 more present odd results.

At this point I can describe several recurring typical issues and some insights:

A model converts in but has several areas which are all white (and which seem to defy any effort at alpha channel editing or texture manipulation and so I suspect must be something hard-coded in the model itself -- though still trying to understand and overcome this issue).
A model converts in but acts squirrely when one attempts to fly it in the game. My temporary fix (as is the case with the above KC-97) is to replace the air file with one from another similar model which is behaving properly in the game -- an old trick well known to many here I'm sure from previous versions of the game).
My discovery that one can simply use a place holder for either panel or sound folders [i.e., create a folder, add a blank panel.cfg or sound.cfg] allows one to bring the model in and see how things look/act more easily. I also do this when I see that a panel requires DLL (which are not accepted by new game and prevent models from being successfully imported). I also try to avoid importing useless gauges and panels that require too much effort to repair afterwards.
Before converting, make sure to edit any changes you wish to make in the aircraft.cfg [i.e., editing information] before importing. saves frustrations afterwards.

I'm sure I've forgotten something and I will also discover new challenges but I encourage anyone to begin experimenting. I've enjoyed seeing what I can bring forward for my own enjoyment -- especially my love of vehicles and ships for further explorations of the beautiful 'world simulator' that FS has now become!

Thank you Asobo and Microsoft for this wonderful game.

KB

**Bookman1960** · July 4th, 2021, 03:16

Martin MB-2 by Paul Clawson

**Bookman1960** · July 4th, 2021, 03:19

Restauravia treasure: Latecoere 25

**Bookman1960** · July 4th, 2021, 03:22

Restauravia treasure: Breguet XIV

**ZsoltB** · July 4th, 2021, 03:40

***K5083*** · July 4th, 2021, 08:02

Originally Posted by Bookman1960

As I've been importing some of my favorite models into MSFS, I keep discovering new challenges and things to try and understand. It seems that for every 5 i successfully bring in to the game, 5 more present odd results.

Bookman,

This conversation really belongs in the Legacy Airplanes thread, but just a few quick ideas.

The untextured, all-white look can result from several things. One is the sim not being able to find the texture because the texture.cfg isn't pointing to the right backup shared texture folder, or maybe to a folder to some other plane in the same family that you didn't install. Another is it not being textured at all but just being a material, which may not be decoded properly by the sim because there have been changes in how the MDL is read.

On the crazy behavior, first make sure you have deleted all [OBSOLETE] entries from the .AIR file using AirEd, as discussed recently on the Legacy Aircraft thread. That cures a lot of wild behavior that started after a sim update that was pushed out in May.

If it is a tailskid aircraft behaving crazy on the ground, try changing the skid to a wheel by changing the first value for point.0 in [contact_points] in aircraft.cfg from a 3 to a 1. Sometimes MSFS does not like tailskids and treats them like super pogo sticks, although other times it seems okay.

You've done some lovely work here, including a few that I might have a whack at myself.

Radioman: Curious what the issues are with the FSX Ryan NYP gauges. Do they not show up at all, are they completely static, or do they move but just show wrong values? If they move but just show wrong values, that can usually be fixed.

August

***K5083*** · July 4th, 2021, 08:23

A little late getting around to posting pics from my Canada Day flying.

August

***Radioman123*** · July 4th, 2021, 10:58

Originally Posted by K5083

Bookman,

This conversation really belongs in the Legacy Airplanes thread, but just a few quick ideas.

The untextured, all-white look can result from several things. One is the sim not being able to find the texture because the texture.cfg isn't pointing to the right backup shared texture folder, or maybe to a folder to some other plane in the same family that you didn't install. Another is it not being textured at all but just being a material, which may not be decoded properly by the sim because there have been changes in how the MDL is read.

On the crazy behavior, first make sure you have deleted all [OBSOLETE] entries from the .AIR file using AirEd, as discussed recently on the Legacy Aircraft thread. That cures a lot of wild behavior that started after a sim update that was pushed out in May.

If it is a tailskid aircraft behaving crazy on the ground, try changing the skid to a wheel by changing the first value for point.0 in [contact_points] in aircraft.cfg from a 3 to a 1. Sometimes MSFS does not like tailskids and treats them like super pogo sticks, although other times it seems okay.

You've done some lovely work here, including a few that I might have a whack at myself.

Radioman: Curious what the issues are with the FSX Ryan NYP gauges. Do they not show up at all, are they completely static, or do they move but just show wrong values? If they move but just show wrong values, that can usually be fixed.

August

The gauges did not show up at all but I can see the rest of the interior of the plane. I am thinking to do a complete gauge swap out to see if I can get working gauges.