c438fb57ca
- Add workaround for race condition flipping the "mergeable" bit for instance pages - Sometimes a page would end up full while another thread was racing to set the mergeable bit, so when we later tried to merge pages we'd get an array index out of bounds - This change makes it so we only ever set the mergeable bit and handle the case of a full page when trying to merge - Should also help us avoid the alternative case where a page that is actually mergeable isn't marked as such |
||
|---|---|---|
| .github | ||
| .idea | ||
| buildSrc | ||
| common | ||
| docs/shader-api | ||
| fabric | ||
| forge | ||
| gradle/wrapper | ||
| vanillinFabric | ||
| vanillinForge | ||
| .editorconfig | ||
| .gitattributes | ||
| .gitignore | ||
| build.gradle.kts | ||
| gradle.properties | ||
| gradlew | ||
| gradlew.bat | ||
| javadoc-options.txt | ||
| Jenkinsfile | ||
| LICENSE.md | ||
| README.md | ||
| settings.gradle.kts | ||
Flywheel
Reinventing the wheel so you don't have to.
About
The goal of this project is to provide tools for mod developers so they no longer have to worry about performance, or limitations of Minecraft's archaic rendering engine. That said, this is primarily an outlet for me to have fun with graphics programming.
Instancing
Flywheel provides an alternate, unified path for entity and block entity rendering that takes advantage of GPU instancing. Flywheel gives the developer the flexibility to define their instance formats and write custom shaders to ingest that data.
To accommodate the developer and leave more in the hands of the engine, Flywheel provides a custom shader loading and templating system to hide the details of the CPU/GPU interface.
Getting Started (For Developers)
Add the following repo and dependency to your build.gradle:
repositories {
maven {
name "createmod maven"
url "https://maven.createmod.net/"
}
}
dependencies {
// On forge
compileOnly fg.deobf("dev.engine-room.flywheel:flywheel-forge-api-${minecraft_version}:${flywheel_version}")
runtimeOnly fg.deobf("dev.engine-room.flywheel:flywheel-forge-${minecraft_version}:${flywheel_version}")
// With loom
modApi "dev.engine-room.flywheel:flywheel-fabric-api-${minecraft_version}:${flywheel_version}"
modImplementation "dev.engine-room.flywheel:flywheel-fabric-${minecraft_version}:${flywheel_version}"
}
${flywheel_version} gets replaced by the version of Flywheel you want to use, eg. 1.0.0-beta
${minecraft_version} gets replaced by the version of Minecraft you're on, eg. 1.20.1
For a list of available Flywheel versions, you can check the maven.
If you aren't using mixed mappings (or just want to be safe), add the following properties to your run configurations:
property 'mixin.env.remapRefMap', 'true'
property 'mixin.env.refMapRemappingFile', "${projectDir}/build/createSrgToMcp/output.srg"
This ensures that Flywheel's mixins get properly loaded in your dev env.