Marco Bergsma
- belkov78
- belkov78
- Europe/Stockholm
- Yes
- No
MCPE-53895
REALMS-11463
Since a couple of days I've had issues with chunks being broken/invisible more than usual on my offline creative map (literally every few minutes, always after a teleport).
A quick teleport -1000 and 1000 back will trigger loading the chunks, but it is quite cumbersome.
I have seen this behavior on our REALM, but never offline.
Things I've tried:
- reinstalled graphic drivers
- uninstalled and reinstalled minecraft (MCPE Win10)
- with or without texture packs
- I tried using previously published (and working, played by hundreds) versions of this map and there the problem also miraculously appeared.
- I also tried on a seperate computer (laptop), which gave the exact same result, leading me to believe this is an issue with the current iteration of Minecraft itself
- I tried looking for logfiles, but it looks like there are non for this version?
Since a couple of days I've had issues with chunks being broken/invisible more than usual on my offline creative map (literally every few minutes, always after a teleport).
A quick teleport -1000 and 1000 back will trigger loading the chunks, but it is quite cumbersome.
I have seen this behavior on our REALM, but never offline.
Things I've tried:
- reinstalled graphic drivers
- uninstalled and reinstalled minecraft (MCPE Win10)
- with or without texture packs
- I tried using previously published (and working, played by hundreds) versions of this map and there the problem also miraculously appeared.
- I also tried on a seperate computer (laptop), which gave the exact same result, leading me to believe this is an issue with the current iteration of Minecraft itself
- I tried looking for logfiles, but it looks like there are non for this version?
EDIT:
I tried using longer render distance (48, 64 and 80) and at higher settings the "some chunks not loading" error went away. Probably because you are now teleporting between 2 points within render distance of eachother.
So for now it looks the bug appear when teleporting outside of render distance.
Since a couple of days I've had issues with chunks being broken/invisible more than usual on my offline creative map (literally every few minutes, always after a teleport).
A quick teleport -1000 and 1000 back will trigger loading the chunks, but it is quite cumbersome.
I have seen this behavior on our REALM, but never offline.
Things I've tried:
- reinstalled graphic drivers
- uninstalled and reinstalled minecraft (MCPE Win10)
- with or without texture packs
- I tried using previously published (and working, played by hundreds) versions of this map and there the problem also miraculously appeared.
- I also tried on a seperate computer (laptop), which gave the exact same result, leading me to believe this is an issue with the current iteration of Minecraft itself
- I tried looking for logfiles, but it looks like there are non for this version?
EDIT:
I tried using longer render distance (48, 64 and 80) and at higher settings the "some chunks not loading" error went away. Probably because you are now teleporting between 2 points within render distance of eachother.
So for now it looks the bug appear when teleporting outside of render distance.
Since a couple of days I've had issues with chunks being broken/invisible more than usual on my offline creative map (literally every few minutes, always after a teleport).
A quick teleport -1000 and 1000 back will trigger loading the chunks, but it is quite cumbersome.
I have seen this behavior on our REALM, but never offline.
Things I've tried:
- reinstalled graphic drivers
- uninstalled and reinstalled minecraft (MCPE Win10)
- with or without texture packs
- I tried using previously published (and working, played by hundreds) versions of this map and there the problem also miraculously appeared.
- I also tried on a seperate computer (laptop), which gave the exact same result, leading me to believe this is an issue with the current iteration of Minecraft itself
- I tried looking for logfiles, but it looks like there are non for this version?
EDIT:
I tried using longer render distance (48, 64 and 80) and at higher settings the "some chunks not loading" error went away. Probably because you are now teleporting between 2 points within render distance of eachother.
So for now it looks the bug appear when teleporting outside of render distance.
EDIT2: I have tested and tested and tested on 2 different computers and I believe there is a bug with render distance. It looks as if the renderer stops to draw too quickly when the drawing distance is set to 16, 32 or 48....
If I teleport between 2 seperate far apart destination with render distance 60 or higher, I never get failed chunks, but on 16 and 32 it happens almost instantly. I also have a powerful PC with 8700K and 1080 GTX.
Since a couple of days I've had issues with chunks being broken/invisible more than usual on my offline creative map (literally every few minutes, always after a teleport).
A quick teleport -1000 and 1000 back will trigger loading the chunks, but it is quite cumbersome.
I have seen this behavior on our REALM, but never offline.
Things I've tried:
- reinstalled graphic drivers
- uninstalled and reinstalled minecraft (MCPE Win10)
- with or without texture packs
- I tried using previously published (and working, played by hundreds) versions of this map and there the problem also miraculously appeared.
- I also tried on a seperate computer (laptop), which gave the exact same result, leading me to believe this is an issue with the current iteration of Minecraft itself
- I tried looking for logfiles, but it looks like there are non for this version?
EDIT:
I tried using longer render distance (48, 64 and 80) and at higher settings the "some chunks not loading" error went away. Probably because you are now teleporting between 2 points within render distance of eachother.
So for now it looks the bug appear when teleporting outside of render distance.
EDIT2: I have tested and tested and tested on 2 different computers and I believe there is a bug with render distance. It looks as if the renderer stops to draw too quickly when the drawing distance is set to 16, 32 or 48....
If I teleport between 2 seperate far apart destination with render distance 60 or higher, I never get failed chunks, but on 16 and 32 it happens almost instantly. I also have a powerful PC with 8700K and 1080 GTX.
EDIT3: well, it appears the bug was fixed with the release of 1.3.0 - I will keep an eye open incase anyone every sees this bug report
When using resource packs that have custom item/entity texts, they don't work on the realm. This is especially prevalent when using functions to execute commands on said items/entities.
This is easily reproducable by creating a simple resource pack and renaming some items, for example, create a en_US.lang file, and add the following text:
item.snowball.name=Wand
entity.snowball.name=Wandand observe the /execute working on @e [name=Wand] on an offline map and NOT on a realm. I tried adding all 29 languages with the proper languages.json file to make sure it's not to do with some Realm localization.
Hi there. I think that 1.12.1 is the current version to be honest. There are no updates because of that reason.
It most likely updated itself on the background to stay current.
Would like to chime in; ive had the same thing happen to me a couple of times and can confirm a friend of mine just reporting the same
Issue still unresolved for containers in custom entities unfortunately.
Windows 10, 8-core i7 with RTX 3060 (very powerful machine) and lags and stutters all over the place. Went back to non-renderdragon version and fps all good again. Except no more RTX shots
Can also confirm this bug. From what I've tested, the gamerules DO stick if you edit them from the Realm menu itself (e.g. weather and day/night cycling). The options for which you need the /gamerule command ingame do keep resetting which indeed requires repeating command blocks to "fix".
Another issue, which I do feel has some relation to this particular bug, is that I have some commands in place to make me auto-equip an elytra. This stops working occasionally. but when I /give myself the elytra it will then magically equip the elytra I already "had". Also, doing a /clear command convinces me the player IS wearing the Elytra although it doesn't show/work. This usually stops working around the same time the /gamerule bug goes away, hence I think they might be related. This is all on a realm; everything works fine again when playing the map offline.
I do realize the 2nd bug might warrant a whole seperate bug report, but I wanted to share because I strongly feel there is correlation.
I can also confirm this has hit my realm and the realm of a friend. We both have realms for many years, based on superflat where we added a lot of stuff below y=0. All (or at least pretty much all) of it is gone or invisible/not rendering.
When flying around for a long time, sometimes stuff comes back and stays as well. It's very, very odd.
Below screenshot shows random stuff loading in...at first all of this was void.
Probably not relevant, but the same map (converted just a week ago) works a charm on Java 1.19
Edit: perhaps important: I play on Windows, my friend on PS4 and Windows while another friend plays on Xbox. All the same problem with realm AND offline copies.
more weird stuff. So I rolled back to a 1.18 copy (Bedrock Windows 10) and structure blocked everything I needed but not everything as I wanted to clear some stuff out anyway.
So I upgraded to 1.19, everything was gone but when putting back the structureblocks on their exact coordinates and loading them, everything was back....untill randomly, parts of the stuff I DIDNT structure began to appear....so I removed it, because I didn't want it and it keeps coming back....
I can keep deleting the stuff in the red outline, but it keeps coming back (on my realm. Haven't tested on my offline copy)
EDIT: can confirm this behavior is also present on an offline copy.....so it's bugged beyond comprehension
so....I reverted back to 1.18.31 to at least be able to keep working on my build. I literally just experienced certain deleted structures at y=-60 to reappear at will.....I delete them (/fill air or by hand) and they just keep getting back.....and this is in 1.18.31, which is very strange.
The structures present in these "perpetual areas" keep coming back, funnily enough, if you /fill them with another block type, the area stays filled with the block used. But the second you /fill with air, it reverts to its previous state...
Probably a duplicate of
MCPE-156679MCPE-156679I can confirm this is (still) a bug.
I created a custom entity with some functionality, and one of the things I added was the ability to sit. It does sit, but I cannot get it to change/execute behavior when it's sitting. It appears the minecraft:sittable code doesn't work for custom entities:
"minecraft:sittable":
{ "sit_event": "minecraft:taking_a_seat", "stand_event": "minecraft:time_to_go" }Steps to reproduce, add the following:
Component group to enable sitting:
{ "sit_event": "buckbeak_sitting", "stand_event": "buckbeak_standing" }"buckbeak:tame": {
"allow_sitting": true,
"minecraft:sittable":
,
{ "priority": 0 }"minecraft:behavior.stay_while_sitting":
}
{ "component_groups": [ "buckbeak_sitting" ] }Then the sittable event:
"events": {
"buckbeak_sitting": {
"add":
}
and then the component group (in this case, I want to set it on fire when sitting so I can easily see the code is working:
"component_groups": {
"buckbeak_sitting": {
"minecraft:is_ignited": {}
}
Nothing ever happens. Other parts, like the "on_leash" event and subsequent component group do trigger.
This is on the Windows 10 (bedrock) version
EDIT: apologies for the crappy code, the editor doesn't outline that well
you are correct, when writing this down I used the wrong component, I actually used the minecraft:burns_in_daylight one.
I need to get back to it then, I perhaps made a mistake, but when looking it up I found an old ticket and natually assume it was still not solved (
MCPE-109399).Will revert once I try again from scratch.
I'm afraid so, BeeTeeKay64.
And while the main part of the bug (a lot of stuff below y=0 gone missing) is fixed, there is still part 2 of this bug that's apparently not addressed; in some cases, older structures below y=0 can't even be filled with air now. See also my screenshot below...I have some old parts that I wanted to simply remove (by hand or /fill with air) but they kept coming back. These particular areas kept coming back, no matter what I tried. So in the end I settled for filling them with emerald so i know these parts could be removed later. After 1.19.2 just hit, I tried removing them and presto; they kept coming back still.
(These emerald structures below y=0 keep coming back unless overwriting with something other than air)
This is just initial testing, but the new 1.19.2 appears to have better performance on my windows 10 RTX laptop. It used to drop to a crawl in certain areas, which now doesn't appear to be the case anymore (even though still dropping slightly, but way less noticable).
So am interested in hearing everyone's opinions on this.
So I tried again with similar results. I did get the component group (burns in daylight) to work when sitting, but the "on standing" event never triggers.
So in my case, my intention was to not make the entity rideable when sitting, and then rideable again when standing. With the code above it simply becomes unrideable after sitting once.
Looking into the content logs, there were some remarks about the sittable part not being parsed correctly, but when putting it through the various JSON parsers and validators, the code appears to be 100% correct. And it should, because I simply copy/pasted it from another section which is 100% correct.
I will attempt a whole new, blank entity with only a sittable component and see how that works. Will revert back again.
Thanks for your insight @TheRedSmarty (I'm still fresh as a pickle with all this, just 2 weeks of "experience")
So, an interesting observation....I still can't get rid of certain structures below y=0 that have existed prior to 1.18.xx
I made them all emerald (as per my previous report) so once the issue is resolved, I can remove them. However, I tried to hollow them out to see what would happen and what do you know?:
If I do this, it stays like this. I just can't get rid of the outer layer....perhaps someone with a bit of knowledge can explain what's going on here.....
In short: certain (pre-existing) areas below y=0 cannot be removed....by hand or by /fill air....you can CHANGE the blocks though and it will stay and you can hollow them out and they stay....other than that; they cannot be removed.....they will be back once you reopen your map/realm
This is still an issue in 1.19.2 - my (and my friends') realm still needs command blocks to fix all the gamerules continiously
I went back to the non-renderdragon version in the end. There were still areas on my map that would just be unplayable....again: powerful hardware (RTX).
On my less powerfull, non RTX desktop I have no problems, which leads me to believe it might have something to do with my RTX card?
I might try playing it (with low render distance) on my internal GFX card to see if I get the same drops.
There might indeed be something wrong with RTX 3000 series card....I didn't even enable the RTX itself....
I upgraded from a GTX 1080 to an RTX 3070 on my desktop.....I never had the performance issues with my 1080 and now with the way more powerful 3070....presto, I get the fps drops.
And yes, I used DDU to uninstall my old drivers and reinstalled clean recent ones. Interesting to say the least.
May I deduct, just to be safe, that if I keep the version below that of 1.19.10 in my behavior packs, the old syntax will still work after the new execute command goes live?
can kind of confirm this happens to me as well for the past 24 hours....tried a gazillion times and also tried resetting the slot
can confirm it doesn't work on XBOX one and controller....cannot possible get to the y-coordinate...not even when using keyboard and arrow keys
Can confirm...displaying a scoreboard (/scoreboard objectives setdisplay sidebar) disconnects, adding a tickingarea (/tickingarea add) disconnects. Combine this with the annoying bug where gamerules (/gamerule commandblockoutput and /gamerule sendcommandfeedback) is completely bugged out on realms, it makes for a less than stellar experience
The problem still persists in 1.19.50 - /gamerule disablecommandblockoutput, /gamerule sendcommandfeedback are just completely stuck in whatever mode they are in. For me personally, on my realm, it doesn't even help of putting a repeating commandblock with the "/gamerule sendcommandfeedback false" command in it. It simply autoenables every single tick.
Not the end of the world, but the immersion is a bit lost when one uses some command tricks to make stuff happen.
Unfortunately just started happening to me on my Realm....I have a lot of paintings....repaired them all....moved away for a bit and came back 2 minutes later to see some of them already gone missing....I did built a command contraption to detect if they would "fall off the wall" as you would call it but this doesn't happen.
They simply disappear
I too would like to chime on on this particular issue. I have had this problem for a couple of versions now that the behavior packs works fine on an offline world, but for some reason doesn't on my Realm. Even when forcing a re-upload by changing the version numbers. Tried resetting and everything. It is happening now on 1.19.83 but has been since the previous version as well. I didn't change anything on the behavior pack since january this year.
GoWraths_BP.zip
attached the affected Behavior Pack as requested. Without the Resource pack you obviously don't get most if any of the intended use but considering the RP is larger than 10MB, I can't attach it. Let me know if you need anything else.
As stated; everything works offline but on my realm it simply doesn't do anything while being enabled according to the Realm info page.
Unfortunately, 1.20 - still not working
I can chime in and confirm this happens on a new vanilla world. I opened a blank, flat world to test a pack and it had the speed-glitch even before I added any packs, after I added the pack and when I removed the pack. It never went away. The same happens on my realm with random people.
I have added the pack. You can reproduce by enabling it on an offline world, then take a snowball (which is renamed as "Wand") and observe you can both throw it and drop it on the ground while executing a command on the entity by using [name=Wand].
When you enable the same pack on a realm, it will not work as the renamed item will still be called a "Snowball"....this appears to work with all named/renamed entities/items. They DO show up in the inventory with the names used in the .lang file, just the entities themselves are not named.
I recorded a video of it happening. I start out at the local world, show that the resource pack is loaded and then proceed to put a snowball item on the ground and /execute a command on it.
I will then proceed on the realm and repeat these steps and show it's not named "Wand" but "Snowball" thus ignoring the custom naming.
Unfortunately an issue when dealing with executing commands on dropped (named) items.
https://youtu.be/yowHqit_0yQ
(I posted in a private YT video as it was too large to fit directly)
So I am going to assume the ticket was resolved awaiting a reply from the initial reporter? I can confirm that the bug still is present in 1.20.15 as it happened to someone visiting my realm last night. I managed to "fix" it for this player by downloading the map, manually removing the packs and the following 4 files:
world_behavior_pack_history.json
world_behavior_pack.json
world_resource_pack_history.json
world_resource_pack.json
and then uploading the map without packs, enter the world and only then apply the packs again.
I'm not sure if this will work for other players joining but it did for one specific player.
just putting this out there so people can test/try and remedy for the time being. (obviously you need a pc for this)