So, lets start with the fact I'm 24 hours into developing a custom modpack for my friends and myself, so the "you seem like a noob" feeling you get when reading this is correct.
That being said, I've used 2 computers with the same results.
I am constantly running out of memory when I try to load a world. I have around 85 mods, and after painstakingly attempting to figure out the compatibility issues, I can load the main MC screen with no issues, so I think the mods are compatible (Because when they weren't, MC wouldn't load the main screen).
My problem comes in loading a world. I load up a single player world (to make sure the mods are playing nicely) and the console shows that it loads spawn, then promptly runs out of memory. I thought it was my crappy work computer, so I borrowed a friends to test the same principles, and same result.
I have tried allocating up to 5GB of memory to Java, and then reduced it incrementally to 1GB.
My computer has 4GB of ram and a Dual Core processor. My friends has 6GB of ram and a quad core processor. I run most other things (I tried mad-pack) on 2GB allocated to Java. Its rough, but I can do it on my crappy work Computer (the 4GB one) with that setting, which is what makes no sense as that has around 130 mods.
I have tried the regular minecraft launcher, and am now using MultiMC5, which is where the below logs came from.
For you techie hounds, here's the entire folder from the files on my friend's computer from the 2GB run (they all seem to have the same, regardless of RAM).
That being said, I've used 2 computers with the same results.
I am constantly running out of memory when I try to load a world. I have around 85 mods, and after painstakingly attempting to figure out the compatibility issues, I can load the main MC screen with no issues, so I think the mods are compatible (Because when they weren't, MC wouldn't load the main screen).
My problem comes in loading a world. I load up a single player world (to make sure the mods are playing nicely) and the console shows that it loads spawn, then promptly runs out of memory. I thought it was my crappy work computer, so I borrowed a friends to test the same principles, and same result.
I have tried allocating up to 5GB of memory to Java, and then reduced it incrementally to 1GB.
My computer has 4GB of ram and a Dual Core processor. My friends has 6GB of ram and a quad core processor. I run most other things (I tried mad-pack) on 2GB allocated to Java. Its rough, but I can do it on my crappy work Computer (the 4GB one) with that setting, which is what makes no sense as that has around 130 mods.
I have tried the regular minecraft launcher, and am now using MultiMC5, which is where the below logs came from.
For you techie hounds, here's the entire folder from the files on my friend's computer from the 2GB run (they all seem to have the same, regardless of RAM).
http://paste.ee/p/qGyyH
Your help is appreciated.
Want to see the world's most gullible person? Click Here!