My pc is quite powerful, and can run shaders fairly well, but I find that if I am in-game, and try switching to another one, the game says it's run out of memory, and returns to the menu. From here I can return to my save, and the shader I tried to switch to, will finally be activated. I have allocated 8GB of ram to the game, surely it can't still be running out? My laptop, which is far weaker, has no issue switching shaders...
With that in mind, I think my minecraft is underperforming, considering the hardware. gtx 1080, 6700k 4.48ghz, 16gb ddr4 ram, SSD, it should run like a breeze, but maybe shader performance is a software limitation? My desktop should be leaving the old laptop in the dust when it comes to fps, but I think it's not really doing much better. But I digress, why am I having issues switching shader on the powerful computer, but not on the weak computer? Thanks.
In my experience the "Minecraft has run out of memory" error screen (not an actual crash) happens if there isn't enough process memory available; in other words, I've seen this happen when using Far render distance with 1 GB allocated, but not less, which can be explained by the fact that a 32 bit program (I have a 32 bit OS) can't use more than 2 GB of memory (actually, in practice this is a maximum; MCMap reports about 1.5 GB available even when Task Manager shows more) and this memory is used not just by Minecraft (the Java heap space) but by the JVM itself as well as OpenGL - for this reason the shaders mod (this also applies to Optifine's shaders and shaders in general) does NOT recommend allocating more than 1-2 GB of memory:
- Java heap size
This can be set in Minecraft Launcher - Edit Profile - JVM Arguments
-Xmx1024M or -Xmx1G is usually enough. 2048M is plenty, depending on render distance and mods. Don't set it too high.
ShadersMod and OpenGL requires a lot of memory outside java heap.
Make sure you have enough memory remaining outside java heap.
This may not be as much of an issue for a 64 bit OS but it can still happen; in particular, Java use a lot more memory than you allocated in-game:
Let's give Minecraft 4 GB of RAM to play with. This would need a PC with at least 8 GB RAM (as the real memory usage is almost double the memory visible in Java).
("at least" will also be higher depending on what else is running, and leaving more memory free will enable the OS to efficiently cache frequently accessed files (Minecraft world save files), improving disk access)
Al right I'm gonna try 2gb of ram. In the meantime, do you think Java would have anything to do with it? I'm currently using the java bundled with MC, but I could try telling it to use my installed 64bit java.
My pc is quite powerful, and can run shaders fairly well, but I find that if I am in-game, and try switching to another one, the game says it's run out of memory, and returns to the menu. From here I can return to my save, and the shader I tried to switch to, will finally be activated. I have allocated 8GB of ram to the game, surely it can't still be running out? My laptop, which is far weaker, has no issue switching shaders...
With that in mind, I think my minecraft is underperforming, considering the hardware. gtx 1080, 6700k 4.48ghz, 16gb ddr4 ram, SSD, it should run like a breeze, but maybe shader performance is a software limitation? My desktop should be leaving the old laptop in the dust when it comes to fps, but I think it's not really doing much better. But I digress, why am I having issues switching shader on the powerful computer, but not on the weak computer? Thanks.
In my experience the "Minecraft has run out of memory" error screen (not an actual crash) happens if there isn't enough process memory available; in other words, I've seen this happen when using Far render distance with 1 GB allocated, but not less, which can be explained by the fact that a 32 bit program (I have a 32 bit OS) can't use more than 2 GB of memory (actually, in practice this is a maximum; MCMap reports about 1.5 GB available even when Task Manager shows more) and this memory is used not just by Minecraft (the Java heap space) but by the JVM itself as well as OpenGL - for this reason the shaders mod (this also applies to Optifine's shaders and shaders in general) does NOT recommend allocating more than 1-2 GB of memory:
This may not be as much of an issue for a 64 bit OS but it can still happen; in particular, Java use a lot more memory than you allocated in-game:
("at least" will also be higher depending on what else is running, and leaving more memory free will enable the OS to efficiently cache frequently accessed files (Minecraft world save files), improving disk access)
TheMasterCaver's First World - possibly the most caved-out world in Minecraft history - includes world download.
TheMasterCaver's World - my own version of Minecraft largely based on my views of how the game should have evolved since 1.6.4.
Why do I still play in 1.6.4?
Al right I'm gonna try 2gb of ram. In the meantime, do you think Java would have anything to do with it? I'm currently using the java bundled with MC, but I could try telling it to use my installed 64bit java.
Welp, it just flat-out crashes on launch at 2gb.
I just tried 4gb, still crashing. BTW, while playing earlier, I noticed that it was usually using about 6gb of ram.
6GB of ram lets me get to the menu, but trying to load my world causes i to run out of memory and return to the menu. So it seems 8gb is required...