Author Topic: Slow Toolset or it just works this way? (Read 4330 times)

Legacy_Zeke · « **on:** January 06, 2016, 01:17:30 am »

I'm wondering is this a normal behavior - when a Properties window is loading of an asset (NPC, Amor, Inventory and so on) there is always a 4-5 sec hang until the window show.

Is anyone else experiencing this or this is how the editor behaves?

5 seconds is not a lot of time but when you work a little longer it really starts to drag out your work.

Simple math: if you open 12 times a "property" window, you have lost 1 minute in waiting.

So yeah, is this normal?

Legacy_kalbaern · « **Reply #1 on:** January 06, 2016, 04:19:29 am »

It can depend on your computer's specifications, whether or not your running in compatibility mode properly and what else you have open at the time, but I wouldn't say its out of the norm for many.

Legacy_Proleric · « **Reply #2 on:** January 06, 2016, 10:14:40 am »

               I have a fairly high spec PC, in XP compatibility mode for the toolset. The lag is maybe 2-3 seconds, which I don't really notice. 5 seconds would definitely be irritating, though.

In nwtoolset.ini under [Start Up] I have

CPU Affinity=0

NWNTX makes the toolset much faster in many respects (e.g. opening areas) but might not help with your specific issue.

Legacy_Zeke · « **Reply #3 on:** January 06, 2016, 10:27:07 am »

Yeah, I've also clicked on every *.exe to be in Windows XP Service Pack 2 compatibility and I'm using NWNTX.

Tried CPUAffinity = -2, -1, 0, 1, 2, 3 ,4

And clicking Properties of an NPC is exactly 5 seconds every time.

My PC has high specs too. Ahh, it looks like I'll have to accept this delay... '<img '>

Little offtopic:

What the "EnableExtensions" line do in nwntx_compiler.ini?

Edit:

Trying without any HAKs, it's down to 3-4. It still seems slow to me.

Legacy_Shadooow · « **Reply #4 on:** January 06, 2016, 11:36:38 am »

Little offtopic:

What the "EnableExtensions" line do in nwntx_compiler.ini?

I belive it enables the __LINE__ __FILE__ macros in scripts.

Btw same problem as you with properties window, though only module propeties takes so long, creatures/items are kind of ok.

Legacy_Thayan · « **Reply #5 on:** January 06, 2016, 03:09:36 pm »

I've had the problem with the property dialog boxes opening slowly for years as well. It ranges from 3-8 seconds, with placeables and doors taking the longest and areas being the shortest. Even using NWNTX. Haven't found any way around it.

Legacy_Zeke · « **Reply #6 on:** January 06, 2016, 04:58:52 pm »

I've had the problem with the property dialog boxes opening slowly for years as well. It ranges from 3-8 seconds, with placeables and doors taking the longest and areas being the shortest. Even using NWNTX. Haven't found any way around it.

Exactly my problem! Sooo I guess there isn't any solution to this.

Legacy_kalbaern · « **Reply #7 on:** January 07, 2016, 03:23:32 am »

On many PCs, popping in game and setting your video settings either higher or lower, then going back to the toolset can have a drastic impact on toolset performance. A while back, I'd reduced my video setting in game so I could get a better live recording while playing. It helped the video recording, but later when I opened my toolset, I also noticed slower loading times for properties. Raising my video settings once again in game resolved it.

Legacy_AndrueD · « **Reply #8 on:** January 07, 2016, 09:27:21 pm »

Am thinking it might be index problem cuz when I use on old 32-bit single core XP with even older AMD card, props come up pretty fast, like only 1 or 2 secs. Now on 64-bit 2 core Win7 Pro with nvidia take VERY long near 10 secs so would love to see pop in 5 secs '<img '> Maybe the 64-bit multicore archo make slower instead of faster? Dunno.

Am also wonder if total number of element with props has something to affect. When was doing modules on XP there only very small area with minimum elements. Now with bigger areas and many placebles, encounter, trigger, etc... seems much slower.

I try use toolset with all secure like virus turned off but not matter afaik.

Legacy_Shadooow · « **Reply #9 on:** January 07, 2016, 09:52:27 pm »

Its doing on my 32bit win7 machine too.

Actually I think the problem is the windows compatibility mode. I bet that win XP on same machine would allow toolset to be fast as it used to be.

Maybe someone with VirtualBox can test?

Legacy_Lilura · « **Reply #10 on:** January 12, 2016, 01:29:01 pm »

I'm wondering is this a normal behavior - when a Properties window is loading of an asset (NPC, Amor, Inventory and so on) there is always a 4-5 sec hang until the window show.

Is anyone else experiencing this or this is how the editor behaves?

5 seconds is not a lot of time but when you work a little longer it really starts to drag out your work.

Simple math: if you open 12 times a "property" window, you have lost 1 minute in waiting.

So yeah, is this normal?

I had a 0.25 sec hang on my Core 2 Duo and now have a much more noticeable 4-5 secs hang with my "gaming" laptop. It drives me nuts.

I tried setting affinity in toolset.ini and using compatibility mode but didn't notice any change. Well, I got a hard lock out of the former... so yeah, reverted to default.

Both Win8.1 x64, Radeon gfx.

I remember on WinXP x86 the toolset was so fast to load and bring anything up...

Legacy_WhiteTiger · « **Reply #11 on:** January 13, 2016, 02:13:21 am »

I like to listen an AUDIOBOOK while you build nwntoolset because while you lost time opening things you are learning something more else

way of life '<img '>

Legacy_Mavrixio · « **Reply #12 on:** January 13, 2016, 11:23:46 pm »

               It is indeed much faster on Windows XP: in my Windows 10 virtual machine it takes 10+ seconds while in my Windows XP virutal machine (on the Same PC and for the same module and creature) it takes less than 3 seconds.
Building in Windows XP also fix the camera issue.

Legacy_virusman · « **Reply #13 on:** January 14, 2016, 02:09:24 am »

The dialog constructor populates script handler boxes with lists of scripts. If your module contains hundreds of scripts, it'll easily execute the same method a few thousand times. Every addition calls SendMessageA, and since that function is in user32.dll, its performance depends on the OS.

Legacy_virusman · « **Reply #14 on:** January 14, 2016, 03:42:28 am »

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)

Bioware Archive

News:

Author Topic: Slow Toolset or it just works this way? (Read 4330 times)

Legacy_Zeke

Slow Toolset or it just works this way?

Legacy_kalbaern

Slow Toolset or it just works this way?

Legacy_Proleric

Slow Toolset or it just works this way?

Legacy_Zeke

Slow Toolset or it just works this way?

Legacy_Shadooow

Slow Toolset or it just works this way?

Legacy_Thayan

Slow Toolset or it just works this way?

Legacy_Zeke

Slow Toolset or it just works this way?

Legacy_kalbaern

Slow Toolset or it just works this way?

Legacy_AndrueD

Slow Toolset or it just works this way?

Legacy_Shadooow

Slow Toolset or it just works this way?

Legacy_Lilura

Slow Toolset or it just works this way?

Legacy_WhiteTiger

Slow Toolset or it just works this way?

Legacy_Mavrixio

Slow Toolset or it just works this way?

Legacy_virusman

Slow Toolset or it just works this way?

Legacy_virusman

Slow Toolset or it just works this way?