homemonster

Pardon me for being word not allowed regarding Lvar creation and interface, but I've been trying to create the same Lvar as below but using one of the split switches on my HC Alpha yoke. The issue for me not being versed at writing these scripts, I own SPAD.NEXT, which appears to have a long learning curve, I own FSUIPC7, but that seems limited to writing Lvars, so I'm now looking into Axis & Ohs if I don't need another degree in computer science.

So if someone has a script they're willing to share, I'll buy Axis & Oh's right now. My needs for heavy Lvar use is small at this point. I'm just trying to find a starting point as to their use, and how to interface between the model and MSFS.

Thanks in advance

I was concerned about the learning curve, and how long it would take me to become sufficient to do these simpler programs. So far the Duke product line is pretty well configured out of the box, but it seems many users are requesting the autopilot trim on both models to be assigned to an unused bind already coded into MSFS. But I will say a quick thank you, for your quick response, and will continue with what I have.

Regards

I to am a novice on Lvar programming. I own Spad.next and FSUIPC7, and am trying to assign the Duke (both models) autopilot trim to one of the HC split switches on the Alpha yoke. I'd like to keep it simple if possible. Any help would be appreciated. If the programs I own are to complex at this early stage, I'm willing to buy another app.

Thanks in advance

Hope I'm not in the wrong forum for this question, but I've sent this problem to Flysimware with no response. My problem is after a major crash on my PC, and rebuild of the OS, reinstallation of

MSFS2020, and reinstall of Flysimware Cessna 414AW v4.4.1, I no longer have working panel gauges, needles are there, but non-working. I've reinstalled several times with same result, so is it possible that I've exceeded my downloads from Flysimware download site, and if so, am I required to purchase again? I bring this up, because I've had this happen before with FSX aircraft, usually due to and error on the vendors part. Everything about the rebuilt OS, MSFS2020, and Cessna 414AW are current. Any thought would be appreciated, as I'm tired of chasing my tail on this problem. I've tried everything! Thanks in advance.

I to try your solution, and thanks for the input, but no joy for me either. Installer dies trying to create "Flysimware_Cessna_414A\pms50_gtn750" in the Community folder. I to have received a fix from FSW. Will have to get a refund.

Thanks

Update, folders are created correctly, but installs stops at this point > "Community\flysimware-cessna-414a\html_u\Pages\VCockpit\Instruments\NavSystems\flysimware_Cessna414A\pms50_gtn750_int <------

I don't the pms_gtn750, installed directly to the Community folder, but on another drive and then linked to the community folder with MSFS Add-On Linker.

Thanks

I've had this issue with other add-ons installing to msfs2020 community folder, so I've had to revert to using MSFS Add-On Linker, which works great, but since the Flysimware 414AW installer doesn't allow for other install folders, I can't install my purchase. Now before everyone suggests verifying Regedit or GPEdit entries for long file names, that's already been done, as has rebuilding permissions for msfs install folder, verifying drive integrity. MSFS works fine, shortcuts  created from Add-on linker are installed correctly. If have done everything on every website I can think of, but still can't install this software. Flysimware as are many other add-on providers are aware of this issue, as they suggest contacting their customer support for a workarounds. So far, I've not heard from them, other than to say, check that long file names are enabled, which as I said, has been done.

Any suggestions greatly appreciated, thanks in advance.

Ok, thanks Jim. I only brought this up since this was not the case with FSX. FSX and ForeFlight both agreed to the same altitude, but I now understand what they’re doing in MSFS. I am aware of the bug concerning altitude swings, and look forward to a resolve.

As of version 5, altitude data from MSFS to Foreflght is not accurate. Mine seems to be off by 1000 feet, ForeFlight showing high. Using Flight Events as my connect socket.

Also exhibits wild barometer data. Hope it’s resolved in version 6, but I doubt it. Too many things for them to fix.

Planes generally flown - Cessna Longitude, TBM930

Doesn't seem you can set VFR altitudes (10,500) on the altitude auto-pilot control, or else I've missed something.

Thanks in advance