comments inline... On Fri, 2003-10-31 at 15:12, Justin Couch wrote: > Kevin wrote: > > > It think that VRML only supports the solid attribute in IndexedFaceSets > > is my problem. However, I think I am using a X3D v3.0 document (one of > > the examples on the x3d site), so theoretically I should have this > > support under all geometry. However, when I tried it, I received a > > parse error saying it was an invalid attribute. > > That's our fault. The spec only added this capability in as a > last-minute item and we haven't had a chance to update the code > internally to support the field. The infrastructure is already in place > to support it (ie all our geometry internally has methods to check on > getting the two-sided-lighting state), but we haven't done the field > handling. Shouldn't be that difficult to do, but we're in a > code-lockdown in preparation for the next milestone release. I'll have a > chat here with the guys to see if it's something we can fit in (even if > it is just to read the field and ignore for now)
Cool...that sounds great... > > > 2. I am misusing the loader somehow. I noticed a vrml97Only flag on > > the BaseLoader that is inherited by the X3DLoader. However, I can't get > > to this flag in my app because it is a protected attribute. I would > > have thought that the X3DLoader would set this to false and render all > > X3D content??? > > X3D is not VRML. If you selected the X3D loader, it will _only_ load X3D > content. Despite visual similarities, X3D and VRML are significantly > different internally. If you want a loader to be able to work with both > formats, use the Web3DLoader. Right, I am using the X3DLoader to load only X3D files. That is exactly what I want. Thanks for the clarification between VRML and X3D though...similar on the outside, not so on the inside. > > > Sorry to be a dimwit...but did this come from the X3DLoader > > implementation? > > No, from the internals of our rendering system. Probably not much use to > you if you're using X3D/VRML directly, but if you're doing your own > coding for Java3D content, that's an example of how to do it. Yes, I finally grabbed an old snapshot of the code (M5) and found the snippet of code. > > > I haven't been able to track down the current source on the site yet. > > As a rule, the dev releases do not zip up the source. That's because it > is typically just a cut of the code from one of our development machines > (usually mine). There's a lot of extra stuff there - stuff which doesn't > compile, or not in the formal compilation list for release etc. So to > get the current source, you need to grab it from CVS. Details are here: > > http://www.xj3d.org/cvs.html Cool...I'll probably try to grab the source from CVS and try to get it implemented myself just so I can finish my prototype. thanks for all of the help...much appreciated. kddubb =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff JAVA3D-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
