WarpD

To get support for this go here for our Support Email.

I will look into this approach and see what is/isn't possible. Best I can offer.

MSFS 2020 is not quite up to the level of capability that Prepar3D is. Because they want it to run on an XBox, it has a great deal of limitations. MSFS 2020 isn't quite as safe for commercial products with regards to IP theft.

The original post is 12 years old! The individual is no longer a part of AVSIM.

Since LVARS are only accessable via either execute_calculator_code (C code only) or in an XML gauge... I don't see how you're going to solve it. There is no C# support for LVARS.

I can't speak for FSUIPC... I've only ever used SPAD.next myself. But, as I stated... the course setting is 100% sim... not a value inside the gauge at all.

The course is set using default FS events... we don't have anything to do with it. If it isn't working on your system with SPAD.next then you may have something not allowing it to function when the FMS (GPS mode) is in control.

They won't buy it... they believe they're entitled to take whatever they want.

Good lord... seriously? I can't imagine waiting for that to load... But yes... I was talking non-AI... didn't realize this was AI.

There is a limit of 18 liveries.

FADEC doesn't control speed of the aircraft. It only controls engine thrust levels, that's it. There is no autothrottle on this aircraft. The performance numbers only provide for fuel burn calculations.

Uh... what??? I found your statement of accuracy something Captain Obvious might say... amusing and redundantly obvious. Nothing about Flight1 in that at all... so how about we not make things up... ok? Keep things civil.

Since Garmin wrote the code... of course it's extremely realistic.

Contact us via our support email. This is going to require a higher support level.

Ken, I'm pretty certain there are military versions with no toilet onboard... :smile:

Can you please provide the date/time on the MPI_GNS.gau file? I know you gave the date... want time as well please.

Could you give me a screenshot of the waypoint entry window with the waypoint entered into it?

I have loaded up a 172 with a 530/430 combo and placed it at KSAT. I then proceeded to the FPL page and started entering waypoints. I entered YENNS which was 159* @ 28.5nm. I added EMBOW which was 343* @ 10.4nm from YENNS. I added GOBBY which was 354* @ 50.7nm from EMBOW. I then went to SkyVector.com and created a flight plan there with YENNS, EMBOW, GOBBY. It stated YENNS was 148* @ 28.9nm, EMBOW was 352* @ 10.4nm and GOBBY was 004* @ 50.7nm. I have confirmed that the waypoints are in the data. I have confirmed that I can enter the waypoints into a flight plan. I have confirmed that the resulting values are relatively accurate (magvar can change headings). Given that... the question is... what isn't correct on your system. Please go to the folder you installed Mindstar into (usually C:\Program Files (x86)\Mindstar\Flight Simulator Addons\) and verify there is a GNS.ini file. If there is, please verify in that file there is an entry that states NAVDATA=REALNAV. Image:

What waypoints do you find missing? I assume you are trying to create a flight plan with these waypoints?

FYI... DIRTO crash issue is now addressed. Go the Eaglesoft support forum and read up on the details... do not just download and install... read the requirements first.

Just to be clear... ShadowPlay is free.

ShadowPlay has a zero, and I really do mean zero impact on frames. It's a hardware accelerated recording system that utilizes the built in H.264 encoder on your video card to record videos in MP4 format. It can record up to 4K resolution at 130bps with minimal performance impact. There is no software that will be able to compete with that.

Johnny... the videos you've seen me make for the XLS+ were ShadowPlay:

I use ShadowPlay

Yes, all of this is normal.