fereevil.blogg.se

1. #FSX LEVEL D 767 DIFFERENT PANELS HOW TO#
2. #FSX LEVEL D 767 DIFFERENT PANELS FULL#
3. #FSX LEVEL D 767 DIFFERENT PANELS CODE#

Last edited by il88pp 01-18-2017 at 01:13 PM.Īre gauges written in C++?Not exclusively.

#FSX LEVEL D 767 DIFFERENT PANELS HOW TO#

How to see if a "plane name".mdl file is an FSX or FS2004 native model is explained in the guide explaining how to merge a VC. But there you can swap the *******_Intererior.mdl file with another.

Some fs2004 planes do have a VC, but that is part of the "plane name".mdl file.Īs you can't edit mdl files, that VC can not be edited or swapped with another. In an fs2004 plane there is in the "Model" folder only two files: In an fsx plane you will see three files in the model foder. Some clearer then others.Īll this only works for native fsx aircraft models. A VC merge.įor installing the VC, here's one guide. When you are finished installing the VC, you can easily undo this, by just changing the lines back to:Īfter these steps, you have a seperate b737-800 you can mess around with without risking the original. (that means, for this paint, use the panel in folder: panel.***)Īs there is no such panel installed, the paint's won't show. Open the aircraft.cfg file in "b737-800_merge_747VC" again, andįor every paint you don't want showing, change: If you just want to see one while testing: While you are installing the VC you may not want all the paints showing in your aircraft selection list. This would show every paint of this pnew plane in the list. The planes will then show in you Aircraft selection list,( as: 737-800- 747VC), seperate from the default 737.īecause they are separately listed, (still as boeing, but not simply as 737-800), there is no need to also change each: Make a copy of the aircraft.cfg before you make changes.Ĭhange every title= line simply by only adding:ĭo that with all title= lines in the file.Īgain, do that with every installed paint. Because in the aircraft.cfg the "ui_type=" and "ui_variation=" lines are the same as well. All title= lines in the aircraft.cfg are the same, and fsx does not like that.Īlso, the "new" 737 would have the same name as the "Original" one. the Other folder called "b737-800 - copy")

(so you en up with the 737 installed twice. To get a more clear idea of what replacing a VC entails. Double that, if you start implementing you own systems simulation.

#FSX LEVEL D 767 DIFFERENT PANELS FULL#

I would estimate a full rebuild of the VC to be something around 1000 hours of effort, plus/minus a significant portion depending on your current skill level.

#FSX LEVEL D 767 DIFFERENT PANELS CODE#

Reengineering things that other developers did without any code documentation is quite the challenge. And you might run into restrictions in the systems simulation, as LD built it to suit their own model, not yours. Even if you re-use all the original gauges, you will still have to at least analyze how they are tied into the animations in the VC (a switch does not visually flick to another position on its own, you have to write code for that to happen). This requires programming skills and at least as much time (if not more) than the 3D modelling. The other is the systems simulation in the gauges, the gauges themselves and the animation control. IMHO the main part is to understand that the 3D model is only one part of the VC.