Getting started...

Engines, Libraries and Tools Xith3D Forums
#1

Hi all,

I’m just getting started with Xith3D and as I was running the examples from the “Getting started guide” I ran into some problems.

First of all in the MultitextureDemo I’m not getting the result I was hoping to see. The cross texture doesn’t show at all, and if I change the order of the textures only the cross is shown. Anyone know why this is happening?

My second problem is with the AseTest example. The program terminates and I get this stack trace:

com.xith3d.scenegraph.IllegalSceneGraphOperation: Illegal attempt to set the parent of this Node (name: '', com.xith3d.scenegraph.TransformGroup@e80842) as it already has a parent (existing parent name: 'Root', com.xith3d.scenegraph.TransformGroup@17653ae) and this would violate the directed acyclic graph constraint of the scenegraph. at com.xith3d.scenegraph.Node.setParent(Node.java:274) at com.xith3d.scenegraph.Group.addChild(Group.java:96) at org.xith3d.gsg.CrudeTank.loadGeom(CrudeTank.java:97) at org.xith3d.gsg.CrudeTank.<init>(CrudeTank.java:64) at org.xith3d.gsg.AseTest.<init>(AseTest.java:85) at org.xith3d.gsg.AseTest.main(AseTest.java:69) Exception in thread "main"

I’d appreciate if anyone have any idea of what might be wrong.

I also have a little question. Many of you probably know of NeHe’s OpenGL tutorials. Has anyone thought of “translating” them to Xith3D? What I mean by “translating” is of course to acchive the same thing with Xith3D, since Xith3D isn’t an OpenGL binding in itself.

Regards,

hesson

#2

Im having the same problem here with asetest example :-/

Maybe the last changes on the cvs affect the node structure and makes the example not to work?
Any help will be welcome!

#3

Ooops,

I am getting the same problem with AseTest, which I managed to post in a different thread.
Hopefully someone will find it.

I had no trouble with the multiple texture stuff… not sure what went wrong there.

#4

sorry guys, that tutorial has been broken more than it has been working. This is due to non-backward compatible changes in the API, I assure you it used to work :slight_smile:

Fixing it is easy, I guess I should get of my backside and do it.

Will.