Renegade's built-in profiler shows that navnodes aren't causing much of blip on your level using Quesa 1.7. In fact, I saw the same amount of slowdown on the version without navnodes. Well it ran much faster without the NavNodes for me, I had no way of seeing the frame rate in Renegades a2 so maybe I just didn't notice it. Without those NavNodes, there would be only about 30 objects. The slowdown is entirely contained in the rendering part of the profiler -- exactly at the point MainView.Update is called. Yes. This is also consistent with what I'm seeing after a preliminary run profiling Renegades with Shark. Note that I didn't see any new bottlenecks with either navnode functions or any other Renegades functions using Shark -- it all sat within Quesa (a 20% increase over 1.6d20). I was seeing the same thing. On the other hand, I've seen only speed improvements in other 3D apps I've built. I know Renegades uses a lot of 3DMF shape created from a string (.AddShapefromString). Maybe there is a bad 3DMF code somewhere that is causing this?? _______________________________________________ Unsubscribe or switch delivery mode: <http://www.realsoftware.com/support/listmanager/> Search the archives of this list here: <http://support.realsoftware.com/listarchives/lists.html> |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Quesa 1.7, Jeff Quan |
|---|---|
| Next by Date: | Re: Quesa 1.7, Lo Saeteurn |
| Previous by Thread: | Re: Quesa 1.7, Jeff Quan |
| Next by Thread: | Re: Quesa 1.7, Jeff Quan |
| Indexes: | [Date] [Thread] [Top] [All Lists] |