Modifié par Androme, 27 septembre 2011 - 08:58 .
(Solved)
Débuté par
Androme
, sept. 16 2011 09:42
Retour en haut
#2
Posté 16 septembre 2011 - 10:10
Androme
-
- Members
- 757 messages
I went into the Task Manager and instead of using CPU 0,1,2,3,4,5,6 and 7 I checked in only on CPU 0,1 and 2 and it's working okay so far. I'm sitting around ~25% CPU useage and the CPU doesn't sound like nuclear warfare. Does this hold? Or is it only a temporary fix?
Modifié par Androme, 17 septembre 2011 - 12:28 .
#3
Posté 16 septembre 2011 - 10:39
Androme
-
- Members
- 757 messages
Modifié par Androme, 17 septembre 2011 - 02:09 .
#4
Posté 17 septembre 2011 - 01:33
sami jo
-
- Members
- 2 248 messages
The game does not handle more than two CPU cores well. CTD issues and serious memory-leak like issues seem to resolve when people set affinity to one or two cores. That is the only known fix.
#5
Posté 17 septembre 2011 - 12:14
Androme
-
- Members
- 757 messages
Alright then, I will try with two cores aswell and see if it's better than with three, thanks.
#6
Posté 17 septembre 2011 - 02:09
Androme
-
- Members
- 757 messages
With two cores there is a massive drop in FPS. With three cores I seem to be doing great with slightly lowered graphics (which I don't mind too much). Around 25% CPU useage is not overkill anyways, I have that with most other games.
Modifié par Androme, 17 septembre 2011 - 02:10 .
#7
Posté 17 septembre 2011 - 07:26
Androme
-
- Members
- 757 messages
Using CPU 0 and CPU 7 I have the same results, using less cores. What.
#8
Posté 18 septembre 2011 - 10:04
Althernai
-
- Members
- 143 messages
Keep in mind that when you use 0 and 7, you are actually using 2 cores whereas when you use 0 and 1, you are using 1 core with hyperthreading.Androme wrote...
Using CPU 0 and CPU 7 I have the same results, using less cores. What.
#9
Posté 19 septembre 2011 - 06:31
Androme
-
- Members
- 757 messages
So using 0 and 1 is recommended, or? (I have no idea what hyperthreading is)
Modifié par Androme, 19 septembre 2011 - 06:31 .
#10
Guest_Future Guy_*
Posté 19 septembre 2011 - 10:38
Guest_Future Guy_*
Guest_Future Guy_*
-
- Guests
This is from the unofficial troubleshooting thread, 2nd post.
http://social.biowar...58/index/189269
"Fix for Crashing to Desktop on Multi-core systems (also slows the memory leakage)This applies especially to AMD processors but also affects some Intel Core 2 Duo and Core 2 quads!For dual core set to CPU 1 only, for quad core set to CPU 2 and 3, for i7s set to 4, 5, 6, and 7."
http://social.biowar...58/index/189269
"Fix for Crashing to Desktop on Multi-core systems (also slows the memory leakage)This applies especially to AMD processors but also affects some Intel Core 2 Duo and Core 2 quads!For dual core set to CPU 1 only, for quad core set to CPU 2 and 3, for i7s set to 4, 5, 6, and 7."
#11
Posté 19 septembre 2011 - 02:33
Androme
-
- Members
- 757 messages
Modifié par Androme, 19 septembre 2011 - 02:37 .
#13
Guest_Future Guy_*
Posté 20 septembre 2011 - 12:26
Guest_Future Guy_*
Guest_Future Guy_*
-
- Guests
To make it easier, so that you can start the game without having to change the affinity in the task manager every time you launch the game, you can use a command switch.
What you do is create a desktop shortcut of the daorigins.exe that's in your bin_ship folder. Then you open the properites of the shortcut and change the target box to point to cmd.exe first, and use the appropriate processor affinity mask, and this will launch a command box briefly, and then the game will launch with the appropriate affinity.
Example target box with console enabled and affinity set to cores 2 and 3:
C:\\Windows\\System32\\cmd.exe /C start /affinity C daorigins.exe -enabledeveloperconsole
Here are some of the affinity masks that I'm aware of:
1 uses CPU0
2 uses CPU1
3 uses CPU0 and CPU1
4 uses CPU2
5 uses CPU2 and CPU0
6 uses CPU2 and CPU1
7 uses CPU2, CPU1, and CPU0
8 uses CPU3
9 uses CPU3 and CPU0
A uses CPU1 and CPU3
B uses CPU0, CPU1, and CPU3
C uses CPU2 and CPU3
D uses CPU0, CPU2, and CPU3
E uses CPU1, CPU2, and CPU3
F uses all cores
On this page, I found a table listing cpu affinity masks for a wow config file. It doesn't list cpu 0 however. It's saying to use a value of "1" for core 1, for example, but I think that is incorrect. Core 1 is value "2" and core 0 is value "1", at least for a command switch anyway.
It's saying for cores 4, 5, 6, 7, to use a value of "120", so you may have to use "119" or "121" instead. You'll just have to experiment with it, and might have to do some googling.
What you do is create a desktop shortcut of the daorigins.exe that's in your bin_ship folder. Then you open the properites of the shortcut and change the target box to point to cmd.exe first, and use the appropriate processor affinity mask, and this will launch a command box briefly, and then the game will launch with the appropriate affinity.
Example target box with console enabled and affinity set to cores 2 and 3:
C:\\Windows\\System32\\cmd.exe /C start /affinity C daorigins.exe -enabledeveloperconsole
Here are some of the affinity masks that I'm aware of:
1 uses CPU0
2 uses CPU1
3 uses CPU0 and CPU1
4 uses CPU2
5 uses CPU2 and CPU0
6 uses CPU2 and CPU1
7 uses CPU2, CPU1, and CPU0
8 uses CPU3
9 uses CPU3 and CPU0
A uses CPU1 and CPU3
B uses CPU0, CPU1, and CPU3
C uses CPU2 and CPU3
D uses CPU0, CPU2, and CPU3
E uses CPU1, CPU2, and CPU3
F uses all cores
On this page, I found a table listing cpu affinity masks for a wow config file. It doesn't list cpu 0 however. It's saying to use a value of "1" for core 1, for example, but I think that is incorrect. Core 1 is value "2" and core 0 is value "1", at least for a command switch anyway.
It's saying for cores 4, 5, 6, 7, to use a value of "120", so you may have to use "119" or "121" instead. You'll just have to experiment with it, and might have to do some googling.
