Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any chance for ES3.1 renderer and Oculus Quest port ? #26

Open
motorsep opened this issue Apr 30, 2020 · 5 comments
Open

Any chance for ES3.1 renderer and Oculus Quest port ? #26

motorsep opened this issue Apr 30, 2020 · 5 comments

Comments

@motorsep
Copy link

Wouldn't it be nice to run this awesome port on Oculus Quest? Any near future plans for that ?

@vittorioromeo
Copy link
Owner

Unless I get some help writing a new renderer, this is unlikely to happen - sorry. It would require a lot of work as the current implementation (based on QuakeSpasm) uses OpenGL legacy immediate mode rendering.

@nephatrine
Copy link

There is already a very good QuakeQuest source port. It doesn't have many of the neat interactivity features this port does, but retains compatibility with Quake multiplayer servers and mods.

@motorsep
Copy link
Author

motorsep commented Jun 9, 2020

There is already a very good QuakeQuest source port. It doesn't have many of the neat interactivity features this port does, but retains compatibility with Quake multiplayer servers and mods.

Exactly the point - it's not a good port you are talking about. QuakeVR is a way better. The author of the other Quake port did bare minimum and refused to add teleportation locomotion (he doesn't care for quality of life features at all).

I don't care for multiplayer, but I care for a lot of other things QuakeVR offers.

@nephatrine
Copy link

@motorsep Neither project is "way better" per se - they just have different design goals. You might not care about server compatibility or mod compatibility, but others do. Making sure those things don't break doesn't mean the other project is bad, it just isn't what you're personally looking for.

Since both projects do cater to somewhat different audiences and needs, I'd be all for @SuperV1234 adding Quest port since the more people able to enjoy it the better (as long as it doesn't take focus away from other things). But in the meantime there are other options is all I was trying to say.

@poVoq
Copy link

poVoq commented Sep 27, 2020

Unless I get some help writing a new renderer, this is unlikely to happen - sorry. It would require a lot of work as the current implementation (based on QuakeSpasm) uses OpenGL legacy immediate mode rendering.

Wouldn't Vulkan work on the Quest? AFAIK vkquake is Quakespasm based and changes could be backported?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants