34 réponses à ce sujet

[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.

[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.

[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.

[Zeke]

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

[WhiteTiger]

I'm with a new notebook. I'd like to know what is the better OS to work in nwn toolset Windows 10 or Windows 7

[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)

 

Hmm, there seems to be a bug under Windows 10. Whatever I try to hook a script I get the following error - http://i.imgur.com/3ikwcCg.jpg

 

And it seems the dropdown menu is kind of bugged - http://imgur.com/HTAfS1J

[Proleric]

Not just Windows 10. The bug, which I reported in a NWNTX thread here, prevents script editing from triggers.

You can still edit the scripts directly. However, to change the list of event scripts for a trigger, you either have to use gffeditor or reopen the toolset without NWNTX.

[AndrueD]

Can cache size be change or can be clear out?

 

Wut I mean is wen mod open it get stord some place til saved.  But where is place stord?  Some ppl call buffer, not cache, but same thin.

 

Like on web browzer, can clear cache nd start new each time if set it that way or can get slow.  Mayb toolset not always clear that place right.

 

Reason I wonder cuz sum time b4 I had problem with game so ned to install new all over agin. After new install, toolset work real fast.  Wen I look property, they pop fast.  Any area alway load very fast. So do all script.

 

But now bout 2 month later, doin same stuff goes slow now.  Am doing same stuff nd not add any new script or anythin but just to check props goes slow now.  Somethin happen nd seem like some area get filled up but not know wher to look to see size when mod load into toolset.

[Proleric]

The module contents are cached as gff files in the folder nwn/modules/temp0 while the module is open. That's deleted when the toolset closes, so it shouldn't affect performance (assuming the drive is defragged periodically).

As I understand it, NWNTX optimises how the toolset stores various reference lists (amongst other things).

I don't know whether there's any persistent temporary storage, though.