Bas van der Graaff

A problem i stumbled across while using jit.gl.model is that the texture looks different when turning matrixoutput on. Looks somewhat like the texture is only rotated or wrapped, but I'm not sure how exactly. Is there a way to either fix this, or make a workaround (do a 2d operation on the texture or texture planes? As I'll be using logos and text it's essential that the texture is displayed correctly.

I've been wanting to add some jit.gl.models to my 3d scenes. The app I've built is a modular effects stacker. I do understand that the matrixoutput of jit.gl.gridshape, jit.gl.nurbs, jit.gl.videoplane is very different from the matrixoutput of jit.gl.model. That's why i don't use the same effects for both of them. But it would be nice to have some effects for the models as well, so that's why i want to use the matrixoutput attribute.

texture-displays-differently-when-using-matrixoutput-on-jit-gl-model

Quote: Bas van der Graaff wrote on Tue, 01 April 2008 17:22

----------------------------------------------------

> A problem i stumbled across while using jit.gl.model is that the texture looks different when turning matrixoutput on.

I can reproduce. I guess this classifies as a bug?

Quote: Bas van der Graaff wrote on Tue, 01 April 2008 17:22
----------------------------------------------------
> Hi Board,
>
> A problem i stumbled across while using jit.gl.model is that the texture looks different when turning matrixoutput on. 

But besides fixing this bug, it would be cool if we could access jit.gl.models internal jit.gl.texture objects, like sendinput for jit.gl.slab...

I can reproduce as well...
But besides fixing this bug, it would be cool if we could access jit.gl.models internal jit.gl.texture objects, like sendinput for jit.gl.slab...

Okay, I got a little bit further. Using a separate texture will al least allow the texture to look the same regardless of the matrixoutput attribute. Downside of this approach is that I now need to get the texture file from the .obj file. Also, only one group is drawn, namely the last one to enter jit.gl.mesh. Using a poly~ should solve this, but i think it's a lot of work just to get something like this working.

Texture displays differently when using matrixoutput on jit.gl.model