Vega Strike Code

Here's about 1/3 of all the warnings from cmake squashed. WARNING: There were/are many BUGS which I could not properly fix; namely variables that were declared without initialization, then initialize inside some conditionals or cases but not others, and subsequently used. In 90% of the cases I initialized them to zero, or to 0.0f, or to enum Ok, etceteras; but this NEEDS attention from someone more familiar with the code. Check the diffs. Many files like that. Warnings from the collision library were made to shut up with a pragma. They rely on sizeof(float)==sizeof(int) and (int&)float(0.0f)==int(0), which happens to be true, currently, with AMD athlons and compatible cpu's. Terribly incorrect library, tho.

Removed obsolete cubemap texture transfer debugging messages.

remove needless debugging printouts

Fixed a typo in my last mesher commit, and made some vs_cubemap_gen progress.

I believe I've squashed a little bug in mesher. See Ticket #16.

A bit more work on vs_cubemap_gen.

Commiting this evening's progress on vs_cubemap_gen before I fall asleep and my head hits the delete key.

Committed the beginnings of "vs_cubemap_gen", a tool that will produce correctly filtered, seamless, high quality dds cubemaps; better than ATI's CubeMapGen by a mile.

Bugfixing highend.fp:
- wrappers and macros for easier gamma control
- degamma/regamma fixes:
* degamma-ing of texture input must happen right at sampling, almost any operation will be nonlinear
* regamma-ing output must happen as absolute last step (even after cloaking and alpha application)
- GAR fix: eye vector isn't always normalized, and GAR needs it normalized.

Implemented a system of folders under /techniques. The work is neither complete nor correct nor yet in use. I'm committing it for feedback and peer review.
Essentially, the numbered folders contain shaders and techniques for a spectrum of hardware capabilities. As you can see from the opaque_onetex.technique I implemented as example, the technique has the same in all the folders, --or most, anyways. The user setting for shader in vssetup determines the folder; the xmesh determines the name of the technique. There are also 3 folders for STAGE, meaning the render stage: FAR = planets and stars; MEDIUM = ships and stations and asteroids; NEAR is the cockpit. Shaders and techniques that are common across stages are in the numbered folders under /techniques. Stage-specific shaders and techniques are in the number folders under the appropriate stage folders. Thus, fireglass is in the MEDIUM stage folder, under folder 6_ps4.0, as it applies only to ships and stations. An atmosphere shader would be under the FAR tree. Note that there can only be one shader for all blended applications under each stage, for performance reasons. Thus "fireglass", which currently only renders glass, but will soon also apply to engine exhausts, etc.