kflight

You are correct but based on this article that seems like long way off considering we don't know where they are at with the MSFS version. https://fsnews.eu/ifly-announces-their-b737-will-not-be-compatible-with-prepar3d-v6/ Also a Dev commented on a MSFS forum https://forums.flightsimulator.com/t/ifly-737-max-update/608439 P3Dv6 are on in for a long wait I think.

Its not supported nor has IFLY come out saying that it willl be. One of the reasons I haven't gone to V6, more third party devs have moved on.

What is your sound reference you are using? The stock sounds are great in my opinon.

If you are using Orbx where there be issues? I have global base and many of the LCs. Kie Simpson

Not a bunch, just a few. Most of us are happy with our thousand off add-ons. I'm locked in on 5.4 and i'm content.

No guarantees they will continue to support P3D. They have to do what is financially responsible for them as a company, and I can't get upset about that. I'm going to lock in to 5.4 for now, may peek at v6 in the future once the workarounds are tested and finalized. Way to many add-ons I like to screw around experimental testing in V6. Kie Simpson

We aren't the target audience. But that doesn't mean that don't mind the 1000 or so Beta testers it brings. Kie Simpson

Invested money and are still enjoying that investment to be sure. Also the other add ons that were developed for v5 are fair game as well. Eventually, many devs will start liquidating these assets hopefully, I'm not paying full price if they have no intention to continue to developement on a product as many have indicated. Also, they aren't using the same old ESP, what is written for P3D v4 onward is significantly different from whatever FSX was. Also, old ESP doesn't necessarily mean BAD. Lots of Dunning-Kruger around the ESP and software developement thrown around here and other places, when many don't understand good code is good code. You don't developed brand new software code if the existing is good, just doesn't make sense. Kie Simpson

I don't know how much we trust reviews on Simmarket but two of the reviewers are complaining about performance issues. Has anyone suffered from performance issues with the Justsim version? I'll probably pick it up today, assuming its user head space and timing. Kie Simpson.

How has custom configurations in NCP caused you issues? I've optimized my setup visuallly and get the most out of my GPU via the RDpresets NCP guide, not sure why it would cause isses beyond someones gap in understanding what they are changing. Kie Simpson

Some people obsess over 100% accuracy to airports they never been too, even going so far as to do google earth satelitte comparasion, rather puzzling to be honest. I can understand if that's your home airport but beyond that it gets quite annoying but to each their own no? Kie Simpson

Solved. Found the issue was with the Flysimware gps management tool located at C:\FLYSIMWARE. Ran the GPS panel layout app and selected Reality XP GTN 750 I'm up. I'm going to recheck documentation to see if that's noted in the flysimware manual.

I managed to get the pop up version of the GTN750 to work with the flysimware FA50, however after hours of trying I'm at a lost on what I need to do to get it integrated in the VC. The right entries show up in the panel config but I fail to get it to show up. Below is the pertinent panel entries. [Window00] file_1024=HANGAR.bmp size_mm=1024,1876 window_pos=0.10,0.05 window_size=0.30,0.90 BACKGROUND_COLOR=0,0,0 visible=1 ident=CONTROL_PANEL gauge00=CONTROL_PANEL!clipboard fuel repair, 50,320,340,320 gauge01=CONTROL_PANEL!clipboard map, 50,650,340,300 gauge02=CONTROL_PANEL!clipboard atc, 50,965,340,280 gauge03=rxpGTN!GTN_750_1,50,1250,340,220 gauge04=CONTROL_PANEL!clipboard CABIN LIGHTS, 516,454,37,37 gauge05=CONTROL_PANEL!clipboard DOME LIGHTS, 516,524,37,37 gauge06=CONTROL_PANEL!clipboard RECOG LIGHTS, 516,594,37,37 gauge07=CONTROL_PANEL!clipboard PANEL LIGHTS, 516,664,37,37 gauge08=CONTROL_PANEL!clipboard kneeboard, 445,1005,530,400 gauge09=CONTROL_PANEL!clipboard OPTIONS, 485,1760,520,110 gauge10=CONTROL_PANEL!clipboard COLDSTART, 550,800,300,70 gauge11=CONTROL_PANEL!clipboard HOTSTART, 550,870,300,70 [Vcockpit01] Background_color=0,0,0 size_mm=900,900 visible=1 pixel_size=900,900 texture=$gps_1 gauge00=Falcon_50!SYSTEM, 0,0,2,2 gauge01=Falcon_50!FUEL_USED, 0,0,2,2 gauge02=Falcon_50!FUEL_SYS, 0,0,2,2 gauge03=Falcon_50!CLICK, 0,0,2,2 gauge04=Falcon_50!SOUNDS, 0,0,2,2 gauge05=Falcon_50!KEYS, 0,0,2,2 gauge06=Falcon_50!AP_MODES, 0,0,2,2 gauge07=Falcon_50!SPD_HOLD, 0,0,2,2 gauge08=Falcon_50!ALT_HOLD, 0,0,2,2 gauge09=Falcon_50!ENGINES, 0,0,2,2 gauge10=Falcon_50!START_SYS, 0,0,2,2 gauge11=Falcon_50!PRESSURIZATION, 0,0,2,2 gauge12=Falcon_50!TEMPERATURE, 0,0,2,2 gauge14=FBGS_XMLSound_x64!FBGS_XMLSound, 0,0,1,1,Sound\FSW#121 gauge15=Flysimware_Fuel_Dump_x64!Fuel_Dump, 0,0,2,2 gauge16=rxpGTN!GTN_750_1, 0, 0, 2, 2,NO_BEZEL gauge17=rxpGTN!GTN_750_1,10,10,900,1036,NO_BEZEL gauge18=rxpGTN!GTN_750_1,66,190,596,509,NO_BEZEL gauge19=dsd_p3d_xml_config_x64!config, 5,5,5,5, ./gauges/dsd_F50_xml_config_x64.ini gauge20=dsd_p3d_xml_sound_x64!Sound, 5,5,5,5, gauge21=Falcon_50!ANNUNCIATOR, 0,0,2,2