That moment when you go to build the BSP for a map for the first time in tool, and it compiles with no errors what so ever.

Then you sit there stunned for a few minutes and recompile it just to make sure that there wasn't so sort of mistake.

k

no, I figured it out for myself.

But I mean, I've made probably more than 100 BSP's in the last few years, that's the first time its ever happened.
Edited by Jobalisk on Dec 12, 2015 at 02:16 PM

Persistence

congratulations. Now if you excuse me I need to get back to my own programming ventures. Java isn't going to write itself.
Edited by Jobalisk on Dec 13, 2015 at 04:09 AM

It's Senor Martillo Grande El Supremo Flanker now.

Persistence has a part to play in a rewarding compile, however I (and I am sure popeak and stunt man agree as well) believe a truly successful compile is the result of a complete understanding of how halo's engine interprets and uses geometry.

Once you have garnered such a knowledge you will be able to manipulate halo in ways you will not believe.

I thought it was Sergeant of the Master Sergeants Most Important Person of Extreme Sergeants to the Max! Senor Martillo Grande El Supremo Primo Flanker?

Hey Its not all about me.

damn it Flanker, stap stealin ma thredz

what? Why does Sergeant of the Master Sergeants Most Important Person of Extreme Sergeants to the Max! Senor Martillo Grande El Supremo Primo Flanker get all the credit? I helped too!

Tru dat. But srsly it's not all about me.


It's about an idea bigger than me, you or any one else for that matter.


Its about a collective community which contributes to each and every need of its qualified an aspiring members.


A hive mind.

<Sheds tear> beautiful!

I guess you could say that, but I'd dumb it down and just state that if you use good modeling practices and model with precision you should be golden. Your models will export no-problemo if you use Editable Poly and routinely check for open edges using Border sub-selection. Also make heavy use of the "Edit Triangulation" feature in Polygon sub-selection mode to check for overlapping edges whenever creating concave polies, or after welding vertices. X/Y/Z alignment of vertices is also highly recommended to avoid phantom BSP's and co-planars (caused by not-completely-flat surfaces, usually due to one or two vertices being slightly "off").

Personally I'm a huge fan of the feeling near the end of the geometry debug process when there are only one or two measly little errors left to fix :P It's very rare I get an error-free export to .jms, but that's probably due to the increasing complexity of the stuff I'm trying to model more than modeling practices...