The bug
When using a Totem of Undying, a red or blue tint can be seen around the screen when in F5 mode regardless of enabled resource packs. This does not happen in 20w21a and previous snapshots.
The red tint occurs whenever there are no more items left in the inventory after using a Totem of Undying while the blue tint happens whenever there are items left after using the same item. The original message from @unknown is shown below:
Well, whenever I am out of totems, I get the red tint, and [whenever] I have totems left in my hotbar, I end up getting the blue tint.
Causes
This bug might be caused by the experimental rendering changes that have been implemented in the snapshot.
It might also affect only certain graphics cards, so please make sure to attempt reproduction and then write down the results in the Comments section. If successful, please check graphics card specifications by pressing F3 + C for 10 seconds and then attaching the crash report here.
Affected graphics cards
This section will be removed if all graphics cards are affected. The list of affected graphics cards so far is shown below:
Intel(R) HD Graphics 4000 GL version 4.0.0 - Build 9.17.10.2932, Intel
GeForce GTX 1060/PCIe/SSE2 GL version 4.6.0 NVIDIA 419.67, NVIDIA Corporation
GeForce MX150/PCIe/SSE2 GL version 4.6.0 NVIDIA 391.35, NVIDIA Corporation
How to reproduce
General procedure
Press
F5to switch from first-person view to third-person view.Obtain a Totem of Undying and then hold it in the main hand or offhand slot.
Use the following command below to teleport 24 blocks high and then die from fall damage:
/tp ~ ~24 ~
Red tint
Make sure there are no other items in the inventory before the player dies from fall damage.
→ ❌ You will notice a red tint after using the item.
Blue tint
Make sure there are other items left in the inventory before the item is used.
→ ❌ You will notice a blue tint after using the item.
Attachments
Comments 7
Please force a crash by pressing F3 + C for 10 seconds while in-game and attach the crash report (minecraft/crash-reports/crash-<DATE>-client.txt) here.
Not sure if you were talking to me, but here it is
Minecraft Crash Report -------- Minecraft Crash Report ----// Why did you do that?
Time: 5/31/20 7:51 PMDescription: Manually triggered debug crash
java.lang.Throwable at dlc.b(SourceFile:461) at dle.p(SourceFile:1539) at dle.e(SourceFile:966) at dle.d(SourceFile:627) at net.minecraft.client.main.Main.main(SourceFile:214)
A detailed walkthrough of the error, its code path and all known details is as follows:---------------------------------------------------------------------------------------
– Head --Thread: Render threadStacktrace: at dlc.b(SourceFile:461)
– Affected level --Details: All players: 1 total; [eam['SlicedBlock'/16, l='ClientLevel', x=-321.41, y=4.00, z=-153.49]] Chunk stats: Client Chunk Cache: 729, 473 Level dimension: minecraft:overworld Level spawn location: World: (-256,4,-256), Chunk: (at 0,0,0 in -16,-16; contains blocks -256,0,-256 to -241,255,-241), Region: (-1,-1; contains chunks -32,-32 to -1,-1, blocks -512,0,-512 to -1,255,-1) Level time: 330240 game time, 1000 day time Server brand: vanilla Server type: Integrated singleplayer serverStacktrace: at dxt.a(SourceFile:471) at dle.c(SourceFile:2007) at dle.d(SourceFile:645) at net.minecraft.client.main.Main.main(SourceFile:214)
– System Details --Details: Minecraft Version: 20w22a Minecraft Version ID: 20w22a Operating System: Windows 10 (amd64) version 10.0 Java Version: 1.8.0_51, Oracle Corporation Java VM Version: Java HotSpot(TM) 64-Bit Server VM (mixed mode), Oracle Corporation Memory: 1372747328 bytes (1309 MB) / 2113929216 bytes (2016 MB) up to 2147483648 bytes (2048 MB) CPUs: 8 JVM Flags: 9 total; -XX:HeapDumpPath=MojangTricksIntelDriversForPerformance_javaw.exe_minecraft.exe.heapdump -Xss1M -Xmx2G -XX:+UnlockExperimentalVMOptions -XX:+UseG1GC -XX:G1NewSizePercent=20 -XX:G1ReservePercent=20 -XX:MaxGCPauseMillis=50 -XX:G1HeapRegionSize=32M Launched Version: 20w22a Backend library: LWJGL version 3.2.2 build 10 Backend API: GeForce GTX 1060/PCIe/SSE2 GL version 4.6.0 NVIDIA 419.67, NVIDIA Corporation GL Caps: Using framebuffer using OpenGL 3.0 Using VBOs: Yes Is Modded: Probably not. Jar signature remains and client brand is untouched. Type: Client (map_client.txt) Resource Packs: Current Language: English (US) CPU: 8x Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz
@SlicedBlock: Your drivers are quite outdated, try if updating them does anything: https://www.nvidia.co.uk/Download/driverResults.aspx/160004/en-uk
I am aware of it although I do not want to update them since it might cause me to experience another bug known as MC-186080.
worked for me when I was in 3rd person mode, but I don't know how to check my graphics card..