Map Compiler Runs but no .bsp

Reece202 · 11-29-2010, 09:35 AM

I'm tryint to compile the first version of my map, and instead of getting a .bps, I get a .log with the following content:

Code:

2 threads
reading c:\program files (x86)\steam\steamapps\sourcemods\fortressforever\maps\ff_cargo_a1.bsp
Error opening c:\program files (x86)\steam\steamapps\sourcemods\fortressforever\maps\ff_cargo_a1.bsp


Could not find lights.rad in lights.rad.
Trying VRAD BIN directory instead...
Warning: Couldn't open texlight file c:\program files (x86)\steam\steamapps\reiscool\sourcesdk\bin\orangebox\bin\lights.rad.
Loading c:\program files (x86)\steam\steamapps\sourcemods\fortressforever\maps\ff_cargo_a1.bsp
Error opening c:\program files (x86)\steam\steamapps\sourcemods\fortressforever\maps\ff_cargo_a1.bsp

What am I supposed to do here?

Bridget · 11-29-2010, 11:32 AM

Why is it looking in orangebox bin folders for an ep1 engine mod? Did you somehow configure Fortress Forever for use in hammer under the orangebox or something? Lol, I dunno.

zE · 11-29-2010, 05:22 PM

having same newb bug, = full bright map

Could not find lights.rad in lights.rad.
Trying VRAD BIN directory instead...
Warning: Couldn't open texlight file D:\Steam\steamapps\ruialmeidasoares@hotmail.com\so urcesdk\bin\ep1\bin\lights.rad.

**Crazycarl** · 11-29-2010, 05:22 PM

If that's the entirety of your log, it means you aren't running vbsp, which is what creates a bsp file in the first place.

zE, the lights.rad error is not a problem. Post everything in the compile log.

Reece202 · 11-29-2010, 08:21 PM

Quote:

having same newb bug, = full bright map

I'd like to play test it before I work out the lighting

Quote:

Post everything in the compile log.

That is everything in the log

I switched everything over to the ep1 folders as per Bridget's post and I still get the same thing.

**Crazycarl** · 11-29-2010, 10:08 PM

That's output from vrad. You need to run vbsp, then vvis, then vrad last, if you want lighting.

Reece202 · 11-29-2010, 11:27 PM

Well, I put in the same parameters you did, but I still didn't get anything. I think that this has something to do with my hammer set-up for FF because I don't get this problem with anything else. The log just shows the vrad thing.

11-29-2010, 05:22 PM	#4
Crazycarl D&A Member Wiki Team Fortress Forever Staff Join Date: Apr 2007 Posts Rated Helpful 31 Times	If that's the entirety of your log, it means you aren't running vbsp, which is what creates a bsp file in the first place. zE, the lights.rad error is not a problem. Post everything in the compile log. Last edited by Crazycarl; 11-29-2010 at 05:24 PM.

11-29-2010, 11:32 AM	#2
Bridget Banned Join Date: Sep 2008 Class/Position: Soldier Gametype: AVD Affiliations: TALOS Posts Rated Helpful 5 Times	Why is it looking in orangebox bin folders for an ep1 engine mod? Did you somehow configure Fortress Forever for use in hammer under the orangebox or something? Lol, I dunno.

11-29-2010, 05:22 PM	#3
zE Pew pew ze beams Join Date: Jan 2008 Gametype: Gathers Affiliations: pew pew Posts Rated Helpful 11 Times	having same newb bug, = full bright map Could not find lights.rad in lights.rad. Trying VRAD BIN directory instead... Warning: Couldn't open texlight file D:\Steam\steamapps\ruialmeidasoares@hotmail.com\so urcesdk\bin\ep1\bin\lights.rad.

11-29-2010, 10:08 PM	#6
Crazycarl D&A Member Wiki Team Fortress Forever Staff Join Date: Apr 2007 Posts Rated Helpful 31 Times	That's output from vrad. You need to run vbsp, then vvis, then vrad last, if you want lighting.

11-29-2010, 11:27 PM	#7
Reece202 Join Date: Nov 2010 Class/Position: Civilian Courrier Gametype: Territorial Control Affiliations: Source SDK Posts Rated Helpful 0 Times	Well, I put in the same parameters you did, but I still didn't get anything. I think that this has something to do with my hammer set-up for FF because I don't get this problem with anything else. The log just shows the vrad thing.

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)