Icecode GL wrote in Tue Oct 08, 2019 11:52 am: it's supposed to work with multiple monitors.
FWIW, we were once talking about a new "canvas placement" to support native OSG windows, this would make the existing CameraGroup stuff optional if it's using the same Compositor/Canvas approach via properties and listeners. I believe Tom and James discussed this back in 2012 already, and more recently this came up when we talked about the Compositor, too.
This kind of infrastructure could also be considered to be the groundwork required for integrating OSG's CompositeViewer support.
Another useful thing to have would be headless support, i.e. without the UI window showing up at all, because that could be a great troubleshooting aid (think running regression tests on the build server),but this kind of feature could also be used to use FlightGear as a back-end to create all sorts of screen-shots in a headless way, e.g. think about updating the manual and its images in a scripted fashion on the build server, with only the startup/environmental settings needed to update arbitrary screen shots, akin to "nightly binaries".