Good points, and I do agree the devil is in the detail. Like life, a balance has to be struck and lets not forget AirManager is probably the best for steam gauges.
The key issue seems to be the plane and how it’s software was written. The WASM instruments seem to be efficient. GO discovers all the Fenix glass data, including clock digits, FCU digits and EFIS digits on one composite image. Perhaps plane developers need to rise to the standard Fenix sets?
The CPU sim limitation is often a thread limitation, threads are dominated by clock speed (and a big cache helps with big textures).
I don’t see the sim using all 4 cores and only about 0.5% of my old 3gHz quad core cpu is used by GO. The Athlon GO client runs at 50% cpu driving 2 displays on a gt740, which is fine.
However, 8, 12 or more cores might be very different for the sim.
Most of all I like the network architecture of OC. Having developed complex engineering software on a large network and GitHub and remote working it seems natural to use multiple PCs. In the old days FSX used multiple PCs with WideView.
Just as with a MSFS popout, GlassOut can only render the display portion of the whole instrument so one needs a method to interact with any controls mounted on the instrument surround or bezel. The majority of users with home cockpits either have dedicated hardware they’ve purchased or built themselves or a functional 2D graphic overlay of the bezel that when placed over the top of the GlassOut display texture gives you a full instrument with display and controls combined just like in the aircraft but on a remote display.
I disagree, the author of glass out has another app, LiftBox. It’s got 80% of the functionality we need
LiftBox control is interesting - it inputs commands into the simulator. Mouse, touch, single knob etc.
GlassOut outputs glass instrument images to other clients, including LAN clients.
They are complimentary products that do different things. It would be interesting to see them used together.
Do you have the problem where no panels appear under discover with many other aircraft, or is it just the TBM 850?
That was the case for me with almost 90 percent of all aircraft. Then I discovered a conflict on my Windows 11 gaming PC involving the flightsim.to mod “Deel - nameplates custom color.”
I’ve always had the ‘N’ key on my keyboard mapped in MSFS 2024 to toggle the visibility of multiplayer nameplates. As soon as I disable the nameplates, all the panels under discover appear immediately. And then the panels stay visible even after I re-enable the nameplates using the ‘N’ key.
I don’t know why this happens, but I’ve tested it—no joke—15 to 20 times with about 30 different aircraft, and the result is absolutely consistent every time. And it makes no difference whether the community folder is empty or full; that really doesn’t matter.
Maybe that’s the case for you, too, and could be also the solution? 
Strangely enough, I have absolutely no issues with the “Deel - nameplate custom color” mod and panel visibility under discover on my gaming laptop. Even the developer of the “Deel - nameplate custom color” mod, whom I contacted about this, can’t explain it from a technical standpoint… And I haven’t received a reply from the GlassOut developer yet, even though I’ve sent two emails. But I think he’s very busy right now and will get back to me eventually…
Cheers!
Well done! You deserve the dedicated Beta tester award 
I’m a retired developer and these repeatable show stopper conflicts can be like gold dust to the development team.
Hi. I tested again today… I’m having the exact same behaviour with the other flightsim.to custom nameplate mod by craigybabyj! If I briefly turn off the nameplates using the ‘N’ key, all the panels under “Discover” suddenly appear within 1-2 seconds. Tested again with 10 aircraft in a row, with an empty community folder. So, there’s evidently a conflict between custom nameplates and GlassOut on some systems… 
As far as I can tell the issue for me is only in the BS TBM850 and only with the GTNXi 750. Some times the GNS 530 doesn’t show up but tht is infrequent. A couple of times the 750 was discovered but that was early on with Glass Out. So far, that is the only plane and the only instrument that isn’t discovered. I know the developer has been travelling for a couple weeks, but he has been very responsive to me. Just no solution yet.
For what it’s worth, I’ve been using POPM since it released, and then tried GlassOut since it’s release and have been using it since.
Running it off same PC as sim, 8 displays on a 5080, 4 off the GPU, 1 HDMI to USB Dongle and 3 ipad’s on Space Desk.
Glassout + Air Manager onto all of them (aside from main display).
The only issue I have, is it doesn’t work that great with the PMDG EFB, it doesn’t like to scroll. Otherwise not a single issue, error, crash or otherwise.
I’m having an issue with touches not always registering. This is all local with the panels running on 2 touch screen monitors. POPM registers every touch perfectly, but with GO I frequently need to tap twice.
Same here. Imprecise touches, especially when scrolling.
Until now, I’m not convinced: I’m getting in 99% blank black screen with the default G1000 planes.
Once I got the default EFB shown and could stream it on my Android tablet. After a few seconds it was frozen. restart didn’t helped. I hope it was not a waste of money
Spent some time flying with GlassOut in the TBM930. Discovery worked fine. Setting up the layout was more painful - we really need keyboard shortcuts to move and re-size the pop-outs, like you do with POPM (unless I’m missing some?). Touch generally worked OK, only occasional double-touches.
However, as my flight continued I started to get glitching on the pop-outs. One froze and GlassOut had to be re-launched to fix it. Several time I saw visual glitches or the whole pop-out turned into multi-colour snow. I played with the rendering methods and with FPS settings etc. Still had issues the longer I flew.
I will continue to test, but this isn’t ready for primetime yet, not for my setup - as you’d expect from a pre-release, of course - and for now, POPM will continue to be my main go-to.
Does anyone have any data regarding performance of popouts vs glass out? My popouts don’t work in SU6 beta and I thought If changing to Glass out might be worth it.