Supreme commander dual core?

Soldato
Joined
27 Oct 2005
Posts
13,804
Location
Netherlands
I thought supcom was multicore :mad: :
Pic of cpu usage shortly after alt tab from supcom.



How can i let the game use both my cores, or is the whole upto 16 cores stuff a Lie :confused:

Cpu is a pentium D 925 btw
 
maybe have to set something on pentium D. I know when i had single core and 100 units it would drop to about 10fps. now i can have 3 or 4 hundred and its more like 20fps
 
Hmm just alt tabbed again, and the 2nd core a nonstop 30% usage, while drops to 0% in windows, the stress on the 2nd core must be very small ie not trying to fill the whole potential up, will alt tab again when i have 200 more units to see cpu usage.
 
Alt tab may be the reason. Try running the game in a window if possible and then look at the cores change use in real time according to what you're doing :)
 
Ok won that game, had 80 units in total on end and no slowdown so i guess it's ok?

Cpu usage of core 2 around 40% at the end now, so 10% more than b4 and the 1st core @ 100% non stop from start..
 
thought sup com was set up so 1 core did normal crap and the other did the combat physics...so alt tabbing would hit pause and thus stop any physics calculations
 
snowdog said:
Ok won that game, had 80 units in total on end and no slowdown so i guess it's ok?

To be honest that doesnt show a lot. Play a full game (4 players with 500 units per player or something) and if it runs playably, it's using both cores :)
 
My mate has just convinced me to buy this game (Got it for 17.99 + free delivery) I have watched him play 1 AI game, is it worth the money...?


I'm not usually in to these games but he always seems to get it right?


Waste or not...?
 
tweakinfreak said:
My mate has just convinced me to buy this game (Got it for 17.99 + free delivery) I have watched him play 1 AI game, is it worth the money...?


I'm not usually in to these games but he always seems to get it right?


Waste or not...?


It's awesome! :cool: imo of course. :p

Brings my rig to it's knees when it's hectic.... I need to go dual-core. :(
 
I'd say 2gig minimum is a requirement alright - thankfully my RMA was all sorted just before the demo and I was prepared for it all.

The dual core thing has me pondering getting an opteron for about 100 and seeing what I can get out of that - as my cpu does come to its knees all too easily :(
 
i played it just fine on a D820 1gb of ram and a 7800GTX with everything on medium at 1280x1024. i have since upgraded to my siggy spec but that was just as it was the right time for me to do so.

the game does utilise multiple cores, but its not done "properly" that is, certain things are assigned to seperate cores, so say physics and AI is done on core 1, rendering on core 2 or whatever. a true multi threaded programme will split everything over both cores.

it does use more than one core though and does benifit from having it available.
 
After quite a bit of research, the game makes great usage of dual/quad core. However, as someone correctly pointed out, the extra cores are only used if there are large numbers of units involved. Even more so, if large numbers of units are moving and firing.

Start a skirmish, make sure the AI has loads of units, make loads yourself and start a huge fight, then tab out and note the usage for a minute ago. That will show you how great dual core can be.
 
eeek, this might be a prob, im not being glib or anything, but ive yet to play this on the main rig (down due to a leaky radiator)

when i get it up n running ill install it, think ill be ok with the game at max everything at 2048x1536? or should i keep it to 1600x1200?

ags
 
e6600 @ 3.6, 1gig ram @ 500mhz...

game against a mate with 1000 unit cap on a 20x20 map...

we both decided to build 50 t4 aeon bots and 200 t3 bots.. alt tab showed core 0 @100% constantly, and core 1 at 30% ish, told them to attack.. alt tab showed core 1 up to 100% constantly... :eek:

As caustic says.. get a lot going on and moving/attacking and it flies way up there :)
 
Back
Top Bottom