People,Why do people go over the top when trying to achive 30fps or more when cctv runs at 24 fps and thats smooth.Could i ask the question why?Dave...

Are you getting 30FPS with the maddog, with full autogen and scenery, in PNW Seattle???? my god, i only can get 16 with QW 757... lucky man!

Yes, but it's not luck, Paul. Besides the Bojote and Nick Needham tweaks - the system itself needs a lot of tweaking, everything from getting rid of Aero; to FSX mode; to 3840 x 1280 x 16-bit; to shutting down all extraneous services - including stopping anti-malware software; to using separate fsx.cfg's via batch files; how you setup nVidia Inspector; the Maddog has its' own tweaks, and so on. There are tools like SysInternals Process Explorer that give clues as to what's running; what is a hog, and so it's a matter of "Do I need this or that right when flying? It's all about recovering proc cycles. Even the bios - whether you have HT on or off makes a difference.

People,Why do people go over the top when trying to achive 30fps or more when cctv runs at 24 fps and thats smooth.Could i ask the question why?Dave...

Very simpleWithout realistic motion blurring, video games and computer animations do not look as fluid as film, even with a higher frame rate. When a fast moving object is present on two consecutive frames, a gap between the images on the two frames contributes to a noticeable separation of the object and its afterimage in the eye. Motion blurring mitigates this effect, since it tends to reduce the image gap when the two frames are strung together The effect of motion blurring is essentially superimposing multiple images of the fast-moving object on a single frame. Motion blurring makes the motion more fluid to the human eye, even as the image of the object becomes blurry on each individual frame.Games do not have natural motion blur between frames unlike film.It has been shown that 24 FPS in a movie = ~60FPS in a video game.If anyone on here cannot see the difference in FSX from FPS in the mid teens to 30 then they need their eyes testing, regardless of how 'smooth' it is. Even the jump from 24 FPS to 30FPS is extremely noticable.In fact, by default, 30FPS is 'smoother' than 15 FPS no matter which way you try and spin it.

Yes, but it's not luck, Paul. Besides the Bojote and Nick Needham tweaks - the system itself needs a lot of tweaking, everything from getting rid of Aero; to FSX mode; to 3840 x 1280 x 16-bit; to shutting down all extraneous services - including stopping anti-malware software; to using separate fsx.cfg's via batch files; how you setup nVidia Inspector; the Maddog has its' own tweaks, and so on. There are tools like SysInternals Process Explorer that give clues as to what's running; what is a hog, and so it's a matter of "Do I need this or that right when flying? It's all about recovering proc cycles. Even the bios - whether you have HT on or off makes a difference.

Thanks :( on the other side, my 560ti was out of vram when approaching PNW KSEA last time around, causing stutters and lots of hdd work, maybe i got the wrong card for FSX and the 480 was in the same price :( :( B) B)

Very simpleGames do not have natural motion blur between frames unlike film.

I blame LCD screens. The old CRT screens had sufficient image decay time to produce the same effect, making lower frame rates much more acceptable on CRT screens.However, it's also down to individual perception. Eyes have a built-in decay time too -- something which is responsible for a lot of trick effects which can be played on vision. It's called "persistence", and it varies somewhat from person to person. I know someone who can detect flicker in a screen running at 60 Hz and needs 100 Hz screens minimum for decent TV -- he's just grown to tolerate slower frame rates for FS, but sticks to FS9 to be sure to get higher ones. I have terrible vision (I have severe RP) and am quite happy with anything over 20 fps, and can tolerate as low as 12-15.And, yes, of course my eyes are tested -- every year since my RP was diagnosed in my forties. ;-)RegardsPete