In the same way as a gaming specialized client such as [removed] but with the client machine connected to a VR headset.
I never tested [removed] since so far I’m satisfied with NoMachine, reading [removed] declare 7ms latency added that for VR needs is too much, since what [removed] is declaring seems to me is all also available in NoMachine (efficient hw video encoding and decoding, UDP slim protocol, etc), I want to understand more about NoMachine before searching for alternatives.
To be honest I’m not sure will be really feasible in term of latency (a VR headset does refresh every 11ms in the most slow case, a optic fiber connection we have in the office will add by himself a 4ms latency, before all the other latency sources), but the potential advantages worth a bit of analysis.