The Meaning of Life, the Universe, and Everything.
Join Date:
1/13/2018
Posts:
47
Member Details
Well I see I'm far from the only one having trouble. 1.13 certainly slowed down my minecraft significantly, but 1.13.2, which was supposed to improve performance, only made it worse for me. The performance isn't that much worse (not better either) but it feels bugged up beyond belief. The first time I played 1.13.2 the game crashed when I tried to launch. Then it crashed when I tried to open a world. Choosing a different resource pack took multiple tries before it worked. Then patches of ground started turning invisible, water and clouds flicker, and the game crashes. New and updated worlds seem to now work, sort of, but I'm fearing that 1.14 won't be playable for me, at least not until I get a new pc.
While i agree 1.13.2 is a mess at best, I still hold hope that Mojang will see the error in their ways and take a step back to optimize the game. I have lag all the without optifine for 1.13.2. My current computer specs are well above the suggested boasting a 1080 ti GPU. All of the issues stemming in minecraft today are caused by a lack of optimization and proper bug testing. While Mojang is attempting to move forwards, I just hope they have learned their lesson and are optimizing 1.14 to play much the same at 1.12.2 does.
I really miss minecraft 1.2.5 and earlier, before 1.3, when they made singleplayer internally use a multiplayer server. Basically, playing singleplayer = multiplayer, except the server is run on your machine.
Now this indeed makes it easier for developers to implement features, and players get the 'Open to LAN', so they can also more easily LAN party with friends, but for slightly outdated machines, it will lag in a lot of occasions, especially when modding.
Obviously some versions are better optimized than others. Personally, I haven't had much trouble up until 1.12. But now it's a mess. It really bothers me and I wish we could go back to single thread singleplayer.
/snip/ However, if people can develop mods like optifine that boost fps, then why can’t a large team of professionals fix thier code? Do they just not care? Personally I feel like they are trying to push people to the bedrock edition - which is both a good and a bad thing.
Hope you understood my points, please tell me if you didn’t quite get my message. =)
Honestly, the recent updates feel like more permanent mods.
Also, refer to just past the halfway point of the following video:
It sure looks like they rendered it with Optifine. For them to get "4k" video on high end machines, they are going to have to get "standard" Minecraft lighting to work on lower end machines. Part of the question is, "How much of this lighting rework is Bedrock exclusive or also applies to Java Edition?" I have no idea, I just know 1.14 claims to have a new lighting engine.
Also, Mojang as a company is taking pains to tell people "Java is not going away." I'd have to look up the specific quote on Twitter, but it's out there often enough to try to get people to accept the official line: Java Edition is not being cut. My server, Copper FerretCraft is both on the Java Server (currently Snapshot 18w44a) and a Bedrock Realm. We play on either as we are inclined, or find something we want to kick around. On the surface, both versions are pretty much the same. The devil is in the details. And WOW what a freakin' devil it is! THAT discussion is NOT this thread. I'll just say the two editions differ enough in their development teams (Redmond for Bedrock, Stockholm for Java Edition) that Redmond is absolutely definitely *NOT* pushing to "win" all the Java Edition fans over to their platform. If you want to start a thread discussing that in detail, we can certainly go through that. But "pushing people from Java to Bedrock" is simply a non-issue between the Redmond team and the Stockholm team.
We are much better off with the following
a) supporting AND THROWING MONEY at sp614x, the Optifine Lead to keep that project going
building and testing new Snapshots like Gnembon in the following video:
Hold Mojang's feet to the fire with specific tests that can be done to show what the problem is so everyone can see it and point a finger to it. Unfortunately, it looks like @TheMasterCaver has been doing this for eons (in Internet time) and we still have our current situation. But he keeps trying anyway, and so should the rest of us.
Considering that the thread goes from August 2018 to November 2018, I guess bumping is allowed as long as the post is on-topic, right?
I'm also having performance issues with 1.13.2, although relatively minor.
In my case, I moved from 1.12.2 which I could run at solid 30 FPS, to 1.13.2 which dipped down to the low 10s on the Nether and 20 to 22 FPS on my base. In both instances, using Optifine (however, I didn't change its configuration when I moved from one version to the other, just to clarify.)
Can someone explain to me why does that happen? What did Mojang change to introduce the performance hits that people have been experiencing and what was their reason to do those changes? :/
Considering that the thread goes from August 2018 to November 2018, I guess bumping is allowed as long as the post is on-topic, right?
I'm also having performance issues with 1.13.2, although relatively minor.
In my case, I moved from 1.12.2 which I could run at solid 30 FPS, to 1.13.2 which dipped down to the low 10s on the Nether and 20 to 22 FPS on my base. In both instances, using Optifine (however, I didn't change its configuration when I moved from one version to the other, just to clarify.)
Can someone explain to me why does that happen? What did Mojang change to introduce the performance hits that people have been experiencing and what was their reason to do those changes? :/
1.14 is a better candidate: with Optifine updated to work with 1.13.2 it looks like the number of poeple whose computers got bricked by 1.13 will be (comparatively) small.
The short version is that much of the performance hits come from poorly optimized code and optimization takes time (which equals money) and skill beyond recognizing the desirability of doing so.
[Aside from the increased effort to achieve elegance in ones coding; non-optimtized, brute-force approaches are also easier to code and easier to explain to non-savy bosses. This was all too often seen as justification for poor work bback whe I was programming and I doubt human nature has changed much in the interim… ]
Rollback Post to RevisionRollBack
"Why does everything have to be so stoopid?" Harvey Pekar (from American Splendor)
WARNING: I have an extemely "grindy" playstyle; YMMV — if this doesn't seem fun to you, mine what you can from it & bin the rest.
Well I see I'm far from the only one having trouble. 1.13 certainly slowed down my minecraft significantly, but 1.13.2, which was supposed to improve performance, only made it worse for me. The performance isn't that much worse (not better either) but it feels bugged up beyond belief. The first time I played 1.13.2 the game crashed when I tried to launch. Then it crashed when I tried to open a world. Choosing a different resource pack took multiple tries before it worked. Then patches of ground started turning invisible, water and clouds flicker, and the game crashes. New and updated worlds seem to now work, sort of, but I'm fearing that 1.14 won't be playable for me, at least not until I get a new pc.
While i agree 1.13.2 is a mess at best, I still hold hope that Mojang will see the error in their ways and take a step back to optimize the game. I have lag all the without optifine for 1.13.2. My current computer specs are well above the suggested boasting a 1080 ti GPU. All of the issues stemming in minecraft today are caused by a lack of optimization and proper bug testing. While Mojang is attempting to move forwards, I just hope they have learned their lesson and are optimizing 1.14 to play much the same at 1.12.2 does.
Quick vent out:
lolcats are still funny
Per https://minecraft.net/en-us/article/minecraft-snapshot-18w43a "New Light engine!"
Also, refer to just past the halfway point of the following video:
It sure looks like they rendered it with Optifine. For them to get "4k" video on high end machines, they are going to have to get "standard" Minecraft lighting to work on lower end machines. Part of the question is, "How much of this lighting rework is Bedrock exclusive or also applies to Java Edition?" I have no idea, I just know 1.14 claims to have a new lighting engine.
Also, Mojang as a company is taking pains to tell people "Java is not going away." I'd have to look up the specific quote on Twitter, but it's out there often enough to try to get people to accept the official line: Java Edition is not being cut. My server, Copper FerretCraft is both on the Java Server (currently Snapshot 18w44a) and a Bedrock Realm. We play on either as we are inclined, or find something we want to kick around. On the surface, both versions are pretty much the same. The devil is in the details. And WOW what a freakin' devil it is! THAT discussion is NOT this thread. I'll just say the two editions differ enough in their development teams (Redmond for Bedrock, Stockholm for Java Edition) that Redmond is absolutely definitely *NOT* pushing to "win" all the Java Edition fans over to their platform. If you want to start a thread discussing that in detail, we can certainly go through that. But "pushing people from Java to Bedrock" is simply a non-issue between the Redmond team and the Stockholm team.
We are much better off with the following
a) supporting AND THROWING MONEY at sp614x, the Optifine Lead to keep that project going
building and testing new Snapshots like Gnembon in the following video:
Hold Mojang's feet to the fire with specific tests that can be done to show what the problem is so everyone can see it and point a finger to it. Unfortunately, it looks like @TheMasterCaver has been doing this for eons (in Internet time) and we still have our current situation. But he keeps trying anyway, and so should the rest of us.
I think this was fixed in 1.13.2
-Michael18751
(This is my new Minecraft forum account I originally joined in 2015)
I have played Minecraft since 2012 and I mostly play on JAVA edition.
My YouTube!: Link
Join My discord!: Link
Only few people still play Minecraft 1.13 on computers when Minecraft is introduced.
Don't expect playing 1.13 fine on theses computers. It's time to buy a new computer.
My videos: https://www.youtube.com/user/robingravel
My cartoons: http://www.dailymotion.com/robin-gravel
Flash Animation (if your computer supports flash):
http://robingravel.byethost15.com/eflash.htm
Few flash movies have easter egg/extras
Considering that the thread goes from August 2018 to November 2018, I guess bumping is allowed as long as the post is on-topic, right?
I'm also having performance issues with 1.13.2, although relatively minor.
In my case, I moved from 1.12.2 which I could run at solid 30 FPS, to 1.13.2 which dipped down to the low 10s on the Nether and 20 to 22 FPS on my base. In both instances, using Optifine (however, I didn't change its configuration when I moved from one version to the other, just to clarify.)
Can someone explain to me why does that happen? What did Mojang change to introduce the performance hits that people have been experiencing and what was their reason to do those changes? :/
1.14 is a better candidate: with Optifine updated to work with 1.13.2 it looks like the number of poeple whose computers got bricked by 1.13 will be (comparatively) small.
For a partial list of possible corporate goals that would logically result in this sort of thing being intentional (rather than just laziness, excessive pressure to 'get it out', or a general disregard for the customer base) see https://www.minecraftforum.net/forums/minecraft-java-edition/recent-updates-and-snapshots/2952602-are-mojang-out-of-their-minds-with-the-new-trading?comment=6
The short version is that much of the performance hits come from poorly optimized code and optimization takes time (which equals money) and skill beyond recognizing the desirability of doing so.
[Aside from the increased effort to achieve elegance in ones coding; non-optimtized, brute-force approaches are also easier to code and easier to explain to non-savy bosses. This was all too often seen as justification for poor work bback whe I was programming and I doubt human nature has changed much in the interim… ]