openvrml-develop

[openvrml-develop] incompatibility between older and newer version of OpenVRML?

[<jo...@pl...>]

We have some vrml models=2E Before we used the older OpenVRML library =

(don=B4t remember
which version it was exactly)=2Cat least we had to change arVrml97* calls=
 =

to arVrml*
calls) Now I=B4m using the newest one=2E

What happens now is that some models are shown ok=2E But with some of =

them my texture get a darker colour and it seems that some light is =

turned off=2E But in my code nothing of all that=2E Has some syntax chang=
ed =

between versions of OpenVRML or are there some incompatibilies=3F I have =

read about the problem with CONVEX=2C which had to be changed to ccw=2E A=
re =

there some more syntax changes=3F

Re: [openvrml-develop] incompatibility between older and newer version of OpenVRML?

[Braden M. <br...@en...>]

On Mon, 2005-11-21 at 09:02 +0100, jo...@pl... wrote:
> We have some vrml models. Before we used the older OpenVRML library 
> (don´t remember
> which version it was exactly),at least we had to change arVrml97* calls 
> to arVrml*
> calls) Now I´m using the newest one.

ar* isn't part of OpenVRML's API. Presumably it's something else you're
using which in turn depends on OpenVRML.

> What happens now is that some models are shown ok. But with some of 
> them my texture get a darker colour and it seems that some light is 
> turned off. But in my code nothing of all that. Has some syntax changed 
> between versions of OpenVRML or are there some incompatibilies? I have 
> read about the problem with CONVEX, which had to be changed to ccw. Are 
> there some more syntax changes?

You'd have to narrow the parameters of the question before I could
provide you with a useful response. Yes, OpenVRML has changed a lot over
the last several years. Bugs have been fixed, and other bugs have been
added.

OpenVRML attempts to implement the VRML97 spec; so there is a standard
of correctness that applies in most cases. If you're not sure whether
something is working correctly, please post a test case (the simpler the
better) and I can provide you with some feedback as to whether the
problem is with OpenVRML or your model. If you're already convinced
OpenVRML's doing something wrong, feel free to go ahead and file a bug
report.

PS: openvrml-develop permits posting only by subscribers in order to
curb spam. Please subscribe to the list if you intend to continue
posting.

-- 
Braden McDaniel                           e-mail: <br...@en...>
<http://endoframe.com>                    Jabber: <br...@ja...>