View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0003256||DarkRadiant||Map Editing||public||22.10.2012 17:53||21.03.2018 10:50|
|Platform||Win32||OS||Windows||OS Version||7 sp1|
|Fixed in Version||2.5.0|
|Summary||0003256: DR 1.8.0: slow/freezes when re-loading maps, textures ro filters.|
|Description||Since upgrading the DR 1.8.0pre myself and Grayman have been putting up with productivity sapping slowness. See the forim thread - |
|Steps To Reproduce||Open a medium to large map, then try to reload the shaders, DR becomes unresponsive and you sit there for a few minutes waiting. The same thing happens occasionally if you try to reload the same map|
Grayman is also having the same issue when turning filters on/off.
|Tags||No tags attached.|
|Will see if the latest version 1.7.3 of DR uploaded by Orbweaver suffers from this issue.|
|Does this issue still exist?|
|As of the 1.8.0 release, yes the issue is still present.|
|Toggling filters becomes verrrrrry slow after asking to see the list of entities in the map. Requires a restart because you become reluctant to turn filters on and off.|
|The filters issue I was able to reproduce easily (is tracked in 0003619), but I can't reproduce the Reload Materials issue, even in large-scale maps. It takes a bit, of course, but far from minutes.|
I started a fresh copy of DR last night, and it took 7 seconds to switch back and forth between large maps. I made 10 such switches right away with no increase in load time.
I left DR open overnight and went back to check this morning. The first load, from a tiny test map to a large map, took 1:52 (min:sec), and an immediate switch from the large map to another large map took 4:25.
Even though these are not long times, they're way off the expected 7s. When I see that DR is taking more than 30s to switch to a new map, I leave it and start a fresh copy of DR and continue my work there. Later, I come back to the original copy, which has finished loading by then, and kill it.
The only time I'm unable to use this process (start new DR and kill old one) is when I need to copy something from one map to another. That's when it gets really bothersome to wait.
I'm working on Win 7 with 12gB of memory and 8 processors.
Edit: the message on the screen while waiting for a load to complete is:
Processing... Loading textures ...
|Is it necessary to leave the instance open over the whole night? Do the symptoms appear without that long pause?|
When mapping, I typically open DR in the morning and don't shut it down until late at night, which means a 12+ hour session. (With breaks, of course.)
The next time I'm settling in for a long session, I'll keep a log of how long DR's been running when I do map switches, and how long each map switch took.
@Gman, how did the 12hr test go..? As this is still an issue.
Just open a map froma fresh start of DR and then loaded the same map and it sat there for a few minutes stuck on "loading textures"
|I have gotten so used to working around this problem (always restart DR when switching maps) that I have no new information to pass along.|
|This tracker is ancient and was fixed several version ago.|
|See last note.|
||Note Added: 0004994|
|27.08.2013 12:27||greebo||Note Added: 0006089|
|27.08.2013 12:27||greebo||Status||new => feedback|
||Note Added: 0006198|
||Status||feedback => new|
|27.11.2013 16:42||grayman||Note Added: 0006279|
|27.11.2013 18:48||greebo||Note Added: 0006283|
|28.11.2013 15:12||grayman||Note Added: 0006289|
|28.11.2013 15:12||grayman||Note Edited: 0006289|
|28.11.2013 15:15||grayman||Note Edited: 0006289|
|28.11.2013 16:06||greebo||Note Added: 0006291|
|28.11.2013 17:17||grayman||Note Added: 0006293|
||Note Added: 0006423|
|09.03.2014 18:01||grayman||Note Added: 0006426|
||Note Added: 0010135|
||Note Added: 0010136|
||Status||new => closed|
||Assigned To||=> user81|
||Resolution||open => fixed|
||Fixed in Version||=> 2.5.0|