this post was submitted on 01 Dec 2023
55 points (96.6% liked)
Games
16758 readers
1088 users here now
Video game news oriented community. No NanoUFO is not a bot :)
Posts.
- News oriented content (general reviews, previews or retrospectives allowed).
- Broad discussion posts (preferably not only about a specific game).
- No humor/memes etc..
- No affiliate links
- No advertising.
- No clickbait, editorialized, sensational titles. State the game in question in the title. No all caps.
- No self promotion.
- No duplicate posts, newer post will be deleted unless there is more discussion in one of the posts.
- No politics.
Comments.
- No personal attacks.
- Obey instance rules.
- No low effort comments(one or two words, emoji etc..)
- Please use spoiler tags for spoilers.
My goal is just to have a community where people can go and see what new game news is out for the day and comment on it.
Other communities:
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
While technically this is a maybe, in practice you really don't want both the source and the receiver to be on wifi because you have to wait for the deck to send a wifi packet to the router before listening for the same packet from the router to the quest (yes this is a bit backwards but it is how we do wifi), everytime.
A deck on an Ethernet adapter os probably gonna work better, but you still have the problem that currently VR on Linux is extremely hit-or-miss. I have a windows install on a separate disk specifically for VR purposes on my main computer.
Also it's possible to use a usb-c to usb-c cable and setup network over USB, which would be faster that having the oculus on wifi, and still be fully portable since you can strap the deck to your body somewhere.
The idea was to use the Deck to run the game and stream it on my Quest2