737 Next Generation

[omega13a]

In my case, the lower half of the 737-900 disappeared because the plane had sunk into the ground for some reason. I haven't touched the file the controlled that after I solved the 'hoovering' problem. Everything was find when I made the Alaska Airlines' More to Love livery. Just that after the upgrade, the plane was now half buried in the ground. It was strange that the 737-600, 737-700, and 737-800 weren't effected. I have a feeling the developers of FlightGear are making changes to the software that are having some bizarre unforeseeable effects...

[GabrielYV]

mmmIt is very strange, every time there is a new version, some aircraft are affected by new general changes, I will check what happens with the cockpit of 737 800YV, if you need help with the 737 family, tell me.
Regards, Gabriel Hernandez (YV3399)

[Octal450]

Why not integrate this one 600 700 900 into our one, to avoid separate repos? If they keep the same systems, etc.

[GabrielYV]

Great Idea, I don't have problem with that

[omega13a]

Why not integrate this one 600 700 900 into our one, to avoid separate repos? If they keep the same systems, etc.

It would definitely make things easier to update though I did try and model each type of engine available for each one of the 737 Next Gen family as well as make the winglet display thing a little more complex (added an option for no wiglets).

[Octal450]

OK guys, Gabriel has asked me to go ahead and do the merge, I will do it this weekend. Then, you guys can let me know if there is anything I missed.

I'm not taking the new FDM as, Soitanen's JSB is much better in every way. I'd just say it should be tweaked for the other models. Also, it's a bit silly to model so many with almost no differences....

Best Regards,
Josh

[omega13a]

Also, it's a bit silly to model so many with almost no differences....

I'm just trying to be as complete as possible.

[Octal450]

Which ones do you think I should bring over, I think its redundant to have all these different ones, and confusing...

J

[omega13a]

I think the most common engine for each of the 600, 700, 800, and the 900. The other engine types could be part of a bonus pack but to make it simple for updating the bonus pack how things are organized should be kept the same.

If this page to be trusted, for the 600 its the CFM56-7B18, for the 700 its the CFM56-7B20, for the 800 its the CFM56-7B24 and for the 900 its the CFM56-7B26.

[omega13a]

The engines need to be remapped. The way the paint kit is set up, it gives you the impression that you can have both engines be painted differently like Southwest's Maryland One (note engine #1 is white while engine #2 is red). However, in reality, that's not the case. If I to make a livery for Southwest's Maryland One, either both engines would be red, white, or red on one side and white on the other. I don't know how to fix this so I will greatly appreciate it if someone can.

[Octal450]

Sorry for the delay Omega, I've been having other priorities. I will try to get this done as soon as I can.

Josh

[omega13a]

Which ones do you think I should bring over, I think its redundant to have all these different ones, and confusing...

J

I made use of the variant-of tag. It seems to have cleaned up things with the aircraft listings in the QT launcher but made no difference with fgrun (my preferred launcher for testing purposes).

[Raptor]

fgrun (my preferred launcher for testing purposes).

Is there any way I can get fgrun launcher for FG 2018.2.2 instead of QT launcher?
Aircraft preview in fgrun is very helpful while placing instruments in a cockpit.

[wkitty42]

FGRun is no longer maintained or supported... it still exists in its repo but no one that i'm aware of has stepped forward to support it...

[Octal450]

Hi there, for Windows, you can download this, and paste it into your Bin folder, if any duplicates, don't overright, and FGRUN will work.

http://itpns.ddns.net/data/FGRUN.rar

I took this files from the FGFS 2016.1.2, the last version to include FGRUN. Been using it since then.

Josh