problems with infinity

[Worsin]

So i have played with FTB packs for a long time now. I left playing Monster Pack to upgrade to infinity.

I always played with the PureBD 128 textures and had NO problems. Ran it on tripple monitors and had super low CPU usage and set the slider to maybe 4 gigs and still got 100+ FPS

Now with Infinity using the same size textures it wont even run. Ive cranked the RAM slider up to 30 gigs and it will eat 15 gigs with CPU hitting 100% and i get like 1 FPS in game.

Removing the texture pack i get normal framerates and its super fast as you would expect.

Strange thing is i cant even load the game if i have the Ram slider set to what i used to play at. If i dont put it up to 6+ gigs it wont even load to the option screen.

My system is:
Intel 4670 @ 4.5ghz
Duel NVidia 769 GTX 4gb cards in SLI (8 total gigs of video ram)
32 gigs of ram
Java 8 (jre-8u40-windows-x64)
Windows 8.1

My system should be destroying Minecraft but its crashing and trying to eat every ounce of speed and ram i have.

Something is obviously very wrong here.

Any suggestions on how to find the problem are more than welcome.

 

[DriftinFool]

Don't use the setting in the launcher that say "Optimization arguments for fast computers". They made my fps bad and when I hit F7 to see where mobs could spawn, FPS went down to 3-5. Also, with Java 8 get rid of any additional JVM arguments you may have added in the launcher options. The Arguments that worked for Java 7 do not work for Java 8. Don't give it that much RAM. 4 gigs should be the high end. I can't see needing more unless you were trying a 512 texture pack. Personally, my PC is nowhere near as powerful as yours and I am getting around 70 in Infinity using the Invictus, Soartex, or Faithful texture packs from the launcher with only 3 gigs of RAM allocated. That is with an i5 760 OC'd to 3.66, 560 Ti superclocked, and DDR3 @1600mhz.

 

[rhn]

Yeah, you are severely shooting your self in the foot by allocating that much ram to the game. Your OS and other processes are getting starved and have to resort to pagefile(harddrive) which slows everything downs IMMENSELY!
You are also causing JAVA to have massive fuckups with garbage handling with all that memory(basically it spends too many resources/cant keep up unloading/handling the RAM).

 

[Worsin]

Ive been trying to run it on 4 and it wont load.

This is also fresh install with no Java arguements and not using that fast computer setting

 

[rhn]

Ive been trying to run it on 4 and it wont load.

This is also fresh install with no Java arguements and not using that fast computer setting

Infinity + x128 might require more than 4GB. You could try and incrementally increase it until it loads. Give it something like 0.5GB more than that.
But I would consider if you could manage with less than a x128. There is a WORLD of difference between the performance of 1.6 and 1.7. Expect 1/2 or 1/3 the performance you got in Monster. Minecraft is not like other games. It will chew your PC up and spit it out no matter how beefy you think it is.

 

[Dkittrell]

Yup ive always gotten 80+ fps in Modded prior to 1.7, my system wasnt OC at all. Since 1.7 i had fps issues and couldn't understand why as my system is very nice. I ended up having to overclock my video card a little bit and now i dont have any issues. For some reason 1.7.10 is resource hungry and after many attempted fixed this was the only thing that really helped

 

[rhn]

Yup ive always gotten 80+ fps in Modded prior to 1.7, my system wasnt OC at all. Since 1.7 i had fps issues and couldn't understand why as my system is very nice. I ended up having to overclock my video card a little bit and now i dont have any issues. For some reason 1.7.10 is resource hungry and after many attempted fixed this was the only thing that really helped

1.7 is just massively flawed and we cannot move onto 1.8 fast enough 1.8 have things like multicore support etc. so here's hoping that will be a big difference.

Just sucked big time that so many mods couldn't skip 1.6 fast enough and we are now stuck with 1.7...

 

[Worsin]

I still feel like something is wrong, game runs fine till i load a 128 pack and go into game. I honestly don't see how anyone can run 128 if my system cannot.

 

[asb3pe]

I still feel like something is wrong, game runs fine till i load a 128 pack and go into game. I honestly don't see how anyone can run 128 if my system cannot.

I used to love Sphax resource pack. Wouldn't play without it. However, I found in the 1.7 modpacks, even on my very good computer (I build my own rigs with the best components, I have 32 gigs of RAM for instance), I had trouble running them with a 128x resource pack. I could get 64x to work, but I still had herky-jerky lag at times.

So I went back to vanilla textures, and everything runs fine on 4GB or less. I suggest you try the same thing. Yeah, I know it sux not to have the cool textures, but if it's a choice between looking good or running good... take the latter every time. IMO of course. You could keep trying to get it to work, but... I just gave up because I'd rather play than futz around. Vanilla it is. You get used to it, kinda sorta.

 

[Worsin]

Yeah, im getting to the point real quick where i just hang it up till 1.8 lol. Its mind blowing how much my speed tanked.

 

[Shakie666]

Java applications should NOT be allocated more than 4gb of RAM under any circumstances. Can't run it with a x128 texture pack? Tough luck, use something less demanding (sorry if I sound rude, but you'll never increase performance by allocating more than 4gb of RAM, that's just how java works).

EDIT: Just found this very helpful analogy from the 'ask simple question' thread as to why more than 4gb of RAM is bad:

Compare your PC to a workshop. The Hard disks are the shelves with tools and materials, the CPU is the trained carpenter and the RAM is the workbench. Bigger building projects might require bigger workbenches to house them. But your projects will not be finished faster from having an oversized work bench. The speed is purely a matter of the speed of the worker(CPU) (and visual representation there off(GPU)). In the case of JAVA it is actually bad to have a too large workbench for a small project due to all the work needed to be spend on keeping the workbench clean all the time.

When you allocate memory to something you are reserving your workbench for one building project only(be there a need for it full time or not). This means that any other building projects will just have to find another work bench. But if you don't have more workbenches it will either have to wait(in which case your PC crashes because OS processes are not allowed to run) or these other projects are forced to be worked on in unconventional places like on the storage shelves(HDs).

Of course its not that simple, as a x128 texture pack obviously needs more RAM, but as I said, java just doesn't like more than 4gb.

 

[asb3pe]

I ran Monster modpack (1.6.4 Minecraft) for many months using 7GB of allocated RAM and 128x Sphax resource pack (it wouldn't run smoothly with just 4GB) but I also had a nice long string of java arguments that seemed to work for me. It ran smooth as glass with 7 gigs... so I hesitate when people say "don't use more than 4 gigs", I'm not entirely certain that is true in all cases, despite this commonly-cited wisdom (related to java GC, Garbage Collection).

But yeah, in 1.7 modpacks, allocating extra RAM just caused me problems nonstop. It probably didn't help that I also upgraded to java v8, and I couldn't find any java arguments that helped the situation, it was just bad lag all the time no matter what. Even with a x64 resources pack, I couldn't get it to run smoothly like I required it to, so I simply gave up and dropped down to 4GB RAM and no resource pack at all and no java arguments. The 1.7 modpacks run perfectly smooth, the only drawback is that I can't run my preferred "cartoon-land" Sphax textures. Oh well, life goes on.

 

[rhn]

Yeah, im getting to the point real quick where i just hang it up till 1.8 lol. Its mind blowing how much my speed tanked.

Seriously, why not just get the x64 version of Sphax? Should run "decently" with that.
Or have some fun with the ton of 1.6 packs that are available. I am personally still playing TPPI for example.

 

[EndlessFields]

I also don't mean to sound rude but you said yourself that the pack runs fine without Sphax x128. Have you tried asking on their support forums instead? Since obviously FTB and Infinity are running fine on their own.