Weird Red Hand
My hand is red, goes away when facing a specific direction and when shaders are on.
This happened after DH updated and my external hard drive unplugged randomly and caused the game to immediately crash (don't ask why mc is on my external hdd). This is on a Nightly build.
Removing the
DistantHorizons.sqlite file didn't fix the problem, might be a problem with the update or mod compatibility.
Using Prism Launcher, Windows 10, MC 1.20.1 w/ Fabric Loader v0.15.11Solution:Jump to solution
My Solution for future reference:
If you have a red hand with Distant Horizons and the Create mod is installed, you need to switch to the "batching" backend of flywheel. This can be done with typing
/flywheel backend batching in chat.
This can also be changed through the Flywheel config file, located in .minecraft\config. If Minecraft is installed on your boot drive and you use the Minecraft launcher this usually can be accessed by putting %APPDATA%\.minecraft\config into the search bar of Windows Explorer, find flywheel.json or input %APPDATA%\.minecraft\config\flywheel.json into the search bar. Open this file with a text editor like notepad, Visual Studio Code, Notepad++, etc and change backend to exactly BATCHING. Using /flywheel backend batching changes the config file for you though.
...27 Replies
perhaps a debug setting? idk
no it isn't
We think the problem might be an incompatibility between flywheel and DH. Flywheel comes shipped with create right? Can you try turning it off?
Either turn off DH blending or Flywheel backend
i don't think you can disable flywheel, although it does come with create. i think disabling it would break create too.
what do you mean "DH Blending", where could i disable it?
still have issue just it doesn't affect the hand anymore?
You can. Type/flywheel backend or batching (idk the difference). You should only see a fps difference, it should still work
Somewhere in advanced, graphics. I forgot the full path
Advanced > quality > rendering?
Something like that
The same thing happened to me yesterday, for me it didn't work changing it on the config menu, you need to go to minecraft folder, then condig, find flywheel.json and change the backend parameter to "OFF", by default is on "INSTANCING"
and create still works perfectly, at least for me
and rebooting mc after doing that
If you want to change the settings in file manually, instead of restarting the game after change, it is much better to change it with the game closed
Some mods might save the config during the game closeup and it would override the change you just made
true
will try later
Using the Batching backend of flywheel fixes the issue
Solution
My Solution for future reference:
If you have a red hand with Distant Horizons and the Create mod is installed, you need to switch to the "batching" backend of flywheel. This can be done with typing
/flywheel backend batching in chat.
This can also be changed through the Flywheel config file, located in .minecraft\config. If Minecraft is installed on your boot drive and you use the Minecraft launcher this usually can be accessed by putting %APPDATA%\.minecraft\config into the search bar of Windows Explorer, find flywheel.json or input %APPDATA%\.minecraft\config\flywheel.json into the search bar. Open this file with a text editor like notepad, Visual Studio Code, Notepad++, etc and change backend to exactly BATCHING. Using /flywheel backend batching changes the config file for you though.
Can also be solved by turning Vanilla Fade Mode to OFF.
DH Settings > Advanced options > Graphics > Quality > Option is at the bottom
This allows you to keep the flywheel backend on instancing.Do you have AMD or NVIDIA GPU?
nvidia, yes
For now for all the people with NVIDIA GPU setting
Vanilla Fade Mode to single pass was enought to fix the issuei know, i edited it
wait
read that wrong
Can also be solved by turning Vanilla Fade Mode to OFF.
setting it to single pass did not fix the issue for me
Well, then why it fixes the bug for me and Puhpine?
no clue
all computers are different
What exact model?
Do you have the newest driver?
it would be better to give a solution that is more likely to fix the issue instead of a solution that only works for some
1650 and no
Well, I use 2.3 only for the blending so disabling the blending is not a better fix then using DH 2.2.1 for me
I'm sure I'm not alone in this. The single pass fix and flywheel backend are the only fixes in my case and skipping over one of them, because it does not work for 1 in 2 people is not a good idea in my opinion
Maybe try updating it and see if anything changed?
IDK
use the solution that works best for you