IS TQ a multi-threading app?

[4th Wiseman]

Meaning does it take advantage of the newer dual core processors or even older dual/quad cpu machines? I tried a search and couldn't find anything.

[Calienon]

pretty sure it is. In the demo, there is an option that says something like "multi-core" = 0, and I believe a dev said they would support multi core

[4th Wiseman]

Cool, I will have to check that setting out.

[Killa John]

I wish I had bought a Athlon64 X2 4800+ instead of my Fx-55 ... but my FX-55 still pwns

[DaveyJJ]

Yes, one of the developers has specifically told me that the retail/final version of TQ supports dual core/dual processors (I've got a Core Duo 2.0GHz myself). There was a text entry in the demo prefs that had the mulltiprocessortrue set to false so it wasn't enabled in the demo (and I never got around to trying to set it to true to try).

[leth]

Hmm are there any other text entry tweaks that we can do to TQ? Since I work with multi-thread programs all the time, I cannot help but wonder what exactly are separated to the two cores. And if TQ is designed so that it will make use of the future multi-core systems...

[Max]

The second processor will primarily be used for background loading (Titan Quest constantly streams the world, art and sounds from disk).

The forceSingleProcessorMode flag in the options does not cause the game to use only one processor. To reduce hitching caused by the Windows thread scheduler on a single processor system, Titan Quest makes efforts to circumvent the normal behavior of the system's thread scheduler. These mechanisms aren't necessary on a multi-core system and on those systems they could degrade performance.

Titan Quest should automatically detect whether or not to use those mechanisms, however technologies like Intel's hyperthreading make the system appear to have multiple cores when in actuality it doesn't. Titan Quest can detect hyperthreading machines appropriately, however we were concerned that a newer chip may be introduced that would be identified incorrectly. Thus we added the forceSingleProcessorMode flag as a precaution (enabling it will will force Titan Quest to use the single processor mechanisms regardless of how many cores there are).

So the long and the short is that you should leave forceSingleProcessorMode as false unless you have a really good reason.

Max

[Marine OKeefe]

Does Intel's HT tech work with TQ?

[FirebirdUK]

I wish I had bought a Athlon64 X2 4800+ instead of my Fx-55 ... but my FX-55 still pwns

I found it hard to decide between the two, but ended up going for the 4800+ - there wasn't much between them (and some of them had the 4800+ on top for some games)

[tiefchord]

The second processor will primarily be used for background loading (Titan Quest constantly streams the world, art and sounds from disk).

The forceSingleProcessorMode flag in the options does not cause the game to use only one processor. To reduce hitching caused by the Windows thread scheduler on a single processor system, Titan Quest makes efforts to circumvent the normal behavior of the system's thread scheduler. These mechanisms aren't necessary on a multi-core system and on those systems they could degrade performance.

Max

BTW: I believe this circumventing is causing issues while the app is either minimized or backgrounded (say I pause and alt-tab). Is there some form of priority or quantum manipulation going on at all times? It's almost as if the process is running at real-time priority even when backgrounded.