EDIT: I'm getting a more important problem, i've got a "template" for compiling maps, i've set it up properly, and it compiles, but when running the map on game, it has no lightning, i don't know wich of the compiling tools is the one to handle the lights, so i have no idea how to fix it(and if i knew wich one was, i would still don't know how to fix it ), if anyone can help me, i would apreciate.
I didn't know where to put this, but as it happens with Trenchbroom 2 specifically, it's here. This may be a noob/stupid question(and probably is) , but every time i try to launch my map to test it in trenchbroom 2, i get this error: "Couldn't load pics/colormap.pcx", it happens with the normal q2 executable, and with KMQuake2 too. i don't know what to do, so i could use some help...
Last Edit: Dec 28, 2016 17:35:57 GMT -5 by ranhcase
Post by knightmare on Dec 30, 2016 17:15:16 GMT -5
Did you check the output from the compiling process? Watch to see if it says LEAKED at any point. If a map leaks in the bsp stage, the vis and rad (radiosity) stages won't run, and you get a fullbright map. There should be a .lin file generated in the same folder as the .map you are compiling. The editor should support loading and showing that, which will show you where the leak is.
Also, the "Couldn't load pics/colormap.pcx" is likely due to Q2 being launched in the wrong path, and it can't find the pak files.
Next you'll need to write a .bat or .cmd file to call the compilers for your map. Here's an example: D:\QERadiant\\kmqbsp3 -chop 1024 -moddir d:\quake2\kmq2_test D:\Quake2\kmq2_test\maps\kmq2example1.map D:\QERadiant\\qvis3 -threads 4 D:\Quake2\kmq2_test\maps\kmq2example1.map D:\QERadiant\\arghrad -threads 4 -bounce 8 -chop 128 -chopsky 1024 -chopcurve 128 -gamedir d:\quake2\baseq2 -moddir d:\quake2\kmq2_test D:\Quake2\kmq2_test\maps\kmq2example1.map pause
I have Quake2 installed in D:\Quake2, and the map compilers are in D:\QERadiant. I'm also using the "-threads 4" parameter for the VIS and RAD stages because I have a quad-core CPU. The "pause" command at the end leaves the window open so you can check the output for any error or warning messages.
Last Edit: Jan 5, 2017 22:23:20 GMT -5 by knightmare