Bob Scott

You can go into GSX and select "Customize Aircraft" then click on the aft door you don't want stairs at and select "No door at this position"...then save. That will prevent GSX from pre-positioning or rolling stairs to that exit.

Not even a hint of the thread topic left in this discussion...

System specs? What does GPU and CPU core loading look like while this is happening? Daytime or nighttime? Weather? At all airports or a particular one?

If someone has a tablet or phone, and elects to read the thread, they won't know that they just signed up to download and page past dozens of pages of your log file until they get to that post. So no, it isn't as simple as "just move on." The log file text wasn't removed, it was placed behind a page break so everyone reading the thread doesn't have to wade through page after page of plain text...something you could have done in the first place...or maybe you could have asked before dropping a giant file dump into a forum post. I doubt the admins at the org would be any less annoyed at a file dump in their forums than I am.

It's not free, but the Aviasoft Remote CDU works very well with the PMDG 737, and it's fairly inexpensive (10 Eurogazinks). Works on any device that can run a web browser.

ActiveSky displays the METARs and TAFs in their native formats, which use regional standards for units. It sends that data to the sim in P3D's internal machine format, and writes out a global weather file which is then read by the add-on and reformatted into what you see on the EFB. So the problem lies strictly in the iFly panel and its display options. I don't have that add-on, so I can't say if there's an available option to display temp in deg C, QNH in HPa, and winds in knots, as is done by most of the world outside the US and Canada with the exception of a small number of eastern European and Asian countries.

With regards to P3D, I truly can't conclude that the latest is the greatest. From the perspective of the complete sim environment (scenery, weather, aircraft options, flight dynamics, avionics, ancillary utilities etc), P3Dv5 and P3Dv4 have the most complete array of available enhancements and extensions, and you probably already have many of them already. In P3Dv4, a good number of rather nice payware add-ons were gifted to the community as freeware--the whole Milviz catalog, Simskunkworks, etc. There are a ton of freeware enhanced small airports published by Orbx for v4, and the author's death precluded anything more than a hope-for-the-best straight port into v5. P3Dv5 is still my go-to for complex jets into large complex add-on airports, as the performance is somewhat better. Add-on compatibility for v6 is really spotty--it will require a considerable amount of program-by-program tinkering to adapt add-ons made for v5 and earlier to v6, and some won't be usable regardless. It's also easy to take the sophisticated tools we have for v4/v5 for granted as well--for example ADE to edit airport characteristics, AIG for traffic, etc. Some of those capabilities will be diminished, and some will be outright left on the table if you move to v6. Honestly, the biggest improvements to the P3D environment in the last four years aren't in software at all. Both P3Dv4 and P3Dv5 have benefitted greatly from significant advances in hardware--the RTX30xx and 40xx series video cards and several generations of fast 5 GHz class 8+ core CPUs have made a huge difference in performance over that time frame. I greatly enjoy my parallel P3Dv5 and P3Dv4 installations running fast and reliable on modern hardware, however I haven't yet been able to make the leap to P3Dv6 because of all that's gone missing amidst the exodus of developers answering the siren's call of SimZilla.

In case anyone is wondering, it is quite inconsiderate of others to post 1000 lines of your log file into a forum post.

The sounds are much better in v1.0.2, although the engine start sound effects are still way too loud on the flight deck. It's liveable. Still getting hit by the startup CTD...about 50% of my attempts to start a flight end with a CTD after selecting airfield, parking, and time and selecting "FLY NOW". It's good for short-to-medium legs now, but abbreviating long legs is a problem as you can't do time-accelerated flight (fuel burn doesn't change to reflect acceleration) nor can you teleport ahead on long flights due to fuel load changes being locked out after engine start. It'll answer the mail for freight ops until the PMDG 777F shows up.

Not a lot, but it made enough of a difference to keep that one golden core that runs my P3D main thread stable at 6 GHz. A 13900K/14900K running at stock speeds is still very, very fast and will rock P3D with CPU package power averaging around the 100-120W range. When you overclock all those cores, power demand and heat production goes up rapidly, requiring an aggressive cooling solution. The 12th gen and later Intel CPUs allow for some interesting partial-overclock scenarios, as well as dynamic clock bumping on select cores based on power/temp thresholds.

Writes to SSDs slow down with a nearly-full drive. So a program like a flight simulator where the vast majority of the storage I/O is read-only isn't affected that much. Also, the old wisdom of putting the OS on a different drive than flight sim has been OBE--the old way was intended to prevent lots of slow I/O due to head thrashing as the drive serviced an OS on one part of the drive and the sim on another. SSDs are random-access...there's no real advantage to separating them anymore. A single large (e.g. 4TB) or a couple medium (1-2 TB) SSDs is the config I'd recommend today. I'd shelve the old 500GB drive or maybe put it in a gaming box for the grandkids.

Because...I actually did read the OEM's marketing and advertising material...not a word in there about flight simulation, but instead they quite clearly focus on gaming. That's not to say that the machine isn't suitable for MSFS, but it isn't configured specifically for it--if they had gone to the trouble, one would expect the specs to at least make passing mention of it. So FS-specific issues like SMT, AV settings, search indexing, network QoS, G-Sync/V-sync, frame generation, etc all need to be looked at with flight simulation in mind...something a machine "built for flight-sim" (i.e. what comes from purpose-built OEMs like Jetline or XForce PC) would already have configured.

Having a saved flight that consistently reproduces the problem is a good start. I'd load that flight, then change the date/time and see if it still occurs--if not, it's likely an AI traffic problem, with a problem airplane or traffic BGL. If it still crashes, reload and try taxiing down the length of the runway to see if it's occurring at a particular point along the runway, which would suggest a scenery problem. It might also be a corrupt sound file that's triggered at an airspeed...FS2Crew or the airplane perhaps, or possibly you have multiple sound devices active and conflicting. If there's precip (rain or snow), try with clear weather to see if the barrage of particles is overloading the GPU or VRAM.

I don't have a list, but in P3D I have flown LPV approaches in the PMDG birds, FSL Scarebusses, Majestic DHC-8, and I believe (not 100% sure) it also worked in the FSW Lear 35/Falcon 50 with the RXP GTN750.

Mixed emotions, to be honest. The product itself works well and puts an almost fully-functional GTN unit into a panel designed for it...but there aren't really a lot of XP acft that are designed for it. Because the author has gone and done a runner on us--and this isn't the first time, either--I can't in good conscience recommend it now. I have no idea if it will be supported in the future, and the database it's using now is already 14 months old. Caveat Emptor--let the buyer beware.

Your complaint is with RealityXP, not Garmin. Garmin graciously allows third-party applications to use their real-world trainer in flight sim applications, but Garmin neither promotes those third-party programs nor do they guarantee their suitability for that purpose. That's between you and the third-party application developer--in this case, RealityXP. Jean-Luc Dupiot d.b.a. RealityXP has, once again, gone off the radar and stopped responding to support requests for many months now. So with that knowledge in mind, you have the option of either figuring your installation issues out for yourself, perhaps with a little user-to-user help here, or taking advantage of Flight1's 30-day money back guarantee, as the RXP Garmins are sold using the Flight1 wrapper.

OK, this one has long passed its sell-by date.

This sorta reminds me of a guy that goes out and buys a $75,000 tournament bass fishing boat and then gets mad because the fish won't just jump into the boat for him... The PC was not "built for flightsimming"--it was (at least theoretically) built for gaming. Might well be that Red Dead Redemption II will run just fine on it out of the box, but not SimZilla. I'd start with the usual diagnostic runs--MemTest 86+, a stress test like Prime95, etc. Maybe try a few different video drivers.

LPV glidepaths are simulated, not by P3D itself, but in some advanced add-on RNAV units and/or aircraft panels. The position data received from P3D via SimConnect serves as a proxy for the GPS satellite-derived position data.

Back to topic, please--which is demand for P3D scenery and acft, not video cards.

Does AAO have the ability to scan a joystick's current button state? I manage this with a Lua script in a different program by reading the throttle quad button state and OR-ing buttons 21-25 bitwise and then sending the appropriate control based on the result. btn 21 is bit 0, btn 22 is bit 1...btn 25 is bit 4. You have six valid values: 0 (00000) = Disarm 1 (00001) = BTV 2 (00010) = Lo 4(00100) = 2 8(01000) = 3 16(10000) = Hi I wait until I have four valid and matching results at 125ms intervals to ensure I don't catch the switch states in between knob positions while the knob is being rotated. This also has the advantage of properly setting the control without need for an initial btn up or down event to sync the TCA's knob position with the sim panel control's state.

With HT off, an AM isn't really necessary. Since the 13900K allows per-core HT control, you can also turn HT off just on the core that runs the main thread (assignable in the config file), and that also will address the major issue that an AM will prevent, which is sharing of the main thread's core with other processes on it's paired virtual HT processor. I have my 13900KS overclocked to 6 GHz on one core (main thread assigned to that one), HT completely off, one block of 4 e-cores disabled in BIOS to reduce power demand/heat, and an AM that blocks P3D from using the last couple of e-cores, which are kept active and available for other processes. The improvement over running stock is marginal and not strictly needed--the CPU is still a rock star at stock speeds. That said, tinkering with and optimizing the config can be rewarding in its own right.

v1.0.2 change list Art Fixes/Changes Fixed - Holes in L1 door Fixed - HP VALVE should illuminate red during fire test Removed - Ice detector probe Added lights to ENT and CLR during IRS test Fixed - make the window scratches less prominent Added - Model circuit breakers that are relevant in checklists Fixed - Tiller animation reversed when using Nose wheel steering axis Fixed - Beacon bulb doesn’t flash with light Fixed - Cabin lights not showing in external view Fixed - Cabin window tint Fixed - FMS Glow reversed. Left FMC activates right glow source and vice versa Fixed - Unable to dim MCDU lights Fixed - Missing Backlight on Oxygen Panel Gauges Fixed - MCP lights illuminate the center window column Fixed - Rotate tires to different positions Fixed - internal door lock lever freighter Fixed - APU Integrated LP fuel pump switch backwards Fixed - Printer buttons lit when C&D Added - Seat sliding back and forth Fixed - Collision zones being too big Fixed - EFB and Altitude select glass flicker in cockpit Fixed - external light LOD issue Fixed - Beacon lights not showing properly Fixed - VOR/ADF gauges missing label Fixed - Glass cover of the rear strobe light does not fit properly. Systems Fixes/Changes Fixed - Aircraft gives CG warning even though no CG has been entered Fixed - Resetting it self back to zero when engines shutdown on older versions it didn't do this Fixed - WASM Crash - Loading waypoints too fast crashed aircraft on ground Fixed - SEC WASM crash Fixed - Next waypoint on ND distance doesn't change at the same time Fixed - GPWS test/cancel PB not testing GPWS Fixed - RMI Issue with 360 Fixed - Gear anims too slow Fixed - When directing, there is a small gap in drawn flight plan and distance is wrong Fixed - auto disconnect tiller option not working Fixed - When landing you get a triple click on touch down if landing with A/THR on you would not get this as the downgrade like modern Airbus Fixed - EGNX TNT 2N Departure Fixed - AP not disconnecting on flight control input Fixed – Green Dot calc in LBS and over 20,000ft seems to be wrong Fixed - Can't delete custom waypoint database Fixed - EXT PWR AC Meter displays no frequency when EXT PWR is connected Fixed - EMER Bus also showing voltage in C&D Fixed - VS selects negative value single digit Fixed – During climb or descent - Pressing ALT.HLD - Aircraft very slow to react (with High ROC, took 1800ft to react ) Fixed - DC EDD BUS during standby generator test Fixed - NAV not following track Added - PLEASE WAIT prompt for VIA/GOTO on LAT REV as can take very long Fixed - When VOR/NAV/ILS set to NAV, Glide indication appears in the vertical scale on PFD (should only appear in ILS Mode) Fixed - Selected autobrake de-selects when gear is dropped Fixed - Entering CG into PRG code crash Fixed – Nose wheel steering tiller issues when using separate axis. Note the EFB ‘Rudder controls tiller’ option must be set to NO. Fixed - Wildly varying fuel calcs on INIT B Fixed - Esc sim / pause bug causing plane to break Fixed - PRE-SET speed works as it should, EXCEPT : On departure with Profile Armed, Should clear itself (replaced by ---) at acceleration altitude (currently stay PRESET until ALT* or LVL/CH pressed) Fixed - Pressing the Status Page - When in normal, should revert automatically in MEMO Page (no need to press CLR pb) Fixed - FMS not clearing properly on landing Fixed - APU FUEL LO PR ECAM still popping up with L INR TNK pumps off Fixed - STEP ALTS page bringing up the wrong page Fixed - PROF is re-engaging when reaching bugged altitude in LVL CHG Fixed - Not able to insert KBDL into FROM/TO Fixed - Freighter: cycling parking brake with engines off does not deplete the accumulator Fixed - Sky high pressurisation bug Fixed - Oxygen supply switch inop in pax version Fixed - THS trims to aggressively Fixed - Elevators don't drop down with no HYD Fixed - Some users reporting that manually adding an alt constraint does not cause vnav path to recalculate Fixed - OIL LO PRESS Never displayed (in low oil press condition) Fixed - Added more details on the flow bar Fixed - When brake glow effect is active. So wheels above 550c the effect goes away when battery selected off. Fixed - Changing restrictions has no effect Fixed - Packs Off operations maybe wrong Fixed - FMC freezes when inserting LFSB ILS15 approach Fixed - VLS band doesn’t move when spoilers extend Fixed - Engine Bleed Flow Bars Fixed - Seen two reports of people's pitots freezing despite having pitot heats on Changed POV L & POV R quick view Fixed – Incorrect turn at holding fix Fixed - Revert active fix is white on ND change Fixed - WASM crash with specific arrivals Fixed FMA in Mach mode says SPEED, should say MACH Fixed - PreSet light not extinguishing when switching to profile mode Fixed - Selected Heading Index on RMI not working Flight Model Fixes/Changes Adjusted - interactive points to not crash when opened on the ground Adjusted - Ground effect reduced to give a more natural entry feel Adjusted - CFD ground effect range reduced to give a better feeling near the end of the flare Fixed - Reduced empty weight of pure F model to give larger payload range Adjusted - Thrust output of engines adjusted at idle. Giving better idle rolling speed at all weight ranges. Sounds Fixes/Changes Fixed - The sounds internally are rather quiet compared to the external sounds, leading to a huge difference in volume when changing views between inside and outside Fixed - Gear Thump Issue When the gear thumps occur, all other sounds are temporarily deadened. Fixed - Engine 1 internal sounds don't seem to change with increased throttle Fixed – Taxi gear cockpit ambient sound Fixed - Whooler sound file seems quite low quality Fixed – engine sounds fade away Fixed - Altitude Alert sound way too low Fixed – Overall sound levels Fixed - Windshear call out from ANN TEST light should play 3 times then stop not keep playing all the time Fixed - All interior sounds are muted at some point during the gear sounds Fixed - Right landing light no sound from Off to On Fixed - GPU Loudness Fixed - Sounds seem to go mute at very fwd and very aft of cabin Fixed - P/B sounds - All 6 buttons here do not make any sounds Fixed - Avionics fans volume decreases when ENG 1 is running, even further when thrust applied Fixed - Buzzsaw sound tied to explicit engine value of between 75-76% Fixed - Engine sound levels during TOGA takeoff not quite right. Fixed - MINIMUM callout not being called at DH Fixed - Fuel pump sounds missing on the outside Fixed - HYD sounds on external view are not audible unless right under LG bay Fixed - Cabin/wing views have muted engine noise Fixed - Fuel pumps seem to not be tied to fuel pump buttons high pitch sound can be heard all the time when AC power applied to aircraft even with pumps off and GPU on Fixed - When aircraft sitting on stand the sound levels using drone camera don't make sense as it starts quiet gets louder and then stays that loud for a very far distance Fixed – Flight deck is very loud but levels drop up and down Fixed - Seats have no sound even when moved Fixed - Eng1 v Eng2 exterior volume E2 is super soft in all phase vs it's twin. it's like 70-80% as loud in various povs around the aircraft.

They were good times, indeed. The first round of BRAC base closures, which included Norton, was announced the day I reported in there--my wife and I heard the announcement on the radio literally as we were driving down the hill on I-15 into San Bernardino. I served five years there and still managed to get out of Dodge before they locked the gates. Fifteen years later, I was at a conference hosted by 12th AF at Davis-Monthan AFB in Tucson. They set up an executive tour of the AMARC boneyard for a few interested conference attendees, and while we were driving in via the back gate, a C-141B with its Norton tail flash still intact was coming out through the same gate on three flatbed trucks, on its way to the smelter after having just been guillotined. I'll admit that seeing that left me a little bit choked up... And in an attempt to not completely hijack the topic here...suffice it to say that minimum procedural separation in high-density airspace is often just that--minimal. It's like that in dense urban airspace all around the world, and on a good number of the air routes as well. On the North Atlantic Track system at night, sometimes it looks like you could walk between Newfoundland and Ireland on the backs of all the jets stacked up at 1000 ft intervals headed in the same direction.

Yup...you're right, I was thinking of the regional products.