winz

No, as long as you haven't disabled the page file, you'll not get an oom. It will just butcher performance as windows will have to heavily use the page swap file to swap memory pages as they are required.

What I meant with clean is that the OS will start to rewrite the page file as it starts to store pages in it. It will not append them, nor will the data stored there previously affect the writing logic in any way. For the OS it's logically clean. Cleaning it up physically is only a security matter and has no effect on performance.

Nope, page file is all about size. You're messing virtual and physical memory together. Application is requesting virtual memory and virtual memory only, it is receiving chunks from its virtual memory. If the virtual memory is fragmented, then the above error will occur, but that has nothing to do with page file. Page file is divided into fixed sized chunks, pages, and it is possible and real, that one big chunk of virtual memory isn't mapped on sequential pages in page file. In fact, application has no idea wheter and what parts of its virtual memory are in the physical ram or page file. When page file is fragmented, then only outcome is even more degraded performance when page file has to be use extensively. You start with clean page file each time you start the os, because you start your mapping table from scratch on each boot. And OS will start to write to it from the beginning, because all entries in the page file are no longer valid. Cleaning will not defrag the page file in and way.

If you got 4GB without page file, then you're limited to 4GB of Ram. Taking into account that FSX can easily eat up 2GB+, that only leaves 2GB for OS+other applications running. Once those 4GB are taken, all applications requesting additional memory will crash with and OOM exception, inluding system critical processes. I see some reason running non-page file configuration on XP, where the memory management is pretty messed up, and the OS will cache memory pages even when there is plenty of physical ram available + every access of HDD is really hurting a XP system. But on vista and 7? No, the memory mamangement was reworked for those, and the OS is keen on using all available ram.

Keep the page file. 4GB is waaaaay to little to disable the swap file, especially when you're playing FSX..

Because I work as a developer and I know that every bugfix, no matter how small, may break some things, and if bugs slipped through initial release testing (they allways do) there is no reason why some potential bugs couldn't slip the bugfix testing. Also, it's called hotfix for a reason. Hotfix is allways somewhat hastily assembled and mostly only basic tests are done, because hotfix is fixing things that are preventing some people to use the product they payed for. So fixing them is the highest priority. And when I read on forum that people are having problem after installing the hotfix, then I have to ask myself if I really need to take chances to break my 100% functional installation. And after looking at the changelog (that is really, really brief) I really don't see any reason why I should risk breaking my 100% functional installation.

Bouncing? The only time NGX bounces off is when I make a veery hard (meesed up) touchdown. If I'll make a soft td, like in the vid you posted, the NGX will remain glued to the rwy. Sure, the compression of shocks is not like in real plane, but the overall behaviour looks good to me.

Tbh, I haven't hot-fixed my installation, and I don't plan to. I have no problem whatsoever with NGX and FSX is such an unstable enviroment, so I'm not taking any chances.

I start my apu just before pushback, for engine start-up mainly. The temperature problem appears even at FL200+. Just a little spin of the temperature control to the left will get the duct temperature from 60+ to around 20 in about one minute.

I'm experiencing the same behaviour on ground/climb. Both engines bleed is on, packs are auto, recip fans are auto, isolation valve is auto. All temperature controls are auto. And the cabine temperature rases to +35degrees, the duct temperature will get to 50+.No warning light lit.The temperature will come down, for both cabin and ducts, the moment I move the temperature controls out of auto, to cold.

AFAIK the AC/DC switches only affects what is beeing displayed (monitored) on the display above them. They do not affect the electric system in any way.To get basic power, you only need to close the battery guard an the stand-by power guard.

The only problem I have is that NGX is eating up all of my free time.

Yes the default ATC is a pita. But you can find your way around the ATC, if you have an external planning tool that supports sids/stars.You start a free flight on your selected departure airport. Listen to the ATIS to get the active runway.You can then use your external tool to create a flight plan with SID selected for the active runway. Save the plan and start a new flight with the plan. This way the plan the FSX ATC want you to follow will contain the SID aswell.As for START, I select one based on the general directions I'm comming from, because I know the ATC will vector me somewhere in the middle of it. I'm thinking about RC aswell, but have already exceeded this month FSX addons budget ^_ ^ Edit: One question about RC, how can it handle traffic? will it work with MyTraffixX?

This can be result of too sensitive/jerky throttle controller. You're trying to set reverse thrust by F2 ( F2 is 'reduce throttle' key command), but your controller is still sending new inputs to the sim, overriding eveything.

Unless you're runnig an ancient (by ancient i mean around 6600gt nvidia series) card, you would be lucky to get 1fps gain by removing all those details like stickers and fingerprints on mfd. The biggest poly and fps hogs are the 3D switches and mfds. Anything beyond the cockpit doors is clamped and not drawn while you're in the cockpit.