P3D v1 Engine Failures in XML gauges?

[lionheart]

Hey all,

Maybe I should ask this here.

Has anyone figured out ways to create engine failures with XML gauges that over-ride throttle, mixture, etc?

For instance, can you easily create a 2 level failure for carb icing? Can one create over-heating 'with' engine RPM lowering, engine sound lowering, etc? (With using Spoilers, you cannot have changes in RPM, sound, etc).

Can one over-ride throttle and mixture with XML gauges?



Bill

 

[teson1]

As you're developing the planes yourself you can set the FS A: parameter like throttle lever position by a K:*_Set events to mimic the effect of the engine issue, and indicate a custom-generated L: value in the gauges or as lever position in the panel/VC instead of the genuine A: value.

I've added a gauge by which the maximum throttle position is limited. This gauge also (roughly) detects lever position of an external physical throttle quadrant, which could be used to display the same position of the lever in the panel/VC as on the external lever.

E.g. if you want to implement power loss do the following:
- By >K: event set FS internal throttle position to something less than corresponds to the throttle position of the external throttle qaudrant.
- Display throttle lever position in the cockpit/VC with a L: variable at the same position as the external lever.

This can get messy so I'm not sure it's robust enough for a commercial product. Just a suggestion.

I'd guess (without having the skill) that the more robust way would be to use FSUIPC/Simconnect to capture external lever positions ect. and set the FS parameter to mimic engine effects.

 

[taguilo]

Hey all,

Maybe I should ask this here.

Has anyone figured out ways to create engine failures with XML gauges that over-ride throttle, mixture, etc?

For instance, can you easily create a 2 level failure for carb icing? Can one create over-heating 'with' engine RPM lowering, engine sound lowering, etc? (With using Spoilers, you cannot have changes in RPM, sound, etc).

Can one over-ride throttle and mixture with XML gauges?



Bill

There are different levers for controlling engine failures:

1) You can custom code the XML gauge needles as to show the intended values, though internally the simulator will keep running its vars as usual. This is the simplest way and the only that can be implemented using XML code exclusively. A good option in most cases, has its drawback in others, for example dissociated sounds, fuel consumption, engine responses, etc.

2) When manipulating throttle,mixture and any other function in XML that can be commanded by a controller (joystick) or keyboard key, you'll have to use a C++ event controller to capture those events when in External view. Not difficult to program, but you need at least a bit of C++ knowledge.

3) You can go further an use C++ with Simconnect to manipulate FS's internal variables -many, not all. This would be the best (though most difficult) option, because your instruments -mostly- show what you commanded FS to comply with.


Tom

 

[vololiberista]

I presume it's the same in FSX. I use the code below to give each engine an individual vibration depending on how many hours they have been running. Eventually the vibration factor will rise to a point where the engine will "malfunction" and need changing i.e. resetting the state.cfg values!
vololiberista

<!-- Engine Vibration Factors -->
<Element>
      <Select>
         <Value>(A:GENERAL ENG ELAPSED TIME:1, hours) 1000 &gt;
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) }
(A:GENERAL ENG ELAPSED TIME:2, hours) 1000 &gt;
if{ (A:GENERAL ENG ELAPSED TIME:2, hours) 1000 / (>L:vib2,number) (L:vib2,number) 0.045 + (>L:vib2a,number) }
els{ 1.081 (>L:vib2,number) (L:vib2,number) 0.045 + (>L:vib2a,number) }
(A:GENERAL ENG ELAPSED TIME:3, hours) 1000 &gt;
if{ (A:GENERAL ENG ELAPSED TIME:3, hours) 1000 / (>L:vib3,number)  (L:vib3,number) 0.050 + (>L:vib3a,number) }
els{ 1.114 (>L:vib3,number) (L:vib3,number) 0.050 + (>L:vib3a,number) }
(A:GENERAL ENG ELAPSED TIME:4, hours) 1000 &gt;
if{ (A:GENERAL ENG ELAPSED TIME:4, hours) 1000 / (>L:vib4,number) (L:vib4,number) 0.027 + (>L:vib4a,number) }
els{ 1.099 (>L:vib4,number) (L:vib4,number) 0.027 + (>L:vib4a,number) }</Value>
      </Select>
   </Element>

 

[lionheart]

Thanks guys....


We need a class on how to make C++ gauges, and a class on how to make things for SimConnect. So many things we could all be doing with our planes..



Bill