View Issue Details

IDProjectCategoryView StatusLast Update
0000399DarkRadiantGUIpublic04.11.2011 06:41
ReporterSneaksieDave Assigned Togreebo  
PrioritynoneSeverityfeatureReproducibilityalways
Status closedResolutionno change required 
Product Version0.9.2 
Fixed in Version1.7.0 
Summary0000399: Flush and Reload... other things?
DescriptionThis occurred to me while looking at the current model renaming situation.
If a modeler/mapper is in WIP with some models, trying revisions etc., it might be useful to have a Flush and Reload for models, as there is for shaders.

But for that matter, what about other definitions (entities? sounds, particles? perhaps those are already covered with shader reload?)

Perhaps the model one is important enough, and the others not... or perhaps none of them are, and the author should just restart each time. Anyway, see what you think about this -- just an idea.
TagsNo tags attached.

Relationships

parent of 0000432 closedgreebo Reload Skins command 
parent of 0001749 closedgreebo Reload defs console command 

Activities

greebo

greebo

29.10.2007 06:37

administrator   ~0000807

Reloading declarations would definitely be useful.
SneaksieDave

SneaksieDave

29.10.2007 15:10

reporter   ~0000808

I just noticed a very nice side effect of this. Obviously, as a user browses more and more textures, their memory demand increases. Just looking at a few dozen textures, my darkradiant process shoots from 50Mb memory to well over 100Mb. Well, when I flush and reload shaders, the memory goes back down to 50Mb! :)

So if it works the same, all flush and reload options can also be seen as a memory optimizer, especially useful when working on large maps and really pushing the system limits. The user can purge the unused models, textures, and whatever else, and the memory won't be strained so much, without having to exit, restart, and reload the whole map again.

Gotta love the little tricks to get the most out of a tool. :)
greebo

greebo

10.11.2007 22:51

administrator   ~0000862

Reload Skins is implemented as a first step.
greebo

greebo

04.11.2011 06:41

administrator   ~0004121

I guess we can close that one as we can reload most things.

Issue History

Date Modified Username Field Change
29.10.2007 01:41 SneaksieDave New Issue
29.10.2007 06:37 greebo Note Added: 0000807
29.10.2007 06:37 greebo Status new => confirmed
29.10.2007 15:10 SneaksieDave Note Added: 0000808
10.11.2007 22:51 greebo Note Added: 0000862
11.11.2007 13:12 greebo Relationship added parent of 0000432
10.04.2009 13:50 greebo Relationship added parent of 0001749
04.11.2011 06:41 greebo Note Added: 0004121
04.11.2011 06:41 greebo Status confirmed => closed
04.11.2011 06:41 greebo Assigned To => greebo
04.11.2011 06:41 greebo Resolution open => no change required
04.11.2011 06:41 greebo Fixed in Version => 1.7.0