World coordinates were passed to GPU as floats: u_model of a chunk and of a model had the world translation, vertices of translucent blocks, particles, precipitation, block wrappers, lines and 3D texts were built in the world space, and the camera position was subtracted in shaders. The float step grows with the distance from the world origin (6 cm at 1M blocks, 2 m at 30M): blocks got skewed, then stuck together. Camera::getOrigin() is an integer point near the camera (X and Z are rounded to 1024 blocks, Y is 0). Camera::getView() is relative to it, and every position passed to GPU is "world - origin" calculated on CPU, so the shaders keep working with small numbers and do not change: u_cameraPos, a_modelpos, u_inverseView and the shadows matrices are in the same space as before, shifted by the origin. Matrices of a shadow map are converted from the origin of its camera to the origin of the player camera. The clouds shader gets the origin wrapped by the period of its waves, the waves stay bound to the world. Vertices of translucent blocks are local to the chunk now, as vertices of opaque ones, and drawn with u_model of the chunk. |
||
|---|---|---|
| .github | ||
| dev | ||
| doc | ||
| res | ||
| src | ||
| test | ||
| vctest | ||
| .clang-format | ||
| .cmake-format.py | ||
| .gitignore | ||
| CHANGELOG.md | ||
| CMakeLists.txt | ||
| CMakePresets.json | ||
| compile_flags.txt | ||
| Dockerfile | ||
| flake.lock | ||
| flake.nix | ||
| LICENSE | ||
| README.md | ||
| run.sh | ||
| vcpkg.json | ||
VoxelCore
Latest release
Build project in Linux
Install libraries
ALT Linux based distros
su -
apt-get install libglfw3-devel libGLEW-devel libglm-devel libpng-devel libvorbis-devel libopenal-devel libluajit-devel libstdc++13-devel-static libcurl-devel libfreetype-devel libssl-devel
Debian based distros
sudo apt install libglfw3 libglfw3-dev libglew-dev libglm-dev libpng-dev libopenal-dev libluajit-5.1-dev libvorbis-dev libcurl4-openssl-dev libssl-dev libfreetype6-dev
Tip
CMake missing
LUA_INCLUDE_DIRandLUA_LIBRARIESfix:sudo ln -s /usr/lib/x86_64-linux-gnu/libluajit-5.1.a /usr/lib/x86_64-linux-gnu/liblua5.1.a sudo ln -s /usr/include/luajit-2.1 /usr/include/lua
RHEL based distros
sudo dnf install glfw-devel glew-devel glm-devel libpng-devel libvorbis-devel openal-soft-devel luajit-devel libcurl-devel libfreetype-devel openssl-devel
Arch based distros
sudo pacman -S glfw glew glm libpng libvorbis openal luajit curl freetype2 openssl
Building engine with CMake
git clone --recursive https://github.com/MihailRis/VoxelCore.git
cd VoxelCore
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
cmake --build . --parallel
Tip
Use
--parallelto utilize all CPU cores during build.
Building project in macOS
Install libraries
brew install glfw glew glm libpng libvorbis lua luajit libcurl openal-soft freetype
Tip
If Homebrew fails to install
lua,luajit, oropenal-soft, download, compile, and install them manually.
Building engine with CMake
git clone --recursive https://github.com/MihailRis/VoxelCore.git
cd VoxelCore
mkdir build
cd build
cmake -DCMAKE_BUILD_TYPE=Release ..
cmake --build . --parallel
Building in Windows
Note
Requirements: vcpkg, CMake, Git, and Visual Studio (with C++ tools).
There are two options to use vcpkg:
- If you have Visual Studio installed, the VCPKG_ROOT environment variable is often already set in the Developer Command Prompt for VS.
- Otherwise, install vcpkg manually:
cd C:\
git clone https://github.com/microsoft/vcpkg.git
cd vcpkg
.\bootstrap-vcpkg.bat
Then set the VCPKG_ROOT environment variable and add it to PATH:
$env:VCPKG_ROOT = "C:\vcpkg"
$env:PATH = "$env:VCPKG_ROOT;$env:PATH"
Tip
For troubleshooting, refer to the official vcpkg documentation.
After installing vcpkg, build the project:
git clone --recursive https://github.com/MihailRis/VoxelCore.git
cd VoxelCore
cmake --preset default-vs-msvc-windows
cmake --build --preset default-vs-msvc-windows
Note
Make sure your
CMakeUserPresets.json(if used) contains the correctVCPKG_ROOTpath.
Building with CLion (MinGW / Ninja)
Note
Requirements: vcpkg, Git, and CLion (bundled with CMake, Ninja and MinGW toolchain).
Warning
Avoid installing tools in paths with spaces (e.g.
Program Files). This may break MinGW builds (especiallywindres).
Install vcpkg manually as described in the Visual Studio section.
Configure CLion
Open the project in CLion and configure CMake profile:
Settings → Build, Execution, Deployment → CMake
Reload CMake project and build the engine.
Build using Docker
Note
First, install Docker Engine: https://docs.docker.com/engine/install
On Linux
Step 1. Build Docker image
docker build -t voxel-engine .
Step 2. Build project inside container
docker run --rm -it -v "$(pwd):/project" voxel-engine bash -c "cmake -DCMAKE_BUILD_TYPE=Release -Bbuild && cmake --build build --parallel"
Step 3. Run the application (requires X11 forwarding)
docker run --rm -it \
-v "$(pwd):/project" \
-v /tmp/.X11-unix:/tmp/.X11-unix \
-v "$XAUTHORITY:/home/user/.Xauthority:ro" \
-e DISPLAY="$DISPLAY" \
--network=host \
voxel-engine ./build/VoxelCore
On Windows
Note
You need an X server like VcXsrv to display the GUI.
Step 1. Install and run VcXsrv
Launch with:
.\vcxsrv.exe :0 -multiwindow -ac
Step 2. Build Docker image
docker build -t voxel-engine .
Step 3. Build project
docker run --rm -it -v "${PWD}:/project" voxel-engine bash -c "cmake -DCMAKE_BUILD_TYPE=Release -Bbuild && cmake --build build --parallel"
Step 4. Run the application
docker run --rm -it -v "${PWD}:/project" -e DISPLAY=host.docker.internal:0.0 --network=host voxel-engine ./build/VoxelCore