Backup your override and work from there. I do ALL my development that way to avoid having to rebuild/update haks, system works fine that way. Just rename your current override folder, create a new one named override and build away, when you want to go back, just rename the new override to new_override or whatever name you wish, and rename your backed up version back to override.
I also tend to work with toolset loaded, and max, and game at same time. Edit in max, export, go to toolset and reload the area to see if it loads correctly, don't even have to reload the mod, just that specific area, hit f9 and test. Exit, ad-infinitum.
EDIT: Note, that the game totally ignores SUB-Folders inside of the override as well, I currently have something on the order of 30 sub folders inside override. Original source files, 1.69 folder, different tilesets I may be working on etc, just move the individual files from the sub folders into override and viceversa whenever I need to work with something else. By using sub-folders, it is also MUCH easier to load source files from those sub folders while working within the main override folder... IE: In max, I just use nwmax to browse to a sub folder to grab a source file, load it, and reset it's output folder back to main override, that way I am actually working on a copy instead of the original.
Modifié par Bannor Bloodfist, 18 mai 2011 - 03:35 .
