search

ValveSoftware / source-sdk-2013

The 2013 edition of the Source SDK
https://developer.valvesoftware.com/wiki/SDK2013_GettingStarted
Other
3.84k stars 2.02k forks source link

Weird behavior with newly compiled tools. (vbsp, vvis, vrad) #294

Open reepblue opened 10 years ago

reepblue commented 10 years ago

I usually use my own vbsp for removing default built cubemaps. After the last update, I decided to clone and make sure my mods are up to date. I also did the same with my compile tools.

Normally, I just replace the stock vbsp in the bin folder. However, when running it in Hammer or batch, the compiler prompt opens vbsp in a new command window, closes, and then the map runs through vbsp a second time; only this time it shows the progress in the wanted prompt.

The stock tools seem to work. But when you do replace it, then undo the replacement, it still bugged. Only deleting and re-validating the files makes it go back to normal. I also tried installing an older version of my vbsp and the same behavior happened.

This also happens with vrad, I can't tell you if vvis does this because the launcher will not compile for me. Any idea if this can be fixed in the project properties somehow?

neico commented 10 years ago

Maybe providing a diff of your changes might help tracking the issue down... Also do you mean both the .exe and .dll by replacement or only the .exe?

reepblue commented 10 years ago

I just edited with the vbsp.cpp with my nocubemap param like I did before. Vrad did the same bug with vanilla code. Also, I think it has to more do with the launcher being that only the dll compiled for vvis, and I used my vvis_dll with the stock launcher and it ran normally. Plus, vbsp only has an exe.