Originally Posted by 'Lax',index.php?page=Thread&postID=158944#post1589 44
KeyClone uses CPU 0-(N-1) and so does Windows, but that's really more to do with how the CPUs are represented internally, not something that really needs to be displayed to Joe the Multiboxer, who counts from 1 to n and doesn't care what 1<<0 means. The above script is fine for setting your CPU affinity, but there's a typo in "Ctrl+Num4" which should be "Ctrl+Num 4" ;)
Is the "1 or less" FPS accurate or an estimate? Is Inner Space or WoW showing you 1 FPS on an indicator?
That is using the FPS reported when the WoW windows launch through Innerspace
Did you check the Task Manager process list to see how the CPU load is distributed and made sure the affinity is getting set to what it's supposed to?
Yes, even after doing the CPu affinity stuff above and verifying that two were using one core and the other three were using the other core (as I have in keyclone), the frame rates were still between zero and no higher than 2
Did you check your WoW video settings to see that they are in performance mode?
Yes, they were at their lowest settings, "performance"
The main difference you would see from switching to Inner Space from KeyClone is that WoW isn't going to be running in a resolution of 336,262, it's still going to be running in the resolution of the main window size. The smaller resolution would have increased framerates somewhat with KeyClone, at the expense of window swapping time. But, I started my 5 box team on a 2.1ghz dual core with 2GB of RAM on Vista 64 and a Geforce 7800 GT, so unless it's driver related, I don't think "1 or less" FPS is caused by hardware bottlenecks. If I knew more specifically what sort of FPS you were getting, and what sort of FPS you get with running only 1 with Inner Space, I might be able to make better sense of it.
Running 1 instance of WoW through innerspace I get 45fps