SomeonePLaysMC
- iplayMCeveryday
- JIRAUSER634820
- Europe/Stockholm
- Yes
- No
MCPE-125695
MC-223792![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
player.json
Possibly Related to
MC-214162
I'm pretty sure this will be a duplicate but i veeery strongly want this to get fixed as in older versions it didn't happen. I searched and I couldn't find anything, but i feel this issue has been reported by somebody else.
So when you look down or up in 3rd person and rotate the camera at coordinates higher that 4096, sometimes the camera will stutter a little bit if you are facing the correct way.
Steps to reproduce:
- Make a new world and set the game mode to creative mode;
- Press F5 to toggle 3rd person view;
- Type in chat the following: "/tp 5000 128 0 0 90" (without quotes);
- If you are not looking down then look down;
- Drop down on the ground (if you were flying);
- Slowly rotate the camera as shown in the video below;
Or you can just walk over 4096 blocks in one direction and then toggle 3rd person view and look down and very slowly rotate your camera 360
*°*and most likely notice it. Note: it gets worse after 8192 blocks away from 0, 0 (center of world)Watch video for proof.
I'm pretty sure this will be a duplicate but i veeery strongly want this to get fixed as in older versions it didn't happen. I searched and I couldn't find anything, but i feel this issue has been reported by somebody else.
So when you look down or up in 3rd person and rotate the camera at coordinates higher that 4096, sometimes the camera will stutter a little bit if you are facing the correct way.
Steps to reproduce:
- Make a new world and set the game mode to creative mode;
- Press F5 to toggle 3rd person view;
- Type in chat the following: "/tp 5000 128 0 0 90" (without quotes);
- If you are not looking down then look down;
- Drop down on the ground (if you were flying);
- Slowly rotate the camera as shown in the video below;
Or you can just walk over 4096 blocks in one direction and then toggle 3rd person view and look down and very slowly rotate your camera 360° and most likely notice it. Note: it gets worse after 8192 blocks away from 0, 0 (center of world)
Watch video for proof.
I'm pretty sure this will be a duplicate but i veeery strongly want this to get fixed as in older versions it didn't happen. I searched and I couldn't find anything,but ifeel this issue has been reported by somebody else.
So when you look down or up in 3rd person and rotate the camera at coordinates higher that 4096, sometimes the camera will stutter a little bit if you are facing the correct way.
Steps to reproduce:
- Make a new world and set the game mode to creative mode;
- Press F5 to toggle 3rd person view;
- Type in chat the following: "/tp 5000 128 0 0 90" (without quotes);
- If you are not looking down then look down;
- Drop down on the ground (if you were flying);
- Slowly rotate the camera as shown in the video below;
Or you can just walk over 4096 blocks in one direction and then toggle 3rd person view and look down and very slowly rotate your camera 360° and most likely notice it. Note: it gets worse after 8192 blocks away from 0, 0 (center of world)
Watch video for proof.
When you look down or up in 3rd person and rotate the camera at coordinates higher that 4096, sometimes the camera will stutter a little bit if you are facing the correct way.
Steps to reproduce:
- Make a new world and set the game mode to creative mode;
- Press F5 to toggle 3rd person view;
- Type in chat the following: "/tp 5000 128 0 0 90" (without quotes);
- If you are not looking down then look down;
- Drop down on the ground (if you were flying);
- Slowly rotate the camera as shown in the video below;
Or you can just walk over 4096 blocks in one direction and then toggle 3rd person view and look down and very slowly rotate your camera 360° and most likely notice it. Note: it gets worse after 8192 blocks away from 0, 0 (center of world)
Watch video for proof.
Camera stutter while looking down/up in 3rd person and rotating thecamera at high coordsRotating 3rd person camera at high coordinates is jittery
[duplicate] maxEntityCramming doesn't affect armor stands and minecarts
No matter what value 'maxEntityCramming' is set to, stacking armor stands or minecarts in a one-block space doesn't have a limit. This can cause extreme lag, even in singleplayer.
What I expected to happen was...:
After the stacked (in one-block space) armor stands/minecarts reach the limit provided by 'maxEntityCramming' gamerule, some of the armor stands/minecarts start to break just like mobs affected by this gamerule die after reaching the limit.
What actually happened was...:
I can infinitely stack armor stands and minecarts in a one-block space without them breaking even if the gamerule is set to 1.
Steps to Reproduce:
(optional) Set the gamerule maxEntityCramming to something small like 3
- Build a 3 block tall "tower" by placing the block of your choice like in the video down below
- Place armor stands next to the top block like done in the video down below
- Notice how you can stack 100, 300, 1000, ∞ armor stands (and minecarts too if done with rails) without a single one breaking (or at least disappearing or doing something)!
I hope this gets fixed, because it can cause a lot of lag and performance issues, and even crash servers.
This is NOT a feature request or a suggestion. If this is how 'maxEntityCramming' works, then this is 'Works As Intended'.
Edit: Now I noticed that it actually duplicates
MC-217927. At first I searched, but did not find anything else. Sorry for the duplicate.
No matter what value 'maxEntityCramming' is set to, stacking armor stands or minecarts in a one-block space doesn't have a limit. This can cause extreme lag, even in singleplayer.
What I expected to happen was...:
After the stacked (in one-block space) armor stands/minecarts reach the limit provided by 'maxEntityCramming' gamerule, some of the armor stands/minecarts start to break just like mobs affected by this gamerule die after reaching the limit.
What actually happened was...:
I can infinitely stack armor stands and minecarts in a one-block space without them breaking even if the gamerule is set to 1.
Steps to Reproduce:
(optional) Set the gamerule maxEntityCramming to something small like 3
- Build a 3 block tall "tower" by placing the block of your choice like in the video down below
- Place armor stands next to the top block like done in the video down below
- Notice how you can stack 100, 300, 1000, ∞ armor stands (and minecarts too if done with rails) without a single one breaking (or at least disappearing or doing something)!
I hope this gets fixed, because it can cause a lot of lag and performance issues, and even crash servers.
This is NOT a feature request or a suggestion. If this is how 'maxEntityCramming' works, then this is 'Works As Intended'.
Edit: Now I noticed that it actually duplicates
MC-217927. At first I searched, but did not find anything else. Sorry for the duplicate.No matter what value 'maxEntityCramming' is set to, stacking armor stands or minecarts in a one-block space doesn't have a limit. This can cause extreme lag, even in singleplayer.
What I expected to happen was...:
After the stacked (in one-block space) armor stands/minecarts reach the limit provided by 'maxEntityCramming' gamerule, some of the armor stands/minecarts start to break just like mobs affected by this gamerule die after reaching the limit.
What actually happened was...:
I can infinitely stack armor stands and minecarts in a one-block space without them breaking even if the gamerule is set to 1.
Steps to Reproduce:
(optional) Set the gamerule maxEntityCramming to something small like 3
- Build a 3 block tall "tower" by placing the block of your choice like in the video down below
- Place armor stands next to the top block like done in the video down below
- Notice how you can stack 100, 300, 1000, ∞ armor stands (and minecarts too if done with rails) without a single one breaking (or at least disappearing or doing something)!
I hope this gets fixed, because it can cause a lot of lag and performance issues, and even crash servers.
This is NOT a feature request or a suggestion. If this is how 'maxEntityCramming' works, then this is 'Works As Intended'.
Edit: Now I noticed that it actually duplicates
MC-217927. At first I searched, but did not find anything else. Sorry for the duplicate.
Stretching Minecraft's window size like in the image below doesn't affect the suffocation overlay when you are inside a block, making it show only in the center of the screen, and you can xray through walls by changing the window size width to something very high.
To reproduce, suffocate yourself with sand or something else, exit fullscreen if you play on fullscreen and resize the window to be large and panoramic like in the image, and you will see that the suffocation overlay only covers the center of the screen, not full screen and you can see through blocks.
Stretching Minecraft's window size like in the image below doesn't affect the suffocation overlay when you are inside a block, making it show only in the center of the screen, and you can xray through walls by changing the window size width to something very high.
To reproduce, suffocate yourself with sand or something else, exit fullscreen if you play on fullscreen and resize the window to be large and panoramic like in the image, and you will see that the suffocation overlay only covers the center of the screen, not full screen and you can see through blocks.
This seems to not happen with nether portal overlays.
Windows 10 Home 64bit
Java 1.8 64bit, Java 1.16 64bit
This time i searched EVERYWHERE in ANY way, shape or form and DID NOT find anything else! So I Hope this isn't once again a Duplicate.
Stretching Minecraft's window size like in the image below doesn't affect the suffocation overlay when you are inside a block, making it show only in the center of the screen, and you can xray through walls by changing the window size width to something very high.
To reproduce, suffocate yourself with sand or something else, exit fullscreen if you play on fullscreen and resize the window to be
large and panoramic like in the image, and you will see that the suffocation overlay only covers the center of the screen, not full screen and you can see through blocks.
This seems to not happen with nether portal overlays.
Stretching Minecraft's window size like in the image below doesn't affect the suffocation overlay when you are inside a block, making it show only in the center of the screen, and you can xray through walls by changing the window size width to something very high.
To reproduce, suffocate yourself with sand or something else, exit fullscreen if you play on fullscreen and resize the window to be wide and panoramic like in the image, and you will see that the suffocation overlay only covers the center of the screen, not full screen and you can see through blocks.
This seems to not happen with nether portal overlays.
Stretching Minecraft's window size like in the image below doesn't affect the suffocation overlay when you are inside a block, making it show only in the center of the screen, and you can xray through walls by changing the window size width to something very high.
To reproduce, suffocate yourself with sand or something else, exit fullscreen if you play on fullscreen and resize the window to be wide and panoramic like in the image, and you will see that the suffocation overlay only covers the center of the screen, not full screen and you can see through blocks.
This seems to not happen with nether portal overlays.
Edit: I could reproduce this from Minecraft InfDev all the way to the current version. This bug was in the game and undiscovered for 11 YEARS!
Stretching Minecraft's window size like in the image below doesn't affect the suffocation overlay when you are inside a block, making it show only in the center of the screen, and you can xray through walls by changing the window size width to something very high.
To reproduce, suffocate yourself with sand or something else, exit fullscreen if you play on fullscreen and resize the window to be wide and panoramic like in the image, and you will see that the suffocation overlay only covers the center of the screen, not full screen and you can see through blocks.
This seems to not happen with nether portal overlays.
Edit: I could reproduce this from Minecraft Inf
Dev all the way to the current version. This bug was in the game and undiscovered for 11 YEARS!Stretching Minecraft's window size like in the image below doesn't affect the suffocation overlay when you are inside a block, making it show only in the center of the screen, and you can xray through walls by changing the window size width to something very high.
To reproduce, suffocate yourself with sand or something else, exit fullscreen if you play on fullscreen and resize the window to be wide and panoramic like in the image, and you will see that the suffocation overlay only covers the center of the screen, not full screen and you can see through blocks.
This seems to not happen with nether portal overlays.
Edit: I could reproduce this from Minecraft Infdev all the way to the current version. This bug was in the game and undiscovered for 11 YEARS!
Suffocation overlay doesn't fully cover the screen when the window size is large.
Stretching Minecraft's window size like in the image below doesn't affect the suffocation overlay when you are inside a block, making it show only in the center of the screen, and you can xray through walls by changing the window size width to something very high.
To reproduce, suffocate yourself with sand or something else, exit fullscreen if you play on fullscreen and resize the window to be wide and panoramic like in the image, and you will see that the suffocation overlay only covers the center of the screen, not full screen and you can see through blocks.
This seems to not happen with nether portal overlays.
Edit: I could reproduce this from Minecraft Infdev all the way to the current version. This bug was in the game and undiscovered for 11 YEARS!
.
.ㅤ
.ㅤ
Windows 10 Home 64bit
Java 1.8 64bit, Java 1.16 64bit
How don't you guys understand?? Ok i give up. Im deleting this issue. Please mark it as invalid.
Goats don't seem to panic when having an effect[issue deleted]
After a goat is hit by a potion, and while it has an effect (such as "water breathing"), when you hit it, it won't run around and panic.[issue deleted]
just tested this issue in 21w19a, but realized this is patched in 21w20a.
Please mark this issue as invalid.
[issue deleted]
just tested this issue in 21w19a, but realized this is patched in 21w20a.
Please
markthis issue as invalid.[issue deleted]
just tested this issue in 21w19a, but realized this is patched in 21w20a.
Please delete this issue or mark it as invalid
Minecraft PE/on Android goes to "Minecraft: Bedrock Codebase" project, not this project. Please post it there.
This may be an issue with Optifine. Bug reports are only accepted in the vanilla version of Minecraft. Try to reproduce this in vanilla Minecraft and let us know.
![[Mod] markderickson](../../../data/avatars/users/18946.svg){kind=small}
@SomeonePLaysMC: MC-225859 has more attention at the moment, so it's going to be left as the parent report. It would make no difference if this ticket was the parent report, and transferring the issue links would create extra work for the moderators.
SomeonePLaysMC please don't reopen AR reports if you don't have any information to add
SomeonePLaysMC please don't trash your reports. Comparing your report to MC-8685 and the sceenshots provided the it appears core of the issue steams from MC-8684 which is why it's a duplicate
I could reproduce it in 21w16a too.
Duplicate of
MCPE-19218Fixed with the help of a behaviour pack and command blocks!
I tried to do my best and fix the bug with a behaviour pack edit, but it turns out that i fixed it with that but with command blocks too
However, this may have some extra visual bugs regarding the player's size.
Video:
https://clipchamp.com/watch/Pv1ErHt8vfw
Did not attach the behaviour pack due to copyright reasons but you can still install the patch:
/gamerule commandblockoutput false
9. Set up 2 command blocks like this:
1. Command: /event entity @a event:scale_2
Repeat Unconditional Always Active Delay in Ticks: 7
2. Command: /event entity @a event:scale_normal
Repeat Unconditional Always Active Delay in Ticks: 7
10. Stand on top of one of the command blocks and execute command:
/tickingarea add ~2 ~2 ~2 ~-2 ~-2 ~-2 bugfixcommands
This should work and should fix the bug!
Have fun!
Edit:
I attached the world too for you to simply try it out (change the extension to mcworld if it is not):
https://filebin.net/qwx5yvpfuoumsowm
(link expires on 5/May/2021)
Edit 2: I created this comment for those who are "too scared" to play on survival, knowing that they will randomly fall through the ground, die, and lose everything; and to prove how easy is this bug to fix.
Possibly Related to
MC-214129This issue is invalid.
Lunar client is a modified client, not made and not supported by Mojang. This bug tracker is only for Vanilla Minecraft versions, official launcher and web services.
Can confirm in Minecraft Java Edition.
But don't worry. It happens at just over 549755813888 blocks away! (but still very hard at this distance)
It was tested (and i recommand to test it like this) at 8796093022208 blocks away in version 1.2.5.
There is NO WAY to reproduce this in java edition vanilla as it's limited to 30000000 blocks, but with very powerful mod you can do that, and you can pass 2147483647 blocks too, and there is a mod for that!
This mod has NOTHING to do with falling through the world, what it does is it only just expands the world limit to the 64 bit integer limit. Anyways, further is information in this video: www.youtube.com/watch?v=F8cMZA8J2Hk (download and credits in the description of the video)
Edit: So i think this happens in every sandbox game, not only Minecraft. Almost every sandbox game stores hitboxes in floating point numbers, either 32 bit or 64 bit, but if the player moves at a critical speed and one edge of the player's hitbox is before a power of 2, and the other is after a power of two, the one before the power of 2 moves, while the other one not. This causes the player's hitbox to shrink or expand, and like this the hitbox width can reach 0 (the "null" state), which can disable the collisions of the hitbox.
This issue works as intended.
The exact same issue was reported on java edition and was marked as "works as intended":
MC-97476Maybe it's won't fix because the "debug stick" is not fully implemented and it's an 'unsupported' feature?
Now I noticed the original one. I searched and did not find anything. Sorry for the duplicate.
Can you take a screenshot with the F3 debug screen enabled, please?
(you can turn on a debug screen by pressing F3 or FN+F3 if you didn't know)
Try to reproduce this issue in Vanilla Minecraft Singleplayer (and possibly open the singleplayer world to LAN if this is an issue with multiplayer) and if you can reproduce it, then attach a video with this issue occurring in your vanilla Minecraft world.
(it is recommended to enable the F3 menu too before filming the video)
I'm pretty sure this Works As Intended as things that are 2 blocks high like doors, tall grass, etc. are made out of 2 blocks (the bottom and the top part), not one single block.
If you look at the outline selection you can see that it only selects the side you are looking at.
Cannot Reproduce.
I went to the nether, spawned a zoglin, then a baby one from that zoglin. The baby one was following the adult one just like any mob.
This tracker is only for bugs and does not accept feature requests and other requests. Please go to Minecraft's feedback website for posting requests: feedback.minecraft.net
Maybe duplicate of
MCPE-65298?I don't think this is actually incomplete, as i understood what does the reporter mean. He probably means that when you mine something that is 2 blocks high, like doors for example, it only shows the cracks on one side of the door (the upper side or lower side), depending which side are you facing and breaking.
One of the steps to reproduce will be:
I still think this works as intended though.
Here is some images of the "bug" shown:
Please attach the latest crash report (that is made from this error) to this issue.
You can find crash reports in C:\Users[your username]\AppData\Roaming\.minecraft\crash-reports
Instead of [your username] put your username.
The crash report gives us a lot of information about the crash so we can diagnose your issue.
It looks like all my reproduce attempts failed.Can you please attach a video of this bug occuring with the F3 debug screen enabled?Also, after you reproduce this bug once again, please hold F3+C for more than 10 seconds and the game should crash (manually generated crash). Then, attach the latest crash report (or the crash report generated by holding F3+C) to this bug report.Edit: It looks like this time I could confirm.
Pressing the keys at the same time will drop one item, and the other one will turn into a ghost item. The ghost item will not show up in the hotbar, however you can still drop it or place it.
Possibly a duplicate of
MC-85287? (which is "awaiting response for some reason)Possibly a Duplicate of
MC-108This report is NOT invalid as the Minecraft Launcher should be able to launch any version. In this report, you mentioned that you were playing on 1.16.3 and the bug tracker CAN handle reports from the Minecraft Launcher that can be reproduced in older snapshots/releases of the game as the Minecraft Launcher should be able to launch any version. This is why there is a version dropdown menu in the launcher. However this CAN be invalid as it could be just a technical support issue.
btw, I still don't actually know if Avoma is a comment bot or just copying and pasting, because i've seen same comments on multiple issues and sometimes on some issues it/he/she comments almost immediately.
Not a duplicate of MC-8684. In MC-8684 it doesn't show that you get inside of a block.
In the description and the attachments of MC-8684, it shows that you are outside of blocks and you can look through solid walls with wide window size, and NO SUFFOCATION OVERLAY IS SHOWN in ANY WAY, SHAPE OR FORM.
In my bug report it shows that you are inside a block and the suffocation OVERLAY that COVERS the screen (AKA A 2D TEXTURE OF THE BLOCK IS SHOWN WHILE INSIDE A BLOCK) when you are inside a block DOESN'T COVER the INTIRE screen.
So in theory my bug works ONLY WHEN YOU ARE INSIDE BLOCKS and MC-8684 bug works ONLY WHEN YOU ARE OUTSIDE BLOCKS.
So this is where MC-8684 differs from my bug report. AND IT IS A COMPLETELY DIFFERENT ISSUE.
Conclusion: only relates to MC-8684.
Also relates to my bug report, MC-225337, but don't confuse it with a duplicate.
MC-225859 was created AFTER this issue.
This issue was created BEFORE MC-225859.
Please Reopen this issue and mark MC-225859 as a Duplicate.
Duplicate of
MC-195461which was fixed in 20w46a. So keep in mind that when the next version (1.17) is going to be released, this bug will not happen anymore.This issue is incomplete, as it does not contain much information.
Make sure to put steps to reproduce, screenshots and videos in your issue.
Also, I don't know how you can change the size of a phantom without the help of mods. So make sure the game is not modified when posting issues.
Then, this might be a duplicate of MC-181823
This issue is not the same. My issue affects another part of the game than in that issue.
My issue affects the suffocation overlay, and MC-8684 affects the FOV.
Also, please force a game crash by holding F3+C for more than 10 seconds (or possibly FN+F3+C if you are on a laptop) and then attach the crash report (caused by the intentional game crash) to this issue.
You can find crash reports in C:\Users[username]\AppData\Roaming\.minecraft\crash-reports
Instead of [username], put your username.
You modified the entity data of the goat.
Not sure if that entity data command makes the goat run off edges.
It could be because of your graphics card.
In the video attached there is a lot of lag too.
I think your Minecraft installation is corrupted.
Click here for a tutorial on How to find a crash report.
I cannot confirm in 1.16.5 too. Are you using any resources packs? One of them can be incompatible with the current version (1.16.5) or corrupted.
Edit: Please also put graphics card details in the Environment section.
Please attach the crash report generated by this issue from C:\Users[username]\AppData\Roaming\.minecraft\crash-reports
Also, this may be invalid because it is a technical support issue and these issues are not tracked on the bug tracker
Probably works as intended, as the villages probably generate with random houses and the "random number generator" picked 1.
Also, please do not put more than 1 single issue in a bug report. Put them in different bug reports
I can reproduce in 1.17 Pre-Release 1.
This means that it is most likely caused by Java, not Minecraft. Please report Java bugs at the java bug tracker or report this to Mojang technical support.
Java bug tracker: bugs.java.com
Technical support: https://help.minecraft.net/hc/en-us/articles/360035130751-Technical-support-resources
Probably this will fix it:
If this doesn't fix it, then try doing the steps again plus the optional step (updating to Windows 10)
if this STILL doesn't fix it, then contact Mojang Technical Support
Technical Support (resources): https://help.minecraft.net/hc/en-
us/articles/360035130751-Technical-support-resources
Technical Support (request): https://help.minecraft.net/hc/en-us/requests/new
"Technical support (request)" will be recommended to click if nothing above works, because you can describe what is exactly happening.
Please also check out minecraft's help page: help.minecraft.net
Yes, in
MC-218803there is a comment saying that it is due to outdated graphics. So most likely that is the problem.Searched the graphics details on google, this is what came out:
https://www.google.com/search?q=intel+hd+4000+release+date
It looks like this graphics "card" was made in 2012
Report this here: https://github.com/FabricMC/fabric-loader/issues
in case it is an issue with Fabric and not a specific mod.
See MC-87935
I wonder how no one seen that this issue is duplicate in the comments
That is not the lead. That is the lead knot. So when you search on this bug tracker "knot stays", in a minute you will find the original issue (MC-16663), so this means that this is a duplicate of MC-16663. So please search before creating a new issue and do not search only once, search for minimum 5 minutes. It is recommended to search for the important words, for example in this issue: "knot" and "stays", and in less than 5 minutes, you will find it.
I think this is only related to
MC-201209In 201209 it shows at certain angles, not with spyglass. With a spyglass, you can reproduce this bug at any angle.
Report this here: https://help.minecraft.net/hc/en-us/requests/new
Doing more research and more reproduction tests:
The sides affected depends on position.
If the spawner is before both X and Z coordinate 2048, then 6 sides are affected.
If the spawner is after X or Z 2048 on ONE axis, and before 2048 in THE OTHER axis, then 4 sides are affected.
If the spawner is after both X and Z coordinate 2048, then only the bottom and the top side is affected. (2 sides are affected)
From what i know, this happens because of precision loss. After 2048, the precision error is bigger than the difference between a full block and a mob spawner, making the mob spawner full on some axises.
So @bugsbugsbugs nothing changed in 1.16.210.
In the attachment of this issue i can see that you have an elytra on you and this makes it a duplicate of
MCPE-109925Thank you for your report. However this issue is "Works As Intended".
"Gived" is not a correct word in English. The past simple form of "Give" is "Gave" and the feedback of the command puts it in the past, not in the present, because you executed the command in the past and the feedback of the command appeared in chat AFTER the command was executed.
Can Confirm in 1.17 RC1
There were no modifications while experiencing this issue. All of this was done in Vanilla Minecraft and there are no attachments that show that the game is modified.
May be intended.
Please read the Mojang Notice in
MC-207896and contact community support discord: https://discord.gg/58Sxm23I think this is a duplicate of
MC-227064because the title, the descriptions and attachments refer to the same thing.With the caves and cliffs update, bedrock now generates at layer -63. This feature was reverted in java edition but it still exists in bedrock edition.
duplcate of
MCPE-128971And he IS most likely on 1.17 because at the affected vesions there is 1.17.10.21 Beta + this issue would be invalid if he wasn't, because of an outdated version.
That sounds to me like lag. I think your server froze for just a little bit.
That can even happen in singleplayer.
Intended per fix of
MC-214965I believe this issue is invalid because candles became unsupported in 21w19a and they are still unsupported in 1.17.
They will become supported in 1.18.
So if this issue won't be fixed, then feel free to report it when candles become supported again.
He/She is maybe on macbook and i'm not sure if FN+F3+B works on macbooks.
And i don't thing "particles" setting matters because of the fix of
MC-203704.Your version is outdated. Try this in the Release 1.17 and see if it works.
I also kinda not understand this bug so it may be incomplete.
See
MC-208803. It's most likely cause your graphics card is too old or graphics drivers are outdated.And i don't think you are supposed to be able to run MC 1.17 with jre 1.8 It only supports jdk 16.0.1
Bug reports are only accepted in English, sorry. If you can speak English, feel free to create a new report in English. You can also use Google Translate to translate the words in English.--
Los informes de errores solo se aceptan en inglés. Si puede hablar inglés, no dude en crear un nuevo informe en inglés. También puede utilizar Google Translate para traducir las palabras en inglés.Summary and description changed to English.
So
MC-203704is reopened?Check out
MC-208803It's because of outdated graphics drivers or card.
Its 218803 sorry
Please include more information, such as steps to reproduce, screenshots and videos with the F3 debug screen enabled.
Maybe try to add more RAM?...
Report this to the Optifine bug tracker: https://github.com/sp614x/optifine/issues
Please put graphics card details in the description.
No response has been given for 1 year+ so this issue should get resolved as Incomplete or Cannot Reproduce.
No response has been given for 1 year+ so this issue should get resolved as Incomplete or Cannot Reproduce.
If you update a 1.16.5 world to a 1.17 snapshot (for example 21w14a), do you still experience this issue? If not, then update to that snapshot and then update to the release of 1.17 and see what happens.
Try to update it to 21w20a, then to 1.17 pre1, then to 1.17 pre2, then to 1.17 pre3, then to 1.17 pre4, then to 1.17 pre5, then to 1.17 rc1, then to 1.17 rc2, then to release 1.17.
In what snapshot/version does the lag start?
Go onto your world in 1.17 that you have lag on, then force a crash by holding F3+C for more than 10 seconds (if you are on a laptop, it's possibly FN+F3+C), then attach the crash report found in ."minecraft/crash-reports/crash-<DATE>-client.txt" to this issue. This will give us a lot of information about what is exactly happening.
More information about how to find a crash report: https://minecrafthopper.net/help/finding-minecraft-data-folder/
At the bottom of the crash report, it says that you have more incompatible data packs. The issue is most likely caused by these data packs that are incompatible with 1.17. Try to disable them and see what happens.
So do you have OpenGL 3.2?
And can you go into your ".minecraft/saves" folder, find the folder with your world name, make it a zip archive, and then attach it to this issue? I want to open it in my Minecraft 1.17 to see if i have any lag on it.
See
MC-218803The issue is probably caused by the resource packs that you have. Try to disable them and see if the issue is fixed.
Srry i noticed it now i put 0 instead of 1
And another thing: does
MC-228302describe your issue? I tested it in 1.16.5 and it doesn't work, then i tested it in 1.17 and it DOES work and it generates a lot of lag and i get only 5 fps.Can you upload the world to google drive and then give us the link?
Ok, thanks for the world! I'll maybe check it tonight (at 20:00 in GMT+1) because now i have a lot of work to do for school.
Ok so i managed to check the world now and what i can say is that there is definitely something up with the world.
When i loaded the world in 1.16.5, i got 25 fps which is kinda low but still playable.
When i loaded the world in 1.17, i got maximum 8 fps, and when i walk the fps cuts in half (i get 4 fps).
I will do more research of this issue and i'll tell you what is actually going on and what you can do to fix it.
But from the screenshot of the main menu, this seems to be more of a duplicate of
MC-218803.Affects 1.17.0.
You don't even need to sneak for this
If you cross 32768 while doing this but not sneaking you can also stop moving and you can sometimes clip though the ground.
Yes. I agree this should be reopened. I couldn't find anything to help, but this might increase your fps:
Turn:
Graphics to Fast;
Smooth Lighting to OFF;
Clouds to OFF;
Render Distance to 6 chunks;
View Bobbing to OFF;
Particles to Decreased;
Entity Shadows to OFF;
Entity Distance to 50%;
Distortion Effects to 30%;
FOV Effects to 30%;
Biome Blend to OFF;
Fullscreen Resolution to 800x600@48 (24bit);
Fullscreen to ON;
VSync to OFF (Optional);
With these settings and without VSync, i am able to get 150+ fps on a new world and 50+ fps on your world, so this should boost your FPS.
This happened to me now when i updated Minecraft to 1.17 on my xbox, but it looked a little bit different. First of all, why are you so far away from the spawnpoint in most of the screenshots, and does this happen for anyone else that updated to the latest version?
Ok, sorry. I was thinking that if awaiting response reports remain awaiting response for more than 1 year, they sould get resolved.
Maybe duplicates
MCPE-44604, which cannot be reproduced for some reason.see
MC-55347MC-175866This is a technical support issue. This site accepts bugs only. This is because your java version is outdated. To run 1.17, you need jdk 16.0.1.
Possible duplicate of
MC-155379Chat messages are not hidden by crafting/chest menus in Minecraft Java Edition.
Are you on the correct version of Minecraft? Does pressing F3 or FN+F3 show some debug information on your screen? If yes, then attach a screenshot with the F3 debug screen enabled.
Can you give us further information about the bug?
Are you stuck in the nether? (Because "hell" in Minecraft means nether)
Are you stuck in fullscreen? Go to video settings and disable fullscreen, or you can press F11 or FN+F11 to disable fullscreen.
Can put some steps to reproduce in the description and attach some screenshots and some videos of the issue happening?
Does it happen on 1.17 and also vanilla client?
It's actually reduceDebugInfo (with r at the start). Are you in the latest version of Minecraft? Minecraft had less debug information and could allow any game rule to be created in the past.
Fix of
MC-226948is most likely causing the bug.Feature that caused this bug is removed in the latest 1.17 snapshots and release 1.17
Does
MC-218803describe your issue?Sorry, we do not accept modded Minecraft clients on this bug tracker. This bug tracker is only for vanilla.
If this does not happen in vanilla then this issue is invalid.
Ok then read the moderator note from that issue, the description and comments
Can confirm in 1.17, 1.17.1 Pre-release 1
Happens to me now in 1.17.
Not Fixed
Yes, but if he is not opped and he didnt use cheats than this is not a duplicate
Contact Mojang Tech Support: https://help.minecraft.net/hc/en-us/requests/new and stop spamming!
This issue hasn't been updated since 30/May/22. It is now harder to reproduce, but i still could do it in 1.19 and 22w24a after a couple of attempts, so i added those versions to the issue.
Reply to toniee98 & DaGreatest12341: Adding a world border to such small distances will be more terrible and actually harder than literally fixing the bug. I barely know something about C++ and how Minecraft Bedrock Edition is coded and this kinda stuff AND I LITERALLY FIXED THE BUG! Don't believe me? Check out my older comment that is the 6th comment before this one.
IMPORTANT EDIT: I attached a tutorial on how to fix the bug by yourself to the bug report. It is probably going to get removed by a moderator or a Mojang employee, but i've done it anyways to raise awareness (that this bug is sooo easy to fix): Working Fix.txt
EDIT 2: Reattached the working fix with some changes to make it more clear
Ok, if this is staying open then i will also add 1.19 (latest release) to affects versions because it isn't there