Alexander Bock

Isn't that the ```json "scene": { "orientation": { "yaw": 0.0, "pitch": 0.0, "roll": 0.0 } } ``` That we already have?

Yea, that's the `scene` tag in the configuration file. It does the same thing as the `Global Rotation` property in the RenderEngine as well

Instead of adding it to the existing asset, it would be cleaner to split them up into separate assets (pioneer-horizons, voyager-horizons, newhorizons-horizons) and then a new interstellar-spacecraft that includes all...

Maybe instead of a check to treat windows on the master differently, it would be better to implement the ability to change SGCT viewport settings interactively. That way we could...

The identifiers also are no longer valid as they have spaces in them

Its strange that the CEF CMake is not already doing that since we are using their functions to download CEF. But yea, agree!

Generally, adding more customizability. Maybe using MarkDown for mark-up of the mission text?

Can't reproduce it on my end. Can you put a breakpoint in apps\OpenSpace\ext\sgct\src\error.cpp line 46 (the `{}` line) and run again and paste the call stack?