JNGP runs very slow

[Wasabee]

This is my first time experiencing this kind of problem with JNGP. When I select models for any units it takes a lot of time to display all available models, even in the icons. I also experience a bit of lag in the trigger editor.

 

[Deleted member 219079]

Have you tried with new download of JNGP?

 

[Wasabee]

It's the latest version of JNGP from BlizzMod.

 

[Deleted member 219079]

Yes, but you can try downloading again and extracting into another folder and trying if the problem exists on that one as well.

 

[Wasabee]

I tried downloading it again and it still runs slow.

 

[Deleted member 219079]

It runs slow on any map with that clean install? But it has run well before?

 

[Wasabee]

I tried testing some maps and jngp varies on each map.
Yes, I've just experience this lag recently.

 

[Deleted member 219079]

Could be AV software or equivalent causing the slowdown.

Maybe you've mistakenly activated the brush list, deactivate it from main menu's Window > Brush List if not already.

Mine is slow too, 2 seconds or so to display asset list, fyi. I don't know the scale of your slowdown so tell that.

 

[Wasabee]

The brush list is already deactivated.
Mine is much slower mostly 10+ seconds which is very annoying and for the triggers around 2 seconds.

 

[Deleted member 219079]

10+ seconds when? Are you talking about an empty map on a clean JNGP install when opening asset list? Any specifications would be nice tbh. Also give vanilla WE a go.

 

[Wasabee]

In an empty map there is no problem. The 10+ seconds are for maps with few to huge content.
I need JNGP for a couple of reasons.

 

[Deleted member 219079]

The vanilla is for control XD

 

[IcemanBo]

You can try to temporary hide doodads/units at "View" or disable other effects, when making some changes.

 

[DaneTheBeast]

I have the same issue.

 

[Dr Super Good]

Make sure anti virus software is not interacting with the editor. Even uninstall it temporarily to rule it out.

Otherwise this would point towards a lack of memory and very slow I/O speed. Either that or a map that is too complex or running in an OS performing a remote security evaluation when trying to access files.

 

[KILLCIDE]

It's most likely TESH. The newest JNGP uses looking_for_help's TESH, which currently has an issue with interprocess communication. I brought this issue up to looking_for_help before moyack made it a part of JNGP. All though, TESH shouldn't be causing slow downs on other parts of the editor other than the Trigger Editor.

 

[Deleted member 219079]

The newest JNGP uses looking_for_help's TESH

The abomination is in there?? Wow all poor souls being exposed to the slow..

I've attached some ver 2.0.7 from 2014 it shouldn't have cancer.

 

[DaneTheBeast]

THANKS @jondrean it works without lag

 

[Chaosy]

Just download the old JNGP and take the tesh from there.
Took me over a year before I figured out why my trigger editor was slow :-/

 

[Pyrogasm]

The abomination is in there?? Wow all poor souls being exposed to the slow..

I've attached some ver 2.0.7 from 2014 it shouldn't have cancer.

Sick. That color scheme is absolutely disgusting, though. -__-

 

[Wasabee]

It seems like the TESH is the one causing these problems because I replaced the TESH Folder of the new JNGP with the old one.