Bob Scott

The other approach to this problem is to edit the airport file (aka ADE, AFCAD, AFX file) and remove the parking spots where statics are parked so that your AI can't see or use them.

The C0000005 error code just means the program tried to access memory outside its allocated address space, and that can be caused by many different kinds of problems, both software and hardware. It's the computer analog to running a fever--lots of unrelated problems can cause it, so it's not going to offer up much of a clue as to its origin on its own. The fact that the offset (DF0BF) is the same in terrain.dll on both of these failures suggests to me that you probably do have something unhappy going on in your scenery config--a bad scenery texture or BGL, or perhaps a boogered-up terrain.cfg file. Something like an unstable overclock wouldn't likely throw the same error at the same place.

I've seen a couple of PSUs loaded at/near the published capacity that eventually failed and took out the motherboard and/or other components, and a few more where the disorderly power interruptions from a failing PSU corrupted a drive to the point where a software rebuild was necessary (an exercise which could have been mitigated by making regular backups, but that's another discussion). Other less catastrophic but still very aggravating consequences of an undersized PSU include CTDs, blue-screen crashes etc when the PSU can't keep up with peak current demand. When that happens, you have some FUD, all right--a Functionally Useless Device. There's a reason the GPU manufacturer publishes a min spec for the power supply.

I have a full surround sound system on my primary flight sim--I found a Yamaha home theater receiver on the scratch-n-dent table at the local Best Buy, and added a couple pairs of Klipsch/Polk bookshelf speakers I wasn't really using. Honestly, surround sound for simming is overkill--the sound configurations of the major sims don't make much beneficial use of anything beyond stereo. What does really add to the sound immersion is a decent subwoofer--I also found a Polk 12" powered subwoofer on the discount rack, and adding that made a really noticeable improvement by adding low rumble and growl that you can almost feel. On my other two systems I use Logitech Z625 2.1 sound systems. The Z625 has a reasonably good subwoofer, crisp 3" drivers with a separate tweeter, and it will take either an analog coaxial or optical/digital SPDIF input. I require SPDIF here, as I also use radio transmitters in my man cave and the optical fiber link prevents RFI from getting into the audio lines when I'm on the radio.

No, I don't. Can you get away with it? Maybe...but PSU manufacturers aren't likely overstating their specs. PSU failures are real butt pain, and can be catastrophic to other system components as well as boogering-up a nicely set up configuration, requiring a reinstall from Windows on up. A higher-capacity PSU is pretty cheap insurance. Either one is likely to be a significant step up from the 2080 in MSFS and are reasonable choices to match the 7800X3D. As to "future proof"--ain't no such thing! There will always be something mo'-better-faster right around the corner.

Send an e-mail to support@aviaworx.com Mark is usually very quick to reply.

In FSUIPC I assigned a key to the rotor brake control, with 76014 as the command parameter. Pressing that key then moves the seat back.

Let's not turn this into another sim-vs-sim evolution, please.

And don't forget to check the power cable, both at the wall and at the computer. Many years ago I had fits with a sudden flurry of uncommanded shutdowns, only to find I had a loose AC power connector after days of troubleshooting. Sometimes, it's the simplest of things...

Yes, you can. On my MSFS box, I have a Thrustmaster TCA Boeing Yoke and an Airbus TCA sidestick--I use the twist axis on the stick for the steering tiller on acft that use the yoke for primary control.

What airplane? 20% N1 at idle on pretty much any jet engine operating at altitude is very low. If you're accelerating in a descent, it's probably because you have too high a descent rate set. Think of it like a sled going downhill--the steeper the hill, the faster you go.

I'm referring to setting the refresh rate to 1/2 the monitor's hardware refresh rate at the driver level--that's done by writing registry settings for the graphics system using a utility like nVidiaInspector or Rivatuner.

I did some reading on adaptive V-Sync, and I now believe that's a considerably different proposition than using fixed 1/2 refresh rate VSync like you'd get by setting it with nVidiaInspector. As I understand it, adaptive V-Sync just turns regular v-sync on and off based on high/low frame rate thresholds--what you need is a constant 30Hz sync rate at the driver level. That can be forced with NVI, and I believe it's also possible with MSI's Afterburner/Rivatuner utility suite. The magic combo for me over years now is running VSync-limited to a hardware-enforced 30Hz refresh rate, and frame rate unlimited in P3D. In my case, I have a 55" 4K TV that will natively accept a 30Hz input, so I can just set the refresh rate to 30 in NCP and then turn V-Sync on with frames at unlimited in-sim. With a monitor that only allows a fixed 60Hz refresh rate, you have to use the aforementioned driver-level intervention to lock at 30.

You might try turning VSync on in P3D with half-adaptive rate set in NCP and unlimited still set in P3D's settings. When the P3D frame rate is moderated by VSync, lookahead frames are no longer produced, and you should see the main thread core (core 0 unless you configure it otherwise) averaging somewhere more like 75-80%. When it's pegged out at 100%, you're in the stutter zone. BTW, are you running with hyperthreading on? If so, adding an affinity mask is important to fence off, at a minimum, the paired virtual CPU on the core running the main thread. An AM of 1365 (0x555 or binary 010101010101) will restrict P3D from running on the 8700K's HT virtual CPUs. P3D with HT off requires no AM, and was considerably smoother with my 8086K.

Again, pasting hundreds of lines of logfile clear text (or a similar amount of any other text) into a forum post is not acceptable in these forums, and not up for debate or discussion. Several folks here have mentioned workable alternatives--please use them if the need arises again.

A couple possibilities come to mind based on past experience with a similar configuration (8086K + RTX3090): If you have dynamic lighting on with SSAA and have your taxi/rwy turnoff lights on, it can really slam the GPU and produce stutters. I ran 4xSSAA with dynamic lighting off in daytime, and 4xMSAA + DL at night. Having them on together was a bridge too far. Acft that don't use DL for their taxi/RTO/landing lights don't tend to have that issue. Could also be AI traffic related--try turning traffic off or down and see if the stutters persist.

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.