Simon

Very good news to see this re-opened.

And whilst I think everyone understands some things are not simple to fix ( i.e.  you mean they are expensive to fix), just closing defects without explanation is not best practice and causes a reaction. Whilst I agree this shouldn't be a discussion forum, that does not mean you cannot be more transparent.

In the spirit of new information, I originally reported this under a different bug report.

At that time the card in question was a 3070 rtx.. I have now switched to a 4090 rtx, and the same problem persists with those texture packs.. maybe that's useful insight? After all, that's the flagship card on the market right now; if that can't cope, you must have a fairly serious underlying problem.

Hope the helps.

Good luck.

FWIW - Same problem for me

Latest version of MC Bedrock

Tried with multiple different RTX packs - all have the same problem, but with varying degrees of how badly. Sometimes it works.. but infrequently.

Have tried all the various suggestions out there from VSync options (Which is pretty broken in its own right), to re installing nvidia drivers, and trying older version of nvidia drivers. Usually, re installing the driver will initially work, but next session it's broken again)

In order of worst-behaving-first

Defined PBR (got it to work once, haven't been able to since), JG Rtx, Kelly's RTX, Vanilla Normals, Vanilla, Mosaic RTX.

(Then there's the whole other sh*tshow which is adding the to realms. I can only get Mosaic to reliably install on a realms. None of the above will work of a realm using my local global resources - it just ignores them and/or fails to uploaded, so Mosaic works, but has to be added to the realm itself, but this may be another related issue. Still get the occasional crash and/or black screen except for torches)

Windows 11 (everything up to date)

CPU: AMD Ryzen 9 7950X  
RAM: 32GB DDR5, 5200MHz
GPU: Nvidia GeForce RTX 4090 

Faulting application name: Minecraft.Windows.exe, version: 1.19.51.1, time stamp: 0x6390ea6a
Faulting module name: nvwgf2umx.dll, version: 31.0.15.2756, time stamp: 0x638e896e
Exception code: 0xc0000005
Fault offset: 0x00000000014ad0a4
Faulting process id: 0x0x5DB8
Faulting application start time: 0x0x1D928E4F38FDC27
Faulting application path: C:\Program Files\WindowsApps\Microsoft.MinecraftUWP_1.19.5101.0_x64__8wekyb3d8bbwe\Minecraft.Windows.exe
Faulting module path: C:\WINDOWS\System32\DriverStore\FileRepository\nv_dispig.inf_amd64_f52c4b8723f8dd33\nvwgf2umx.dll
Report Id: 7fa65edf-5c74-4771-87d4-ada98aa12b3d
Faulting package full name: Microsoft.MinecraftUWP_1.19.5101.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

Michael.

This MC-248295 report is the same as I reported. I found your answer in this report MC-248295, and found out you didn't understand this person either.
So I'll do new report when game stop working on my computer and I do photos.

Thanks, I will double check, but I'm sure the game is responding to Nvidia panel changes. 

I don't know if this helps but...

Out of curiosity I just spent an hour running around on Nintendo Switch using VanillaBDCraft on 32, 64 and 128 settings.

Whilst there is clearly some framerate drops near the area in question, its still very playable (I'm quite suprised) even at 128... and certainly didn't become troublesome.

By contrast, I retried on PC and within the area of where the drops / farming / chickens etc is it is all but unplayable; as before, low CPU and GPU usage but frames rates <20 and falling... however move away about 4 chunks and it literally snaps back into life... move back, immediately grinds to a halt. 

Anyway.. from an hour's random testing.. Switch is fine afaict, and PC is bugged.

Apologies, didn't meant to be imprecise by also being somewhat flippant 🙂 It's just amusing to have spent a weekend digging into the bowels of my PC setup, only to be undone by eggs 😉

I can't say for sure that one thing is worse than the other. 

I am as sure as I can be that its just a by-product of drops in general. What made it hard to spot initially is that in the area in question there are various mechanisms for collecting drops such as wheat, so the frame rate would drop and then climb again... but I didn't make the connection.

Since finding it, I've observed this happens when

• random stuff drops (such as eggs by spawned chickens)

• wheat drop etc, such as farmers produce.

• drops from mining / breaking stuff up when ,for instance, my inventory is full and I don't collect them up.

• and.. as of last night, after a bit more experimentation, I got the same effect when repeatedly placing water and then removing (for solidifying concrete powder) However in this case its impossible to say whether some drops occurred nearby... so treat is as questionable evidence.

• Naturally, if the game hasn't already frozen and one can move far enough away, the frame rate picks up again. 

Of course none of these are completely isolated tests. 

Eggs were a problem because, all the other thing were in my control (or automatically collected)... but random eggs being dropped were harder to spot.

Yesterday I ran the game for many hours using several different texture packs with no problem (both marketplace and other wise), just to satisfy myself the problem is only with the high res packs 

These were:

Defined PBR

Wanderlust

RealCW

Plus, Vanilla and Natural Texture pack both on their own and alongside NVIDIA PBR Pixel Art.

All of this ran flawlessly. Same world, same location, both on and off Realms server. A pleasingly comfortable capped 80fps with RTX on (12 chunks render distance), and FPS well over 120 without RTX, and 44 chunks distance. This is @ 3440x1440, both windowed and 'full screen' . In all instances the graphics card behaved as expected. ditto the CPU. 

In the error case in question, the slow down happens in lockstep with LOWER resource usage of both GC and Processor.

So, VanillaBD, PureBD and Hattoricraft I know have this problem for what appears to be all types of drops... and the effect is much more pronounced on a Realms server.

Also note. I have checked this out multiple times by completely wiping the game and reinstalling.

One final note I should have mentioned: In the process of diagnosing this, there was also clearly a problem with the default VSync setting in minecraft. It further lowers FPS unnecessarily (and seemingly with no relation to the actual refresh rate of the monitor which is 165 in my case). I have since turned this off and use NVIDIA to perform any FPS capping or other sync. The above problem exists regardless of vsync setting (tested).. but, mentioning for completeness. I understand this vsync issue is already well known.

Hope all that helps.

After a whole weekend chasing wild geese, I finally discover it's the damn chickens (drops!)

So, I can confirm this still happens on 1.18.2 (Bedrock) PC... 

Ryzen 2700 3.8 Ghz

Nvidia 3070 rtx

16Gb

Render distance (doesn't matter.. it happens on everything and with Ray Tracing on or off.. no difference)

AA (doesn't matter, happens with all settings)

64, 128 and 256 versions of the packs all exhibit the problem... just takes less time to grind to halt the higher the resolution.

In my investigations (before I came across this bug listing) I have tried sooo many combinations of things its laughable; however I can confirm it only seems to affect a number of "HD" resource packs, or at least the impact is only noticeable with them. It may happen with a low res pack, but perhaps it takes too long to matter.

PureBDcraft

VanillaBDCraft

Hattoricraft

Are the main ones used to confirm this.

When using no resource packs, other lower res pack like Wanderlust and all with and without raytacing, everything appears fine. At least, I've played for over 300 hours without the problem.. only switching to other HD packs has caused this.

Which also means I've tried virtually everything else and its not the usual stuff like vsync, GPU enablement etc.. my system and settings are all as correct as they can be and without this problem frame rates are in the hundreds, or around 60-100 with ray tracing.

Its eggs (and other drops)... pick em up and the frame rate shoots back up... let them lay them, and each one further lowers the FPS until the the thing hangs completely. 

Yes.. I timed eggs 🙂

Also, this effect appears to be more pronounced when using a Realms server. (But it happens locally as well)

As I happen to be monitoring at the same time, I can confirm there are NO CPU, GPU, Ram or VRAM bottlenecks... in fact, interestingly the resource utilization goes down with each additional item dropped. 

Now.. hopefully a fix will follow... but in the meantime do I just use a low res pack.... or take it as an added game challenge? lol.

No it's not I didn't modify anything? it even says that in the report. I only turned LAN mode on to go into creative and go to the chunks

In 21w39a I spawned too on ocean.

Dhranios

Only I was standing on the blocks.

If it's anything like my experience, I was asked to migrate and I'm now locked out entirely. Trying to log in with Mojang no longer works. Clicking back to login with microsoft winds up taking me to a (wrong) web page with a mojang login box and no microsoft login box. Clicking "log in" again in the corner presents a microsoft login. When you eventually log in with microsoft on the web page, no luck there either - no obvious means of launching the game or fixing the issue. Seems to be screwed up. If that's whats happened to you too, please clarify. Just trawling through looking for possible solutions on these bug tickets.

I had the same issue - when I click the green button I get taken to a web page with only a mojang login option. Clicking the LOG IN text again in the top corner then presents a Microsoft login option. Logging in simply takes me to a profile page with no obvious means of launching the game (java edition). There is a big yellow "change settings in microsoft.com" button. Clicking that takes me to https://account.microsoft.com/?refd=www.minecraft.net with no visible indication of what settings to change. First impression is that these guys have botched it and not tested it at all.

This is the same Christina, I have done all the steps you mention above and still no joy with minecraft on the switch, However works fine for my son using his login details on xbox.

Hopefully this will be sorted soon by the devs.

This all started when he used minecraft on xbox. I have just signed out of his microsoft account on switch, but still taking ages to load. Surely there must be a fix. The online subscription does not end until end of 21.

Yes, that is essentially the conclusion of this bug, as well as some others.

I see the resemblance to MC-11193, I definitely believe Pistons are affected by world position, but I think this is just the same issue in 2 different versions, fixing one will most likely fix the other.

However I don't think MC-9714 is related. Sure it's a redstone bug but I think it has to do with the wires, not the Pistons. Unless more tests are done that show different results based on Piston coordinates.

Well yes but also no. Is the Netherite Block on the exact coordinates I said? If not that explains your result, you see if that structure is placed with its center where I said, XYZ (62, 58, 7), some of the blocks should be pushed up, however other coordinates give different results. Even if you are unable to reproduce the extension of the Sticky Pistons it should be considered a bug, as removing the bottom Sticky Piston makes the side Pistons extend, and if you replace the side pistons with Repeaters gives signals with or without the bottom Sticky Piston (but of course it's a single redstone tick signal with the Sticky Piston, and a continuous one without it).

Also can you confirm your contraption looks like this? I am aware I might have done a poor job explaining and you might have misunderstood my instructions.

No Marty, I do not have any of the sort, and that's strange considering it happened to me consistently in 3 different worlds, superflat standard, superflat readstone ready and a random seed. Closing and reopening the game does not affect anything. But are you meaning that all the upper Sticky Pistons extend and leave their block? Or do they just not move?

I dont think its suppoed to say "If you believe that this is IN error" but instead say AN error!?