I suggest you move the 2nd GPU to a 2nd PC, on a wired network.
My wired 1 Gigabit network uses a cheap Netgear unmanaged 4-port switch:
I have tested Glassout with an old Athlon PC and 24In monitor. That PC was shipped with Windows 7, now its running Windows 10.
About 0.4% CPU is used on the Xeon quad core sim machine and 1% of network.
As for AI, I think it is highly overated.
I think the second-PC idea is where this becomes really useful for cockpit builds. A wired LAN and a small client machine feels cleaner to me than trying to solve every extra-display problem with another GPU in the main sim box.
For normal desktop use it may be extra complexity, but once you have several panels or touchscreens, separating the display workload also makes troubleshooting easier. If something crashes or a driver behaves badly, at least the main simulator machine is not carrying all of that at once.
Expensive and overly complex too. It’s less than 1% of the use cases.
Is this for Air manager or Air Panel? I guess for Air manager.
You mentioned Air Manager so yes indeed Air Manager.
Just curious. Has anybody tried Glassout with VR and a passthrough?
Yep, works as well as anything else you can “see” in real life depending on your passthrough quality. GlassOut isn’t going to know or care whether you’re in VR or not.
Do we have a breakdown of all the use cases?
One group of use cases is the increasing number of owners of WinCtrl hardware, which can result in highly realistic Boeing, Airbus or fighter jet cockpits.
BTW Mobiflight has presets for 15 types of Boeing/Airbus WinCtrl hardware, and Python scripts.
My 2nd PC was free, inherited from a relative. I recycled a 24in monitor bought originally for work from home. $18 just about pays for 3 coffees; Glassout is very simple to setup.
I am still having mixed results with Glassout on the Black Square TBM 850 and the TDS GTNXi 750. Some times it gets discovered and other times it either doesn’t get discovered at all or is discovered and only has a black screen. Too unreliable for me to consider it fixed.
Is anyone else with either a Black Square plane and/or a TDS GTNXi 750, having these problems? If not it may be a conflict with something on my flight sim computer.
I have a Caravan and Duke.
Once I set up the PMS50 GTN750 and saved the layout, I’ve had zero issues with it.
Surprised that the TDS is giving you issues. Hope you get it sorted - GlassOut is great.
Based on having lots of interaction with cockpit builders over the years and more recently since MSFS I can say that those who run multiple PC’s is a low percentage. If cockpit building is considered niche then doing it with a multi pc setup is even more so. There are obviously lots of reasons why this is so.
Thanks for the feedback. Yep it is niche, but as a kid I loved making model planes with my late Father. Then we moved onto balsa gliders etc.
As an adult I built a small dinghy in plywood - that is definnatly niche! But I now have good friends who have also built boats.
So cockpit building is fun for me and the WinCtrl devices are fantastic for a mini-cockpit. Not full size, just whatever I can squeeze into our hobby room.
The networking of AirManager inspired me, to be able to offload complex instruments onto older PCs and focus the main PC on the window views. Ditto Mobiflight for controls, I’ll add potentiometers to control dimming of screens and WinCtrl instruments.
I was on good terms with the head of IT where I developed software. When they cleared out local servers Brian passed on the good machines to staff. I soon had PCs named “FlightSim” and “WingMan” networked at home.
GlassOut with networked AirPanel can be achieved.
Please refer to the instructions from the author on how to network AirPanel.
Disclaimer: I have not tired the instructions.
Has anybody using triple (or multi) monitors/render windows managed to get it to work? I get a DXGI crash on my triple 4k setup as soon as it starts discovering displays…
Glassout version 1.10 issued today resolved my issue with Duke/PMS50 GTN750/650. The panels are now discovered and function perfectly. Thank you!
I’m struggling to get the automatic plane detection working with V1.10 (and previous build)
I have a profile named “FenixA320”, which includes a template of the 4 main screens on a single 24in HD monitor, PFD, ND, Upper ECAM, lower ECAM, running on a networked PC. It displays manually ok. But GlassOut will not load it automaticallly, even if I shut down GO and restart it whilst the flight continues.
It’s not clear from the docs the workflow required i.e. sim first, GO next and the pattern matching is confusing.
[I know its a developer regex, but I think that’s a bit too technical for the average user.]
I really hope that OG does not require a plane change before producing a match, that would require us to restart flights which would be a pain. Perhaps my profile is not named correctly for Fenix?
Latest Glass Out release is 1.11.0 Still doesn’t discover my TDS GNXi 750 at all, on the Black Square TBM 850.. Worked once a few days ago and not since. Switched to the TBM 930 and the G3000 avionics are discovered and moved to a touch monitor. However, the Glass Out does quit sometimes in flight.
You’re reporting this to them, right?
It is more or less an early (Beta?) release.
Yes, via email to developer.
I’ve definitely been getting a DXGI CTD (crash to desktop) as soon as I start GlassOut since version 1.11. It worked perfectly with version 1.10.