Hi Robert, At the moment I'm not ready to make a submission. No one else has noticed this problem so I wouldn't hold up a new osg release. I have the source code so I can easily build osgParticle that works for my usage. If you would like something for 2.8.1 I can easily modify the code to take an environment variable or compiler option. Let me know if this is what you want.
I would still like to know more about FlightGear's usage. Eventually, I think we will either come up with a way in FlightGear to use the earlier ModularEmitter code or, for 2.9 or later, add a way to select the mode in ModularEmitter. If we go back to the earlier code we will certainly need to keep watch on the mailing list for anyone having trouble. ---- Tom Jolley > -----Original Message----- > From: Robert Osfield [mailto:[email protected]] > > Hi Tom, Tim et. al, > > I think what we probably need is a bit of revamp internally > in osgParticle to properly support double precision > positioning of the particle system and emitter. Exactly how > this should look I can't say right now, I'd need to sit down > and work out the current osgParticle class structure and see > how it might all fit together. I haven't looked at it > closely recently so I don't recall the details off the top of my head. > > Longer term osgParticle could do with be rewritten to use > shaders + point sprites rather than the CPU centric > implementation that we have right now. Perhaps this could be > done at the same time as the above. > > Short term we are stuck with an fix that works for FlightGear > and perhaps other apps that use osgParticle in similar ways, > but breaks other apps that use osgParticle in other ways. > Reverting to an older rev will just break things for > FlightGear and other similar apps. So we are between a rock > and hard place. > > Perhaps a short term solution would be to have an compile > option or better still a variable that can control which > behave is selected internally. For OSG-2.8.1 we need to > stick to ABI compatibility, so the compile option would be > the only way, but which should be the default.... perhaps an > env var could be used to toggle the variable. > > Do one of you guys want to come up with an interim solutions? > > Robert. > _______________________________________________ > osg-users mailing list > [email protected] > http://lists.openscenegraph.org/listinfo.cgi/osg-users-opensce > negraph.org > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
