Re: [osg-users] Problem reading Openflight file switch node

So I debugged this and realised that before the second elements where added to the ValueList the lists were cleared and reset to empty lists. So when the next element is added the list is set to the default value which is true. It appears in subsequent rounds of adding new children to the list

Re: [osg-users] Problem reading Openflight file switch node

Just tried it on Centos 6.5 (x86) running OpenSceneGraph 3.2.1 and I got the expected behaviour with the first three elements of the set are different from the second three elements in the set. With OpenSceneGraph 3.4.0 on the same machine I get the erroneous values of all 1.

Re: [osg-users] Problem reading Openflight file switch node

On 18 December 2015 at 01:14, Tony Vasile wrote: > The problem is in 3.4.0. Our original models came from Creator and were > developed years ago. I built OpenSceneGraph 3.4.0 straight out of the > source and the two osgSim serializers were built. If you look at my example >

Re: [osg-users] Problem reading Openflight file switch node

I first found the problem on Centos 6 x86_64. The problem is there on OSX 10.11 in OpenSceneGraph 3.5.0 but not in 3.2.0 on the same platform. I have done a diff on the OpenFlight plugin directory but nothing sticks out. Tony V -- Read this topic online

Re: [osg-users] Problem reading Openflight file switch node

On 18 December 2015 at 09:08, Tony Vasile wrote: > I first found the problem on Centos 6 x86_64. Which versions of OSG have you tested under Centos? > The problem is there on OSX 10.11 in OpenSceneGraph 3.5.0 but not in 3.2.0 > on the same platform. I have done a diff on

Re: [osg-users] Problem reading Openflight file switch node

On 18 December 2015 at 10:34, Tony Vasile wrote: > Just tried it on Centos 6.5 (x86) running OpenSceneGraph 3.2.1 and I got > the expected behaviour with the first three elements of the set are > different from the second three elements in the set. With OpenSceneGraph > 3.4.0

Re: [osg-users] Problem reading Openflight file switch node

Hi Tony, I'm converting my models to osgb, and it seems the switch masks are working. Are you maybe saving to another format? Cheers Sebastian The problem is in 3.4.0. Our original models came from Creator and were developed years ago. I built OpenSceneGraph 3.4.0 straight out of the source

Re: [osg-users] Problem reading Openflight file switch node

Who ever did the original model had one version of the geometry when the antenna was rotating and another version of the geometry was the stationary. When I try this on OSG 3.4.0 I see both versions of the geometry out of phase with one another. Tony V

Re: [osg-users] Problem reading Openflight file switch node

Hi Robert, I have been using osgconv. Isn't that the same thing as opening it up with the OpenFlight plugin and writing the file straight out? Do you mean to use the osgPlugins directory from OpenSceneGraph-3.2.1 in the source tree for OpenSceneGraph 3.4.0? I tried just a symbolic to the OSG

Re: [osg-users] Problem reading Openflight file switch node

On 18 December 2015 at 11:41, Tony Vasile wrote: > Hi Robert, > I have been using osgconv. Isn't that the same thing as opening it up > with the OpenFlight plugin and writing the file straight out? > If it were the same I would have suggested it. osgconv runs various

Re: [osg-users] Problem reading Openflight file switch node

Hi Tony, try to save to osgt, osgb and osgx, and check if the problem persists. IIRC the serializers for those formats are different from the osg, which would narrow down the bug. Cheers Sebastian Hi Sebastian, I just saving the output to osg. Tony V

Re: [osg-users] Problem reading Openflight file switch node

Hi, Our tool is called Remo 3D and is free to use as read-only for purposes like this: http://www.remograph.com/download.php From what I can see, the model is fine - apart from the medium LOD containing an extra small radar geometry, but that probably has nothing to do with your problem.

Re: [osg-users] Problem reading Openflight file switch node

The problem is in 3.4.0. Our original models came from Creator and were developed years ago. I built OpenSceneGraph 3.4.0 straight out of the source and the two osgSim serializers were built. If you look at my example snippets from 3.4.0 and 3.2.0 on 3.4.0 I am getting the switch values all set

Re: [osg-users] Problem reading Openflight file switch node

Can you provide a simple model to reproduce the bug? If you're not able to debug your build, your plugin might not fit the build. I've used the Openflight plugin for quite a while but haven't experienced problems with the switch masks. Cheers Sebastian -- Diese Nachricht wurde von meinem Android

Re: [osg-users] Problem reading Openflight file switch node

On 13 December 2015 at 12:44, Sebastian Messerschmidt < sebastian.messerschm...@gmx.de> wrote: > Can you provide a simple model to reproduce the bug? > Tony attached a radar_flt.txt file to his first post in this thread, this needs to be renamed to radar.flt. I don't have Creator so have no way

Re: [osg-users] Problem reading Openflight file switch node

Hi Robert, On 13 December 2015 at 12:44, Sebastian Messerschmidt > wrote: Can you provide a simple model to reproduce the bug? Tony attached a radar_flt.txt file to his first post in this thread, this needs to be

Re: [osg-users] Problem reading Openflight file switch node

Is there anyway to debug this to see what is going wrong? I have tried to step through the Reader but I can't seem to get into plugin. I'm sure the fix is simple mistranslation. The code works when the sets only contain one option but is broken when the options have more than one element in

Re: [osg-users] Problem reading Openflight file switch node

Just tried this on 3.2.0 on my MacBook and got what I believe is the correct result. Code: osgSim::MultiSwitch { name "articSw2" nodeMask 0x cullingActive TRUE description "featureId(artic0)"

[osg-users] Problem reading Openflight file switch node

We are having what we think is a problem with reading our OpenFlight file. We have a switch which has two groups of nodes under it. The first three pieces of geometry are supposed to be visible when the switch is in position 0 and the second three are supposed to visible when the switch is in