Probably a good idea about switching around the order the tools check for file types.
BTW, I was wondering if there is any reason not to just include all of the objects that objlist outputs, instead of only selecting a key few that are most important to LoS. I realize that objects like trees and rocks aren't ultra-important for LoS, but I don't think it is particularly bad to have trees and stuff blocking LoS. The main question I have is; does adding every object in the object list cause a huge overhead on LoS processing? I have tried it with a few SoF zones which produce 20MB+ map files in some cases. If the CPU isn't going to go crazy by doing that, I don't see any reason not to do it. And, if so, maybe Azone2 could have an option put in that will combine itself with the object list tool. Then, it will list all objects for the zone and automatically build the map file to include all of those objects to save considerable work and time to check each one out by hand manually. Maybe a feature like that could be added as an option when running Azone2 or something.
|