|
Post by kaldair on Nov 6, 2007 15:52:14 GMT
Okies I tried this on my pos laptop & wow what a difference! I went from almost certainly crashing (or more commonly having the graphics "freeze" on the screen) upon going through the first Hells transition map from the workshop (no matter the layer) to no gfx lag issues at all. I set mine to 32. I did notice last night in Cania, however, that the first spawn (which was large) had every mob invisible except for one spider! Many others complained of large amounts of invis critters as well. Interestlingly enough, as we progressed, the amount of invis mobs decreased, until by the 5th or 6th spawn on the 1st map, I never had another invis critter. No clue how NWN is programmed, but based on other experience I've had I'd say that my client/PC combo has trouble loading a large rush of unique sprites at the same moment, but then adds them to a cache over time until all are present & available to be displayed. It's almost like it's trying to load them sequentially, and if there''s over a micro second's delay it skips one and proceeds to another, with the skipped one(s) then being invisible. I'd have to say all of the client-side lag I was having that I could easily see was gfx related was gone. Another biggie that was gone was some kind of "Immo-glow" synchronization that used to freeze me up like crazy. What was happening was that any time an Immo transitioned into the area I was in, I'd lag out until every Immo glow on the screen synchronized to flash at the exact same time. Depending on the Internet latency this could be a few seconds. Now that's gone as well. I also thought that the herky-jerky, "rubberbanding" movement issues that were worse the last couple of days were much better as well, but time will better tell on that as it usually is not there or horrible.
Thanks Acaos,
Kaldair
|
|
|
Post by chirikov on Nov 6, 2007 18:43:52 GMT
anyone with a multi-core system may want to consider changing the 'client cpu affinity' option as well. not sure how extensive the effects are, but you may be able to get a bit more stability at least
|
|
|
Post by illandous on Nov 6, 2007 19:24:30 GMT
anyone with a multi-core system may want to consider changing the 'client cpu affinity' option as well. not sure how extensive the effects are, but you may be able to get a bit more stability at least You will need set cpu affinity = 1 or you will get some crazy images.
|
|
|
Post by dodrudon on Nov 6, 2007 19:29:37 GMT
anyone with a multi-core system may want to consider changing the 'client cpu affinity' option as well. not sure how extensive the effects are, but you may be able to get a bit more stability at least You will need set cpu affinity = 1 or you will get some crazy images. Or =0. NWN will barely work otherwise on dual cores. I'd say it's less of a performance enhancement than a required system setting =P.
|
|
|
Post by chirikov on Nov 6, 2007 19:50:23 GMT
i dunno, mine was originally set at -1, and i changed it to 2. no apparent performance decrease, otoh i dont know if any performance increases are due to that or the memory allocation increase
|
|
|
Post by Yomi on Nov 6, 2007 19:52:02 GMT
I've run for over a year on two different dual core/proc machines with affinity=-1 with no issues (no instability, no crazy images, performance seems fine). I'll set it to 1 and see if anything changes. Both machines running WinXP, the dual Xeon using XP SP1, the E6400 using XP SP2. I'm not saying it's not a bad idea for people to change, just that it isn't required on all systems. Edit: I run Climate Prediction software full time on all my computers, so all CPUs are always at 100%. Forcing affinity would likely be a good thing wrt cache, but it ought to work regardless.
|
|
|
Post by chirikov on Nov 6, 2007 19:55:37 GMT
according to biowares patch notes:
- Added a new option to the nwnplayer.ini file under [Game Options] "Client CPU Affinity" (for Windows only). If you have more than one CPU on your PC, then you can use this setting to make the game run on only one of the CPUs by specifying the number of the CPU (0-31). Setting "Client CPU Affinity=-1" will turn off CPU affinity.
|
|
|
Post by chirikov on Nov 6, 2007 20:00:12 GMT
hmm, just realized i used the wrong setting (forgot the index starts at zero :x). should use either 0 or 1 if im going to use it
tbh, there probably wouldnt be any real performance increase using this setting, but i can see potential stability increases if you run a lot of background programs. it depends on how the load is being split
|
|
|
Post by dodrudon on Nov 6, 2007 20:19:51 GMT
I wonder if I could break my computer by making NWN think there are 32 cores... hmmmm...
|
|
|
Post by The Apostasy on Nov 11, 2007 10:45:47 GMT
I run an old hand me down PC (3k Athlon XP, 2X AGP on a 64MB card etc) not a real gaming rig and reconfiguring the nwnplayer made a MASSIVE difference. Screen rotation chop is gone, and spawn freeze is almost non existent so far. Thanks for this very useful info.
|
|
|
Post by gargazon on Nov 12, 2007 20:05:04 GMT
How do you make this change?
|
|
|
Post by Gailin Iceheart on Nov 13, 2007 0:50:12 GMT
The Cpu affinity patch was made to make people believe that bioware had actually done something. It was mainly publicized due to the arrival of NWN2. Affinity settings on NWN have never shown much difference, if any, as well as NWN2. Most of the problems occuring with NWN2 are mainly because they put a faulty product on the market. JMO. Try looking here for more info: www.tweakguides.com/NWN2_1.html
|
|
|
Post by gren on Nov 28, 2007 12:01:45 GMT
Reading this with interest and will try it tonight. 2 gb or ram should mean that's not a problem. Used to play on 'Hall of the Worlds' and there was an area there that was changed to include horses. Spawn lag was terrible but you just learned to liev with it.
Not come across any horses in HG yet (that I can remember anyway) but a few of the weregoats in Fox Trail are invisible so hopefully will sort that.
Been using a dual core laptop for almost a year now, never edited the ini fiel and never had a problem.....at least one that I would attribute to this anywa.
|
|
|
Post by rump on Jan 21, 2008 3:08:29 GMT
|
|
|
Post by FunkySwerve on Jan 21, 2008 3:20:55 GMT
Copied the link from the other forum in case it goes down:
Not sure if you guys know this but:
More gore;
Open nwnplayer.ini and change "Memory Level= 1" to "Memory Level= 2"and "Memory Access=1" to "Memory Access=2"
Then, in-game go to options, and change Violence Level to Special.
Your nwnplayer.ini file will look like:
[Game Options] Memory Level=2 Memory Access=2
Chunky deaths a la Baldurs Gate are now yours, as are big pools of blood.
Running in Windowed mode.
To run NWN in window mode, you need to edit the nwn.ini file, in the [Display Options] section and add the following line:
AllowWindowedMode=1
under the FullScreen line.
Hit ALT-ENTER to enter/exit window mode when NWN is running.
This is great for chatting on MSN whilst playing, and for surfing whilst waiting for a rest
As ever when altering a file, make a copy and store it, but these are safe to run.
Moving this to Bug/Problem Report and stickying.
Funky
|
|