what happened in 1.7.x

[Runebooke]

what happened in 1.7.x? To be specific, I am not getting the same performance as I did with the 1.6.4 packs.
I used to get insane(120+) fps on servers; now, I get 60. This problem is also noticed in SSP. I did manage to correct the issue with Optifine, but before I did not need it. I am just wondering if this is me, or is this something new that happened with Minecraft?

 

[rhn]

what happened in 1.7.x? To be specific, I am not getting the same performance as I did with the 1.6.4 packs.
I used to get insane(120+) fps on servers; now, I get 60. This problem is also noticed in SSP. I did manage to correct the issue with Optifine, but before I did not need it. I am just wondering if this is me, or is this something new that happened with Minecraft?

This is a common thing with 1.7. It's performance is pretty bad. Why? Mojang+JAVA+some great idea we didn't need or want I guess.
It can be helped a bit with Fastcraft, but other than that you just have to suck it up I guess. Just so sad that everyone was in such a hurry to stop development on 1.6 prematurely, and 1.8 sounds quite a ways off...

 

[gold49]

1.7 has screwed up a lot of people's fps, do not know the exact reasons off the top of my head but I believe it is mostly unoptimized code in the base game.
There are also some other mods to help performance in 1.7 like fastcraft and the new one from cofh team, I think it is called cofh tweaks or something.

 

[Padfoote]

and 1.8 sounds quite a ways off...

Thankfully. The performance there is far worse than 1.7.

 

[Crhymez]

Thankfully. The performance there is far worse than 1.7.

Worse? I get an insane amount of fps in 1.8 compared to 1.7
Isnt Fastcraft using the same "code" of 1.8 in 1.7 to help`?

 

[lenscas]

I just love the fact that no one said to make sure that vsync is off.

As for 1.8 vs 1.7 I can't run even a single mod in 1.7 without fastcraft and with it I can easily hit 70+ fps on a modpack with about 160 mods. in 1.8 I can get 100+ fps. I don't have vanilla 1.7.10 data as I never played it.

 

[malicious_bloke]

tbh with a combination of fastcraft and cutting down my modlists from the frankly absurd ~200 in Monster to a more sensible 120-130 in my altered version of Infinity, my FPS is actually better now than it was in 1.6.4

It might also be that I know more tricks for reducing lag in modded MC now, so I don't build wizard's towers with every single automated process being rendered in the same chunk :3

 

[McJty]

I'm getting better performance in 1.7 (compared to 1.6) with the following: Java 8, Fastcraft, Optifine.

 

[Dezz]

I'm getting better performance in 1.7 (compared to 1.6) with the following: Java 8, Fastcraft, Optifine.

See, for me, Java 8 causes large lag spikes where my game freezes temporarily

 

[Hambeau]

1.7.x versions were actually performing better than 1.6 versions, until Mojang released 1.7.10 and re-introduced some kind of bug, possibly a rendering issue.

 

[FyberOptic]

Worse? I get an insane amount of fps in 1.8 compared to 1.7
Isnt Fastcraft using the same "code" of 1.8 in 1.7 to help`?

No, 1.8 uses an almost entirely rewritten render engine other than a few minor bits, there's no way to easily recreate that in 1.7 nor would you want to.

 

[asb3pe]

See, for me, Java 8 causes large lag spikes where my game freezes temporarily

And my experience is the exact opposite. I used to have to jump thru hoops to get java 7 to work (experimenting with all those java argument strings). Now with java 8 the game runs great and I don't have to use a single java argument either. Zero headaches with Infinity modpack on java 8 compared to when I was playing Monster modpack on java 7. Everybody's computer is different, all I can suggest is that you view gaming like you would any hobby - which means, if it's something you enjoy, then spend the money on it. Buy (or better yet, build) the best computer you can, and keep it on the cutting edge, upgrade/replace stuff every year.

Here's a reddit post that's related to java and RAM issues, posted yesterday, I thought there were some good comments in it, worth a shot to read thru and see if you can find something that might help you.

http://www.reddit.com/r/feedthebeas...emitechnical_explanation_of_why_you_shouldnt/

Specifically, I noted this comment in the middle of the page:
"Apart from not allocating too much RAM in the first place I highly recommend that anyone with a modern multicore CPU should use the -XX:+UseConcMarkSweepGC argument. This garbage collector is specifically designed for low latency applications.
You can also tell it to try and keep GC pauses under a certain number of milliseconds using the -XX:MaxGCPauseMillis=? argument, but it can and will ignore that limit if it can't keep up.
Those are the only arguments I use (with Java 8):
-XX:+UseConcMarkSweepGC -XX:MaxGCPauseMillis=50"

 

[Cptqrk]

See, for me, Java 8 causes large lag spikes where my game freezes temporarily

Are you using Aroma Backup? I notice the freezes too, but only when Aroma is doing it's thing...

/shrug

Question @asb3pe the java argument you have there.. is the " at the end a typo, or needed?

-XX:+UseConcMarkSweepGC -XX:MaxGCPauseMillis=50
or
-XX:+UseConcMarkSweepGC -XX:MaxGCPauseMillis=50"
?

 

[asb3pe]

Are you using Aroma Backup? I notice the freezes too, but only when Aroma is doing it's thing...

/shrug

Question @asb3pe the java argument you have there.. is the " at the end a typo, or needed?
-XX:MaxGCPauseMillis=50
or
-XX:+UseConcMarkSweepGC -XX:MaxGCPauseMillis=50"
?

don't use any " marks, that was from my quoting of the reddit posting. Sorry for the confusion. The first one is the correct text to put into the FTB Launcher under advanced options. I think you could just use one argument: -XX:+UseConcMarkSweepGC

The second argument with the 50 milliseconds isn't nearly as important IMO since he says it will be ignored anyway if java can't keep up with Garbage Collection.