• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Crappy coding or AMD's fault?

Battlefield 2
Adobe Premiere

So far, those are the programs I've encountered that simply will NOT play along with an Athlon 64 X2. For BF2 to be playable, I need to make it run on one core only, and for Premiere to capture DV, I need to do the same. Wtf?
 
It is not uncommon for todays games to be uncomfortable running on both cores. In fact, every game I have played to date has had one problem or another with my dual core setup. Setting the affinity to one core or the other is the only fix.
 
Originally posted by: mrSHEiK124
Battlefield 2
Adobe Premiere

So far, those are the programs I've encountered that simply will NOT play along with an Athlon 64 X2. For BF2 to be playable, I need to make it run on one core only, and for Premiere to capture DV, I need to do the same. Wtf?

I dont play bf2 so i can't tell but my premiere captures fine in my 3800 x2..
 
I love how people who don't know jack sh!t about software development like to say everything that doesn't work the way they want it to is due to "crappy coding". Most of these people couldn't even give a list of criteria that would qualify code as good or bad.
 
Originally posted by: notfred
I love how people who don't know jack sh!t about software development like to say everything that doesn't work the way they want it to is due to "crappy coding". Most of these people couldn't even give a list of criteria that would qualify code as good or bad.

The consensus is that Battlefield has one of the worst engines ever.
 
Originally posted by: notfred
I love how people who don't know jack sh!t about software development like to say everything that doesn't work the way they want it to is due to "crappy coding". Most of these people couldn't even give a list of criteria that would qualify code as good or bad.


how about 1) it's a bloody pain in the ass to write good dual core code 2) bf2 code sucks anyway. It's quite possibly the most resources hogging engine I've ever seen for what you get. They should have just gone with U2.5
 
Its Windows' fault. Think of it, in Linux, the operating system was compiled for dual core and 64bit. Windows is well generic and cannot manage dual core properly hence why these problems occur.

 
Originally posted by: gnumantsc
Its Windows' fault. Think of it, in Linux, the operating system was compiled for dual core and 64bit. Windows is well generic and cannot manage dual core properly hence why these problems occur.

And I was under the impression that the hardware abstraction layer is changed out to a multiprocessor hal as soon as it detects the second core or logical CPU (hyperthreading). Oh yeah, and there is a 64 bit version of windows that you can get. I even remember microsoft doing a free trade for people who had valid windows license.

Now, I may be an idiot, but I seem to like the seemless (well it does require a reboot) single to multiprocessor change versus a a kernel compile.
 
Back
Top