Perception Range resets?

[Legacy_Highv Priest]

               I was going about my mod like normal when I discovered the perception range of my banker NPCs(from scarfaces system) had been reset back to default(originally short because I don't need him picking up on numbers from other players fifteen meters away). I couldn't understand why the banker all of a sudden became skynet and started reprogramming itself. I knew I didn't change it and then it hit me "could closing toolset with task manager cause this?". So I tested it and it does! Which is just downright freaking annoying. I thought it was bad enough that my laptop can't see any 3d models without locking up with that stupid "Access violation at address 063E8CED in module ig4dev32.dll"(which apparently is IMPOSSIBLE to get rid of.). I don't want to have THREE of my computers devoted to nwn alone. I already have 1 hosting and this laptop where I normally do the scripting abroad at starbucks or panera. I don't want to have to use my gaming machine for something as small as toolset.

So outside of explanation... Is there any method to avoid perception range being reset or to set perception range when spawned in? or is there perhaps someone who has gotten so far into nwn's core programming they can tell me how to get rid of that stupid lock up?

It's not a serious issue, but resetting all the bankers on the server requires updating all instances for 300ish areas(you know since you can't choose which areas get the update) ... Which takes about 15 minutes on my non-gaming laptop.(lol gaming laptop , such a funny paradoxical word)
               
               

               
            

[Legacy_Rolo Kipp]

               <trying...>

Highv Priest wrote...
...
I thought it was bad enough that my laptop can't see any 3d models without locking up with that stupid "Access violation at address 063E8CED in module ig4dev32.dll"(which apparently is IMPOSSIBLE to get rid of.).
...

A question on that (I started with an old, crippled Thinkpad R40 and do almost all my internet in Starbucks) what toolset do you use? The vanilla one or NwNTx? I switched to NwNTx and my jaw dropped. Well, using Skywings compiler, too. But it made a big difference with me.

The other thing is that access violation... I seem to remember having the same issue, but I can't remember if it was a corrupted .bif or missing blueprint. you might compare your .bifs in the data file with a clean install (other computers?) and see if something is amiss.

...
It's not a serious issue, but resetting all the bankers on the server requires updating all instances for 300ish areas(you know since you can't choose which areas get the update) ... Which takes about 15 minutes on my non-gaming laptop.

You can choose the area. View the area, then update blueprint. When the dialogue appears it's "Yes" for all areas, "No" for just that one.

And 15 mins is way too long.

<...but probably not helping much>
               
               

               

                     Modifié par Rolo Kipp, 27 décembre 2012 - 06:51 .
                     
                  

            

[Legacy_Highv Priest]

               

Rolo Kipp wrote...

<trying...>
A question on that (I started with an old, crippled Thinkpad R40 and do almost all my internet in Starbucks) what toolset do you use? The vanilla one or NwNTx? I switched to NwNTx and my jaw dropped. Well, using Skywings compiler, too. But it made a big difference with me.

The other thing is that access violation... I seem to remember having the same issue, but I can't remember if it was a corrupted .bif or missing blueprint. you might compare your .bifs in the data file with a clean install (other computers?) and see if something is amiss.

You can choose the area. View the area, then update blueprint. When the dialogue appears it's "Yes" for all areas, "No" for just that one.

And 15 mins is way too long.

<...but probably not helping much>

I use the vanilla toolset because I've learned in the past using less then known things means it's harder to find answers when something goes wrong. I actually didn't know NwNTx existed, I'll have to try it out.

http://boardreader.c..._bcr3Xdo04.html

It's explained pretty good in the one above this.

http://frc.proboards...nt&thread=10189

This one is interesting. How do I know what bit nwn is using?

The issue is a result of the nVidia chipset not reading alpha layers(or something to that extent, I remember reading at a time it was nVidia's fault and not BioWare's) I did A LOT of research with it before trying to come up with a solution, even to the extent of disassembling nwtoolset.exe in order to find that stupid lockup and delete it entirely only to find out it doesn't exist in nwtoolset.exe or any nwn files for that matter because it's an issue with the actual video driver itself....(but hey at least I learned a lot of neat things about nwn)

http://www.processli...g4dev32/403044/

I've diagnosed it quite well, but can't seem to find a grounds to make it STOP happening. Somewhere along the way the coloring becomes all corrupted and skewed. The issue doesn't corrupt my module, it just messes up the graphical look of it pretty badly. Sometimes if I so much as view a SINGLE 3D object it will lock up with the error message I explained above. Clicking OK or the X doesn't close it and I have to use task manager or something similar to close out of toolset. Since it doesn't actually change any files it doesn't corrupt my toolset, but apparently loading up from a backup can cause things to be reset back to default settings.