setting affinity in vista/win7

[final60]

It doesnt seem possible to set the .exe to any particular core. It just shows access is denied. Has anyone else had this problem? Or been able to set affinity in vista / win7?

[suib0m]

I always change affinity when playing Ryzom, never had any problems with it. I use Vista Home Premium, dunno if that has any bearing. Could it be a permissions issue?

Peace,
- Sui

[iceaxe68]

I purged vista from my systems, but am running win7, and setting affinity I think works the same in both. There is a trick to it.

I'm working from memory here, so hopefully this will not be too far off.

You do have to have admin or equivalent permissions on the system, not sure exactly which permission applies here.

Start up task manager, switch to processes tab.
Here's the trick: Click the "Show processes from all users" button down at the bottom.
Now you can right click the ryzom process(es) and set affinity as expected.

I run two clients at a time this way, with each set to a different core, which runs quite nicely. Leaving both on core 0 degrades performance. If you have the luxury of more than two cores, it also leaves one or more cores available for other things.

Also, I recommend to only set the affinity to a single core per process. I've had instability when trying to run one client on multiple cores. YMMV, of course. [SEE UPDATE BELOW]

[murmadog]

vista x64, no problems for me...

[kiakaha]

You need admin permissions to change the affinity.

This app changes your affinity in predefined ways on the fly:
http://sourceforge.net/projects/affinitychanger/

(Handy for you dual boxers out there )

[kiakaha]

Also, I recommend to only set the affinity to a single core per process. I've had instability when trying to run one client on multiple cores. YMMV, of course.

I used to run both my clients on 2 cores each, not a problem at all (Vista 64)

[iceaxe68]

I used to run both my clients on 2 cores each, not a problem at all (Vista 64)

Cool, it might just be my system.

UPDATE:
I've been running both clients on all 4 cores lately, or on two cores each, works fine either way. Must have been a one-time thing.