metalmike

Deleted.

This is especially noticeable in cinematic mode. Every time the camera seems to change angles, the engine sounds "revv up" again. I've noticed this with multiple aircraft.

Has there been any fix to this? Several updates later the problem persists...

Gotcha, I'm running 64-bit Windows 10.

As the title says, just lately I've been getting unexpected "dings" in FSX:SE due to memory (which is unusual; steam edition has honestly been pretty good to me), while when I look at process explorer, FSX is inching close to 3GB of VAS used, rather than 4GB. Any ideas? The first instance of this happening was flying into T2G Seattle on Pilotedge with the NGX. I was using ORBX PNW, AS16+ASCA (lowest cloud texture resolution possible) and my textures for SEA are downsized to 1024. Autogen I believe was on "normal", water low 2.x. I got an OOM right after vacating the runway. Secondly, it happened in the LA area flying the A2A 172 on PE, though before this flight I had manually changed the LOD radius to 6.5, so that might have been the culprit in some way. (figured flying GA would allow me more wiggle room in terms of memory and performance, and usually that is the case without issue) Yesterday I was flying out of JFK in the PMDG 744, LOD radius 4.5, autogen normal, FSDT JFK textures downsized, all other settings same as the Seattle scenario I mentioned above. In this scenario, I WAS running AI Ship traffic (the addon one that's available here) I run Steve's DX10 fixer. I also run FTX Vector, but I have most of the features turned off, aside from the main highways and roads, and a few other things such as beaches, golf courses, etc. This sort of thing has only cropped up recently, and the only thing I can remember installing recently is some photoscenery for Utah and Arizona (which was turned off in all these cases). Like I said, in all of these cases, the memory was only showing about 3GB of usage at the onset of the "dings".

The MD11 runs the best for me, as it is the oldest and least detailed. Of the more "modern" ones, the NGX performs better than the 777 and 747 on my machine.

In the aircrafts cfg file, under the specific livery entry make sure it says "model=vc". I think by default the field after "model=" is just blank and therefore has only a 2d cockpit unless you change it.

Turned out to be Ezdok v2's effects processor settings. Just had to turn all the "turbulence" settings in EZCAv2 off.

Fresh install of FSX:SE on a new PC, using ActiveSky 2016. This his happened with both the FSL A320 and the NGX (I haven't flown any other of my aircraft yet). I'm constantly getting a subtle left and right bank, even if I turn off Active Sky and clear all the weather. Can't seem to pinpoint what might be causing it because, like I said, it continues even with the weather completely cleared.

I'm pretty sure they no longer support the MD11. I could be wrong?

That's correct, but I did not remove the Orbx afcad. Disabling "Anchorage terrain" is all that needs to be done.

OP says it's not tested in FSX. Any brave souls tried it for FSX:SE or even just boxed? Wanna know if there are any guinea pigs out there before I drop $10, as cheap as it is.

I am trying to tune 118.75 in standby comm 1, but it keeps just reading "DATA" when I get close to tuning the frequency. What am I missing?

I was having a problem with FSUIPC crashing my sim on startup yesterday as well. He just recently released version 4.962 which fixed the problem for me.

For what it's worth, I follow a guy on Twitter who flies for Atlas, and they do indeed use KGS. Michael H