The A2A Simulations Community

The windshield.dll should not crash with P3D v5 and ASP3D. At least it doesn't crash on my system.

Have you tried previously to install Active sky for V4 into P3Dv5? Maybe your P3D is still loading the old as_connect_64.dll that was intended for older P3D versions.

The configurator is numbering the joysticks according to the rules from SDK and LM. However, we don't have a way to verify that from P3D itself and it seems to bug out in some unusual hardware configs. Rare, but annoying. If all else fails, you can check the numbers assigned to controllers in your P...

Hi, in order to get the prop effect working you need to set the variable (L:Eng1_RPM, number) somewhere in XML to the RPM of your engine.

Hook wrote: ↑

15 Apr 2020, 03:57

Don't you get the same effect by removing or renaming the Windshield.ini file?

No, that's only a configuration file loaded once the DLL is initialized.

The (L:Throttle1Position) is a local simulation variable. You can access it from XML or C++ gauge, but you can't access it remotely from Simconnect, at least not directly. You would need some custom code on the simulator side, that reads the variable and sends the value at another app either using S...

Hmm, somebody called?

We've dealt with similar issue in the past and it was FSUIPC that caused radios to stop functioning properly. I thought we made a workaround for that, but it may be that something's still not quite right with ADF. I'll need to investigate.

Sorry, on-the-fly change of audio device is not supported ATM, aicraft reload is required.

Unfortunately that's not possible at this moment.

Unfortunately yes, I haven't seen any Warthog extension on the market that would match your requirements. Though I have seen some DIY extensions built from curved PCV tubes. Not as pretty, but functional. Another off-the-shelf option is VKB stick with curved extension. Better than Warthog, but more ...

Hello,

this already works using FSX/P3D assignment for "Auxiliary fuel pump (on/off)". I think by default this function does not have any shortcut assigned.

We reported this issue to Lockheed some time ago.

In 76C there is a short delay between typing the code and actually changing squawk (3-4 seconds), so in case of errors the pilot has time to correct.

Hmm, I don't think we're doing anything special, they should work the same. Set the code and that's it.

It's a limitation of FSX SDK. Even if the axis can be assigned in FSX menu, it may not be visible from the part of SDK which we use.

Hello,

it may be a long shot, but do you have autosave function enabled in FSUIPC or other addon that periodically saves P3D in the background?