Diamond

Well, thanks a lot for spoilers!

At least nobody will complain that the game is too short.

Context switching is actually switching from one thread to another on one core, and not necessarily from the same process. So context switching occurs with all CPUs, not just dual core. E.g. your running thread might be pre-empted (stopped temporarily) and, say, some other process' thread is scheduled to run for a certain time until OS decides it is time for someone else to use the CPU (that is how multi-threading and multi-tasking works). I have no idea why context-switching might be a problem though. Taks was referring to the situation where a thread is pre-empted and scheduled on the other core after that, but I am not exactly sure why that would be a problem, unless he meant something else. All I know now is that the performance problem manifests itself on some specific configurations, and is not connected to whether the CPU is dual core or not.

You can set thread's priority, but you can't interfere with the way they are scheduled and the way context switch occurs. These are low-level tasks which are handled internally by the OS.

You can't possibly do that.

I somehow fail to see the logic behind that conclusion. Why FX uses only one core and X2 uses two? Anyway, yes, dual core CPU's main advantage is parallelism, however making a linear process (like rendering and compiling) to take advantage of multiple CPUs is not a trivial undertaking. If the program is not taking advantage of multi-threading, it will be scheduled on one core by the operating system. For those who were running the pre-sale toolset: how does its performance differs from in-game performance? Edit: by the way, the toolset uses two cores.

Damn you! I only get NWN2 on 9th of November earliest. Must resist... the urge...

The atmosphere is excellent. The best Introversion's game to date.

Says the one who is banned from an NWN PW server. But seriously, I agree.

Depends what you played first. I played Diablo II first, so Diablo I seems quite bland to me. *shrug*

Haven't got the game yet (the downside of living in AU), but I am truly annoyed by how whiny the people at Bioware forums are, geez.

Try Atari NWN2 support forums or Bioware NWN2 forums, which seem to be the major place for official answers these days.

DEFCON! USA is pwned hard with mid-range nukes from submarines Retaliation strike

I'm so predictable.

...and that this thread has got far greater view-to-reply ratio than any other thread in WoT.

Eh? No, Microsoft .NET is a complete runtime environment, just like Java. [start technobabble] For example, normal programs would run in native mode, i.e. directly in the operating system, .NET programs run in the intermediate .NET environment, and that environment runs in the operating system. So think of it as a mini platform on top of Windows, that is simpler to program for, and hence allows a simpler, faster, and cheaper development process. [End technobabble] Microsoft .NET is needed for the toolset, I can't think of other components that would need it.

Probably that, or they are forcing the application settings via nView or something. I am also thinking different XP service packs.

If this works as in NWN1, try holding mouse wheel and rotate the camera.

Maybe your emulation software is running as a Windows service, or a driver, so it won't be visible in the task manager.

[quote name='

Probably you have some other title with an older version of SecuROM installed that might cause problems. Just a guess. Anyway, it is kind of annoying that NWN2 uses copy protection. Hopefully there will be a patch soon to remove it (as well as No-CD).

[quote name='

Who usually wants to know what you are wearing?

Couldn't explain that any better than the Wikipedia article, that pops up in the first link in Google search.