I have forwarded to users as requested.

In particular it "appears" to be this line 96
P->setPosition(P->getPosition() * worldToPs);

If I remove this line the problem goes away... (work in progress...)

----- Original Message ----- 
From: "Robert Osfield" <[email protected]>
To: "OpenSceneGraph Submissions" <[email protected]>
Sent: Thursday, May 21, 2009 8:48 AM
Subject: Re: [osg-submissions] Something fishy with ModularEmitter.cpp 8881


Hi James,

There must be a difference in the way you are using osgParticle from
what the examples are doing that is triggering this problem as the
examples didn't break with this change (r8881) from Tim Moore.

Tim's submission included other modifications to osgParticle, these
are also a topic for current discussion on another thread.

So it looks like Tim's changes fix some issues, but introduce new
ones.  The final solution may well be to refactor the code in
osgParticle for tracking coordinate systems.  Unfortunately I'm not an
expert on osgParticle so am very much in the same boat as yourself and
others in terms of having to read the code to understand how it works
- this means I can't just pinpoint a problem and come up with a quick
solution.

Could join the existing osg-users thread on problems in osgParticle or
start a new one, so the discussion can go on with a wider coverage,
osg-submissions really is just for submissions.

Cheers,
Robert.

On Thu, May 21, 2009 at 3:37 AM, James Killian
<[email protected]> wrote:
> After a solid week of continuous builds I have finally found the code
change
> which breaks are game. See picture.
>
> In this picture, before build 8881 (Which is only the ModularEmitter
> change)... I shoot the upper ship and the particals are only emitted from
> that position... With the 8881 change the particals are being emitted from
> both that position and the position of the ship below. I was hoping this
> information may be enough to investigate the 8881 change submitted to see
if
> it is sound... I'm going to review our code stress from the game end and
see
> if perhaps there is something we are doing wrong as well. Now that we have
> narrowed it down, hopefully the cause will reveal itself very soon.
>
>
> _______________________________________________
> osg-submissions mailing list
> [email protected]
>
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org
>
>
_______________________________________________
osg-submissions mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-submissions-openscenegraph.org

_______________________________________________
osg-users mailing list
[email protected]
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Reply via email to