You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 20, 2022. It is now read-only.
So this isn't a ManyMC specific issue, however on 1.12.2 shaders on M1 are very broken and even on 1.18 there are weird artefacts, BSL shaders also have a broken font. On 1.12.2 shaders however sometimes lock game to very low fps and don't use full performance - 10 percent of the times I get 50fps, while 90 I get 4 fps and the MacBook doesn't get hot at all. Also looking through leaves blocks beyond don't render. Also seus v10 shaders work on normal MacBooks after a fix but not on M1
To reproduce
Steps to reproduce the behavior:
Install 1.12.22.
Install optifine
add shaders
look through leaves or launch multiple times
Screenshots
-BSL when its low fps + leaves issues
-SEUS v10 that would work on not M1
System configuration
ManyMC version: 0.1.2
Java version: [e.g. Azul JDK 8)]
M1 Pro
The text was updated successfully, but these errors were encountered:
Yep, thank apple's OpenGL implementation for this. There's nothing straightforward we can do, some people are working on a better OpenGL but that will take time. Feel free to ask on discord for more info on working shaders and OpenGL status.
Describe the bug
So this isn't a ManyMC specific issue, however on 1.12.2 shaders on M1 are very broken and even on 1.18 there are weird artefacts, BSL shaders also have a broken font. On 1.12.2 shaders however sometimes lock game to very low fps and don't use full performance - 10 percent of the times I get 50fps, while 90 I get 4 fps and the MacBook doesn't get hot at all. Also looking through leaves blocks beyond don't render. Also seus v10 shaders work on normal MacBooks after a fix but not on M1
To reproduce
Steps to reproduce the behavior:
Screenshots
-BSL when its low fps + leaves issues


-SEUS v10 that would work on not M1
System configuration
The text was updated successfully, but these errors were encountered: