Performance Tweaks

A guide on how to optimise performance for your Origination instance.

This section is a work-in-progress. More tweaks will be added as time goes on.

The following steps are a list of potential methods you can take to improve your performance and load times for the client. These steps are ideal for those both struggling to run the instance, and for those who want to simply improve the experience.

1. Adding Aikar's Flags as Launch Parameters.

Using Aikar's Flags, an optimimised set of flags for running Minecraft, you can potentially increase your performance. The modified set of flags I recommend for this pack are the following:

-XX:+UseG1GC -XX:+ParallelRefProcEnabled -XX:MaxGCPauseMillis=200 -XX:+UnlockExperimentalVMOptions -XX:+DisableExplicitGC -XX:+AlwaysPreTouch -XX:G1NewSizePercent=30 -XX:G1MaxNewSizePercent=40 -XX:G1HeapRegionSize=8M -XX:G1ReservePercent=20 -XX:G1HeapWastePercent=5 -XX:G1MixedGCCountTarget=4 -XX:InitiatingHeapOccupancyPercent=15 -XX:G1MixedGCLiveThresholdPercent=90 -XX:G1RSetUpdatingPauseTimePercent=5 -XX:SurvivorRatio=32 -XX:+PerfDisableSharedMem -XX:MaxTenuringThreshold=1 -Dusing.aikars.flags=https://mcflags.emc.gs -Daikars.new.flags=true

These can be added in the Java settings of the instance or launcher you are using. I have removed the flags that define the .jar file and min/max memory as most launchers should sort this anyway.

2. Setting the priority of the instance to High.

Enter your Task Manager (CTRL + Shift + ESC), navigate to the "Details" tab, and right-click on the instance while it is open (the name of the instance will be javaw.exe). Hover over priority, and select "High". This will instruct your system to prioritise allocating resources to this application, which can improve performance. Do be aware this can be sometimes detrimental to other applications running in the background.

3. Using a launcher other than CurseForge.

Although CurseForge is arguably the easiest method to get set-up with Origination, you may find performance issues due to Curse insisting that Overwolf must always run in the background while running modpacks through their launcher. Overwolf uses a small amount of RAM from experience (between 200MB-1GB at a time), so using a different launcher may help to free up some memory on low memory systems.

4. Minimise the number of background applications in use.

It should go without saying, but having background applications open will increase resource usage on your system. If you're struggling to run the pack, then maybe try closing some things you aren't using at the time. You can see everything that is running on your PC at once by opening Task Manager (CTRL + Shift + ESC).

5. Modifying settings in-game to maximise performance.

In-game, navigate to Options > Video Settings and adjust your settings to the following to start with:

General

Render Distance: 12 chunks (lower if lag persists).

Shadow Distance: 12 chunks (lower if lag persists).

Simulation Distance: 12 chunks (lower if lag persists).

Fullscreen Resolution: Current.

VSync: Off.

Max Framerate: Keep it to the refresh rate of your monitor or lower (typically in the range of 30-144fps).

Quality

Graphics: Fast.

Clouds: Off.

Weather: Fast.

Leaves Quality: Fast.

Particles: Minimal.

Biome Blend: 0

Entity Distance: 64.

Performance

Chunk Update Threads: Default.

Always Defer Chunk Updates: Off.

Use Block Face Culling: On.

Use Fog Occlusion: On.

Use Entity Culling: On.

Use Particle Culling: On.

Animated Only Visible Textures: On.

Cull Leaves: On.

Cull Leaves Depth: 1

Advanced

Leave all as default, unless you know how and why you'd change these.

MoreCulling

Leave all as default, unless you know how and why you'd change these.

Animations

These shouldn't impact performance much. But disable all if you absolutely need to save on resources.

Particles

These shouldn't impact performance much. But disable all if you absolutely need to save on resources. If your world has a farm or chunk that is generating a lot of one particular particle, feel free to disable it to help with performance.

Details

Mostly preference, shouldn't impact performance much. Weather can be disabled if you experience lag spikes during rain and snow.

Render

Mostly preference again, but a lot of rendered blocks/entities might be the cause of some lag in some instances. So feel free to disable some of these to improve resource use again.