-
Notifications
You must be signed in to change notification settings - Fork 116
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
Java Virtual Machine Launcher Forge #568
Comments
Check the instance logs. You may need to increase the amount of memory allocated to the java instance- the log of you trying to run it will say something to that effect. If they do not, can you post them here? You can change the java settings globally in the settings or per-instance in the instance options. I had a similar thing on my machine for forge 1.12.2 but increasing from 256->1024mb in the global settings fixed it. |
The issue was I had the memory allocated too high |
This is causing some older modpacks to be unplayable as the maximum amount of memory that can be allocated is capped at 1024mb |
Are you referring to this value? In that case the maximum value is the amount of that launcher is able to access, not hard capped at 1024 (see my example below) You might need to allow your computer to allow more memory to the system/JRE. Which modpacks in particular are you haivng trouble with? I can try on mine |
Describe the bug
Works:
1.20.1
1.18.2
Doesnt:
1.12.2
1.16.5
Steps to reproduce
Expected behavior
To open minecraft.
Additional context
No response
The text was updated successfully, but these errors were encountered: