On 24 Sep 2009, at 14:49, Major Johnson wrote: > Origins: turns out that the origins were messed up for those things, > thanks!
Great, glad it's sorted. > Looked back at the compile log file, and there were a lot of these I > didn't > see before, at least, on the last two compiles I did last night*: > > Static prop models/props_granary/grain_sack.mdl outside the map > (-44.00, > -1645.00, 860.00) > Static prop models/props_2fort/miningcrate001.mdl outside the map > (367.00, > -152.00, 1382.25) > > Which at this point I'm confused, as I never touched any of my props > (at > least, not those) yesterday, but I do recall a stack of grain-sacks > that was > not showing. Here's the best part, those coordinates are exactly > where the > props should be: inside the map--that grain sack being one of the > ones that > went missing (which I only noticed tangentially and didn't look into > at the > time). Yes: once VBSP encounters a leak (i.e. an entity that is touching the "void", in your case the trigger_teleports), it doesn't know what the "inside" or "outside" of the map is anymore, and will often report spurious extra errors. That'll have been the cause of those messages. --VFIG _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlmappers
