- Jun 22, 2015
- 18
- 1
hi!
so i used BSPSource v1.3.20 to decompile cp_dustbowl.bsp from \Steam\SteamApps\common\Team Fortress 2\tf\maps\, but there are actually a bunch of bugs present. (a bunch of them show in Hammer itself, and a bunch of them show in the compile-log.)
most importantly, there are I/O errors and errors having to do with areaportals/occluders, that are messing up important triggers and graphics.
so i'm wondering; have i messed something up when (de)compiling, or is there no way to avoid getting these errors..?
and not that fixing them would necessarily be an issue, but i haven't mapped in like 12+ years and basically have to figure everything out from scratch again.
the plan was to start editing an existing map to make it a bit easier on myself, but now i wonder if i'm out of luck on that one
cheers!
Bu
edit: solution at post 4
so i used BSPSource v1.3.20 to decompile cp_dustbowl.bsp from \Steam\SteamApps\common\Team Fortress 2\tf\maps\, but there are actually a bunch of bugs present. (a bunch of them show in Hammer itself, and a bunch of them show in the compile-log.)
most importantly, there are I/O errors and errors having to do with areaportals/occluders, that are messing up important triggers and graphics.
so i'm wondering; have i messed something up when (de)compiling, or is there no way to avoid getting these errors..?
and not that fixing them would necessarily be an issue, but i haven't mapped in like 12+ years and basically have to figure everything out from scratch again.
the plan was to start editing an existing map to make it a bit easier on myself, but now i wonder if i'm out of luck on that one
cheers!
Bu
edit: solution at post 4
Last edited: