29 réponses à ce sujet

[Annaire]

Figured it out!

Here's the deal. Most of what I read suggested if you have a dual core processor, to turn off affinity by ( if you're using nwn 1.69 like you should ) going to the player ini file and setting client cpu affinity to -1. However! This simply turns off affinity, not the fact that your computer has multiple cores.


See the issue?

What you have to do, for a newer dual core processor is set the affinity to -2. This will disable affinity, and a core. If you have three cores, I imagine you would use -3. Don't quote me on this last part though.

If you have an nvidia gpu you then need to go into the nvidia control panel and select nwnmain.exe and turn threaded optimization off.

If you are using Vista or Windows 7, you have to run nwnmain.exe exactly, no shortcuts - from the parent directory where you installed the game. You also have to run it in XP SP2 as administrator.

After a lot of trial and error, this was how I was able to get NWN to run smoothly on my XPS laptop.

If you have any questions about any of these steps please post and i'll do my best to check back and answer them.

Now... if I could just get X-COM UFO defense to work on a modern PC....

Modifié par Annaire, 24 septembre 2010 - 08:41 .

[Jedijax]

What is this about? What is it supposed to solve? I mean, I'm using a quad core duo extreme machine running at 2.8 gigs. Is this something that affects me?

[Annaire]

NWN was basically designed before multi-core CPUs were available on the market  so it was not programmed with them in mind. For most people it causes a conflict which prevents them from running the game or causes it to crash when the processors/cores try to share the load.

If you have no issues I wouldn't worry about this = )

[Jedijax]

Oh, ok... I followed your advise, anyway, and decreased the value in affinity to different numbers, getting no change in-game whatsoever, but discovered it can't be set to lower than -2. Every time you set it to -3 or -4, it simply resets to -2. Thought you might like to know, seeing as you mentioned something about it earlier.

[Calvinthesneak]

Specifies the CPU the game client will use on a multi-core computer. Cores are numbered from 0 to the number of cores minus 1. As of patch 1.69, a value of '-1' is treated as '0' and a value of '-2' indicates that the game should use the default affinity (if any) provided by the operating system. (Added in patch 1.67.)

[Jedijax]

Great, Calvin, thanks! But, in general, is turning the affinity to -2 actually good when you have a multi-core processor like mine? Or should I leave the thing in 0. I mean, it causes me no trouble, but does it actually bring any benefits?

[Calvinthesneak]

Set it to 3, 2, 1 or 0. It forces the issue, I'm not sure what auto affinity will do, and you can probably keep it on a seperate thread from your operating system for better performance.



I don't know how many cores you have. I would say leave it at 0.

[Mudeye]

Machines with multiple cores try to balance the computing between each of the cores. 

NWN and most other applications are designed for a single core.  A newer single core application would probably know to lock itself onto a single core though.

A multiple-core machine will sometimes swap an application back and forth between the cores so each core gets part of the runtime.  If you have an application designed for a single core then this just slows things down since it takes time to swap the application. 

Setting the application affinity to any particular core should lock it in place and prevent it from getting swapped around.  If you are a developer you might want to run the toolset on one core and the application on another.  That should reduce (but not eliminate) the competion between the applications for system resources.

Turning off affinity altogether may lock the app on a single core and fix the problem or it may let the OS bounce it wherever it wants depending on your system setup.

Modifié par Mudeye, 05 octobre 2010 - 08:52 .

[simomate]

NWN works perfectly fine for me, without any sort of troubleshooting. I've got Win 7

[1xs3thx1]

I have an AMD Phenom II Six Core Processor Running at 3.2 GHz on Windows 7 but I am yet to see if NWN works for me, I shall try it soon and update you all.

[the_critical_process]

I've tried 0, -1, -2, -3. I've tried running nwnmain.exe and nwn.exe in XP service pack 3 and also 2 compatibility. I'm running an Intel Core i3, 3.2 GHz, 8GB ram, graphics card (which is from my old machine yet) is ATI Radeon 1900 (512) with updated drivers. NWN is still unplayable, even the red smoke on the login screen is ultra-choppy, and the tilesets for the most part render as pure white, with about 1 frame per hour, oof. Can anyone give me some advice? Thanks.

[Mudeye]

You've probably tried this but to get a baseline: 1) set all video options to lowest possible settings, set the resolution to the lowest possible. 2) Make sure your install is clean. That is installed fresh and no hakpaks or add-ons. 3) Shutdown background processes. 4)Try to start the basic NWN campaign.



Is this Windows 7?

You can see the entire process list in the Task Manager. There are often unnecessary programs running that may slow things down.

[the_critical_process]

Yes it is Windows 7, but why a fresh install? I was following the instructions in the sticky:

Shia Luck wrote...



There are two main ways to put NWN onto a windows 7 machine.



If you have a new machine as well as your old machine and a home network or flash drive etc and simply want to transfer your nwn to the new machine, then the easiest thing to do is use windows explorer to copy from the old machine to the new, and then delete it from the old machine. You keep all your settings and everything using this method. (Only use this method if your NWN is patched and working perfectly)



1. On the win 7 machine, use windows explorer to find your NWN install on your old machine and drag and drop the complete nwn folder to c drive on your new machine.

2. In the nwn folder find nwnmain.exe and nwn.exe.

3. Right click on these and select properties. Set them to run with full permissions, as administrator and under compatibility mode windows XP service pack 3. (If your old machine was vista, then this has probably already been done, but check anyway!)

4. (If you want a desktop shortcut) Right click on nwnmain.exe and create a shortcut. Drag and drop this to your desktop.

5. Update your drivers for video and sound. (If you have a laptop this means going to your laptop manufacturers support page, otherwise go to the manufacturers of your cards' support pages.)



If you wish to install from the disk(s)



1. Install game using a custom install. When you are given the path to the install folder, change the path using the browse folder button so that it is not installed in 'programs (x86)', but directly on C drive. Do not make any shortcuts during the install process.

2. (Diamond edition only) Run the patch on the disk.

3. Go to the patch page and download the correct 1.69 critical rebuild and install it.

4. Open NWN folder and find nwnmain.exe and nwn.exe.

5. Right click on these and select properties. Set them to run with full permissions, as administrator and under compatibility mode windows XP service pack 3.

6. (If you want a desktop shortcut) Right click on nwnmain.exe and create a shortcut. Drag and drop this to your desktop.

7. Update your drivers for video and sound. (If you have a laptop this means going to your laptop manufacturers support page, otherwise go to the manufacturers of your cards' support pages.)



Good Luck

And why worry about other programs running? There is process power to burn and then some, ya?

[Mudeye]

I'm just going through a process of elimination. The simpler your setup the easier it will be to find the problem.



Sometimes people state that they have just installed and have problems but they have actually installed lots of other things too that didn't get mentioned.



If you followed the second method then you should have a clean install.



It sounds like you have a fast CPU, but something is making it slow down. It could be: the NWN setup, the module you are running, the graphics card and setup or the rest of the computer. Just need to figure out which it is.

[the_critical_process]

Well I've decided to face this ogre again. A fresh instal did show some signs of promise. But then installing the two expansions and the critical rebuild brought the problems all back again. And this was straight on the C-drive, not in any folder -- which somehow means I don't have "permission" to alter the nwnplayer.ini (to try the CPU Affinity changes) this time (though as I said, that didn't help before).



What to do, any ideas?

[the_critical_process]

Hmm I'm not exactly sure how to do that. When I run NWN, and look at the Task Manager, there's a "nwmain.exe*32" running on CPU 25 (though it flops back and forth between a 25 and 24). All others are running on CPU 00. Does that look like a culprit? When I R-click and choose "Set Affinity" I get told "Access is denied". (It seems with Windows 7 I don't have permission to do all kinds of things...) This is even though "Full Control" is checked and it's being run as an "administrator".

[the_critical_process]

It's just like you said, yes. I don't guess that puts me any closer to knowing what's wrong and being able to play NWN though, ya?



As an aside, why 4 graphs if it's only a dual-core?

[the_critical_process]

I understand what you said about the drivers, but what is meant by benchmarking?



Also, all other games seem to be fine.

[t2couger]

i had proformance issues on my i7 that was OC to 3.8g 6gig ram and 285gtx.  i was getting around 28fps with dips lower. i disabled Hyperthreading and my fps jumped up and hovers around 60. 

[lordofworms]

you can disable hyperthreading in the BIOS on boot-up. then restart PC again after saving changes.