voxel-raycaster

Author	SHA1	Message	Date
mitchellhansen	10bc771807	MBP was having problems with out of bounds memory operations with the way the cam dir was handled. sf::vector3f -> float3 and while accessign the Zth element. I'm assuming it was because of some weird backend stuff regarding that gentypeOdds are actually gentypeOdds + 1. Converted write_imagef's to write_imageui's though I don't think that really helps anything. Fixed the bottom half of the screen getting cut off. View matrix import error. Fixed problem the MBP had with negative values during device init, that was a weird one.	8 years ago
MitchellHansen	4e96985104	added lighting, stole a terrain generator and ported it.	8 years ago
MitchellHansen	e1080baab0	opencl has no rand, SO rand method to make fog a little better	8 years ago
MitchellHansen	6f5d2b2f6f	Changed to non branching algo, sped up a good 30-50 ms at the current max ray dist. Also changed bounds checking a little, not sure if it's faster	8 years ago
MitchellHansen	160756186d	mouse and camera movement work, stress testing. Can actually handle an impressive amount of resolution and voxel space for 0 optimization!	8 years ago
MitchellHansen	f487895f9f	that was a pain. Got it working on windows again. MSVC was being really picky about a few errors. Good thing though, I'm not really sure why clang + osx let me be that lax with memory	8 years ago