I wonder, does FPS Limiter have to run with the same core affinity or priority as FSX?

What FPS limiter does is:- Start- Open DirectX- Patch a method in DirectX- Start FSX and let it use the patched DirectXSo as soon as FSX is started, all FPS Limiter code runs as part of FSX and thus uses the same settings as FSX.Daniel

Thank you Daniel42.gliderdriver

I'm wondering if this "not working" problem is limited to i7 and it's b****y permissions. I've been having the dickens of a time with Steam/MW2 recently, plus an inability to cut 'n' paste. There are all kinds of internet posts on this i7 issue - some caused by an update to IE8. I think I fixed part of the problem by upgradng to IE9 beta. When launching Call of Duty ModernWarfare2 - Steam immediately connects to the internet and updates itself, by copying Steam.exe to SteamTmp.exe and then deleting the original Steam.exe and downloading a new one: the problem was - it couldn't delete the original one, so it errored out. Tons of posts on the Steam site, but the fix which worked for me was by taking ownership of the Steam root folder. (There's a small registry mod from http://www.howtogeek.com/tag/windows-7/ that adds a "Take Ownership" option to a rt.click on a file or folder - great little addon). This may be the problem with DirectX, and so I'll go and play with it for a while. It's nice to finally have a Windows system and hardware that makes FSX the way it was supposed to work (thanks to a number of folks's fixes), but i7 can sure be a pain in the butt sometimes.

I have a Nvidia video card (8800 GT) and windows XP. It does not work either. It is hopeless.

Old System:Dell XPS 720 H2CIntel Quad Core Extreme QX6800 2.93 @ 3.73GHz4GB (2x2GB) Corsair Dominator EPP 8500C5D FSB 800MHz @ 1066MHz2x160GB WD SATA Raptors, Sound Blaster X-FiNvidia 2x8800GTX 768MB SLI, Dell 2407WFP PanelXP driver: 169.21, Vista driver: 169.25Logitech Z680 5.1 Speakers, G5 Mouse, Saitek X52WinXP Media Edition SP3 on C: (SATA 0) w/ Internet/AV/Office/FS9/Falcon4 AFVista SP1 on D: (SATA 1) (Dual Boot) w/FSX3DMark06: 17,018/6992/7123/5667With drivers later than 169.25, I had massive autogen spiking with FSX set at UNLIMITED. I installed FPS Limiter locked at 30 and no more spiking. Oe of the 8800's failed and Limiter still worked without SLI.New System:Intel Core I7 975 Quadcore OC @ 3.75 Ghz (Air)Asus P6T DLX V2 X58 1366, BD Combo Plextor B310SA6GB (3x2GB) Corsair Dominator DDR3 1866C7GTHIS ATI 4890 1GB, Samsung 24", Saitek X-52 ProLogitech Z680 5.1 Speakers, G15 Keyboard, G5 MouseThermaltake Element S Case, Corsair 850HX PSUC: Intel 80GB SSD w/Windows 7 Home 64D: WD 300GB Velocity Raptor w/FSX+Accel+GEX, F4AFE: WD 1TB Caviar Black w/Data SH4On my new system, I still have autogen spiking with FSX at UNLIMITED. With FPS Limiter locked at 30, no spiking.FSX has no red x at the top right. The Command Box opens when Limiter starts and will stay open. When FSX opens, the green fps setting will appear in the upper left. No flashing.I have never turned off UAC, Vista 32, Vista 64, Win7 64. UAC is only a problem when FSX is installed in C:\Program Files.The path is usually the problem.My BAT file reads:start D:\"Games\Microsoft Games\FPS Limiter MAX\"FPS_Limiter.exe /r:D3D9 /f:30 /x:OFF /l:OFF "D:\Games\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFolder D:\Games\FPS Limiter MAX has the EXE, BAT, and DLL files.Have FunDave

There´s nothing wrong with this tool, works perfect here (i7) - locked at 30 FPS.You need to have everything updated, Java, DirectX etc.Any processes running (Anti virus etc.) messing up the system?

When I double click the bat file, it opens a cmd box and loads FSX but doesn't limit it, even with the OSD option on there is no OSD so something isn't functioning properly. If I run as admin I get the flash of cmd box which I managed to capture with this errorMoving the .dll to that location has no effect and I get the same error. All the files are in the same folder (C:\FPS Limiter 0.2). I updated directx and java to no avail. The only thing I think might be causing the issue is that I'm stuck in dx10 preview mode. Running fsx in standard dx9 causes it to crash at load-up with this error showing up in event viewerFaulting application name: fsx.exe, version: 10.0.61472.0, time stamp: 0x475e17d3Faulting module name: ntdll.dll, version: 6.1.7600.16559, time stamp: 0x4ba9b29cException code: 0xc015000fFault offset: 0x00084391Faulting process id: 0xe14Faulting application start time: 0x01cb845a06fae9d5Faulting application path: C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\fsx.exeFaulting module path: C:\Windows\SysWOW64\ntdll.dllReport Id: 66fc9fdf-f04d-11df-a6ae-90e6ba46babbAny ideas? (running W7 64bit btw)

I would uninstall FSX and delete the Microsoft Flight Simulator X folder. There is something wrong with your computer or the install if FSX won't run in default DX9.Reinstall in C:\Games folder (new). Then you can leave UAC alone without any problems.Install Limiter in C:\Games\Microsoft Games\FPS Limiter MAX.Dave

I would uninstall FSX and delete the Microsoft Flight Simulator X folder. There is something wrong with your computer or the install if FSX won't run in default DX9.Reinstall in C:\Games folder (new). Then you can leave UAC alone without any problems.Install Limiter in C:\Games\Microsoft Games\FPS Limiter MAX.Dave

I concur with the above. I was gonna spell this out too, but the Chief beat me. I was looking for the thread about the Program Files(x86) folder in Vista and 7 but couldn't find it. It has to do with permissions.

I would uninstall FSX and delete the Microsoft Flight Simulator X folder. There is something wrong with your computer or the install if FSX won't run in default DX9.Reinstall in C:\Games folder (new). Then you can leave UAC alone without any problems.Install Limiter in C:\Games\Microsoft Games\FPS Limiter MAX.Dave

Thanks, I suspected as much but wanted to avoid the reinstall. Will crack on with that another day!

Have reinstalled (install must've gone funky as it fixed my dx9 issue, cheers for the heads-up chaps), and in the process discovered many of my "tweaks" had actually resulted in worse results than stock. I've gotten to the stage where the limiter opens fsx fine, gives the green "30fps new limit" while in the menu, but I'm getting a solid 60fps in flight according to fraps and the green OSD is nowhere to be seen. Unfortunately I forgot to install outside of program files (x86) so I suspect a UAC issue, but can anyone confirm or deny my suspicion? Seems odd that it works in the menu but not in flight. So close!Cheers for any help!

I don't run inside of the x86 folder, so I'm not sure. Have you given the FPSLimiter admininstrator privledges? Disable UAC, and test?

Have reinstalled (install must've gone funky as it fixed my dx9 issue, cheers for the heads-up chaps), and in the process discovered many of my "tweaks" had actually resulted in worse results than stock. I've gotten to the stage where the limiter opens fsx fine, gives the green "30fps new limit" while in the menu, but I'm getting a solid 60fps in flight according to fraps and the green OSD is nowhere to be seen. Unfortunately I forgot to install outside of program files (x86) so I suspect a UAC issue, but can anyone confirm or deny my suspicion? Seems odd that it works in the menu but not in flight. So close!Cheers for any help!

If you hit F10, do the FPS numbers show up (and disappear when hitting again)?If yes, can you make numbers increase/decrease with F12 and F11?Thirdly, does the Windows Task Manager show fps limiter as running?If yes to the above, it is working as intended.

If you hit F10, do the FPS numbers show up (and disappear when hitting again)?If yes, can you make numbers increase/decrease with F12 and F11?Thirdly, does the Windows Task Manager show fps limiter as running?If yes to the above, it is working as intended.

No joy with the hotkeys. Will try disabling UAC when I get home tonight and report back. Have set FPSLimiter.exe to run as admin to no avail.

No joy with the hotkeys. Will try disabling UAC when I get home tonight and report back. Have set FPSLimiter.exe to run as admin to no avail.

One more thing to try.. during startup of FSX you should also see the fps limiter window.Click on it to make it active as FSX starts up. That should make the FPS counter visible.