Page 1 of 1 |
|
Posted: Sun, 8th Jul 2007 19:23 Post subject: Silent Storm |
|
 |
I'm playing this game on a 8800gtx core 2 duo system with all the works.
I really loved playing it in the past, but now something is just completely wrong.
The game chugs as if it was Crysis 2 or something...I tried reverting back to the 152 drivers but nothing changed...is anyone with a similar system playing it?
thx fer any whelp.
Blame! don't act!
|
|
Back to top |
|
 |
|
Posted: Sun, 8th Jul 2007 23:59 Post subject: |
|
 |
|
|
Back to top |
|
 |
|
Posted: Mon, 9th Jul 2007 00:22 Post subject: |
|
 |
hafriski wrote: | turn off the second core |
If you don't know how to do that I believe he means setting the affitnity which you do by opening the task manager, right clicking on the game > set affinty and disable cpu 1
|
|
Back to top |
|
 |
|
Posted: Mon, 9th Jul 2007 06:31 Post subject: |
|
 |
Are you saying that from experience cuz it didn't do shit.
Blame! don't act!
|
|
Back to top |
|
 |
|
Posted: Mon, 9th Jul 2007 08:15 Post subject: |
|
 |
Hellbeans wrote: | Are you saying that from experience cuz it didn't do shit. |
It's a known problem with "some" games, somes games will act rather odd when both cores are enabled like for me Flatout2 menus and car spinning showing off the features go super fast like it was on FFW until one of the cores is disabled
|
|
Back to top |
|
 |
|
Posted: Mon, 9th Jul 2007 19:08 Post subject: |
|
 |
I know but that's not SS's problem...dunno what it could be...would really love to play it again.
Blame! don't act!
|
|
Back to top |
|
 |
|
Posted: Wed, 11th Jul 2007 21:07 Post subject: |
|
 |
Hellbeans wrote: | Are you saying that from experience cuz it didn't do shit. |
I said it because i finished the main game and the addon 2 weeks ago on my Amd x2 6000+
and i was forced to turn off the second core to play this great game , with the second core this game was running too fast or too slow
|
|
Back to top |
|
 |
|
Posted: Fri, 13th Jul 2007 15:12 Post subject: |
|
 |
Well It didn't work for me...bah.
You have a completely different CPU so it's obvious it could have been just an AMD issue...thanks for the help anyway.
Blame! don't act!
|
|
Back to top |
|
 |
Page 1 of 1 |
All times are GMT + 1 Hour |