Joined: 08/08/2008 11:36:13
I am having trouble with VUE not picking up edits in nested vpk files. I organize my courses based on a VUE map of the topics coverd that then drills down to maps of individual topics and sometimes to maps within those. I save everything as VPK because I need the maps to be portable. So in effect there is one big map. This is fine, but I am finding that when I edit submaps, the changes don't stick. The workaround I found is to do a Save As on the child VPK into its own file, then completely remove the resource reference in the parent, then relink whenever I mae any changes to a child vpk. The danger here is that if the resource is removed before it is save to a separate file it is just lost except via undo (not even sure that works - I have had to restore from backups when this happened.).
The desired outcome would be to be able to work in a child vpk file, click on save within the child VPK to update it in the master, and then save the master when exiting, or to just have saving the master vpk serially save all the child VPKs in their current state.
The simplest solution, which in some ways I would prefer to the "one-big-file' approach would be to make a double exception for VPK files: first, don't allow recursion. a reference to a vpk file will always be external. Second, allow VPK files to be relative or maybe require them to be in the same directory, to keep portability. I actually prefer working on the individual files and saving them separately. Or maybe make this approach an option in preferences.
I know from reading the forums that the VPK file is supposed to replace the need for relative paths, but in the case of nested vpk file,s zipping everything together does not work well if the inside parts cannot be updated easily.