EDIT - THIS IS OBSOLETE INFORMATION. VALVE HAS FIXED THE NAV EMBEDDING IN THE HALLOWEEN UPDATE 2015. NAV FILES NOW LOAD CORRECTLY WITHIN BSP.
This week i had very enlightening experience with the workshop and nav files. I'm sharing this because i want to avoid anyone going through the same thing i did. Here's what i figured out and sorry if it's old news for some.
TF2 workshop doesn't like nav files. They simply will never load up from the bsp correctly (getting back to this part lower). This causes bots not to move or boss enemies, such as HHH and monoculus never actually leaves. So, to avoid further bloodshed, never pack nav files to the bsp when you upload your map to workshop. Always share the .nav file separately. Here's why:
- If player subscribes to a map, starts it up with map workshop/mapIDhere - the map will load up fine but again, the bots won't move as the nav is completely ignored, even if it's packed inside the bsp file. This will only cause further harm if player does the next step, trying to fix it or someone tells him to do it.
- If player has subscribed and decides to to take the map off from STEAM\SteamApps\workshop\mapIDhere - then places it to STEAM\SteamApps\common\Team Fortress 2\tf\maps and starts the map with map mapfilename.bsp - the map will cause players game to crash. This may not happen if there was no nav packed in within the bsp.
- Player can fix this crash by placing separate .nav file to STEAM\SteamApps\common\Team Fortress 2\tf\maps and even the workshop map will load up fine. Though if the map is executed through map workshop/mapIDhere, this nav is still ignored.
There is no way to have a functional map file with bots working uploaded to workshop.
If you ship a map with bots or boss enemies and navigation file is needed, just don't pack nav into the workshop version of the map, share it separately. It won't work anyway if you do pack it, and will cause a crash if player tries to load the map up outside workshop commands (map workshop/mapIDhere)
This week i had very enlightening experience with the workshop and nav files. I'm sharing this because i want to avoid anyone going through the same thing i did. Here's what i figured out and sorry if it's old news for some.
TF2 workshop doesn't like nav files. They simply will never load up from the bsp correctly (getting back to this part lower). This causes bots not to move or boss enemies, such as HHH and monoculus never actually leaves. So, to avoid further bloodshed, never pack nav files to the bsp when you upload your map to workshop. Always share the .nav file separately. Here's why:
- If player subscribes to a map, starts it up with map workshop/mapIDhere - the map will load up fine but again, the bots won't move as the nav is completely ignored, even if it's packed inside the bsp file. This will only cause further harm if player does the next step, trying to fix it or someone tells him to do it.
- If player has subscribed and decides to to take the map off from STEAM\SteamApps\workshop\mapIDhere - then places it to STEAM\SteamApps\common\Team Fortress 2\tf\maps and starts the map with map mapfilename.bsp - the map will cause players game to crash. This may not happen if there was no nav packed in within the bsp.
- Player can fix this crash by placing separate .nav file to STEAM\SteamApps\common\Team Fortress 2\tf\maps and even the workshop map will load up fine. Though if the map is executed through map workshop/mapIDhere, this nav is still ignored.
There is no way to have a functional map file with bots working uploaded to workshop.
If you ship a map with bots or boss enemies and navigation file is needed, just don't pack nav into the workshop version of the map, share it separately. It won't work anyway if you do pack it, and will cause a crash if player tries to load the map up outside workshop commands (map workshop/mapIDhere)
Last edited: