Canvas view camera element: Difference between revisions

m
update progress based on hackathon: Hackathon Proposal: CompositeViewer and Canvas
m (update progress based on hackathon: Hackathon Proposal: CompositeViewer and Canvas)
Line 13: Line 13:


{{infobox subsystem
{{infobox subsystem
|image      = cvcanvas-777.jpeg|Demonstration of multiple view windows in flightgear
|started    = 11/2020
|name        = Canvas Camera Views
|name        = Canvas Camera Views
|description = Rendering arbitrary views to a texture/Canvas
|description = Rendering arbitrary scene views to a texture/Canvas
|status      = planned/prototype
|status      = experimental prototype
|maintainers = none
|maintainers = none
|developers  = none
|developers  = Cgdae,  Icecode
}}
}}


Line 35: Line 38:


== Proof of Concept ==
== Proof of Concept ==
{{Main article|Hackathon Proposal: CompositeViewer and Canvas}}
<!--
{{Note|This is inspired by the long standing idea to render camera views to a texture for use as tailcams, gear views etc <ref>https://forum.flightgear.org/viewtopic.php?f=71&t=23929</ref>, it's based on code originally provided by F-JJTH<ref>https://forum.flightgear.org/viewtopic.php?f=71&t=23929#p317448</ref>, and subsequently reworked by Icecode GL and Hooray to integrate it with the Canvas system back in 2017<ref>https://forum.flightgear.org/viewtopic.php?f=47&t=32846&p=318046</ref>
{{Note|This is inspired by the long standing idea to render camera views to a texture for use as tailcams, gear views etc <ref>https://forum.flightgear.org/viewtopic.php?f=71&t=23929</ref>, it's based on code originally provided by F-JJTH<ref>https://forum.flightgear.org/viewtopic.php?f=71&t=23929#p317448</ref>, and subsequently reworked by Icecode GL and Hooray to integrate it with the Canvas system back in 2017<ref>https://forum.flightgear.org/viewtopic.php?f=47&t=32846&p=318046</ref>
At the time, the main issue was that the new view element needed to be explicitly updated, but that should no longer be the case thanks to James' work on the setPixel() API <ref>https://sourceforge.net/p/flightgear/mailman/message/36926486/</ref> which also means that sc::Image now has a <code>dirtyPixels()</code> API which we can reuse <ref>https://sourceforge.net/p/flightgear/simgear/ci/ad3621e23b4056e1be7e8d9eb8dd4d513455add8/</ref>
At the time, the main issue was that the new view element needed to be explicitly updated, but that should no longer be the case thanks to James' work on the setPixel() API <ref>https://sourceforge.net/p/flightgear/mailman/message/36926486/</ref> which also means that sc::Image now has a <code>dirtyPixels()</code> API which we can reuse <ref>https://sourceforge.net/p/flightgear/simgear/ci/ad3621e23b4056e1be7e8d9eb8dd4d513455add8/</ref>
Line 429: Line 435:
  # Canvas
  # Canvas
</syntaxhighlight>
</syntaxhighlight>
-->


== Roadmap ==
== Roadmap ==