Im loading a bitmap from a file as unsigned char array. Then I convert it to floats, do some math with it, and then put it back into another bitmap.
Im using Visual C++ 2010 express, and when Im running the programm in Debugmode it works fine. But as soon as I put it into Releasemode, the output is only a completly black bitmap.
Does anyone have a clue what could cause this? I dont get any warnings at all (with high warninglevel).
That should be everything that is important:
struct f3{
float r,g,b;
};
unsigned char * shadowMapImage;
f3 *shadowMap;
shadowMapImage = new unsigned char[mapWidth*mapWidth*3];
shadowMap = new f3[mapWidth*mapWidth*3];
LoadFromFile(); // Fills shadowMapImage with fread(shadowMapImage, 1, imageSize, filePtr);
WIthout any code to see I'm guessing that data structure or variable might not be initialized the right way or might not be initialized at all or that your conversion between unsigend char and floats is not ok. Could you post the code-snippet?
shadowMap = new f3[mapWidth*mapWidth*3];
shouldn't that be: shadowMap = new f3[mapWidth*mapWidth];
since f3 has the rgb already in it?
Also your second loop should probably read:
shadowMapImage[k] = (unsigned char)shadowMap[(z*mapWidth+x)].r;
shadowMapImage[k+1] = (unsigned char)shadowMap[(z*mapWidth+x)].g;
shadowMapImage[k+2] = (unsigned char)shadowMap[(z*mapWidth+x)].b;
None-the-less I still don't see that accounting for the errors. As was pointed out, usually converting from a float to an unsigned char you need to multiply by 255, and divide by 255 when going from unsigned char to float, as usually the float's are treated as normalized. You did neither of these but it still seemed to work in debug mode so perhaps this wasn't necessary in your case. Its hard to say really given what little code is there.
The only thing the Mathfunction really does is change the values in shadowMapImage with some +-. There really is no more code to be concerned about.
I dont normalize the floats because I need them as they are, from 0 to 255.
My first guess would also have been a normalization-issue, but if that is not the cause I guess the best course of action is to narrow down the point of failure. Is the image loaded correctly? Does it look ok, if you save it without any modification?
In situations like this you should try to come up with a minimal program that still shows the problem. In the process of simplifying your program, you are likely to figure out what the problem was. Even if you don't, you'll have something to post here so we can test it ourselves.
I think I got the problem. Its kinda wierd.
It HAD to do with the Mathfunction, but why it worked in debugging mode is a miracle.
Actually, the numbers were calculated invert (means 255 was 0, 0 was 255). But where should have been 0, there was 211. I cant tell why.
Breaking it into smaller pieces really helped, thanks!
