I died, and after breaking my grave a zombie stole my gear..Now he is flying around...And i can't reach him, i hope it runs out of power
seems he's having a great time up there
I died, and after breaking my grave a zombie stole my gear..Now he is flying around...And i can't reach him, i hope it runs out of power
I died, and after breaking my grave a zombie stole my gear..Now he is flying around...And i can't reach him, i hope it runs out of power
I died, and after breaking my grave a zombie stole my gear..Now he is flying around...And i can't reach him, i hope it runs out of power
*plays Chariots of Fire on the world's smallest violin*
I died, and after breaking my grave a zombie stole my gear..Now he is flying around...And i can't reach him, i hope it runs out of power
*plays Chariots of Fire on the world's smallest violin*
^This, except world's worst violinist playing the violin
It shouldn't be using 8-10 GB in the first place, let alone increasing. My RAM usage sits around 3.5 GB.Is anyone getting memory leaks with this modpack? It's normally starts around 8-10 Gigs for me, then shoots up to 15 Gigs max.
That's ok, I ran into my doppleganger once (mob that has the same armor and weapon as you) on Clouds of Darkness in the TF. I was wearing a jetpack and infused armor so strong that I didn't take damage from mobs... and now so was he. Was a pretty epic battle, and it ended by me using blocks to trap him into a corner and leaving him there.
You should not have that much RAM allocated. Too much memory is as bad as not enough. 2.5-3 gigs is all the pack needs. I am running 64x textures with only 3.25 gig allocated with no issues using Java 8 64 bit.Is anyone getting memory leaks with this modpack? It's normally starts around 8-10 Gigs for me, then shoots up to 15 Gigs max.
BTW, in case you are using infinity I just fixed a bug in RFTools that would cause crashes in the following situation:
I asked the infinity maintainers to update the pack soon but in the mean time you can manually put rftools 2.31b there. It doesn't change anything else besides fixing this bug:
- You are playing on a server
- You are in the overworld
- You teleport to an RFTools dimension
http://www.curse.com/mc-mods/minecraft/224641-rftools#t1:other-downloads
Is this fix part of 1.0.1? We have 1.0.0 on our server and people are really annoyed with these bugs?
I'll give it a try. When will 1.0.2 be ready, because if it's just around the corner I'll just ask my server host to update to 1.0.2 when it becomes recommended.I know that 1.0.2 has 2.40 which is also ok but 1.0.2 is not yet recommended (although we have been using it a lot the past few days with no issues). I have no idea what is in 1.0.1 though. Perhaps try updating a local client and see if it contains rftools 2.31b?
I'm using Java 7 (I've read older packs - older Forge versions mainly - may not work right with java 8).You should not have that much RAM allocated. Too much memory is as bad as not enough. 2.5-3 gigs is all the pack needs. I am running 64x textures with only 3.25 gig allocated with no issues using Java 8 64 bit.
... I tried mapping the entire TF biome range in the 237-255 id block, generated the test world again, and teleported to x = -1900 z = 2450. With great delight, I encountered no Enchanted Forest. Short of any more extensive testing, this seems to fix things.
I'm using Java 7 (I've read older packs - older Forge versions mainly - may not work right with java 8).
Java 7 is even worse at handling memory than Java 8. With Java 7, I would almost guarantee that is your issue. Like I said, more is not better when dealing with how Java uses memory. You only want what you need and no more. So, like I said originally, set it for 2.5-3 gigs and no more. With 64 x texture packs, 3-3.5 is good. If you are using shaders, it might need to be as high as 4 gigs. Anything beyond that is just making it run slower.
As far as Java 8, it doesn't work with older packs because of a Forge issue. If you are not playing old packs, then I would strongly advise upgrading to Java 8. It runs so much better. I gained 20 FPS over Java 7 with all the best JVM arguments while using it with no arguments.
FYI: The version of Thaumic TInkerer packaged with Infinity 1.0.0 and 1.0.1 is bugged, and the Osmotic Enchanter will crash your world when you hit the "go" button or when you try to log back into the world. Manually upgrading to a more recent version (which is not available on Curse- look on Nekosune's jenkins) fixes it.