AtlasGenerateTextureTOCFromLargeJPEG bug?

#1 Hi,

Been experimenting some more. Still have the problem, everything is blue.

But first of all, *** notice to Ben ***, in order to get the image to match the terrain mesh I have to use a flipped mesh in L3DT as mentioned in the TDN Atlas2 article. That article says to notify you if that is the case, so you are hereby notified :-)

Next - I made a simple terrain so that I could match up the shadows and features easily. See screenshot.

[IMG]http://img172.imageshack.us/img172/1683/screen1qo1.th.jpg[/IMG]

That is how I knew I had to use the flipped mesh to generate the textures in the end. However there is still a problem. Although the shadows match the features now, the numbers I drew on the texture show back to front, as if I had mirrored the texture. I haven't mirrored the texture as it is not symmetrical, and mirroring it would throw out the shadows.

The question is, is this part of the problem with the textures being blue? Is the colour problem also causing the mirroring of the numbers? Or is it some other bug?

Thanks,

Dave.

#2 That "icy blue" color is a sure sign the red and blue channels are being flipped. So the real question becomes what is causing it, and would your problem be fixed by the latest revisions Ben made to the Atlast code in the last few days (and whether that code is in CVS yet).

#3 Hi Ryan,

Thanks for that. I checked CVS this morning (GMT) after spotting that small post about RGB channels, but there were no updates. Glad to hear it sounds like the same problem though. It makes it marginally less likely it's something I'm doing :-)

Cheers,

Dave.

#4 Not out yet, I've been pretty busy with 1.5 release tasks (Matt Fairfax is technically driving that but somehow I ended up getting tasked with stuff...d'oh! :P).

Will try to talk to Brian tomorrow about it, though. Thanks for making noise about this - keeps me honest.

#5 Thanks Ben, I can manage OK now that the blender terrain is working for me. This was a side trip whilst trying to figure out what I was doing wrong with that.

Be nice to see what a unique landscape with high def texture looks like sometime though :-)

Cheers,

Dave.

#6 Just wondering if theres any updates on this, Im getting the exact same error. I updated my Atlas directory from CVS a few hours ago, and still got the blue terrain. Is there anything else I should update?
(I dont want to start from a clean build if I can avoid it, ive made quite a few engine changes)
JS

#7 My AtlasGenerateTextureTOCFromLargeJPEG function works fine, but I'm generating textures from Vue5 rather than L3DT. I'll try a texture from L3DT later tonight. My guess is it's something with L3DT or the JPEG file it's generating.

#8 Thanks Tim, It would help if I could narrow down the bug to L3dt. Its possible theres a setting somewhere that should be altered.
JS

#9 It seems that I pulled down the CVS update incorrectly, I tried with the latest CVS head, and my terrain is fine. Sorry for the waste of time.
JS

#10 I couldn't find any problems with L3DT's jpegs, so I'm glad you found the problem.