- Dec 17, 2016
- 15
- 1
First of all: this question isn't about TF2 maps but instead about maps for a mod, since I don't have an account in any other mapping forum and VDC is dead AF, I thought I'd post here. Technically, it's a Hammer problem.
So, I've picked up a mod I started some time ago again, but I've got a problem with maps. When I compile a map after changes and load it again (map <mapname> in the console), the changes won't show up. I have to delete the map file and compile the map again and again (usually three to four compiles and subsequent map reloads) until the changes show up, and even then, the map is always fullbright, no matter how many lights there are. mat_fullbright 0 doesn't do a thing (sv_cheats is on, btw), and I have to go through the whole delete-compile-reload process a couple dozen times until my changes are actually working, meaning per 5 minutes of work in Hammer, I spend thirty minutes until I can review my changes.
Obviously, this makes mapping near-impossible, so I hope somebody knows a fix for that.
Technical details:
I'm mapping for a Portal mod, I use the Hammer editor distributed with Portal (not from the SDK) with a profile set up for the mod. Since the default compile profiles don't work, I had to build one from scratch as well, calling vbsp vvis and vrad by their path instead of $bsp_exe since those don't work either.
I assume something major is fucked up with the Hammer config, but since it's working, I don't feel like tinkering with it unless absolutely necessary. I've had bad experiences with Hammer through all games I've mapped and modded for, including Hammer always switching to the wrong profile, crashing upon compile, crashing upon startup and crashing upon creating certain entities. All in all, Hammer has failed more often than it's worked, even rendering me unable to map for a couple weeks once until I found it doesn't like backward slashes in exe paths.
I really hope anybody can help me, and I hope I'm not violating any rules by asking a not-TF2-related question (well, technically, it's about Hammer and not a certain game... I think).
Greetings,
HashtagMC
So, I've picked up a mod I started some time ago again, but I've got a problem with maps. When I compile a map after changes and load it again (map <mapname> in the console), the changes won't show up. I have to delete the map file and compile the map again and again (usually three to four compiles and subsequent map reloads) until the changes show up, and even then, the map is always fullbright, no matter how many lights there are. mat_fullbright 0 doesn't do a thing (sv_cheats is on, btw), and I have to go through the whole delete-compile-reload process a couple dozen times until my changes are actually working, meaning per 5 minutes of work in Hammer, I spend thirty minutes until I can review my changes.
Obviously, this makes mapping near-impossible, so I hope somebody knows a fix for that.
Technical details:
I'm mapping for a Portal mod, I use the Hammer editor distributed with Portal (not from the SDK) with a profile set up for the mod. Since the default compile profiles don't work, I had to build one from scratch as well, calling vbsp vvis and vrad by their path instead of $bsp_exe since those don't work either.
I assume something major is fucked up with the Hammer config, but since it's working, I don't feel like tinkering with it unless absolutely necessary. I've had bad experiences with Hammer through all games I've mapped and modded for, including Hammer always switching to the wrong profile, crashing upon compile, crashing upon startup and crashing upon creating certain entities. All in all, Hammer has failed more often than it's worked, even rendering me unable to map for a couple weeks once until I found it doesn't like backward slashes in exe paths.
I really hope anybody can help me, and I hope I'm not violating any rules by asking a not-TF2-related question (well, technically, it's about Hammer and not a certain game... I think).
Greetings,
HashtagMC
