First post, by Gambit37
My working folder for Glidos has textures for three levels. It's already getting unmanageable as I can never find anything; in particular it's tricky finding which folders relate to which level.
Would it possible to improve the texture management? here's a couple of suggestions in order of preference:
1) Read textures directly from a zip file -- so you could have one zip per level -- nice and compact and easy to manage. Games like Doom3 and Thief do this (although the extensions are not ZIP)
2) Use a subfolder based on the name of the level for each set of textures
3) Also, for development (or indeed generally) would it possible to specify the root texture folder as somewhere other than in the Glidos folder? It's a pain having to copy stuff from my development drive into my Program Files folder all the time, especaiily as I try and keep *all* data separate from programs and am running out of space on C:\ anyway! My dev drive has tons of space free and it would be nice for Glidos to be able to read my dev folder directly....
In fact, I just thought of something else that would be really cool. In conjunction with (3), it would be really handy to change the interface of Glidos for Tomb Raider/UB so that users can choose a set of texture packs to load or stick with the original graphics. That way, users won't have to mess with INI files and they could easily switch between texture packs designed by different people (I have been sent some things by other designers for other levels). It would work just as well with either implementation of (1) or (2) -- you just install graphics into a sub folder off the root textures folder, named GAMBIT for example, then within that are either subfolders for each level or the zip files.
What do you think Paul?