キ

This issue was fixed in the full release of 1.21.120.

This file is used by the game. When a new player creates their first world, a seed is selected from StarterSeeds.txt.

I had already provided steps to reproduce the issue in a previous comment. The fact that you are requesting them again suggests that the comment was not reviewed when it was originally posted, nor at this time, which is disappointing.

I will provide the steps I used to reproduce the issue once more.

Steps to Reproduce:

Method 1:

1. Enable Improved Input Response in Settings > Video.

2. Open a world.

3. While chunks are loading, move the camera around with the mouse, similar to the motion shown in the attached video.

Method 2:

1. Ensure Minecraft is closed.

2. Open the options.txt file located at
   AppData\Roaming\Minecraft Bedrock Preview\Users\games\com.mojang\minecraftpe.

3. Set gfx_vsync from 1 to 0 to disable V-Sync.

4. Launch Minecraft.

5. In Settings > Video, expand Fancy Graphics Options and set Framerate Limit to 60 FPS.

6. Open a world.

7. While chunks are loading, move the camera around with the mouse in the same manner as before.

Observed Results:
Even though the frame rate consistently remains at 60 FPS, the camera movement frequently appears jittery. While the issue is less noticeable in the attached video due to compression, it is very apparent in-game.

Expected Results:
Camera movement should remain smooth at all times unless the frame rate drops.

The issue appears to be related to chunk loading, as it only occurs while chunks are being loaded.

This sounds like a malfunction of the “Lower Framerate When Controller Is Disconnected” option (which is currently misnamed; see MCPE-235087 for context).

This option reduces the game’s framerate to 10 FPS after one minute of inactivity with the Pause menu open, or after 15 minutes of inactivity with the Pause menu closed. When activity resumes, the framerate should return to normal.

Do you have this option enabled? If so, try disabling it. It can be found under Settings > General.

Note: This option can only be changed from the main menu, so please make sure to exit your world before checking.

I suppose for now I will live without Vibrant Visuals

It is unclear whether this is a typo; however, no add-ons are required to use Vibrant Visuals. Go to Main Menu > Settings > Video, open the Graphics Mode dropdown menu, and select Vibrant Visuals.

Note: Mojang Studios is tracking the Marketplace content download issue and the Text-to-Speech issue in the following reports:

• MCPE-235141

• MCPE-232656

A moderator will likely close this report as a Duplicate soon.

Skeleton horses are not pets and cannot be tamed, so displaying a death message for them does not make sense. The fact that they can be ridden and controlled does not make them pets or tameable mobs.

This behavior is consistent with other non-tameable but rideable mobs, such as pigs and striders.

Your command block is not connected to any redstone dust. The redstone line must be connected directly to the command block in order for it to receive power. Alternatively, the command block can be powered by placing a redstone torch or a redstone block directly adjacent to it.

Regarding the Previous Output field, as the name implies, it displays the output from the last command that was executed. Since the command block was just placed and has not yet been powered, it is only showing the default information. Once the command block is powered and a command is executed, the Previous Output field will update accordingly.

If the command block still does not function after being properly powered, providing a video of the issue would help with troubleshooting.

I have identified an important detail regarding reproduction of this issue. It appears to occur only when the CPU is lightly loaded. As a result, the CPU must be under low load for the issue to reproduce.

Playing in a Flat world with a powerful CPU should be sufficient. If using a weaker CPU or playing in an Infinite world, lowering the render distance or other settings may help reduce CPU load and reproduce the issue.

I am not using a laptop; I am using a custom-built desktop PC.

The system specifications are as follows:

• CPU: Intel® Core™ i5-14600K Desktop Processor

• GPU: AMD Radeon™ RX 9060 XT (16 GB)

• RAM: 32 GB DDR4-3200 MHz

@[MCQA] Baslod, please refer to my comment above.

Here is a video demonstrating the issue using an on-screen overlay. As shown, once the second hotbar slot is reached, the game no longer detects scroll wheel input.

As a side note, when requesting that users install specific software, I would strongly recommend naming the software explicitly and providing a direct download link, rather than expecting users to locate and download it themselves.

When Copy Coordinates UI is set to Block Position, it copies the coordinates of the block you are looking at. In this case, you are looking at an entity rather than a block, so the coordinates are correctly reported as invalid.

You can also reproduce this behavior by spawning an entity anywhere, looking at it from any distance, and then opening the chat; the coordinates will likewise be shown as Invalid Coordinates.

No bug is being described here—the feature is functioning as intended.

This behavior still occurs in the latest Preview version, 26.0.26.

Pink Petals are not affected. @Freccjjbb, unlike birch trees, oak trees do not require a nearby flower to generate with a Bee Nest, so this was simply a case of unlucky RNG.

See MCPE-155833, where the oak tree issue is tracked.