20,741
edits
Canvas scenery overlays: Difference between revisions
Jump to navigation
Jump to search
→Canvas Integration
| Line 152: | Line 152: | ||
|date = Jun 2nd, 2016 | |date = Jun 2nd, 2016 | ||
|added = Jun 2nd, 2016 | |added = Jun 2nd, 2016 | ||
|script_version = 0.40 | |||
}}</ref> | |||
Notice that the photoscenery patches are fairly old meanwhile, [https://forum.flightgear.org/viewtopic.php?f=5&t=21882&p=201862#p201862 last I looked at them], I had something working that would render an arbitrary texture to a hard-coded tile using a lat/lon tuple - but meanwhile, all the PagedLOD refactorings are complicating things a bit - I guess that Stuart or poweroftwo would be in a better position to judge if/how that functionality can be generalied and integrated/exposed at the SimGear level to be useful here ... | |||
Also, given the shifting focus of the discussion, the Canvas route may be super-flexible, but it won't align nicely with all the effects/shader and PagedLOD infrastructure that you need, i.e. the Canvas system would literally need to provide its texture in a PagedLOD-compatible form which has other implications, especially from a multi-threading standpoint, and a texture would need to be able to use shaders and effects, for both, input and output. | |||
Thus, for prototyping and a proof-of-concept, the old patches may be suitable and should be straightforward to integrate with the Canvas system to come up with a geographic Canvas placement - but all the other fancy stuff you are talking about would sooner or later benefit from using osg::PagedLOD and osg::OverlayTexture - none of which is currrently used by the Canvas system.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=287626#p287626 | |||
|title = <nowiki> Re: Next-generation scenery generating? </nowiki> | |||
|author = <nowiki> Hooray </nowiki> | |||
|date = Jun 5th, 2016 | |||
|added = Jun 5th, 2016 | |||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||