1- # Quake 3 VR
1+ # [ Quake 3 VR] ( https://ripper37.github.io/q3vr )
22
33** Quake 3 VR** (a.k.a. ` q3vr ` ) is a PCVR port of Quake 3 Arena game based on:
44
5- * ` ioquake3 ` - community maintained fork of idTech3 engine,
6- * ` Quake3Quest ` - port of ` ioquake3 ` to Quest 2/3 mobile headsets.
5+ * [ ioquake3] ( https://github.com/ioquake/ioq3 ) - community maintained fork of
6+ idTech3 engine,
7+ * [ Quake3Quest] ( https://github.com/Team-Beef-Studios/ioq3quest ) - port of
8+ ` ioquake3 ` to Quest 2/3 mobile headsets by ** Team Beef** .
79
810It includes several bugfixes, improvements and QoL features built specifically
911for VR.
@@ -23,20 +25,16 @@ for VR.
2325 * zoom with reticle for railgun
2426 * comfort options like vignette, height adjustements, weapon lasers, etc.
2527
26- > [ !CAUTION]
27- > Please bear in mind that this port is currently in ** beta** state, which
28- > means that there may be some bugs and compatibility issues that will be fixed
29- > over time.
30-
3128
3229## How to play
3330
3431To download and set up the game:
3532
3633* Go to [ Releases] ( https://github.com/RippeR37/q3vr/releases ) page and download
37- the most recent release and install (or extract) to directory of your choosing
34+ the latest release and install (or extract, if selected portable version) to
35+ directory of your choosing,
3836* If you own full version of the game, place ` pak0.pk3 ` file from original game
39- in the ` baseq3/ ` subdirectory
37+ in the ` baseq3/ ` subdirectory.
4038
4139then any time you want to play simply:
4240
@@ -47,17 +45,17 @@ then any time you want to play simply:
4745> It's highly recommended to go through configuration options in ` Setup ` menu -
4846> before jumping into the game - to set controls and settings to your liking.
4947
48+ > [ !NOTE]
49+ > The game has built-in update notifications. Whenever new version will be
50+ > released, you will be notified about it on game startup.
5051
51- ## Feedback / bug reporting
5252
53- > [ !IMPORTANT]
54- > This project is currently in ** beta** . Feedback from users is required to make
55- > any further improvements and fix bugs. If you've spotted any problems or have
56- > any improvement ideas, please open GitHub issue with details and/or reach out
57- > on Discord.
53+ ## Feedback / bug reporting
5854
59- For your convienience this repository comes with a pre-defined template for
60- creating issues which should make the process easier.
55+ If you've spotted any problems or have any improvement ideas, please open GitHub
56+ issue with details and/or reach out on Discord. For your convienience this
57+ repository comes with a pre-defined template for creating issues which should
58+ make the process easier.
6159
6260Please remember to include any details that may help reproduce and analyze the
6361problem such as logs, your computer configuration, etc.
@@ -72,8 +70,8 @@ your controlers.
7270
7371* ` B ` on left hand opens/closes menu or goes one level up (like ` ESC ` )
7472* ` B ` on right hand resets position of Virtual Screen
75- * ` Trigger ` on active hand - selects currently selected option (like ` LMB ` )
76- * ` Trigger ` on inactive hand - makes this hand active
73+ * ` Trigger ` on active hand - cursor click
74+ * ` Trigger ` on inactive hand - makes this hand the active one
7775
7876### Controls as spectator
7977
@@ -92,10 +90,10 @@ made in the in-game `Setup` configuration menus.
9290
9391### Changing bindings/setting custom actions
9492
95- If you wish to change bindings, you can try doing so from your
96- VR runtime's input configuration screen (e.g. Steam VR input bindings) or
97- manually set specific actions to given keys. To do so, you need to create
98- ` autoexec.cfg ` file in the ` baseq3/ ` subdirectory and set custom bindings with:
93+ If you wish to change bindings, you can do so from your VR runtime's input
94+ configuration screen (e.g. Steam VR input bindings) or manually set specific
95+ game actions to given keys. To do so, you need to create ` autoexec.cfg ` file in
96+ the ` baseq3/ ` subdirectory and set custom bindings with:
9997
10098```
10199set vr_button_map_<key> "<action>"
@@ -124,7 +122,10 @@ These are the default mappings:
124122| ` B ` | ` "+movedown" ` | Crouch |
125123| ` A ` | ` "+moveup" ` | Jump |
126124
127- Please refer to [ Quake 3 Quest website] ( https://quake3.quakevr.com/ ) for more
125+ Default controls for Valve Index:
126+ ![ Default controls for Valve Index] ( https://ripper37.github.io/q3vr/media/bindings.png )
127+
128+ Please refer to [ Q3VR website] ( https://ripper37.github.io/q3vr ) for more
128129details.
129130
130131
@@ -146,8 +147,6 @@ If you're having some problems consider:
146147* Checking if there isn't a newer verions of ` Q3VR ` available which may already
147148 have a fix for your problem
148149 * You can also check older versions to see if it worked before
149- * ** [ BETA] ** During beta, the game will open a console in the background with
150- logs - they may contain something that will hint what's the problem
151150
152151If you're unable to find solution to your problem yourself, please reach out to
153152the community (see section below) or
@@ -178,7 +177,9 @@ cmake -S . -B build
178177cmake --build build --config Release
179178```
180179
181- Check out [ GitHub Actions workflow] ( .github/workflows/build.yml ) for reference.
180+ Check out [ GitHub Actions workflow] ( .github/workflows/build.yml ) for reference
181+ and [ GitHub Actions] ( https://github.com/RippeR37/q3vr/actions ) for recent
182+ builds.
182183
183184
184185## Contributions
@@ -198,3 +199,20 @@ on VR games, ports or tools you can do so via:
198199
199200Please also consider supporting authors of ` ioquake3 ` and ` Quake3Quest `
200201projects.
202+
203+
204+ ## Credits
205+
206+ This port is based on work of:
207+
208+ * id Software (creators of idTech3 and Quake 3 Arena)
209+ * ioquake3 team (creators and maintainers of [ ioquake3 fork] ( https://github.com/ioquake/ioq3 ) )
210+ * Team Beef (creators of [ Quake3Quest port] ( https://github.com/Team-Beef-Studios/ioq3quest ) )
211+
212+ I would also like to personally thank everyone who helped working specifically
213+ on this port with special thanks to:
214+
215+ * Royd0
216+ * @ernie
217+ * XQuader
218+ * Dteyn
0 commit comments