Horde3D

I was told that with optimization enabled Horde3D crashes, when I looked into the problem, I found out that valgrind does not show any suspicious memory errors (well, 2-3 things that might cause problems but don't look as if they contributed to the problem).

I so far could track the problem down to a crash in PipelineResource::releaseRenderTargets() (somewhere releaseRenderBuffer() there it crashes), which happens because the framebuffer created is reported as incomplete by OpenGL ("if( status != GL_FRAMEBUFFER_COMPLETE_EXT ) return 0;" fails).

Just wanted to leave a notice here, I'm probably now going through the warnings GCC outputs with -Wall -Wextra, maybe sth there solves it.

Fixed as of
http://bitbucket.org/mgottschlag/horde3 ... de49a0d9d/

Please review and apply.

This fixes at least one bug in utImage.cpp (ambiguous else used) and critical pointer conversions in utMath.h. Possibly fixes more.

Btw: Is there a bug in utImage.cpp:2950ff? read_next_pixel seems always to be 1?


Fixed repositories:
http://bitbucket.org/mgottschlag/horde3dext
http://bitbucket.org/mgottschlag/horde3d

Thanks a lot. The initialization warnings was something I wanted to fix for a long time. I merged your code with the public trunk!