The Meaning of Life, the Universe, and Everything.
Location:
In a little piggy hut :D
Join Date:
3/21/2015
Posts:
150
Location:
In a little piggy hut :D
Minecraft:
Piggyfacepork
Member Details
This mod is AMAZING! it gets rid of SO much lag and it has other awesome features, not just stoping lag! (Stuff like zoom, transparent water and multi textured blocks!)
and the the installation is SUPER easy! 4 clicks and you are ready to go!
6 out of 5 Diamonds @sp614x Thank you for making this mod!
Rollback Post to RevisionRollBack
Hello I'm you're friendly neighborhood Piggy! I'm not very active on the forums but when i'm on i like to help people and look at suggestions.
Although thinking about it, it's been a couple of years since I last did anything Java related, so I think I mixed that up a little.
-Xmx = The "Maximum" amount of RAM that can be used
-Xms = The "Initial" or Minimum amount of RAM that can be used
So, setting -Xmx and -Xms to, lets say, 4GB. When Minecraft loads a world or chunk, it will use the minimum amount which is set to 4GB, but when you move your character again causing the game to load more chunks, it has nothing left, because the maximum it can use is 4GB but it's already used all of that as the minimum is 4GB.
So it has to immediately dump the memory as fast as possible to free it and then load 4GB again. Which causes latency and crashes as it can't do it fast enough.
By setting -Xmx to 4GB and -Xms to 256MB, if a chunk needs to be loaded, it can use as much or little as it needs between 256MB and 4GB to load it. 4GB is Way more than will ever be needed, so it most cases the first call will just use 256MB - 1GB, then the next call will use 256MB to 1GB, by this time the first call is complete and the memory can dump it and get it ready for the next time it's needed. So you always have some in reserve and Minecraft can used as little or much as it needs.
I think that's more accurate. Damn, I think my memory is maxed out and has been dumped... Or I could just be getting old
That makes no sense at all.
-Xmx sets the maximum amount of memory usable for the Heap
-Xms sets the amount of memory that shall be allocated at the point the JVM starts
Both has nothing to do with the memory minecraft uses for chunk handling, it only defines when and how much heap should be allocated from the OS, because it makes a difference if java access already allocated memory or have to allocate memory before it can use it. If you specify Xms and Xmx on the same size, it only means that the garbage collector will run less often as because it never needs to free allocated memory back to the system. So if you walk around and a lot of chunks are not displayed anymore they are still in this memory and will only be cleaned up if minecraft needs more memory and the heap is already full.
Xms == Xmx, means wasting memory if not need but theoretically save some nanoseconds because there is no need for additional memory allocations (malloc at start)
Xms =< Xmx, less memory wasting, but if more memory needed your JVM has to spend some nanoseconds to ask the system for more memory (malloc as needed)
Xmn should not be set, or only set if you know you need it, with this setting you set the size of the "new objects space" in the Heap, so every time minecraft instantiate a new object its memory sits there, this area sees the garbage collector more often, and objects from here are only moved to the regular heap if they "survive" a couple of garbage collections.
Hint: if you really have plenty of RAM, never set it to more than a littlebit under 32G, because Java uses compressed memory pointers, this is the maximum amount of ram allocatable with 32bit long addresses, as soon as you hit the barrier, java switches to 64bit pointer and this will slow down your application significantly...
-Xmx sets the maximum amount of memory usable for the Heap
-Xms sets the amount of memory that shall be allocated at the point the JVM starts
-Snip-
Well, thank you for explaining it properly, I guess I was further off than I thought. I did say in my OP that I'm no expert in Java and the little I did do with Java was years ago.
The main thing is, the original guy was helped and no longer has an issue, and people can read the technical stuff about it if they want, too.
Hey sp614x I know you are busy with the 1.9 update, however I could really use these features. If you get the time could you please supply the shaders with Irregular z-buffers for both the shadow map and view space, and also access to the nvidia conservation rasterizer. I'm aware that it is an opengl 4.3 extension however we can run it in 430 compatibility.
is Parallax Occlusion Mapping not working with 1.9 yet?
As far as I know yes, POM is working just fine, I have had it enabled yesterday. But the texture pack you use has to support it with the proper normal and bump maps.
ok so do you have a laptop or a pc? if you have a laptop sorry i cant help you. if you have a pc do you use a hdmi splitter? if yes try without. if no try a new hdmi cable. if you dont use a hdmi cable sorry i kant help you
This mod is AMAZING! it gets rid of SO much lag and it has other awesome features, not just stoping lag! (Stuff like zoom, transparent water and multi textured blocks!)
and the the installation is SUPER easy! 4 clicks and you are ready to go!
6 out of 5 Diamonds @sp614x Thank you for making this mod!
Hello I'm you're friendly neighborhood Piggy! I'm not very active on the forums but when i'm on i like to help people and look at suggestions.
That makes no sense at all.
-Xmx sets the maximum amount of memory usable for the Heap
-Xms sets the amount of memory that shall be allocated at the point the JVM starts
Both has nothing to do with the memory minecraft uses for chunk handling, it only defines when and how much heap should be allocated from the OS, because it makes a difference if java access already allocated memory or have to allocate memory before it can use it. If you specify Xms and Xmx on the same size, it only means that the garbage collector will run less often as because it never needs to free allocated memory back to the system. So if you walk around and a lot of chunks are not displayed anymore they are still in this memory and will only be cleaned up if minecraft needs more memory and the heap is already full.
Xms == Xmx, means wasting memory if not need but theoretically save some nanoseconds because there is no need for additional memory allocations (malloc at start)
Xms =< Xmx, less memory wasting, but if more memory needed your JVM has to spend some nanoseconds to ask the system for more memory (malloc as needed)
Xmn should not be set, or only set if you know you need it, with this setting you set the size of the "new objects space" in the Heap, so every time minecraft instantiate a new object its memory sits there, this area sees the garbage collector more often, and objects from here are only moved to the regular heap if they "survive" a couple of garbage collections.
Hint: if you really have plenty of RAM, never set it to more than a littlebit under 32G, because Java uses compressed memory pointers, this is the maximum amount of ram allocatable with 32bit long addresses, as soon as you hit the barrier, java switches to 64bit pointer and this will slow down your application significantly...
Well, thank you for explaining it properly, I guess I was further off than I thought. I did say in my OP that I'm no expert in Java and the little I did do with Java was years ago.
The main thing is, the original guy was helped and no longer has an issue, and people can read the technical stuff about it if they want, too.
Magic Launcher says there are "no mods available". Manually moving the files into the jar didn't help either.
Any help please?
Hey sp614x I know you are busy with the 1.9 update, however I could really use these features. If you get the time could you please supply the shaders with Irregular z-buffers for both the shadow map and view space, and also access to the nvidia conservation rasterizer. I'm aware that it is an opengl 4.3 extension however we can run it in 430 compatibility.
Conservative raster: https://developer.nvidia.com/sites/default/files/akamai/opengl/specs/GL_NV_conservative_raster.txt
aaaannd here: https://developer.nvidia.com/gpugems/GPUGems2/gpugems2_chapter42.html
Irregular Z-Buffers: https://en.wikipedia.org/wiki/Irregular_Z-buffer
and here: http://pl887.pairlitesite.com/papers/ism-TR/TR04-09.pdf
that error always keep spamming me..
very nice mod!
is Parallax Occlusion Mapping not working with 1.9 yet?
site optifine.net down
I sure hope you mean you "donated". You didn't buy anything, you're supporting sp614x so he can continue to develop the mod.
As far as I know yes, POM is working just fine, I have had it enabled yesterday. But the texture pack you use has to support it with the proper normal and bump maps.
ok so do you have a laptop or a pc? if you have a laptop sorry i cant help you. if you have a pc do you use a hdmi splitter? if yes try without. if no try a new hdmi cable. if you dont use a hdmi cable sorry i kant help you
That makes sense. It worked too! Thanks!
There was something like this a little while back. I cant find the post right now, but if you look back a bit you may find something.
i think i found a Connected Textures bug, the sideways log texture displays like this when the affected texture points to the north and east.
Does anyone know how i can get this to work for 1.9.2?
Wait.
Wise MCers don't update until all the Mods they use do...
Links to pdf format, downloadable, command lists for (these often clarify/expand descriptions, and where possible link to the author's posting):
MoreCommands: http://www.mediafire.com/view/qjc9c6klcnp660e/CmdLstMoreCommands.pdf
WorldEdit: http://www.mediafire.com/view/bi7r00xd9rgxrrt/WE_Commands.pdf
What? You can easily change versions.
How about you learn to read the rules!