16 réponses à ce sujet

[Bertie Lagerschmecken]

Before I spring for this game, I would like some idea if my set-up will be able to run it well enough not to get seriously annoyed at the performance. I don't mind forgoing some special effects (not too fond of over-the-top  visual effects on spell detonations anyway.) Upgrading hardware is not an option at this time, but suggestions welcome.

I currently have a Dell XPS700 w/:
Intel Core2 Duo, E6600 (2.4 GHz, 1066FSB), 4 MB cache;
2 GB DDR2 SDRAM @ 667 MHz;
1 GB NVIDIA GeForce 7950, GX2 Dual GPU
Win. XP Media Ctr, 2005.

Thanks,
Bertie

[ZootCadillac]

You'll be fine with that. Some pessimists might point out that you have a low end ( with regard to game spec requirements) cpu but the game clearly ( from all the specs running it and discussions about that here ) does not require as much cpu as stated but it does require more GPU than is stated.



The 7 series Nvidia may be getting on now but the 7950x2 was the top of that range and apart from any specific DX10 effects you'll run it fine.

[GhoXen]

One problem that low-end CPU may lead to is occasional memory leak. When you experience very slow loading or looting times, you can try restarting the game to temporarily solve the problem.

[dragoaskani]

GhoXen wrote...

One problem that low-end CPU may lead to is occasional memory leak. When you experience very slow loading or looting times, you can try restarting the game to temporarily solve the problem.

You dont even know what a memory leak is clearly by your answer. Here let me enlighten you.

Memory Leak- (Definition) A condition caused by a program that does not free up the extra memory
it allocates. In programming languages, such as C/C++, the programmer
can dynamically allocate additional memory to hold data and variables
that are required for the moment, but not used throughout the program.
When those memory areas are no longer needed, the programmer must
remember to deallocate them.



When memory is allocated, but not deallocated, a memory leak occurs
(the memory has leaked out of the computer). If too many memory leaks
occur, they can usurp all of memory and bring everything to a halt or
slow the processing considerably. In other environments, such as Java,
the operating system allocates and deallocates memory automatically.
Specifically allocating and deallocating memory, while error prone (in
case one forgets to deallocate), allows the programmer more control
over the computer's resources. Memory leaks are bugs in software.

So do us all a favor, before you come into a tech support forum and try to tell people what something is. At least know a little about the problem first.

[JironGhrad]

To further elaborate on drago's answer... there are issues with at least a dozen processors (I've got over 100 verified fixes now) failing to release threads from the cores as it shuffles the game around. This affects both AMD and Intel CPU's (AMD X2s and X4s, late model Intel Core 2 Quads and some i7s).
These particular problems can be resolved by setting the affinity as explained here. For people experiencing similar symptoms but not helped by affinity settings, then your processor is probably not one of the affected model revisions (certain processors share the same designation- for example i7 920, but are of a different hardware series, eg. Revision 1 or Revision 2).

Modifié par JironGhrad, 14 novembre 2009 - 08:36 .

[GhoXen]

dragoaskani wrote...
So do us all a favor, before you come into a tech support forum and try to tell people what something is. At least know a little about the problem first.

You know, I think my reply was more informative and relevant than yours. The OP does not need to know why or how a problem may occur, I told him that it may occur due to his particular CPU. The poster above me has posted a fix.

[ZootCadillac]

GhoXen wrote...

dragoaskani wrote...
So do us all a favor, before you come into a tech support forum and try to tell people what something is. At least know a little about the problem first.

You know, I think my reply was more informative and relevant than yours. The OP does not need to know why or how a problem may occur, I told him that it may occur due to his particular CPU. The poster above me has posted a fix.

Yes but unfortunately you were incorrect because a memory leak has nothing to do with his cpu and is a programming issue. So sure, tell him his dog may bite, but don't blame it on him having a blue hat.

[GhoXen]

ZootCadillac wrote...

Yes but unfortunately you were incorrect because a memory leak has nothing to do with his cpu and is a programming issue. So sure, tell him his dog may bite, but don't blame it on him having a blue hat.

The case here is that while it is a programming issue, his particular CPU is more prone to been "bitten" than some other more recent CPUs. I've seen the problem once on my 965, but that is hardly comparable to many 6600 users who claim to experience the problem every 30 mins.

[warmaku]

you should at least use the rest of your memory room and add another gig of ram

[Meataxe70]

Very low end system, with NO problems, other than slow Ostegar scene. Single core 2.4 Celeron, 2GB DDR2 memory and a 7600GTS -512 card. Have had no problems other than slowdown while running to said Ostegar location, once inside no problems. Probably due to high graphic nature of said scene. Most settings are on low, some on medium. I had planned to upgrade, but that's been delayed. System going on 5 yrs old. It would appear there is a nice range of low-end to high.

[dragoaskani]

GhoXen wrote...

ZootCadillac wrote...

Yes but unfortunately you were incorrect because a memory leak has nothing to do with his cpu and is a programming issue. So sure, tell him his dog may bite, but don't blame it on him having a blue hat.

The case here is that while it is a programming issue, his particular CPU is more prone to been "bitten" than some other more recent CPUs. I've seen the problem once on my 965, but that is hardly comparable to many 6600 users who claim to experience the problem every 30 mins.

CPU's have nothing to do with memory leaks, or resistance to memory leaks, or any other spin you can try to think of to save face. Its a fact that its all about the code not releasing the memory that it allocates for itself. Period, no ifs ands or buts about it. Geez.

[GhoXen]

dragoaskani wrote...

CPU's have nothing to do with memory leaks, or resistance to memory leaks, or any other spin you can try to think of to save face. Its a fact that its all about the code not releasing the memory that it allocates for itself. Period, no ifs ands or buts about it. Geez.

Do explain to the 6600 users just why they need to adjust their affinity, while I do not have to.

[dragoaskani]

That has nothing to do with memory leaks, and everything to do with the code not properly using the multiple cores. This game fails hard on alot of multiple core processors.



I have a OC'd single core at 4.2 and the games memory leak afflicts me as well with a restart needed every hour or two.

[GhoXen]

That's not the case in my experience. I'm running on a 965 BE and only experienced a memory leak after the game running for over 12 hours. While it's true that some people encounter it on an hourly basis, it often is not the case for most people.. not that frequent anyway.



If it truly affects everyone that badly, there would be more threads and posts concerning this topic than only a handful of threads with fewer than 20 replies each.

[ZootCadillac]

GhoXen wrote...

dragoaskani wrote...

CPU's have nothing to do with memory leaks, or resistance to memory leaks, or any other spin you can try to think of to save face. Its a fact that its all about the code not releasing the memory that it allocates for itself. Period, no ifs ands or buts about it. Geez.

Do explain to the 6600 users just why they need to adjust their affinity, while I do not have to.

You are getting hung up on the idea that the CPU, whatever it is, has anything to do with a memory leak. It's between the instruction (programming) and the RAM address ( your ram ) not being released after it is no longer in use / being addressed.

[dragoaskani]

GhoXen wrote...

That's not the case in my experience. I'm running on a 965 BE and only experienced a memory leak after the game running for over 12 hours. While it's true that some people encounter it on an hourly basis, it often is not the case for most people.. not that frequent anyway.

If it truly affects everyone that badly, there would be more threads and posts concerning this topic than only a handful of threads with fewer than 20 replies each.

Just a little hint for you. Less then 1% of a game player base tends to visit the associated forums. There are thousands upon thousands of people who are in all probability having the memory leaks and have no clue what to do about it. They get annoyed and frustrated at the load times and eventually may stop playing, or may come to the forums.

And as Zoot said, Memory leaks HAVE NOTHING TO DO WITH THE CPU, THEY ARE A BUG IN PROGRAMMING CODE GET IT THROUGH YOUR SKULL
That being said there is nothing to say that the memory leak and the cpu problems are actually related to begin with.
It could be a compound issue where the systems memory leak combined with unoptimized usage of multiple cores = big suck. I am done debating this with you. I work on computers every day of my life, I am not gonna waste my time educating you when there are many people that have things that I might be able to help with. So good day sir.

[Bertie Lagerschmecken]

Whew!

Thanks much,

Bertie