Superluminal

I've experimented with routes from various European cities to KSFO, and I can routinely summon up an OOM somewhere over the north Altantic simply by having RW28R entered as the arrival runway. Editing the AIRAC data, as mentioned above seems to work but is fiddly. The best method method of avoiding OOMs is to only enter your arrival runway close to the ToD. Airports with this OOM issue and the 30-degree radial / memory leak issue that I know of are KSFO, KSEA and VHHH. There are others, but these are the ones that give me issues on my normal routes.

I went to P3D at version 2.4, and haven't looked back. I didn't have the slightest issue with having to re-purchase the PMDG NGX and 777, as in my opinion P3D is that good, has a future, and easily eclipses FSX

August it is, then...

It does indeed sound like the EZCA entries are still present in the aircraft config files. Prior to un-installation, the EZCA Config.exe should be run, and when you reach the Ezdok Camera Addon window, click the Restore FSX Files button. This should remove all EZDok / EZCA references in the sim.

I seem to get more consistent framerates in P3D (2.4) than in FSX. In FSX with the 777 loaded I could get anything from 15 fps (EGLL) to 60+FPS at cruise (DX10 enabled) In P3D, frame rates range from 25 fps (FlyTampa OMDB 2.3) TO 45 fps at altitude. Hard to explain, but it's just nicer to fly the 777 in P3D ASN and Rex 4 Textures, ORBX Global & Vectors, PMDG 777 installed in both FSX & P3D Win 7x64 / i7 4770K @ 4.4GHz / MSI GTX760 / 16 Gb DDR3 / Both sims installed on 500gb SSD

http://www.fsxtracker.com/download It's free, bug free, works like a charm, has online map and terrain modes. All you have to do is create an account, run the client and load a flightplan into FSX It also automatically logs all you flights / times / distances / fuel burn etc.

A virtual TSA agent, with sidearm, who appears in the cabin to detain bickering and argumentative forum members passengers

I routinely do 12-15 hour long hauls for my VA, KSEA-OMDB / YSSY-KDFW for example. I run FSX on DX10 all the time, and have never had an OOM. Indeed, I keep the 777 and FSX loaded for weeks at a time, flying hundreds of thousands of miles without ever exiting the 777 or FSX (2 + months is the longest if I recall correctly, when Windoze did a restart behind my back) I have ORBX Global & Vector installed, as well as payware airports galore, plus a whole raft of other FSX addons. Don't want to crow about my lack of OOMs or such, but I find it odd that some are plagued with them, and some have never even seen one. The FSX machine has an SSD, an Intel 4770K overclocked to 4.4, and 16Gb of RAM, and Nvidia 760 GPU

I can thoroughly recommend the CPFlight MCP & EFIS 'EL' versions - very well built, coupled with superior drivers. Works seamlessly with the NGX and Level-D Very keen for the PMDG 777 driver support, due soon...

There is probably some issue with your payment, and a security flag has been raised by the system. I recall RSR posting something to this effect a long while ago. Best contact PMDG direct via their ticket system: http://support.precisionmanuals.com/Main/Default.aspx

OK Finn - In the interests of balance and inquiry, I'm gonna give it a try next flight.

Can't comment on the Q400, but I do know that assigning an Affinity Mask = 7 is akin to running FSX on a tri-core cpu. With regard to PMDG products (in whose forum this thread resides), I've found the 14 mask to be very well suited.

Using a mask of seven ( binary 0111) will mean that FSX is assigned to the first three cores, and is sharing cpu resources with Windows and everything else on your system, leaving the (already under-utilized) fourth core twiddling its thumbs. Mask 14 tells FSX to use the second, third and fourth cores, leaving the first one for Windows, Firefox, whatever... Bit of a no-brainer, and proven to work. Try both and compare usage under Task Manager, and keep an eye on the graphs before, during and after loading FSX.

Remember that when presented in binary, the last digit represents the first core . For example, to enable FSX on cores two, three and four on a quad core non-hyperthreaded cpu, the binary is 1110, and the decimal affinity mask setting is indeed 14. Some of the examples posted in this thread instruct the CPU to use three cores, but do not exclude core one. Try to keep the first CPU core for windows and ancillary programs. Exclude FSX from it. Hopefully now everybody's confused, but if not, it should also be remembered that cores one, two three & four are actually cores 0,1,2 & 3. Binary converter: http://acc6.its.brooklyn.cuny.edu/~gurwitz/core5/nav2tool.html or the easy route: Flight Simulator X (FSX) & Prepar3D (P3D v1 / P3D v2) - Affinity Mask Calculator: http://www.gatwick-fsg.org.uk/affinitymask.aspx?SubMenuItem=hardware

You're welcome - pleased it worked.