Solution 1: Don't automatically run the map after compiling.That just baffles me... why shouldn't you playtest your map after a compile? Compiling from Hammer (as is my personal preference) combined with Steam gives me no single error...
Solution 2: Don't even think of automatically run the map after compiling.
People should hand their parts in without bugs.Impossible. There will always be bugs (or at least flaws).
Good idea with ending it in 10 days. Now it will finnaly be completed.Well, completed... I wouldn't say so. I've played trough a small part of it now and I've seen several things that could use some fixing or tweaking.
Or, you could RAISE the maximum viewable distance, but that would increase r_speeds.Incorrect. Polygons beyond the maximum viewable distance are being rendered. They're just not visible.
Tryin to make it all complicated..You'll soon see it is quite complicated...
And software runs faster and that's that.Am I allowed to laugh? When you don't have a 3D-card, or a very old one, it's probably faster. But nowadays we have raw power in our GPU's so to state 'software runs faster' is nonsense. Software mode is significantly slower compared to OpenGL when you have a decent video card. So it's not OpenGL that's slow, it's your card that's slow...