This is a proof-of-concept Quake map viewer. It handles basic geometry and curved patch rendering but with no support for game-specific shaders, entities etc. It implement PVS and frustum culling so performance is optimal. At the moment only the Quake III Arena maps are supported but an interface is provided for other BSP versions in the future.
To run the application, supply the bsp filename as a cmd line argument:
QuakeBspViewer.exe maps/ntkjidm2.bsp
Launching the viewer in VR mode (full screen Direct Mode):
QuakeBspViewer.exe maps/ntkjidm2.bsp -vr
Launching the viewer in VR mode (windowed Direct Mode):
QuakeBspViewer.exe maps/ntkjidm2.bsp -vr -window
In non-VR mode, use tilde key (~) to toggle statistics menu on/off. In VR mode, toggle between statistics, VR debug data and IR tracking camera frustum rendering (if camera is available). SPACE key will recenter your tracking position.
Note that you must have Quake III Arena textures and models unpacked in the root directory if you want to see proper texturing on screen, otherwise you'll just see a bunch of lightmapped, colored checker-board textures filling the screen which is less than impressive.
To move around use the WASD keys. RF keys lift you up/down and QE keys let you do the barrel roll (in non-VR mode only).
This project uses following external libraries (included but I feel I have to mention it here):
- GLEW extension library
- stb_image library for image handling (c) Sean Barret
- SDL2 library for window/input
- OculusVR SDK 0.5.0.1 and corrsesponding runtime for VR support
This viewer was made using resources on following websites:
And yes, I know that Q3 sources are open now but I felt like taking up a challenge ;)
You may encounter wrong rendering of bsp leaves that contain doors, moving platforms etc. This is because they are handled differently by the original game. For this reason, you'll notice that doors may not render or appear suddenly when the camera reaches certain arbitrary position on the map (q3ctf1 is a good example where some bsp leaves don't render at the right moment if PVS is enabled).
Having the Oculus Rift in extended desktop will very likely result in heavy judder even if you have no FPS drops. At this time OpenGL support is still less than optimal in OculusSDK.
Here's a list of ideas that could be fun to implement over time:
- add support for older bsp formats (ie. Quake1, Quake2)
- render map entities (weapons, armor, other pickups)
- support loading data from pk3/pak files
- add support for rendering Quake 3 shaders (if you're REALLY bored)
- bsp patch tesselation on the fly - you give the level, we rework it!