Hi Werner,
Great to her you got to the bottom of this issue, amazing how such a
small and innocuous looking change can have such a dramatic impact.
BTW, the short hand for setting the binding in OSG-3.4 onwards is:
geometry-setNormalArray(array, osg::Array::BIND_PER_VERTEX);
The separate
Hi Robert,
final analysis:
In our software we did the following patch to make it run with high fps
in master of 3.4 branch:
osgNormals=newosg::Vec3Array;
+osgNormals->setBinding(osg::Array::BIND_PER_VERTEX);
geometry->setNormalArray(osgNormals.get());
Hi Robert,
the 3.4.0 tagged version is OK with the frame rate.
We discovered your commit in the 3.4 branch causing the problem:
From1f1c21772ae0dd10a93cd31ab81bf563802b7b2dMonSep1700:00:002001
From:RobertOsfield
Date:Thu,3Nov201611:31:07+
Hi Wener,
On 28 March 2017 at 16:24, Werner Modenbach
wrote:
> I know it is actually not your duty giving help here but you are very
> familiar with the driver calls and it would help a lot if you can provide
> an idea what kind of setting might cause this issue.
>
Hi Robert,
I have done 1 week of testing now on the dramatic performance issue.
As I said, when linking my program against osg 3.2.1 I get 60 fps
and linking the program without any change against version 3.4.0 I get
2.5 fps.
Exporting my scene and running it in your viewer in 3.4.0 also has
Hi Werner,
Hopefully others will be able to chip in as I don't have a answer right
now, it's certainly very odd. If it were a general problem then we'd seen
lots of issue with it being reported.
With this level of slow down it's almost like your'e invoking a software
renderer when running with
Hi Robert,
I updated my project from version 3.2.1 to 3.4.0.
I'm on Window 7 Pro.
Unfortunately the frame rate dropped significantly from 60 fps to 2.x fps.
I verified it several times by just linking to the 2 versions without
any change of my code.
Please see the 2 screen shots with the stats
7 matches
Mail list logo