Well this is a new one on me

I went to compile earlier and i had the maxvisdistance set in the VIS command line andi also had -wadinclude set and when the compile proccess gets to VIS it gets an error and that popup window with the option to END NOW but it compiles fine without the maxvisdistance command

Im pretty good with compile errors and their origins but i have not come across this one before

the compile log may be helpfull, if some window pops up a screenie/ written down Version of it would help. Its like asking a mechanic to fix your car only telling them it rattles. If they cant look at some it They'll never know.

I had the same problem, I was testing this out and it never worked for me...I want to know the solution for it. Same with that "bazooka only" really is the "bazooka or nade only" error/glitch and causes an extremely interesting error when the breakable is hit by a rocket.

There was no error log nor problem id number the VIS program just stops responding when it gets to the maxvisdistance command line and gives me the window that says END PROGRAM

I didnt need to set the vis distance because the map's r_speeds were fine without doing so so i dont need this to work for this map but for future reference i would like to know what caused the problem

I dont have a clue, thats a pretty strange one.