studiorailgun/Renderer
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
1,909 Commits 4 Branches 0 Tags 272 MiB
Java 84.7%
C 11.8%
GLSL 2.6%
TypeScript 0.5%
JavaScript 0.3%
master
Go to file
austin 720e147d99
Some checks failed
studiorailgun/Renderer/pipeline/head There was a failure building this commit
Details
fix destroying blocks
2025-06-09 15:09:37 -04:00
.vscode block meshgen memory work 2025-05-27 15:06:45 -04:00
assets fix single block shader 2025-06-08 23:39:06 -04:00
docs fix destroying blocks 2025-06-09 15:09:37 -04:00
saves/testscene1 fix testing 2025-05-11 14:12:10 -04:00
src fix destroying blocks 2025-06-09 15:09:37 -04:00
test/java/renderer/ui ui test data updates 2025-04-14 18:24:10 -04:00
.gitignore fix single player loading 2024-12-03 16:14:07 -05:00
.gitmodules moving native code around 2024-12-03 12:38:40 -05:00
build.sh integrate cmake + ninja 2024-12-01 23:45:29 -05:00
buildNumber.properties particle vs work 2025-06-05 09:19:23 -04:00
CMakeLists.txt refactor native test code location 2024-12-06 13:21:25 -05:00
CMakePresets.json update cmakepresets 2024-12-02 19:20:38 -05:00
DEPENDENCIES.md proof of concept of loading html to define ui 2025-05-05 17:53:33 -04:00
Jenkinsfile fix testing 2024-12-04 19:30:35 -05:00
pom.xml pull up lwjgl ver, fix profiler bug 2025-05-24 19:13:50 -04:00
README.md integrate cmake + ninja 2024-12-01 23:45:29 -05:00
template.json cleaning up top level folder 2024-11-23 14:49:57 -05:00
tsconfig.json tsconfig update 2025-05-16 10:48:05 -04:00

README.md

Storm Engine

A multiplayer-focused game engine

Building

Cloning

When cloning the repo, make sure to grab all submodules with git clone --recurse-submodules git@git.austinwhoover.com:studiorailgun/Renderer.git

Windows

  1. Install
  1. From choco install
  1. Run build.sh

The build will be in <Project Directory>/build

Alternate Build Profiles

Several build profiles are defined in maven to support different functions

  • fast - Only runs the fast unit tests
  • integration - Runs the integration tests
  • integrationDebug - Runs the integration tests with the memory-debug jar linked

Documentation

Building

The documentation uses Doxygen to build.

On windows, it's recommended to use Doxywizard to build the documentation.

To build

  • Open the file <Project Directory>/docs/Doxyfile
  • Navigate to the Run tab
  • Click Run doxygen
  • Click Show HTML output