this bug has been going on for months, uninstall/reinstall does not fix, usually about 1-2 minutes before blocks bug out.
Minecraft Crash Report ----
// Who set us up the TNT?
Time: 10/31/19 6:01 PM
Description: Manually triggered debug crash
java.lang.Throwable
at cya.b(SourceFile:530)
at cyc.m(SourceFile:1477)
at cyc.e(SourceFile:925)
at cyc.b(SourceFile:410)
at net.minecraft.client.main.Main.main(SourceFile:155)
A detailed walkthrough of the error, its code path and all known details is as follows:
---------------------------------------------------------------------------------------
– Head –
Thread: Client thread
Stacktrace:
at cya.b(SourceFile:530)
– Affected level –
Details:
All players: 1 total; [dmp['SneakyMidget'/159, l='MpServer', x=-229.72, y=66.00, z=72.47]]
Chunk stats: Client Chunk Cache: 729, 482
Level dimension: minecraft:overworld
Level name: MpServer
Level seed: 0
Level generator: ID 00 - default, ver 1. Features enabled: false
Level generator options: {}
Level spawn location: World: (-208,69,32), Chunk: (at 0,4,0 in -13,2; contains blocks -208,0,32 to -193,255,47), Region: (-1,0; contains chunks -32,0 to -1,31, blocks -512,0,0 to -1,255,511)
Level time: 1295 game time, 1295 day time
Level storage version: 0x00000 - Unknown?
Level weather: Rain time: 0 (now: false), thunder time: 0 (now: false)
Level game mode: Game mode: creative (ID 1). Hardcore: false. Cheats: false
Server brand: vanilla
Server type: Integrated singleplayer server
Stacktrace:
at dkf.a(SourceFile:421)
at cyc.b(SourceFile:1923)
at cyc.b(SourceFile:425)
at net.minecraft.client.main.Main.main(SourceFile:155)
– System Details –
Details:
Minecraft Version: 1.14.4
Minecraft Version ID: 1.14.4
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: 917784864 bytes (875 MB) / 1979711488 bytes (1888 MB) up to 2147483648 bytes (2048 MB)
CPUs: 12
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: 1.14.4
LWJGL: 3.2.2 build 10
OpenGL: GeForce RTX 2070 SUPER/PCIe/SSE2 GL version 4.6.0 NVIDIA 441.08, NVIDIA Corporation
GL Caps: Using GL 1.3 multitexturing.
Using GL 1.3 texture combiners.
Using framebuffer objects because OpenGL 3.0 is supported and separate blending is supported.
Shaders are available because OpenGL 2.1 is supported.
VBOs are available because OpenGL 1.5 is supported.
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: 12x AMD Ryzen 5 2600X Six-Core Processor
Attachments
Comments 10
no brightness values have been changed, and this has been ongoing for 2+ months now. Im pretty positive its the most current version as i just reinstalled the game the same day i made this post.
This is still an issue at 1.15 this has been happening since like 1.13 but nobody ever has a fix, they usually just make me wait until the next patch so i can say its still broken
Wow, you mods are hilarious, yes this is still happening in 1.15.2 with latest drivers. Are you guys ever going to actually give some sort of support, or troubleshooting? So far your only answer is waiting for the next patch then asking me is it still broken when you've offered zero support, only commenting every month to ask has our minor patch fixed your game breaking problem.
There's no support here. This is a bug tracker and it is important for the developers to know if a bug still applies to the latest version so it can be looked at at some point.
With the rendering changes in 1.16, it might be fixed for you now in 1.16 Release Candidate 1 or later.
This actually appears to be a duplicate of MC-186601, which hasn't yet been resolved because this seems to be a more active ticket. If you have any additional information to provide regarding this issue, feel free to comment on the parent ticket. If you feel that this issue is affecting you, feel free to vote for the duplicated ticket, to give Mojang a basic idea of how many people are impacted by the problem. Just to further inform you, this will not determine how quickly the bug gets handled or fixed.
Have you changed the brightness value outside of Minecraft? Did this start happening just recently or for a while now? Also, can you check whether the issue is still in the latest 1.15 development version of the game (currently 19w44a)?