Slow Toolset or it just works this way?

[Legacy_Thayan]

               

Thank you, virusman!

               
               

               
            

[Legacy_Lilura]

               

Here are your 5 seconds back:

nwntx_optimizations-1.0.6-pre.rar

(This will remove suggestions from all script selection combo boxes, so you'll have to pick scripts using "..." button)

 

 

SO much faster... thank you!

               
               

               
            

[Legacy_Zeke]

               

Here are your 5 seconds back:

nwntx_optimizations-1.0.6-pre.rar

(This will remove suggestions from all script selection combo boxes, so you'll have to pick scripts using "..." button)

 

Whoa! Thank you!

 

Are there any customizations (cuts) that can be done? Just curious.

               
               

               
            

[Legacy_virusman]

               

Oops, there was a bug that actually caused errors when clicking OK in the properties dialog. Please re-download from the same link. Should be fixed now.

               
               

               
            

[Legacy_Shadooow]

               

Oops, there was a bug that actually caused errors when clicking OK in the properties dialog. Please re-download from the same link. Should be fixed now.

Could you also improve module properties window? It seems script list is loaded into Cache tab.

               
               

               
            

[Legacy_Thayan]

               

This may be better suited in the NWNTX thread, but since I've finally narrowed this down to the nwntx_optimzations.dll being present, I'll bring it up here:

 

Whenever that .dll is being used by NWNTX, when you click on an object in the area view pane, it does not jump to or hightlight the object in the object list on the left side of the toolset. I never realized how much I relied on that until now for the purposes of checking the tag or name or the object, or making sure I have the right one I want to modify/delete, without having to actually go to its properties. So I just have to ask: is there any way to get that functionality back? Or is that part of the reason that makes this optimization .dll so fast?

               
               

               
            

[Legacy_virusman]

               

This may be better suited in the NWNTX thread, but since I've finally narrowed this down to the nwntx_optimzations.dll being present, I'll bring it up here:

 

Whenever that .dll is being used by NWNTX, when you click on an object in the area view pane, it does not jump to or hightlight the object in the object list on the left side of the toolset. I never realized how much I relied on that until now for the purposes of checking the tag or name or the object, or making sure I have the right one I want to modify/delete, without having to actually go to its properties. So I just have to ask: is there any way to get that functionality back? Or is that part of the reason that makes this optimization .dll so fast?

Yes, NWNTX Optimizations disables that highlighting precisely because it was causing the freezes when selecting objects.

               
               

               
            

[Legacy_virusman]

               

Could you also improve module properties window? It seems script list is loaded into Cache tab.

Should already be improved w/regard to module event handlers. Cache tab contains a list, not a combo box, so removing the options would make it unusable.

               
               

               
            

[Legacy_Shadooow]

               

Should already be improved w/regard to module event handlers. Cache tab contains a list, not a combo box, so removing the options would make it unusable.

I just found out that its only first time this is slow. First time it took 20 seconds on my PC (was 30+ without NWNTX), but second time and third time it showed in 1second so that works for me.

 

Now, if there would be a way to disable that feature that mess with my modules whenever I work on more than 1 at once. I know I can quit toolset before opening different module and Im trying to follow that, but its easy to forget...

 

Anyway, good work.

               
               

               
            

[Legacy_Zwerkules]

               

This may be better suited in the NWNTX thread, but since I've finally narrowed this down to the nwntx_optimzations.dll being present, I'll bring it up here:

 

Whenever that .dll is being used by NWNTX, when you click on an object in the area view pane, it does not jump to or hightlight the object in the object list on the left side of the toolset. I never realized how much I relied on that until now for the purposes of checking the tag or name or the object, or making sure I have the right one I want to modify/delete, without having to actually go to its properties. So I just have to ask: is there any way to get that functionality back? Or is that part of the reason that makes this optimization .dll so fast?

That's interesting because I have the same problem since I don't have a computer with Windows XP any more. It worked fine under XP, but doesn't highlight anything in the object list any more on other Windows versions. I find that very annoying, but I don't have NWNTX. I also don't remember which game version I had when I still had XP. Maybe it already was 1.69, maybe not. I don't know if a patch changed something in the toolset or if it happened when I got a computer with Vista instead of XP.

               
               

               
            

[Baaleos]

               

I usually find that a module also loads scripts incredibly slow if you try to open them from the script side panel.

I usually go to Module - Properties, Events, then open an event, then use the script editor to open the specific script I want.

 

Otherwise the script panel will hang for about 1-2 minutes.

               
               

               
            

[Legacy_Proleric]

               

I usually find that a module also loads scripts incredibly slow if you try to open them from the script side panel.
I usually go to Module - Properties, Events, then open an event, then use the script editor to open the specific script I want.
 
Otherwise the script panel will hang for about 1-2 minutes.

In my experience, that problem occurs when you have a large number of scripts.

One remedy is to move most of the stable ones into a hak.

Another is to switch to a smaller number of monolithic scripts (e.g. one per event, with tag- or variable-driven logic). Obviously, that approach is easier when starting a new module.
               
               

               
            

[Baaleos]

               

True - the module actually had the stable scripts moved to a hak a while ago.

Eg: quest scripts etc

 

But even then, was well over the 16k in the module....

I kinda just kept expanding using nwnx_resman.

 

Eventually I moved to a Continuous Integration system, where I had the module content in individual folders that then got pulled together via batch file prior to opening toolset.

This gives rise to the large script count

Then when the module is finished, saved etc I run another batch file to separate the module out into the individual file types.

Then it commits to SVN, and gets built by Jenkins. (scripts compiled etc)


Only NCS files get saved to the module, which then cuts down on the script count.

Its just the mdoule editing phase that is laggy.

               
               

               
            

[Legacy_Thayan]

               

Using the latest nwntx_optimizations.dll appears to break the Creature Wizard. Nothing happens when you click the Next button after selecting the Monster Type. I tested across multiple modules both with and without haks and in any case, if I was using NWNTX I could only get it to work after removing that dll.

               
               

               
            

[Legacy_Zeke]

               

Hmm, strange, just tested and it works for me. What OS are you on?