Cubes don't display properly if !(width == height == depth)

[mrdoob]

Cubes don't display properly if !(width == height == depth)

[mrdoob]

Link to online example or didn't happen ;)

[mrdoob]

Although I have the feeling the camera orthographic code is still wrong...

[timjb]

I have the same issue in an application I'm writing at the moment.

[timjb]

Here you go: http://timjb.github.com/three.js/examples/camera_orthographic.html

[mrdoob]

Crazy! I'll take a look tomorrow first thing.
Thanks for the link!

[alteredq]

I used ortho camera in normal mapping demo and there were no obvious issues.

Changing camera to perspective doesn't affect the bug.

Seems more like something to do with Cube mesh construction code, like some assumption doesn't hold any more with unequal sizes.

[mrdoob]

Fixed!
Sorry about that :$

[alteredq]

If all bugs were so easy ;)

I'm chasing some tricky ones already for few days :S

It seems at least some new problems are related to Chrome 10 switching on by default HW acceleration of 2d canvas.

[mrdoob]

Like visual glitches?

[alteredq]

Nope, like nothing showing at all when textures are generated from 2d canvas (affecting OBJ converter and AO minecraft demo).

At first I was confused and though these were texture coordinate problems (both demos accidentally happen to mess with UVs, on purpose), now I narrowed it down to problems with programatically generated canvas when using hw accelerated 2d canvas (even when there is no WebGL involved at all).

[mrdoob]

Well, you've got Henry's solution already ;)

[alteredq]

Glad at least something got explained. Still have some mysteries of our own ;)