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

FSXA Adding a timer.

lionheart said:
How do you 'add' vibration, Vololiberista? I didnt find this command in Events in the SDK.
Click to expand...
Well it's a bit complicated!! At least the way I did it. The pre-flight checklist requires that the vibration meters are tested so that means I have to use L: vars as well as A:vars. The principle A:var is (A:TURB ENG1 VIBRATION, number) eng2 etc. So obviously? I decided to use L: vars to add a wear factor according to the hours the engines have been running. And other L: vars to to account for testing. Also there are vibration meters each for the LP and HP compressors.
Code: 
This extracts the value stored in the state.cfg file previously mentioned and puts values into the front and rear vib sensors.
(A:GENERAL ENG ELAPSED TIME:1, hours) 1000 >
if{ (A:GENERAL ENG ELAPSED TIME:1, hours) 1000 / (>L:vib1,number) (L:vib1,number) 0.075 + (>L:vib1a,number) }
els{ 1.079 (>L:vib1,number) (L:vib1,number) 0.075 + (>L:vib1a,number) }

Code: 
This increases the vibration factor according to the throttle position.
<Element>
      <Select>
         <Value>(A:Turb eng1 N2, percent) 1 &gt; (A:General eng1 throttle lever position, part) 0 &lt; and
if{ 1.2 (>L:rev14,number) } els{ 0 (>L:rev14,number) } </Value>
      </Select>
   </Element>

Code: 
This sets the test values
<Element>
      <Select>
         <Value>(L:EF_1,number) 0 &gt;
if{ 7.7 (>L:efvib1,number) } els{ 0 (>L:efvib1,number) }
(L:EF_2,number) 0 &gt;
if{ 9.5 (>L:efvib2,number) } els{ 0 (>L:efvib2,number) }</Value>
      </Select>
   </Element>

Code: 
This determines when warnings are produced
Element>
      <Select>
         <Value>(A:TURB ENG1 VIBRATION, number) (L:vib1,number) * (L:efvib1,number) + (>L:viwarn1,number) </Value>
      </Select>
   </Element>

   <Element>
      <Select>
         <Value>(A:TURB ENG1 VIBRATION, number) (L:vib1a,number) * (L:rev14,number) + (L:efvib1,number) + (>L:viwarn1,number)</Value>
      </Select>
   </Element>

Code: 
This is the forward LP gauge for engine 1.
<Gauge Name="Eng1 vibration gauge" Version="1.0">
   <Image Name="vib_backxx.bmp" Luminous="Yes"/>
   <Element>
      <Position X="0" Y="278"/>
      <Image Name="vib_needlexx.bmp" Luminous="Yes">       
         <Nonlinearity>
            <Item Value="10" X="0" Y="215"/>
            <Item Value="0" X="0" Y="0"/>
         </Nonlinearity>
      <Delay DegreesPerSecond="20"/>
      </Image>
      <Shift>
         <Value>(A:TURB ENG1 VIBRATION, number) (L:vib1,number) * (L:efvib1,number) + (L:vib_test,number) + </Value>
      </Shift>
   </Element>
   <Mouse>
      <Tooltip>Engine 1 LP Vibration (%((A:TURB ENG1 VIBRATION, number) (L:vib1,number) * (L:efvib1,number) + (L:vib_test,number) + )%!2.3f!%%)</Tooltip>
   </Mouse>
</Gauge>

Easy peasy :) not!
 
Ahhh so....... Dang... You deserve an award for all this amazing work you do on that plane, Volo. Goodness man....

So, there 'isnt' a K: command for adding vibration, it is all L:vars basically and then readings.
 
All this talk of failures and engine wear is very chilling...

In my own virtual flying world pilot error is the main cause of air crashes - I don't need hardware failures to break an aircraft!:(

Nice technical discussion though and loads of learning going on here.

Walter
 
lionheart said:
Ahhh so....... Dang... You deserve an award for all this amazing work you do on that plane, Volo. Goodness man....

So, there 'isnt' a K: command for adding vibration, it is all L:vars basically and then readings.
Click to expand...
No I don't think there is.
 
BaiterOne said:
All this talk of failures and engine wear is very chilling...

In my own virtual flying world pilot error is the main cause of air crashes - I don't need hardware failures to break an aircraft!:(

Nice technical discussion though and loads of learning going on here.

Walter
Click to expand...
It's all about modelling the a/c systems. Flight simulators are all about managing crises. In this case it's how close to the flight manuel can one get.
 
BaiterOne said:
All this talk of failures and engine wear is very chilling...

In my own virtual flying world pilot error is the main cause of air crashes - I don't need hardware failures to break an aircraft!:(

Nice technical discussion though and loads of learning going on here.

Walter
Click to expand...


Roger that Walter. I too am one of those that do not like malfunctions, but lots of customers do these days.
 
You must log in or register to reply here.
Back
Top