Uploaded image for project: 'Minecraft (Bedrock codebase)'
  1. Minecraft (Bedrock codebase)
  2. MCPE-167119

RTX / Ray Tracing Torch Lighting Broken in 1.19.6 update

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Duplicate
    • None
    • 1.19.60
    • None
    • Unconfirmed
    • Windows

      Good Afternoon, Thank you for taking time to look over this bug report. 

      I first noticed this issue after the 6th of February. At least that was my last world backup that this issue wasn't present. At first, I thought it was just some RTX bug or the Lumen 3.0 beta Texture pack acting up. I didn't pay much attention to it the first day. Then the next day, it still was present, and looking weird. The torches just felt much brighter than normal. I was use to placing a torch what felt like every 4-5 blocks to light a room, now one almost lights a cavern up (sarcastically speaking). 

      Then it struck me the white balance of the torch was messed up. Its bright white, it didn't have t he yellow "warm" hue to it. Ok well then I went crazy thinking ok maybe this is how it was suppose to be from the beginning, and I was use to playing a bugged version. 

      Then I notice my white wool was blue. (I don't have an image of this) and the texture looked beyond broken. This got me to start testing. I removed the texture pack, loaded an new one, same result. 90% of the wool was solid blue. Strange things were happening, so I did a little digging. 

      I noticed an update had taken place a few days since I started noticing the issue with the torches. I was like ok, maybe they did fix the issue and my torches are just brighter now. Not exactly. I was working on a gold farm, I've been playing Minecraft from Alpha, and I knew something was broken when a red stone torch put off the same light as my normal torch. As I made the redstone tower, I didn't have to use any light. That I found very odd, since Redstone torches have almost no light, but a faint red glow. 

      Now this got me really curious, so I started looking around I tested multiple worlds, different saves all gave the exact same results as the 1.19.6 screen shot. I came to the conclusion it was the update the corrupted the lighting. Now I just needed to prove it. I found a video talking about an un-official launcher that will let you run old versions. I found this out because pretty stupid of the devs, and I don't care what reason, you Auto-Update your worlds, and you cannot roll them back or choose to stay on "x" version, like Java. * Which let me stat for the record now, this needs to be a thing in the official version. * 

      Now after spending a little time checking to make sure this launcher was legit, I installed it and tried my worlds. First world I imported couldn't be used as it was too new. So I kept importing till I found my 6th's export. Opened up the world, everything looked normal. Success, I got the proof I needed. I went into creative and flew to about the exact same location and set up the torches. Success, red stone glows properly, Normal torch looks like i remember, but the Soul torch, seems off. I put up a lantern an immediately noticed the blue hue was missing. So as of 1.19.51 Soul torches have been bugged. 

      My world / play through was not advanced enough yet to see this without creative for the soul lights so I thank creative mode for helping out here.

      I hope to see this resolved in a coming patch, as i have a hard decision to make for now, continue in the old world and have to spend days reworking the gold farm stuff, or continue on the current version where the lighting is jacked up, hoping this gets resolved quickly. As for now it's just the gold farm progress next week could be significantly harder to roll back and redo progress. 

      Thank you for your time, good luck on the bug hunt. 

      • Nightingale

            Nightingale1176 Nightingale1176
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: