haahahaoh well its just past 9pm here in Australia i bet its nice n sunny there,i am about to head to bed as i have work tomorrow.have fun with your 737.

I have 1.5GB of RAM and I still run slow in anything except the 2D cockpit. With VC and default scenery I was down at 6fps.

Lee,This is only a fix for the poor frame rates in 2D - sorry but I thought I made that clear. Programming changes are required to resolve the excessive consumption of memory which will then resolve the VC problem and the very slow loading when selecting the PMDG737.Cheers,

Ray,Awesome! It worked! I'm now getting 20-25 fps at 4X AA. I may try downgrading to the lovely 29.42 driver yet to see if I can squeeze even more performance out of her.Thanks :D

Hi Greg,Great stuff! :-hah Since I posted last night I've changed back to a fixed page file but increased the size to 1Gb from 700Mb. The frame rates have stayed high.Cheers,

Hmm, I might try that too.

I know most may not agree with the nVidia driver resolution as it may not have worked for them but, there is a knowledge base for this issue. There are poor results noted in individual driver revisions.Like I said, this is NOT a solution for everyone but if you are getting slammed with bad FPS, then what do you have to loose?Good luck! :-wave...Good Day.http://www.clearedasfiled.com/images/simpics/cirrus.jpgwww.flightfactory-simulations.comHomepage at www.clearedasfiled.com!

Ray my frame rates with 2d are excellent however with the VC a whole different story... :(Starts normal but how longer you fly (memory is leaking :( )it gets worse...Rule of thumb regarding swap file:varMem = your installed memoryMinimum = 1,5 * varMem and max = 3 * varMem(In my case that is for the paging file size: 1500 mb / 3072 mb with 1gb ddr)So every system where the swap file is less or equal the installed memory should see an improvement in performance when they adjust accordingly the above rule of thumb :-)When you allow windows to determine the file size the system will do according the above rule...One remark even a swap file gets defragged :(So hoping soon for a solution about the memory usage with this beautiful aircraft :-)Still a great tip for some users thanks for sharing Ray :-)Andr

Hi Andre,The formula you posted would explain why performance was poor on my system. I was using the minimum of 1.5x available memory - 750Mb page file. Once that was increased the bottleneck disappeared. I've now set it to 1Gb fixed.You mentioned yesterday about a defragging program for XP. Can you supply some details please? It sounds quite interesting.Regards,

What, ho, chaps. Wizard stuff. Been doing some more experimenting and measuring and... long message follows, but experts can skip lots of it.Tonight I did my first smooth landing in the 737TNG and it was just wonderful! This plane is a gem to fly, a beaut, a triumph.How did I get it smooth? Simple, and horrible, that's how.There's no doubt in my mind that the problem is memory-related. With 512 real and 1024 virtual, as per recommendation from Mr Proudfoot, I was able to maintain my usual target 16fps from startup right through to climbing through FL180. Then the expected frame rate hell broke in. But I was monitoring it!What the monitor showed was a classic case of what's called 'thrashing' in the paging file. For those not familiar with how demand paging systems like Windows work, here's a brief (heh) explanation. (Experts, please don't jump on me, I know it's simplistic to the point of error):In your computer you have real memory, in the memory chips; and virtual memory, on the paging file on your hard disk. When the amount of memory that your operating system and applications need exceeds the amount of real memory that you have, the system looks to swap some portions (pages) on to the virtual paging disk. This is slow but lets you keep on running. Which portion to swap out? The system keeps track of which pages of the real memory are the 'least recently used' and moves those out. When, later, the application needs to use data or program code from that memory, the system looks again for a LRU page and swaps it - writes it out on the page file and reads the one that it needs back in. (The design of the LRU algorithm is complex and how well it works determines how well your system performs - but only when the memory requirements exceed the real memory available.) The process I've described is called a page fault.OK, well and good, but there are three problems with such a scheme. One is that not all pages can be swapped out: some must remain in real memory. A trivial example: the LRU code itself can't be swapped out! The more complex your system environment, the more pages get flagged this way. The second problem is that as the memory demands continue to increase, the resources it takes to do the paging increase so your system starts running slower and the CPU works harder. The third problem is the worst and the catastrophic one. When the memory demand goes very high, the system looks for a page to write out (page A), does so, brings in the new page (page :(, finds that B refers to A, finds that B is the winner in the LRU race, writes out B, brings in A... and sits there 'thrashing', doing very little else but paging! Operating system designers go to extraordinary lengths to prevent the thrashing ending up in a stalled system, but when it gets bad your machine will... run... very... very... slowly.End of simplistic tutorial. What I was able to measure on my Win2K system, when the FPS with the 737 dropped through the floor, was fantastic thrashing - bizarre high numbers of page faults, CPU at 100%, hard disk in constant flat-out use. Solution: pause FS2002 and wait. And wait. And after about 2 minutes (!!!) the monitoring showed that the system had sorted itself out. Back to FS2002 - frame rate was back up again to what it should be!So how I did the smooth landing was this: (1) descend to 800'agl, with 1-2 FPS; (2) pause FS2002 and get a drink; (3) drink it, slowly; (4) repeat (2) and (3) once; (5) unpause FS2002 - and I landed with 16fps! (Lime juice, ice, and sparkling water, since you ask.)I hope it's clear that every PC will behave differently in this situation. Let me repeat: EVERY system will behave differently. And what works for one user as a 'fix' will be completely ineffective for another user. The choice of graphics card, and how it's operating, will affect things. (AGP aperture is one item I'm thinking about here.) Now there may indeed be variations between graphics cards and drivers,but I think in most cases they're just factors in the quation, not a prime cause. Which OS you are using: I use Win2K; others use Win/XP or Win98 where the paging algorithm is different. What other applications are you running? A network? A broadband connection? - They'll all 'fix' pages and reduce the amount of pageable memory. And so on. Every PC different.SO, unless somebody does some good convincing otherwise, I'm as sure as I can be that:a) The main cause of the intermittent catastrophic FPS problem that so many of us are having is the huge memory requirement of the 737TNG plane;:( There are only two 'real' solutions, all others are band-aids:1) go out and buy more memory - in my case I'd need to double it to 1Gb and 512Mb of PC/1066 RDRAM ain't exactly cheap;2) PMDG to agree that there's a problem in their product, and fix it.I do wish that PMDG would comment on this issue, if only to say "You're wrong!"With that, gentlemen and ladies of the jury, I rest my case. Good evening!- Pete

Hi Pete,A very well explained argument. Top marks. Now I really do think it's time that PMDG programmers stepped in and commented on this problem even if it's just to say we're working on it. There have been two big threads in the last 24 hours read by hundreds of people many of whom have presumably bought this product and I haven't seen one single acknowledgement from PMDG. I know they've worked hard and need a rest probably but this is a major issue and needs resolving. PMDG might well be working on a fix but if we don't hear from them then we're no wiser as to what's going on.On that point I think I'll stop too. Over to PMDG.Regards,

That

Yes Ray this is the full version set and forget :-)it's from diskeeper :-)http://www.diskeeper.com/coverpage.asphttp://www.execsw.co.uk/home/html/home/dis...r/diskeeper.htmSee information from them :-)Restore Speed and Performance To Your ComputerFragmentation occurs on all computers, no matter how advanced your system is. Fragmentation slows down your computer