Idea Second Orbiter window

[4throck]

For dual screen setups, the ability to have a second Orbiter window would simplify things.

The second window only needs to show the external view (VC would be a bonus, but not crucial) with the possibility of choosing a viewing angle.
That way, you could use your secondary monitor as a side window, for example.
There's no need for interaction with the second view.

I know that Camera MFD worked kind of like this, but it's too slow with the standard client under full screen view and incompatible with the new ones.

 

[Ripley]

http://orbiter-forum.com/showthread.php?t=28826

 

[4throck]

I know about that, and tried it.
It's too complicated, because you need to have 2x the disk space to run 2 Orbiter installs, uses 2x the memory, etc.
And to run 3 or 4 monitors... you would need that many installs.

The best example of my request is what MS Flightsim does.
Someting like this:

Camera MFD does this, but it's only fast enough for small windows. If I extend the MFD to cover the full screen, my FPS drops to 1!

 

[kamaz]

I know about that, and tried it.
It's too complicated, because you need to have 2x the disk space to run 2 Orbiter installs, uses 2x the memory, etc.

Actually, you can run multiple Orbiter instances from a single install. Source: I developed the add-on in question this way

About memory, well... Orbiter is 32-bit, so limited to 4GB -- given that my machine has 16GB of RAM I could run 4 orbiters in parallel easily

 

[ao7g]

Mmh... my 2 cents :

3 computers were needed for this, but it is doable with only 1 also, with Kamaz's add-on.

 

[4throck]

Ok, got that working on my machine and it's doable. Usage is not as straight forward or stable as I'd like, but it works. :thumbup:

The fact that you are running a second instance of Orbiter doesn't bog down my PC. Actually the second one loads faster than the first. Perhaps they are sharing resources?

 

[dbeachy1]

The second instance loads faster because at that point the Orbiter files used on startup are already cached in memory via Windows' disk cache, so it doesn't have to wait for disk I/O like the first instance did. :tiphat: