sen4mi Posted Thursday at 06:00 AM Posted Thursday at 06:00 AM The newest release of xEdit (v4.1.5q) includes some important features, but I am struggling to use it. And I am hoping maybe someone here can lend me some insight about what could be going wrong. My problem is that it's slow, painfully slow, and it seems like it has gotten slower in the few days that I have had it. For example, currently, when I start it up, there's a message about the recent changes. It took about five minutes for the form to become interactive. And in that time, xEdit used maybe 4 seconds of cpu time. The rest of the time was spent waiting. When the dialog eventually pops up to select the plugins I want to look at, I use the right click menu to "select none" and while that happens right away, there remains a white rectangle where the menu had appeard which does not fill in for several minutes. I am now up to maybe 10 seconds of cpu time consumed by this process (and, while I type this, I check back on xEdit, and it still has not filled in that white rectangle, and I am not yet able to select the plugins I am interested in.) It was not this slow when I first installed it, but it was painfully slow back then, also. Version 4.1.5p does not have these issues (though it also had a 64 bit exe which I used exclusively - the v4.1.5q release did not include an exe labeled with a 64). Does anyone know anything about what I could do to address this kind of behavior?
sen4mi Posted Friday at 07:49 AM Author Posted Friday at 07:49 AM After experimenting with this: some of the problem could be attributed to the anti-malware software on my machine. But whitelisting xEdit (and the files it works on) reduced the stalls but did not eliminate them.
sen4mi Posted Friday at 08:28 AM Author Posted Friday at 08:28 AM (edited) Well... I think I might have discovered the issue. But I have no idea what to do about it: It looks like each active ESM is opened by xEdit as a DLL. I have no idea why it would do that - are ESM's supposed to be executable code? EDIT: no, that should not be the problem - not by itself. v4.1.5p does the same thing, and does not get hit by these slowdowns. Edited Friday at 08:54 AM by sen4mi
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now