• 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.

FS2004 MakeMDL.part.xml modifications

Hi Tom,

I got it working already by now, I found some examples in another thread that got me in the right direction.
 
Sure. I don't have an identical entry in FS2004, but here is one that is almost the same, it limits the test to left hand engines.

XML: 
<part>
     <name>L_chocks</name> <!-- visible when brake is on and LH engines are stopped -->
                 <visible_in_range>
                      <parameter>
                           <code> (A:BRAKE PARKING POSITION, bool) 1 == (A:GENERAL ENG1 COMBUSTION, bool) 0 == (A:GENERAL ENG2 COMBUSTION, bool) 0 == &amp;&amp; &amp;&amp; </code>
                       </parameter>
                       <minvalue>1</minvalue>
                 </visible_in_range>
</part>

Hope this helps,
 
I got the blocks condition to work on the DC-6 after exporting the mdl from MCX. But now I have broken something in the props. Once I have solved that I can put the export function in the development release I think.
 
tgibson said:
Wow, that's great! Sorry to hear it's such a hassle.
Click to expand...
It's actually less of a hassle than I expected beforehand. I mean this feature request is on the MCX wishlist only for 10 years now :D, I had been delaying it all the time and also thinking that not so many people use FS2004 anymore, until somebody asked again and I was tempted to have another look at it. It's actually quite fun to figure out.

I haven't looked at mouse rectangles for the virtual cockpit yet, I'm sure that will be a future request once the aircraft MDL export is there.
 
I have also found out what is wrong with the props now, I can get it right be making sure the visibility conditions are on the right nodes. But the way MCX reads the visibility conditions from FS2004 MDL files is not perfect, so I guess I need to improve that a bit first :D
 
Still working on it, i think I'm close to getting it to work now. But the last weeks progress has been slow because work was quite busy.
 
Good news, I have finally been able to export an aircraft to FS2004 MDL format and afterwards it seems (most) animations and visibility conditions do work in FS2004.

I need to double check some test cases and try some other models. But I think I can put this functionality in the development release soon now.
 
You must log in or register to reply here.
Back
Top