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

Hide Engine code when Cowling is Closed

That would not work reliably, since airspeed indication is driven by a pressure device (pitot tube) and is affected by ground winds...

Far simpler would be to use an on-ground condition.

I had an on-ground condition with the first re-release of the Kodiak. The control worked a dust effect, which also was looking for dirt calls. It played havoc with a ton of computers, lolol... I dont wish to go that route unless its totally full proof and will not cause crashes and super low frame rates from looped gauge requests.

Bill
 
Well, note to all on this,

I solved it with a Visibility code that Fr. Bill had made in the past based on 'Plane on Ground'. Works like a treat. Thanks Fr. Bill.

Here is the code;

Code:
    <PartInfo>
      <Name>aircraft_on_ground</Name>
	    	<Visibility>
		   <Parameter>
                 <Code>(A:SIM ON GROUND,bool) 0 &gt; if{ 1 } els{ 0 }</Code>
		   </Parameter>
		</Visibility>
    </PartInfo>




Bill
 
I would write a simple XML timer gauge that times your animation from 1 to 100 on a number lvar then have your visibility trigered by one end of the range ie.

in the gauge...

(L:blo, bool) if{ (L:blaa, number) 1 + (>L:blaa, number) }

then to limit

(L:blaa, number) 101 == if{ (L:blaa, number) 100 (>L:blaa, number) }

then to reset

(L:blo, bool) 0 == if{ (L:blaa, number) 1 - (>L:blaa, number) }

and

(L:blaa, number) -1 == if{ (L:blaa, number) 0 (>L:blaa, number) }

Then in the modeldef.....

animate your cowls with the (L:blaa, number) keyframes 0-100 and no lag
0 closed 100 open

Then tag the visibility with (L:blaa, number) 1 &gt;= that way the engine will apear as soon as the variable hits 1.

You can change the speed by changing the amount to + or minus the number variable. as long as the variable will hit the end numbers exactly...

I use this sort of animation all the time for example to control 'remove before flight' signs that i only want to flap @ certain windspeeds. I know its not the neatest solution but compile it as an spb and the performance hit from having this sort of animation going will be minimal.
 
Back
Top