MCExplorer44

• Video attached below. One new detail worth noting is one time this morning the texturecache file was able to grow to 55MB and then the issue appeared to stop happening. Every other time the cache file does not grow beyond 59K and contains almost nothing but 0x00 values. Render pipeline timing issue perhaps?

• The game reacts normally, though it does slow down the more I explore in open areas.

• The %appdata%\.minecraft folder only contains Java Edition logs and I could find no recent logfiles in there indicating they logged during the times this issue was occurring. There are no recent crash dumps to provide.

• No add-ons nor resource packs are enabled at this time.

• I included details system specs in the issue report section above.

• The only background process I was using was Process Monitor to get technical data, but it doesn’t affect performance and the issue happens whether or not it is running.

• The only overlay enabled is the Windows 11 OS-provided gaming overlay.
  
  

  [media: flushbuffer.mp4]

Additionally, vines are replacing tree trunks everywhere they generate. Forest and the three taiga biomes also exhibit mangled trees.

This issue is resolved with recent updates.

This appears to be fixed in Preview 26.0.29.

MCPE-153072 probably means allays need the can_swim property set to true in the minecraft:navigation.fly component so they can pathfind out from underwater blocks. But in this bug, they are pathfinding on the surface successfully - they just can’t detach themselves from it and move very slowly as of this release. They could touch water with no issues in the previous 26.0.26 Preview.

Still occurs in the 26.0.23 Preview. It is very noticeable when switching between riding a boat and riding a nautilus, as the nautilus turns smoothly like boats do in 1.21.124 Retail.

This would explain why the Deep Dark looks like it's lit up with the experiment enabled.

This appears to be fixed in 1.21.120-23. Thanks!

This happens because jigsaw pools include block processors which randomly change blocks. Ancient cities use them to create decay by replacing many of the deepslate and wool blocks with air and if there is a lever or candle or anything else on the block that is selected for removal it ends up floating.

While this is technically a bug, it is how jigsaw structures work in both versions of Minecraft and is more of an unfortunate side effect of the current implementation.

This issue should probably be moved to Launcher bugs by an admin as the Preview editor works and the new shortcuts just need to be documented. The launcher should be updated to use the new app resource locator string.

Thanks! You’re a lifesaver! Since the old shortcut didn’t work I didn’t know what the new resource locator string was (though now realizing looking through the default apps setting should have clued me in).

The issue seems to be the music system now only plays music files from the “music.game” section of the sounds_definitions.json files. For testing, I created the following sound definition file and packaged it as a global resource:

{
	"format_version": "1.14.0",
	"sound_definitions": {
		"music.game": {
			"category": "music",
			"sounds": [
				{
					"name": "sounds/music/game/one_more_day",
					"volume": 0.5,
					"stream": true
				}
			]
		}
	}
}

No matter what biome you are in in the overworld, you will only hear One More Day.

Note that if you are in Creative Mode that mode’s music does play as before. (But it seems the Creative Mode music definitions are hard coded somewhere as there are no definition entries for it in Bedrock.)

This may not be a bug. All non-marketplace add-ons need to add the following section merged into their manifest to prevent achievements being disabled:

"metadata": { "product_type": "addon" }

Issue is present in 1.21.70 retail release.

This is fixed in 1.21.70-25. Thanks!

I cannot edit my own issue for some reason. This bug is still occurring in 1.21.70-24.

I believe this is the Nvidia App causing this issue since it updates the Minecraft preferences to what it believes they should be set to when you launch the game.