Post install
This page contains a few things you can do after installing Adrenaline to get better performance, better stability, etc. Some mods are already configured well enough to get improvements, so this guide will not include information about those. Depending on your system, you may or may not see an improvement, however on low-end systems you should notice an improvement.
I recommend adding a few mods for extra features, but this part is optional as some people may just want to have plain vanilla w/ optimization. Here are a few ones I usually add:
- Sodium Extra for an FPS counter, greater particle control and other features
- Reese’s Sodium Options or Xander’s Sodium Options for an improved Sodium menu
- Iris Shaders for OptiFine shader support
- Shared Resources for shared game files across instances
Most people will do this already. If you haven't though, you should. This all depends on your system, so choose what works well for you.
Start by changing your render distance. The higher this number, the further you can see. On low-end systems, this should be set to 4-8 chunks. Mid-range systems will usually work well with 8-16 chunks, and high-end systems should be fine with 12-24 chunks.
After this, you can change your simulation distance. This is the distance in chunks that entities, blocks, fluids, etc are ticked, meaning that things like farms outside of this distance may not work properly. Unless you have areas with big farms and such, the default 5 should work well. If not, use 8-12. This only really affects singleplayer - you won't notice anything while playing on servers.
I recommend keeping V-Sync turned off unless you notice bad screen tearing, which in that case, turn it on or use Adaptive V-Sync. To use Adaptive V-Sync, you will need to install the Sodium Extra mod. If you are using Additive, SE is already included.
In the quality section, set graphics quality to "fast" on low-end systems and "fancy" on mid-range to high-end systems. This will affect if leaves are transparent or not, weather particles, and other things.
Set particles to "minimal" on low-end systems, and "decreased"/"all" on other systems. For greater control over particles, install Sodium Extra.
Before setting your memory used by Minecraft, you should first check your system's memory. To see this on Windows, open up Task Manager, go to the performance tab, and under "memory" you should see the amount you have installed on your system.
Allocating more memory to Minecraft may increase performance greatly, but setting it too high can cause issues as well. If you have a low amount of memory installed, please make sure to keep enough memory for your system. As a general recommendation, 2-4 GB (2048-4096 MB) is usually all you should use for bare Adrenaline/Vanilla. Playing with many mods? I'd suggest 3-6 GB (3074-6144 MB), however you may set this lower if needed. Do what works for you. Never set your allocated memory to the same amount as your installed memory.
In Prism Launcher, you can set your memory by going to Settings > Java > Maximum memory allocation. You may set the minimum memory too, however I haven't noticed any improvement over using the default.
Warning This part is generally meant for advanced users! If you don't understand how to do this, then you should ignore this and stick with what you have now. I will not offer support for setting this up.
For your JVM, I recommend the use of GraalVM. It's the one I personally use and I have not had issues with it. After installing, in whatever your launcher you are using, set your Java runtime. In Prism Launcher, you can go to (Instance?) Settings > Java > Java Runtime.
After this, you should set your Java flags. You can get good flags from this very detailed repository which also includes information about which JVM distribution you should choose, and more. These flags are a great improvement over the defaults.