20,741
edits
Canvas FAQs: Difference between revisions
Jump to navigation
Jump to search
→Canvas vs. Tail/Scene Cams
| Line 155: | Line 155: | ||
|date = Oct 17th, 2015 | |date = Oct 17th, 2015 | ||
|added = Oct 17th, 2015 | |added = Oct 17th, 2015 | ||
|script_version = 0.40 | |||
}}</ref> | |||
we've had a number of aircraft developers, who would also require this functionality for implementing mirrors and/or tailcam views rendered to instruments, or FLIR-type views. All of these wouuld be possible to support once the view manager is refactored such that it can [[Canvas Development#Supporting Cameras]] | |||
For the time being, I'd suggest to use the multi-instance approach mentioned by ludomotico - depending on your requirements (and your willingness to tinker with experimental code), you could also check out FGViewer: [[FGViewer]] | |||
Given how FlightGear has evolved over time, not just regarding effects/shaders, but also complementary efforts like deferred rendering (via rembrandt), we'll probably see cameras (and maybe individual rendering stages) exposed as Canvases, so that there's a well-defined interface for hooking up custom effects/shaders to each stage in the pipeline - Zan's newcamera work demonstrates just how much flexibility can be accomplished this way, basically schemes like Rembrandt could then be entirely maintained in XML/effects and shader (fgdata) space.<ref>{{cite web | |||
|url = https://forum.flightgear.org/viewtopic.php?p=216741#p216741 | |||
|title = <nowiki> Re: create window </nowiki> | |||
|author = <nowiki> Hooray </nowiki> | |||
|date = Aug 16th, 2014 | |||
|added = Aug 16th, 2014 | |||
|script_version = 0.40 | |script_version = 0.40 | ||
}}</ref> | }}</ref> | ||