Jump to content

Home

Map-killing compile error


wedge2211

Recommended Posts

In the BSP process...

 

--- FixTJunctions ---

************ ERROR ************

MAX_ORIGINAL_EDGES

 

What does this mean, and how do I make it go away?! Whatever it is makes the BSP process fail entirely so there's no .prt file and the VIS process can't work, which gives me HOM every-freaking-where. Ugly!

Link to comment
Share on other sites

Wow, Wedge, you managed to find an error for which the Google is null. Bad luck indeed. Since Google was a wash, I'm really at a loss, but I can always prescribe the usual: try and get back to a state of .map-ness as it was at the time of your last successful compile. Have you got a decent .bak file lying around? Is there anything particularly suspect that you've added or subtracted from your map since your last working compile? Sorry, bro, I hate it for you.

Link to comment
Share on other sites

  • 2 weeks later...

The quick fix is a -notjunc flag in the BSP phase. However, this leaves the occasional sparkly here and there. ydnar thinks that this is a bad idea, and a better one is to reduce the number of brushes you have visible, or something like that. But I didn't want to lose brushes, so -notjunc was good enough for me.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...