The A2A Simulations Community

Yes, depending on if you've bought MSFS on Steam or on MS Store, the program looks for one of the storage folders listed here in section 7.E https://a2asimulations.com/forum/viewtopic.php?t=74691 Changing the aircraft name in the community folder will also change the name of that storage folder, so ...

There is no such lvar and there won't be, as these displays sometimes show dashes or letters and lvars can only store numbers.

Current dme hold frequency is already there in the frequency simar for the third nav radio.

Hello, you have to set at least one of the wind and gravity scalars (wX, wY, gX, gY) to a value different than zero. These scalars control in which direction the rain moves on the texture. Here's an example from one of our aircraft: [Window] x=0 y=0 w=2048 h=846 wX=0 wY=-1 gX=0 gY=0.7 gCurve=3 speed...

There's an option for that setting in our tablet, so you should change it there. The aircraft probably takes priority over the GPS setting.

Can you suggest any 3rd-party gps which uses navigraph database. I have tried to search for it but cannot findone, You can use navigraph hub to update your MSFS database too, then it should have the same data as Navigraph. But as AKar pointed out, some advanced approaches won't be available in the ...

GNS530 is developed by Asobo and Working Title teams. It's using the navdata built in MSFS.

Hello, Comanche does not have any nav data, it depends on the 3rd party GPS you use.

Easiest way would be probably by adding a new custom sound to sound.xml, linked to the LocalVar posted above. Similar way to how we already have some custom engine sounds defined in our sound.xml. SDK lists all the parameters you can use. https://docs.flightsimulator.com/html/Content_Configuration/S...

To have it play in sync you have to hook the sound to our simvar (L:LightStallWarning,bool)

It's just a graphics engine limitation at dusk and dawn, the radios are off.

No, not needed in the current version.

The takeoff trim for Comanche is reported as 0.78 RAD which is roughly 45 degrees! And the maximum value is set to 100 degrees! This cannot be right and this is the reason why XPForce cannot handle it. It seems that it uses the absolute values and expects trim position to be within -30 to +30 degre...

L:XpdrLight

Indeed, it looks like Microsoft forgot to put the shortcuts for the fine grade levers control in the UI, these shortcuts only exist internally in the SDK.

We will tweak the stock button controls for the next patch.

Yes, for example in real life there may be a need to change sensors calibration.