Hi Cory,
The Optimizer has a range of optimization traversals that deal with
various problems commonly exist in databases, in an ideal scene graph
the optimizer wouldn't do anything for you, so one should view it like
patch for a problem. Sometimes you can't fix the problem directly
because you
On 7/30/2010 4:06 AM, Robert Osfield wrote:
The Optimizer has a range of optimization traversals that deal with
various problems commonly exist in databases, in an ideal scene graph
the optimizer wouldn't do anything for you, so one should view it like
patch for a problem.
It is definitely
Hi Cory,
On Fri, Jul 30, 2010 at 3:02 PM, Cory Riddell c...@codeware.com wrote:
It is definitely a patch for a problem. We aren't loading anything from
a database. Rather we are using a commercial geometric modeling kernel
to create and tesselate fairly complex bodies. OSG's Optimizer is
I'm getting to the point where I have to start tuning my app a bit and
so I added a call to Optimizer::optimize() today. Wow!
On a typical model, my app was able to push just under 40 fps at
1920x1200 (debug build). After running the optimizer, it's pushing
around 100 fps.
The trade off of
you can save your model after optimization and load it optimized no
need to wait 20 seconds then
-Nick
On Thu, Jul 29, 2010 at 10:39 PM, Cory Riddell c...@codeware.com wrote:
I'm getting to the point where I have to start tuning my app a bit and
so I added a call to
Our app is very CAD-like. The purpose of it is to create and edit
models. Reloading models is a relatively rare activity.
Cory
On 7/29/2010 1:54 PM, Trajce (Nick) Nikolov wrote:
you can save your model after optimization and load it
optimized no need to wait 20 seconds then
-Nick
I should add that our primary save format is .sat (ACIS), not .osg.
On 7/29/2010 2:35 PM, Cory Riddell wrote:
Our app is very CAD-like. The purpose of it is to create and edit
models. Reloading models is a relatively rare activity.
Cory
On 7/29/2010 1:54 PM, Trajce (Nick) Nikolov
7 matches
Mail list logo
