From: Damien Gerhardy (damien.gerhardy++at++sydac.com.au)
Date: 02/20/2006 19:36:22
There is a bad performance problem with the Performer 3.2.1 intersection
code on the windows platform.
Raycasting has always been slow in performer but there is a huge
difference between Performer 3.1.1 and Performer 3.2.1.
We raycast all of our 'features' to the world terrain (hundreds of them).
To place some "special" features we do a series of raycasts (using
pfNode::isect)
left, right and then down which is a little time consuming but puts them in
the
correct location every time.
I would estimate that on average these "special" features take about
0.25-0.5 seconds
to place using Performer 3.1.1 (worst case about 1 second).
When I place these "special" features using Performer 3.2.1 it can take up
to 39 seconds
to place a feature. There are no code changes on our part, just rebuild the
software
and rebuild the pfb's for the associated version of performer.
Has anyone else seen this?
Any tips on what I can do to get around it?
Is there a fix coming soon because we can't use Performer 3.2.1 if its this
slow?
Caution - This e-mail and its contents contain privileged information that
is intended solely for the recipient. If you are not the intended recipient
you are hereby notified that any use, dissemination, distribution or
reproduction of this e-mail is prohibited. If you have received this e-mail
in error please notify the Postmaster at sydac++at++sydac.com.au immediately. Any
views expressed in this e-mail are of the sender and may not necessarily
reflect the views of Sydac Pty Ltd.
This archive was generated by hypermail 2b29 : Mon Feb 20 2006 - 19:46:39 PST