jorgen.s.andersen

Disk speeds do have an impact on stutters, but it is minimal compared to 1. raw CPU power, and 2. processing speed in your GPU engine. But with a SSD your load times will be reduced significantly. When you come to the tweaking, here's a handy-dandy tool for calculating the AffinityMask values: http://www.gatwick-fsg.org.uk/affinitymask.aspx?SubMenuItem=utilties Note that the current consensus says to turn Hyperthreading off - you do that in your motherboard's BIOS. And while on the topic of that BIOS, you might want to check with the manufacturer of your motherboard for a BIOS update. Jorgen

In ADE, try this: before you save your project, hit the button "Compile Airport" - this will compile the airport's BGL and put it where you loaded your project. Jorgen

For starters, to optimize P3D to your specific computer, go here: https://www.prepar3d.com/SDKv4/prepar3d/getting_help/advanced_configuration.html Jorgen

It is not necessary to run FSX in compatibility mode under Windows 10. What IS necessary, though, is installing FSX outside C:\Program Files (x86), and run it as Administrator. Jorgen

I have had one of these for almost 3 years now, and I still use the default button layout - I guess I have gotten used to it! Mind you, if you are running P3D, the button layout is different! If you really want to go into button reconfiguration with either FSX or P3D, then you need to get the proper versions of FSUIPC (paid version). Jorgen

The things is that you need the UP-TO-DATE version of AIFP. When you go to convert the flight plans, it will now actually ask you if you want to delete the FS9 flight plans... Jorgen

Mr. Zippy knows where they can be found... my memory sucks that way! But, do yourself a favor and look over the threads here in the forum on installing FSX, there are a couple of tricks that will make life easier for you later on. Jorgen

The specs on that Imac doesn't say anything about the OS, I notice... Jorgen

You are certainly not alone! Since this is a comparatively new Win 10 installation, have you set it so it doesn't reboot on its own after completing the Windows Updates, that occur every second Tuesday of the month, US time? Jorgen

You do remember correctly, but registration emails from my provider, kabelmail.de, go unanswered. I sent an email on May 31st, and it has not been answered. Jorgen

With a 3.0 GHz base clock rate, this CPU is not going to fly a lot with P3D. The "Turbo Boost" rate doesn't matter much, permanent overclocking to 4.1 GHz might make a difference, but then there's the 8 GB of RAM - with no RAM clock rate. Jorgen

Your memory is OK, they got hacked a couple of years ago, and I was able to re-register then. Now they apparently got hacked again recently, and the mess now is the result. Jorgen

It is possible to run P3D with the computer described - barely. You'll be mightily frustrated, I'm sorry to tell you. Jorgen

I have even sent email through my regular email client, and no response. Jorgen

If the builder overclocks and thereby takes over any warranty obligations, then that problem is solved. The question of an i7 vs. an i9 is diffucult, but I would expect that the i9 is more efficient in handling instructions than the i7... I would take the one that can be overclocked to the highest rate, and if that rate is the same then pick the less expensive one. You may also want to look over this thread, sto.... er, copied from L-M's support forums: https://www.prepar3d.com/forum/viewtopic.php?f=6315&t=134300 The topic of CPU vs. GPU reliance is also a difficult one, since I don't know of any published ratios for that. However, P3D is generally acknowledged as being able to offload more processing to the GPU than FSX. The reason I would go with 11 GB of VRAM is that the picture that the GPU "paints" can be more detailed if you have more VRAM. Jorgen

For a CPU you need to get the one from Intel that can run at the maximum GHz rating possible, but remember that the second you overclock, the warranty goes out the window. The number of cores does not matter that much. For the RAM, as high a MHz rating as possible. For the graphics card, get the 2080TI - reason: 11 GB of VRAM. You should, as one of the first things you do with this system, update the BIOS on the motherboard. If the shop who builds this system for you also installs Windows, ask them to do the update. Jorgen

Westway, You missed the essential points: at what clock rate is your i9 running? And what model number is your GeForce RTX card? Jorgen

Also the hardware specs would be nice.... Jorgen

Indeed I remember that for instance the good old AIA models used to have a reflective and a non-reflective model version of each airplane. Jorgen

I am very sorry to hear that. Rest in Peace, John. Jorgen

Il88pp, Every system is apparently different. I have been using Ccleaner and Eusing's Registry Cleaner for some years now and have never had a damaged system..... unless you count that one that's located between my ears..... Jorgen

Loyd raises an extremely important point, which I forgot all about: Never, ever, install FSX to the default location, where the installer wants to put it at C:\Program Files(x86), but to something like C:\FSX, or, much preferred, to a different physical drive. This is especially important under Windows 10, where it seems that the UAC devil is much more aggressive than in earlier versions of Windows. Thanks for refreshing my ailing memory, Loyd - Jorgen

Steve, there are really no issues with running FSX on a Win 10 system, provided you take control of Windows 10. This topic has been trashed out a couple of times in these threads. But to answer your specific questions: 1. Yes 2. No 3. There might be, use a registry cleaner before reinstalling 4. See 1. If you meant best way to go about registry cleaning, then use Ccleaner (free version is OK), or Eusing's Registry Cleaner (again, the free version is OK). Now, bear in mind that an external HDD will be s-l-o-w... if you can find a way to add a SSD inside the computer you might be better off.... Jorgen

+1. I have UT for both FSX and P3D, and it looks just fine. No need for ORBX. Jorgen

You might also want to google "ntdll.dll error" - you will find a lot of hits. Jorgen