-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] pojavlauncher keeps getting blackscreen after installing fabric 1.18.2 with 43 TOTAL mod i have used to optimize my game #5324
Comments
anybody can have a blackscreen anytime, an image does not help lol |
wrong log, send latestlog.txt as said in the issue template |
and be sure to send it as a file and not as output as that generates spam, also delete your previous spam message |
happy or something is also wrong? |
good, remove memoryleakfix |
How?? |
its a mod just delete it |
got it |
I have deleted the mod, now I am about to test it so I will give you an update if it works successfully |
it actually works now. tysm. little bit of the game taking a bit long to load compared to vanilla but that is seriously good! I will close it from now on. |
Describe the bug
when I installed 1.18.2 with fabric alongside with jre-17 runtime everything was about to work perfectly until this happened.
I did use 43 mods to optimize the game however that's before the blackscreen being occurred. The problem MIGHT be through the mods, but idk. none of the YouTube tutorials literally helped me. speaking of YouTube tutorials, all of the vids I watched to fix the problem are from indian people. i did try to fix it all by myself but that didn't work either. the only version it worked is vanilla.
anybody that has a fix, please let me know.
The log file and images/videos
latestlog.txt
Steps To Reproduce
Expected Behavior
I expect my game being launched successfully just like vanilla, not a fully blackscreen from the game.
Platform
Anything else?
this is seriously some sort of bug I have never encountered. Anyways, thank you.
The text was updated successfully, but these errors were encountered: