www.jpct.net

jPCT - a 3d engine for Java => Support => Topic started by: ToddMcF2002 on May 17, 2007, 03:38:10 pm

Title: Can some Object3D Properties Be Exposed?
Post by: ToddMcF2002 on May 17, 2007, 03:38:10 pm

Namely Culling, Transparency, Blending, Texture?  Assuming of course you have this state.  If not I'll track them in a wrapper but I wanted to avoid abstracting the API in case anyone else wants to use this devkit app I'm making without stumbling on a bunch of custom wrappers.

 

Title: Re: Can some Object3D Properties Be Exposed?
Post by: EgonOlsen on May 18, 2007, 10:21:49 am

Culling and transparency are easy to expose. I'll do this on monday (hopefully). Blending is easy too, but pointless when using the OpenGL-renderers because it's valid for software mode only. Texture isn't possible because the method actually assigns the texture not to the object but to each polygon. And that assignment can be changed per polygon afterwards. So an Object3D can't return a texture that's valid for all its polygons or at least it doesn't know if it is.

Title: Re: Can some Object3D Properties Be Exposed?
Post by: ToddMcF2002 on May 18, 2007, 02:07:17 pm

Nice.  Culling and Transparency would be perfect.

Title: Re: Can some Object3D Properties Be Exposed?
Post by: EgonOlsen on May 21, 2007, 06:38:40 pm

There you go: http://www.jpct.net/download/beta/jpct.jar (http://www.jpct.net/download/beta/jpct.jar)

Title: Re: Can some Object3D Properties Be Exposed?
Post by: ToddMcF2002 on May 21, 2007, 08:33:12 pm

Thanks Egon.  I'll integrate it tonight on the devkit.  So obviously when I release the the source it will be dependent on that.

Title: Re: Can some Object3D Properties Be Exposed?
Post by: EgonOlsen on May 22, 2007, 06:44:31 pm

Quote from: ToddMcF2002 on May 21, 2007, 08:33:12 pm

So obviously when I release the the source it will be dependent on that.

That should be fine. I'll release that version (more or less) as 1.14 (maybe next week or so) and do the shadow mapping in 1.15 (as initially planned).