@Hambeau
I tried it with an unlocked pack, and even the one I made myself (which I cannot even lock ^^). Nothing changes.
I even went so far now to make a complete reinstall of anything minecraft related (this time even remembered to delete the folders in %appdata%). Including a reinstallation of java (have a 64bit system and using the newest 64 bit version of it).
Sadly everything without any real result, besides that Vanilla minecraft runs with clear, unchangeable 3GB allocated memory now (instead of 2.7GB) but curse is still the same.
Weird thing is, that when I use the FTB-launcher it works completly fine. I tell it to use 4GB, it uses 4GB. Not sure what is different between this launcher and the others.
Pretty much tried any settings in the curse-launcher and minecraft launcher now which changes stuff, nothing works.
Only weird thing I noticed now is, that the task-manager says the java-app (so minecraft) uses 4GB of RAM (no matter what I allocate
), but minecraft itself says it uses only 2.7GB.
I was already told that from the launcher-allocated memory not 100% reaches minecraft itself, but is it normal that the other processes that lowers this number devours anything over 2.7GB.
I'm really at my wit's end now, especially since I have so many different numbers now which makes no sense for me:
- Task manager says minecraft 'always' uses around 3'600~3'900 RAM
- Minecraft itself says it always uses ~3GB in vanilla and ~2.7GB in using curse
These numbers never changes no matter how much I play around with the -Xmx java argument or with curse-settings, like anything is completly ignored by my minecraft
[edit]
Maybe I should ask around in the mojang forum, since vanilla minecraft is effected, too. Slowly feel bad to use this thread... it 'was' meant to get a simple answer, but I guess my minecraft wants more attention, heh ^^"
[edit 2]
Finally found the culprit! (annoying the mojang support-chat gave me hint where to look, hihihi)
I had - no idea from when x.x - a java argument in the enviromental variables that locked it to max 3GB. Guess the ftb-launcher overwrites this variable, but other launcher gets overwritten by it.
Thanks alot for all the help here! Phew, was quiet a search for this one lil thing I must have set up like ages ago x.x