1.7 modpack performance

[maaltan]

I realize the current 1.7 modpacks are still in development, but i decided to try them out today. I am finding the performance to be absolutely abysmal. The fps is ~1fps .. if i stare at a wall maybe 3fps. the CPU usage is hitting 70-80% which I've never really seen before from minecraft. I let the new world stablize for about 15 minutes and i got up to about 10fps. But as soon as i move it dies again. Minecraft 1.7.2 vanilla runs at locked 60fps.

I have set all the settings i can find to the lowest values and have given the JVM all the memory and threads my machine can handle.

I see this behavior in "the dark trillogy" and "resurrection"

My computer is relatively high end (including a brand new AMD R9 290, cpu is slightly dated intel i7 940 @2.93gz 16gb of ram) and I am using java 7.

Is this just a reflection of the development state of the modpacks or am i going to have to upgrade to 4gzh cpu to play?

Edit:
this is a client side issue. I just booted the multiplayer server to seperate the JVMS. The server sits quietly doing almost nothing while the frontend is burning the cpu. the shift-f3 pie chart shows 90% of time is being used for tick updates.

 

[ljfa]

I doubt that it fixes the issue, but giving Minecraft 16 GB RAM isn't a good idea. You generally shouldn't be using more than 4 GB.
Well you can at least try it.

 

[maaltan]

Yeah... i started at reasonable levels and increased to see if it would help , sorry i forgot to mention that.
I just installed java 1.8, but it didn't seem to help anything.

(FYI for anyone that might drop by, The java page auto-detected the 32 bit version of java 1.8. I recommend locating and downloading the offline 64 bit windows JRE se 1.8.x installer to be sure)

 

[Hambeau]

Giving Minecraft more that about 4GB will cause Java to choke on it's own vomit, pardon the expression.

Earlier this week someone found the apparent typo that causes the problem. and apparently it's in the Mojang 1.7.10 code that checks if a block needs to be rendered or not.

I don't know the details but a comparison that should be ">=64" (64 or larger) was written as "==64" (exactly 64) causing excessive rendering. I understand a fix is coming.

For the time being you can add "FastCraft" to your mod folder to mitigate the problem somewhat. FtB hasn't added it because the author doesn't want to make it available for pack release yet, despite pack developers' begging for it.

Here's a link:

 

[maaltan]

Interesting.... do you have any links, etc about this bug in 1.7.10? Google seems to be failing me.

I was in fact using 1.7.2 vanilla version. I just tried the 1.7.10 and framerate was no longer pegged at 60 (vsync) and was dropping to mid 40s frequently so this seems to be the issue.

 

[mcalpha]

It is not a regression in Vanilla, it's a patch that Forge missed when updating to 1.7.

 

[DeathOfTime]

The java page auto-detected the 32 bit version of java 1.8.

Chrome has a 64bit version. Possibly other browsers as well. Not for sure. The reason java recomends a 32 version is because it detects a 32browser. Though the broswer doesn't really care. The only thing that seems to care is the intel driver detection program. It will only work with a 32bit java. That might have changed by now though.

 

[b0bst3r]

All is resolved using the latest Forge

http://pastebin.com/pZQNPZYC

 

[Hambeau]

I stand corrected. I got the impression somehow that the Mojang code was at fault.

@b0bst3r's link is the one I saw mentioned.

 

[epidemia78]

1.7 became stable enough to suit me a while back even before this fix. Although I did go ahead and update forge and java to version 8 yesterday. Not sure if helping.

 

[Shevron]

All is resolved using the latest Forge

http://pastebin.com/pZQNPZYC

Never managed to really figure out how to update forge in FTB packs? Where does it live?

is FTB/versions/x.x the place, or that's Mojang's MC files?

I'm trying to play DW20's 1.7 pack, and something just doesn't feel right performance-wise. Feels choppy, and every few minutes I get a 15-second complete freeze.

 

[ljfa]

Never managed to really figure out how to update forge in FTB packs? Where does it live?

I have no idea either. But it's easy to do with MultiMC when you make a copy of your instance.

I'm trying to play DW20's 1.7 pack, and something just doesn't feel right performance-wise. Feels choppy, and every few minutes I get a 15-second complete freeze.

I'm experiencing something like this when memory is running low, e.g. when I'm letting my browser run in parallel to the game.
How much RAM dido you have and how much are you giving Minecraft?

 

[Shevron]

Got 4GB (I know - need an upgrade), and assigning 2.5GB to MC when using either MultiMC or FTB launcher.

I've run much larger 1.6 modpacks on this setup, and I don't see why 1.7 modpacks with a lot less mods should need more.

 

[jordsta95]

Got 4GB (I know - need an upgrade), and assigning 2.5GB to MC when using either MultiMC or FTB launcher.

I've run much larger 1.6 modpacks on this setup, and I don't see why 1.7 modpacks with a lot less mods should need more.

http://pastebin.com/pZQNPZYC

Is why,
Seriously, when you have the game doing a billion slow calculations a second (not an exact number) instead of a few thousand fast ones, it causes anything more than vanilla+ (i.e. NEI, WAILA, Iron Chests, and other basic mods) to lag the game to hell.

 

[Shevron]

Is why,
Seriously, when you have the game doing a billion slow calculations a second (not an exact number) instead of a few thousand fast ones, it causes anything more than vanilla+ (i.e. NEI, WAILA, Iron Chests, and other basic mods) to lag the game to hell.

Which is why as asked, where in FTB does Forge reside

Read that pastebin, and I want to apply the latest Forge version (if the latest version pushed out that fix anyways).

I'm quite handy with FTB and its modpacks, configs etc, but never figured out how to update Forge.

 

[jordsta95]

That's because you can't even find the minecraft jar file, or at least I haven't been able to. I believe it references a library folder in your ftb downloads folder: (Folders)
FTB
-Agrarian Skies
-Direwolf201_7
-Library
-Running Red
-Running Red 2: Vampire Money
-etc.

Both Agrarian Skies and Running Red would look in the Library folder for the 1.6.4 minecraft jar file, and then get the forge jar file they require from there too, whereas DW20 and RR2 would get the 1.7.10 jar file, and the correct forge versions from their too...
I don't know if there is a way to change which one it references, but I would assume one of the straggling files in once you open up the modpack folder would be what you need to alter:
Agrarian Skies
-configs
-mods
-etc.
One of the files in there would be what you would edit

 

[Shevron]

I thought Forge resided in the FTB\versions directory, as there's 1.6.4 and 1.7.10 there - but then I downloaded Forge and realised that the jar file sizes are very different, so probably not the ones I would need to change.

Can someone from the FTB team shed some light on this? @Eyamaz ? *wink*

 

[b0bst3r]

...ftb folder....\libraries\net\minecraftforge\forge

 

[Shevron]

Thank you!

 

[mamama1]

Hi,

i've updated forge to 1.7.10-10.13.2.1307 -> no Change in Performance, still only about 15fps and between 90-100% CPU load on a fresh world, not local Server
updated forgeMultipart to 1.7.10-1.1.1.322 -> still no Change in Performance.

I have a Notebook with Core i7 M 620 @ 2,67GHz and 8GB of Memory as well as an nvidia Quadro NVS5100M with 1GB dedicated Video Memory. FTB Ultimate (MC 1.4) runs just fine.

Second Hardware I tried this on is some Core i7 870 @ 2,9GHz, 16GB of Memory and an nvidia Geforce GTX 660Ti with 2GB Memory - even two instances of FTB Ultimate (MC 1.4) run smoothly, FTB Infinity runs at ~10-15 FPS and 90-100% CPU load

Third box, on which Infinity finally works is my newest Core i7 4790 @ 3,6GHz and 16GB of Memory and an nvidia Geforce GTX770.

does anyone have an idea whats the issue here?

thanks!
greets mamama1