Scenery LOD ideas for FlightGear: Difference between revisions

Scenery LOD ideas for FlightGear (view source)

1,237 bytes added , 19 February 2014

m

no edit summary

20,741

edits

Revision as of 11:27, 19 February 2014 (view source) Stuart (talk \| contribs) (Comments from Stuart) ← Older edit		Revision as of 11:35, 19 February 2014 (view source) Hooray (talk \| contribs) mNo edit summary Newer edit →
Line 132:		Line 132:
	-Stuart		-Stuart

			'''Hooray:''' Right as is, it's definitely destructive and it ''will'' require a tile reload obviously (supported by Robert Osfield's comments on the osg list) - I was referring to doing the reload automatically, instead of having to run a corresponding fgcommand (we're currently using your rendering dialog and its "reload scenery" button for this. For instance, see the OSG demo code using the simplifier - i.e. see [http://www.rozengain.com/blog/2011/02/16/openscenegraph-level-of-detail-management/] - there are several LOD nodes created which can be selected. Obviously, at the cost of increased memory consumption (so this may be a no-go for scenery) - but it may still be a useful feature for developers/power users (especially to come up with good numbers/heuristics), but also help with Aircraft/Cockpit/AI related LOD management. So, I'm all for coming up with a wrapper in SimGear that we can add to the terrain/tile manager, but also use in the main aircraft/cockpit and for AI models. Using a different type of visitor pattern may not be feasible for scenery I guess, until we have some way to tell how much RAM is actually being consumed --[[User:Hooray\|Hooray]] ([[User talk:Hooray\|talk]]) 11:35, 19 February 2014 (UTC)