SteveW

I was at Cosford last September and there seemed to be just as much room as usual.

Uncheck "Master weather enable" on the weather page.

Ideal Flight S - native P3D v6 install - installs outside the sim (Flight 1).

Since we become members of the Users group when we log into windows and become authenticated, permission to alter file or folder content is properly achieved by adding the Modify permission to the Users group on that folder or file. I don't think this is a cure for Randy's problem, since the Users group already has modify access to the SteamApps folder. Hi Randy! A while since we spoke. I hope all is good with you and yours.

Very nice gesture of Rob to put Tom in it instead... Good work Rob.

"AM 253 for P3D - quick loading & Core 0 for P3D only Offload addon's for P3D to batch with HEX A0 for avoiding Core 0" Seems OK to say that. I took it to mean 'reserved core zero by pushing addons above core zero', therefore core zero is used only by P3D, even if it's only one of the LPs, which is key to P3D; using 253 or any AM that enables only one LP of the first core encountered by the sim processes.

I just used 36 as an example. GSync does actually work by dropping the frame rate to match the frequency down to 30.

Seems like a very savvy setup. Have you tried locking at a division frequency of the monitor? e.g. for 144hz refresh you can lock (on the fps slider in P3D display settings) at 36 = 144/4, set gsync to 36 and it will match any drop outs in fps down to 30.

On the Free Flight page, in section 2. Current Location press Change, look at lower right hand side, Active Runway with Gates and Parking in dropdown menu.

I would add that using the device name requires DNS be intact. These days that's most likely all of the time but it is a possible source of problems. Start out by using the IP addresses, and when all is working change to the device names before retesting. With networking addons it's easiest if the same logon credentials are used on each PC, make the Profile name and password the same on each. When logging onto Windows we become members of the Users group. When making a folder to install applications onto, remember that these belong to the user that created the folder, not anyone else. To ensure no snags in future with other profiles or logons, add the "Modify" permission to the "Users Group" on the app installed program files folder. If P3D is installed into the default Program Files folder, add the Modify permission for the Users group on that folder so that addons that expect write permission there can write to their files without special privileges. Problems from unnecessary path length mentioned in the guide do not manifest from the storage system itself which uses virtual FATs and addresses are all the same. Instead long paths can present a problem with certain apps when they convert relative paths into real paths. In general it's not an issue.

Simplifying the null zone information for a regular experience is pretty fair, what can you do? The guide is very good and rather nicely lays out several important paths for further study. Remember it can't cover all aspects of each subject and will always lack some detail that may be important to another.

Simply ALT+ENTER into windowed mode and drag the window to display as 2.37 to 1 = 2560/1080. i.e drag the window so that it is for example 1900 wide by 801 pixels high. OK it doesn't contain the same number of pixels and it won't be at the resolution of the new monitor, but you can see what you'll be getting in terms of views.

Click on the update link on the NVidia Inspector program and it will update you properly. Always start with a fresh profile, with NVidia Control Panel 3D section choose each profile and Restore/Apply. See here: More about using CP, and NI, for DX9, DX10, and DX11

This is of general interest and possibly misunderstood by some FSX DX9 evangelists. I've used FSX DX10 Preview mode since it was introduced simply because of the improvements to the aircraft handling. The fact that the taxiway/runway intersections flashed at many airports caused me no concern whatsoever. Back then PC's were not so quick as they are today and the differences were not marginal. I consequently ignored scenery and planes that didn't support DX10. However now we have Steve's fixer, and the free .bat fixer in the file library, the dodgy looking graphics are gone too.

With HT enabled the CPU does more work in the same amount of time than it would with HT disabled. More work = more heat. An increased overclock = more work and will add more heat. If the system heat situation is far enough up the curve, you may need only a tiny increase in work to overheat it. If you've turned HT on and not considered that multi-threaded apps often start two processes per core instead of one this too will add to increase heat in the system which can lead to CTDs. You shouldn't get CTD's with a clean install and no addons.