[osg-users] Problems porting from osg-3.4.0 to osg-3.6.0

[Robert Osfield]

Hi Harman,

The new code looks OK to me.   Can't say anything more about the
issues you are having though as you don't provide any specifics.  If
you can keep VTP compiling against new and older versions of the OSG
for a while then you could possibly put some debug output on bits of
code that you are suspicious of and see what values both versions of
the OSG are generating, or create a small test program that
illustrates the usage case that you think might be a problems and so
similar testing.

If it does turn out there is change in behaviour then the later
approach would be helpful for others to test things out to see what
might be going on.  If there is bug on 3.6.x then we can fix it and
make sure it's part of the next stable point release.

Cheers,
Robert.
On Thu, 4 Oct 2018 at 14:31, Herman Varma <hermanvarma at eastlink.ca> wrote:
>
> Hi,
>
>
> I have upgraded the vtp code to osg 3.6.3
> Everything compiled and linked properly. However I still have some execution problems.
>
> I just want to check if  the code below is coded properly
>
> FQuat TransformExtension::GetOrient() const
> {
>         const osg::Matrix &xform = m_pTransform->getMatrix();
>         osg::Quat q;
>
> //      xform.get(q);
> // Replacing xform.get(q)
> // with
>         q = xform.getRotate();
>
>         return FQuat(q.x(), q.y(), q.z(), q.w());
> }
>
> ...
>
> Thank you!
>
> Cheers,
> Herman
>
> ------------------
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=75036#75036
>
>
>
>
>
> _______________________________________________
> osg-users mailing list
> osg-users at lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org