• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

P3D v5 ModelConverterX Conversion of a FS9 aircraft

Messages
136
Country
switzerland
I´m actually converting the Fokker S-14 Machtrainer from Emile and David. It has some static elements, like a gpu and chokes, which I don´t know under what condition within MCX, I should select them to show up. Sure, the chokes could be with parking brakes but what is with the gpu?
I have some planes, after parking the plane has a timer and after this, pilots dissappear and chokes, ladder etc. show up.

How can I do this with MCX?

Any help is appreciated.

Dan
 

Attachments

  • S-14.jpg
    S-14.jpg
    149.4 KB · Views: 71
Do you have a link to the file? The likelihood that GPU is a standalone component is pretty low. You can see if it has it's own distinct texture, again, low probability, but eliminating that, would solve it. Most likely GPU is part of the canopy animation, that is where I'd put it, that and the chocks. you can tell if they vanish as the canopy cycles and if that is the case, you will have to redo the canopy animation, or tolerate a fixed canopy, to eliminate them.

IF the above is true and you intend to proceed, then isolate the canopy assembly and export to Collada. It is important to get the canopy aligned, so if you cannot get the parts with the canopy closed, advance the animation until the canopy is closed, export that way and skip the next paragraph.

Import the assembly in Sketchup or Blender or whatever and find the GPU and chock parts. Erase them completely. Export this edited assembly to Collada.

Back in MCX, use the Merge Tool, to combine your fixed canopy with the rest of the model.
 
Hi Rick
Here is one link. The plane comes in different versions.
When importing in MCX, you need to set some variables to 1 instead of 0 to get the extra objects. I can isolate the gpu, its powerline is somehow connected to a part over the canopy. But my question ist rather, how shall i use it. When does it show up?
What terms are selected to make it visible? Is it a visibility condition in MCX, or should I use an animation to make it show up? The visibility conditions do not make real sence to me. A lot of engine related stuff, but of course, zero rpm would be a condition but not the only one. That´s the reason, I need help. Engine off is one condition, I can´t select a second one.
Dan
 
I have my ground equipment show up when the engine is shut down and the parking brake is on.

The part name in my modeldef file:

XML:
   <PartInfo>
   <Name>ground_equipment</Name> <!-- visible when brake is on and all engines are stopped -->
      <Visibility>
         <Parameter>
            <Code>
              (A:BRAKE PARKING POSITION, bool) 1 == (A:GENERAL ENG1 COMBUSTION, bool) 0 == (A:GENERAL ENG2 COMBUSTION, bool) 0 == (A:GENERAL ENG3 COMBUSTION, bool) 0 == (A:GENERAL ENG4 COMBUSTION, bool) 0 == &amp;&amp; &amp;&amp; &amp;&amp; &amp;&amp;
            </Code>
         </Parameter>
         <MinValue>1</MinValue>
     </Visibility>
    </PartInfo>
 
@tgibson
That´s what I´m looking for. I made sure, to load the modeldef file with your entries according to your tutorial.

Now, how do I tell MCX, this is ground equipment?
 
Ok, I got it. If the right Modeldef.xml is loaded, I have the ground equipment as visibility option.
 
I tried to add more definitions into modeldef, but when I load the object, MCX creates an error; Object reference not set to an instance of an object.
The definition were not used and the code looks ok. I had to transform it from FSDS to MCX format. There´s another ground_equipment option which I just named 2.

XML:
  <PartInfo> 
    <name>ground_equipment2</name> 
        <Visibility> 
            <Parameter> 
                <Code>
                    (A:RADIO HEIGHT,feet) 10 &lt; (A:BRAKE PARKING POSITION, bool) &amp;&amp; (A:General eng1 oil pressure, psi) 20 &lt;
                </Code>
            </Parameter>
            <MinValue>1</MinValue> 
        </Visibility>
    </PartInfo>

<PartInfo>
      <name>instructor</name>
      <Visibility>
         <Parameter>
            <Code>
                (A:PAYLOAD STATION WEIGHT:2,pounds) 1 &gt;
            </Code>
         </Parameter>
        <MinValue>1</MinValue> 
      </Visibility>
   </PartInfo>   

<PartInfo>
      <name>belt_copilots_seat_empty</name>
      <Visibility>
         <Parameter>
            <Code>
                (A:PAYLOAD STATION WEIGHT:2,pounds) 1 &lt;
            </Code>
         </Parameter>
        <MinValue>1</MinValue> 
      </Visibility>
   </PartInfo>

There were no such problems, when I added T. Gibsons extra definitions. Can someone see, what´s wrong here?

Thanks
Dan
 
In ground_equipment2 you need an &amp;&amp; at the end of the Code section.
 
That did it. You have any hint, how to learn this language?
I have a little programming experience in Pascal and reverse Polish notation, but here, I hadn´t seen the missing AND.
 
When writing conditions, you need one less comparison (AND or OR) than the total number of conditions. Since you have 3 conditions, you need two comparisons. They can either be placed as you did, after each comparison, or all at the end of the line.
 
Tom, did you create a condition, for pilots to be in the plane and dissappear, after the engines were shut and cooled down?
 
Hi,

No I didn't, sorry. But you should be able to test A:GENERAL ENG1 COMBUSTION, bool and that A:GENERAL ENG1 OIL TEMPERATURE, celsius is below a certain value, determined by testing. If you have a multi engine plane you may want to test the other engines too.
 
Back
Top