After licensing Rayve on Gumroad, access is provided to the Rayve zip file. The zip file contains a Visual Studio project. Just unzip into a folder and load the solution into Visual Studio. Visual Studio Community edition can be used. The key source files and libraries can also be extracted for use with other development environments.
The project folder contains the key files needed for compiling a game with Rayve.
rayve.hpp - C++ header file.
rayved.lib - Debug library.
rayve.lib - Release library.
cvtmat.txt - Material name conversion file.
The deploy folder contains everything needed for running a game with Rayve, and can be distributed on its own.
rayved.dll - Debug dynamic library (Should be removed for final distribution).
rayve.dll - Release dynamic library.
glfw3.dll - Window and input management. (www.glfw.org).
hiadpi.dll - 3DConnexion SpaceMouse driver. (3dconnexion.com).
libz.dll - Zip file manager. (www.zlib.net)
oalinst.exe - OpenAL installer. (www.openal.org)
shaders folder - Rayve compiled shaders.
data folder - Assets imported by Rayve for use in a game are stored here.
The assets folder is a place to store files created and used by asset creation software such as 3D modelling tools. Exports from asset creation software go into the deploy/data folder.
The OpenAL installer should be run on any deployment to confirm the OpenAL driver is available on the system.