Canvas view camera element: Difference between revisions

Line 52: Line 52:
== The Future ==
== The Future ==
for now we are emphasizing in implementing camera views in Canvas. We also keep in mind that this might be an important groundwork for what might be RTT support for effects/shaders. For that we obviously need a link between  Canvas and Effects. It's kind of a good thing that both systems are completely separated and don't know of each other, we are given more freedom when it comes to joining them. This link is kind of delicate and has to be well planned out.<ref>{{cite web
for now we are emphasizing in implementing camera views in Canvas. We also keep in mind that this might be an important groundwork for what might be RTT support for effects/shaders. For that we obviously need a link between  Canvas and Effects. It's kind of a good thing that both systems are completely separated and don't know of each other, we are given more freedom when it comes to joining them. This link is kind of delicate and has to be well planned out.<ref>{{cite web
  |url    =  https://forum.flightgear.org/viewtopic.php?p=318059#p318059
  |title  =  <nowiki> Re: Canvas:View development </nowiki>
  |author =  <nowiki> Icecode GL </nowiki>
  |date  =  Sep 2nd, 2017
  |added  =  Sep 2nd, 2017
  |script_version = 0.40
  }}</ref>
Shaders can recieve many input textures and modern shaders support MRT (Multiple Render Targets) too. It makes sense to come up with some kind of well defined link between Canvas and Effects that allows for inputting/outputting canvases via effects. This would allow the same things that per-element effects would allow but with more flexibility and less overlapping functionality. <ref>{{cite web
   |url    =  https://forum.flightgear.org/viewtopic.php?p=318059#p318059  
   |url    =  https://forum.flightgear.org/viewtopic.php?p=318059#p318059  
   |title  =  <nowiki> Re: Canvas:View development </nowiki>  
   |title  =  <nowiki> Re: Canvas:View development </nowiki>