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
So I can finnaly use PrismLauncher instead of GDLauncher.
This suggestion is unique
I have searched the issue tracker and did not find an issue describing my suggestion, especially not one that has been rejected.
You may use the editor below to elaborate further.
The main issue is blocked JVM Args,
My hardwere has 6.9 GB Ram because 1.1 is hardwere reserved I am using zram for extra ram.
I am alaways using -Xmx -Xms args to allocate memory higher then 6.9. Some modpacks will crash unlikly if I dont allocate 8 GB Ram (Tested with Project Ozone 3) thats modpack is RAM Hungry.
Sorry for my bad english.
The text was updated successfully, but these errors were encountered:
Can you explain what you mean by skipping the "checkJVMArgs()"? What does GDLauncher do here that you're asking for
The launcher stops him from allocating more than 6.9 GB of his 8 GB ram because 1.1 GB is hardware reserved. So he tried using the -Xmx-Xms JVM args to allocate it but the launcher doesn't let him do that aswell
Role
To be simple / play modpacks.
Suggestion
A checkbox that bypass a checkJVMArgs()
Benefit
So I can finnaly use PrismLauncher instead of GDLauncher.
This suggestion is unique
You may use the editor below to elaborate further.
The main issue is blocked JVM Args,
My hardwere has 6.9 GB Ram because 1.1 is hardwere reserved I am using zram for extra ram.
I am alaways using -Xmx -Xms args to allocate memory higher then 6.9. Some modpacks will crash unlikly if I dont allocate 8 GB Ram (Tested with Project Ozone 3) thats modpack is RAM Hungry.
Sorry for my bad english.
The text was updated successfully, but these errors were encountered: