I installed windows 10 update a month ago, since then toolset loads haks horribly slow, opening properties is very slow as well and when clicking into “fields” like script events, it shows cursor with like 3 sec delay. Anyone knows how to fix this? I mean other than reverting windows 10 update…
Ive had considerable slow downs for the original toolset since as far back as 2009. ive learned to deal with it until i went to E.E which just seems to fix all those problems. Thats just for me though. I currently run E.E on windows 10 with no issues and original (1.69) with some issues, mainly speed.
I’m noticing this problem of the toolset slowing down with wine as well especially when dealing with conversation files and the script windows. It is extremely irritating but I can’t pinpoint exactly when this started as I work with the toolset on and off. But I think it started in the last 3 months or so. I’m going to use different versions of wine to figure out which version is the best and fastest to use with the toolset and update here if it actually is the newer wine’s fault. I’m still using the 1.69 toolset.
Maybe you could have a look into the taskmanager and see, how much CPU, HD- and/or network ressourced are used.
Note, that the problems with toolset has been resolved for me (except for a problems related to very large modules). Unfortunately I don’t remember what or when it got fixed, whether it was caused by my drivers that I updated or it went away after new version of EE. But right now on build .28 toolset is running fine for me under windows 10.
This has got me thinking that even in Linux it might be a graphic driver issue and not a wine issue at all, because using different versions of wine does not seem to make any difference. The Nvidia driver got updated recently in linux too and it might be that.
UPDATE: Just a couple of hours after writing this post, linux is also receiving another graphics driver update so maybe hopefully, this problem will be resolved for us linux users as well!
ANOTHER UPDATE: After updating the graphics drivers, the issue seems to have improved somewhat…not perfect though.