Please remember that this is not a support forum. If you want to discuss this among yourselves, there are plenty of places you can find and chat with other community members, such as the Discord or Reddit. If you want to discuss it with Mojang, you need to contact the Community Management team on Discord or their Twitter accounts. Comments here should provide new information for the developers, and we also welcome sharing workarounds with each other, but excess chatter will be removed.
When Ray Tracing is supported by the GPU, the game runs with decreased performance even when Ray Tracing is not enabled in the settings.
From testing, an RTX 3080 Ti gets drastically lower framerates than a GTX 1060 does in the same world with the same settings. In situations that are known to cause frame drops (such as having a large number of entities, lots of item frames, or using a high-res resource pack), the performance hit is greatly exaggerated on RTX GPUs.
It can be proven that this is not an issue with the GPU itself by using the workaround listed below or downgrading the Nvidia drivers to an older version (442.74) where Minecraft doesn't detect the GPU as Ray Tracing capable. The performance will be back to expected levels. Some Windows versions may also stop the game detecting RTX, fixing the performance. Versions without Render Dragon (meaning they don't have RTX support) also have correct performance.
It seems that when the game does not detect a Ray Tracing compatible GPU, it runs at the FPS it should.
Minecraft Preview shows that RTX cards use "D3D12 RTX" and GTX ones just use "D3D12". The RTX version has a large FPS hit for players who aren't using Ray Tracing.
Steps to test the difference:
While using a GTX GPU that has no ray tracing capability, get into a situation that will tax the system slightly. (for example place 100 filled item frames or spawn 50 mobs)
Make sure VSync is disabled and note the average framerate.
Swap the GTX GPU for a more powerful RTX one. (or disable DXR Raytracing in NVIDIA Profile Inspector)
Load the same world with the same graphics settings. (with Ray Tracing off in the settings)
Experience a lower framerate than the less powerful GPU.
Expected Result:
The RTX graphics card is significantly more powerful than the GTX one, so it should have a higher FPS.
Observed result:
The RTX graphics card performs much worse than the GTX one.
Screenshots/Videos:
Performance comparison between GTX 1060 and RTX 3080 Ti, with all other hardware/settings/packs left the same.
[media]
Notes:
When Ray Tracing is disabled in the game settings, it is not fully disabled. Something seems to change when RTX is available for the GPU.
This bug looks to be the root cause of MCPE-153297, MCPE-111547, MCPE-157142, and possibly MCPE-142934 for some users.
I think this bug is capping the performance of everyone playing using an RTX GPU, but goes unnoticed as people with frame drops aren’t comparing the performance to a lower-spec GPU without Ray Tracing support.
Workaround:
With the latest version of NVIDIA Profile Inspector, you can now disable DXR Ray Tracing for only Minecraft, fixing performance! Select the Minecraft profile and set "Raytracing - (DXR) Enabled" to "RT Disabled".
The game will report that your device is incompatible with RTX, however you'll now have performance that matches a non-RTX GPU! If you ever want to use Ray Tracing, just change the setting back to "Default" and the in-game option will be unlocked. For some reason the Minecraft profile in Nvidia Profile Inspector doesn't affect Minecraft Preview, so to test D3D12 on that version of the game you'll need to temporarily disable DXR on the global profile and re-enable it when you're done.
Alternate workaround:
Minecraft switches to D3D11 if the GPU recovers from a crash while RTX is enabled.
We can test a "timeout detection and recovery" by running "dxcap -forcetdr" in an administrator command prompt. This may require "Graphics Tools" to be installed in the optional features page of the PC's settings. When I tried this the screen went black for a few seconds and then Minecraft Preview reported that it was using D3D11 instead of D3D12 RTX! There's a black screen in game until Ray Tracing is off again but after that it'll be on D3D11 until the game is restarted. FPS improved by a lot around item frames and 512x packs worked perfectly. Doing this can and did cause issues with other software/hardware. I'm not an expert, so if you use this it's at your own risk!
Linked issues
is duplicated by 4
Attachments
Comments 26
I would say this is not a duplicate of that issue, as this one does not include GTX graphics cards as being affected. However this bug is likely the cause of that one and I agree it should not have been marked as a feature request!
Yeah, but the two issues are talking about pretty much the same thing, doesn't matter though. The more information, the better! Thanks for your support and for creating this issue. It's nice to know that I'm not the only one. I put your bug report in my report at the top of the report so they can gather more information from other people.
This issue has been in the game for so long now. It makes doing basic minecraft things unplayable.... The GPUs affected are all Nvidia RTX GPUs(not sure about other non Nvidia RTX Capable GPUs) and I think the GTX 1060(Nvidia has said this GPU has RTX capabilities, but im not sure if its affected), 1070, 1070 ti, 1080 and 1080 ti. These GTX GPUs have a small amount of RTX capabilities like reflections and/or shadows which is probably why this problem is happening.
I went as far as messing around with minecrafts game files and still haven't found a better solution than downgrading Nvidia drivers.. What I find a bit odd is if I remove the ray tracing folder from minecraft, the issue still exists.
My youtube has 2 videos showing the difference in performance with Nvidia Driver 442.74 and the latest version.
After hours of testing, I have figured out that this bug is caused by Minecraft using "D3D12 RTX", which is the version that only Ray Tracing compatible GPUs are allowed to use. The 1060 just uses "D3D12".
In 1.18.30, a version affected by MCPE-152645, you can force "D3D11" (DirectX 11) and bring performance back to normal! There is less item frame lag than the 1060 and 512x packs work fine! However, DirectX 11 doesn't support RTX, meaning you get a black screen in-game while Ray Tracing is enabled in the settings.
If anybody knows of a way to force D3D11 or D3D12 on the latest version, that would be a good workaround until Mojang can fix DirectX 12 RTX or make it optional.
Edit: Added more specific DirectX version names from Minecraft Preview
I've only done a small amount of testing but it looks like this bug has finally been fixed!
The patch notes only mention that the debug HUD text was modified, but there have clearly been more changes under the hood.
"D3D12 RTX" has now been renamed to "D3D12+", and RTX features are now only enabled when Ray Tracing is enabled!
This update has given me a 400% FPS boost in my world's most taxing areas, and there is no longer any FPS drop when holding a 512x resolution item. Absolutely overjoyed that this is fixed.
This change also means that MCPE-153297 and MCPE-111547 are both fixed, along with MCPE-142934 for some users.
I spent a few minutes trying out preview 1.19.80.22, and was getting expected FPS values. I was able to look at a 10x10x10 of chests and maintain a constant 240FPS. I Tried holding a high resolution item(512x512) and didnt drop to 20FPS like it normally would with D3D12 RTX.. It seems like the issue with RTX capable GPUs performing poorly, is fixed.. I agree with Liam though that high resolution items render improperly with a ray tracing resource packs enabled.
Fixed in 1.20.0.21
I have tried the latest preview 1.20.0.21 and the problem was solved. I am attaching screenshots of the same area, one in the official version and the other in the previously mentioned preview.
[media][media]
After testing, I can confirm this is fixed in 1.19.80! (again not mentioned in the changelog)
Compared to Preview 1.19.60.20, this update brings me a 4x FPS increase and I can now play on my world without needing any workarounds. Thank you for fixing this.
[media]As stated in the Description, the bug tracker is not the place for discussions. Please do so on Discord / Reddit, etc. Comments that appear to be questions directed at other users will be removed.
If you think you have found a new bug, please search first and create a new report if not already reported.
Pretty much a duplicate of: MCPE-157142