martin not sure about resolutions yet, we may need to wait and see but feel free to share more here about your preferred resolution and specs etc -- maybe we can get those requests on the team's radar.

Hi Nathan,

2 remarks on that:

Even Android 10" tablets and smartphones do come with similiar high resolutions, tendency is much higher.

I understand the limited available number of pixels of the Quest (3) for only that part of the displays showing a specific monitor, or even 3 of them.

But instead of resizing the PCs display _before_ streaming (down to full-hd, which is app. 2 Mpixels) with a driver, resizing and recalculating it _again_ in the Quest, seems not to be the best and most efficient way to go.

But meanwhile you are able to (and require on some apps) a real high bandwidth, much higher than those streams will produce.

And... in my understanding, _downscaling_ resolution of a streamed display is much more efficient than (which may occur whren only getting full-hd 2 Mpixel and zooming in) first _downscaling_ on the PC and afterwards _upscaling_ on the Quest.

So, maybe it cld. make sense to stream the _original_ resolution of the physical monitor(s), using _the same resolution_ for virtually added ones, and to scale them _only_ within the Quest, or optionally let the user define the reuired resolution on start up (as it is possible eg. in the MS native RDP client).