Problem with my toolset

[Legacy_EmphaticStatic]

               

Hi!

 

I'm working on a module, and placing placeables, but when I test/play it, the changes won't show. It is just like the toolset isn't saving the changes.

 

I had this problem in the past, but don't remember how I solved it.

 

Can it be that my NWN is installed in my program x86 folder? I have no other problem than this, never has problem to run the game.

 

If that's the problem, can I install it also on C: or will that be conflicting?

 

Thanks for you help!

               
               

               
            

[Legacy_Tarot Redhand]

               

You don't say what OS this is on. Also is it 32 or 64 bit?

 

TR

               
               

               
            

[Legacy_ehye_khandee]

               

The BUILD function may be the critical part here. You must BUILD and SAVE a module to see changes in many cases.

               
               

               
            

[Legacy_Proleric]

               

The BUILD function may be the critical part here. You must BUILD and SAVE a module to see changes in many cases.

 

Well, you need to save it. During development, Build is unnecessary unless you've changed an included script, in which case Build offers a convenient method of recompiling all scripts. Prior to release, the other Build functions such as missing resources are worth running for good order.

 

Turning to the OP, are the changes there in the toolset when you re-open the module? My first guess is that you might have two copies of the module, one in the program file, the other in the c drive root. You could be changing one then running the other. If that's the problem, I'd back up all the files you've made, uninstall nwn and remove any residual files, then reinstall in the c drive root where it's supposed to be (afaik).

 

Less drastically, there may be a way of changing paths somewhere so that only one version is used, but I don't have detail on that.

               
               

               
            

[Legacy_kalbaern]

               

Yes, you can install it in the normal place on your C drive. If this was a GoG download, you should be able to redownload it to the proper directory. You can also just manually move the the directory, but you'll need to delete any current short cuts and replace them afterwards. I actually have three copies of NWN on my own computer, made by copying the first install over to other drives or even my desktop .... actually, make that four versions, one on each of my three drives and my vanilla copy in a folder on my desktop.

 

Most folks don't need more than one NWN install, I just do it to manage haks, CEP versions and other things for PWs other than my own that I assist is all.

 

You don't need to do a build to see changes. Just save then test. Their are only two cases where you must build a module. 1) When changing an include file that is used in multiple scripts it can help to do a script only build of the module. 2) When changing factions, the module will start a non-abortable build as it adjust factions in every area and blueprint in you module. While the module will initiate a build when you add/remove haks, you can abort this rebuild using a cancel option that appears shortly after it begins.

               
               

               
            

[Legacy_EmphaticStatic]

               

Thank you all for your replies!

 

By testing/playing the module, I meant I save it and go play it directly ingame, on my computer. But then the changes won't show. Like if the module doesn't save or something.

 

I did a second installation on my C drive, I'll see if the problem persist.

               
               

               
            

[Legacy_Tarot Redhand]

               

Quick test -

 

1. Load module into toolset

   
2. Make a quick easily reversible change to the module such as putting a placeable in the middle of the area where you start

   
3. save the module

   
4. Press the F9 key to launch NwN from within the toolset (the toolset will automatically minimize on the taskbar)

 

If the change doesn't show up check that nwtoolset is set to run as an administrator. If you don't know how ask and I'll explain. However if it does show up, you have probably been launching a different module with NwN.

 

TR

               
               

               
            

[Legacy_EmphaticStatic]

               

I made a new test with the installation that is on my C drive and it works now. Thanks!