SCtester

The issue has been resolved as of Jan 24th.

The symptom of this issue specifically relates to the fog, whereby the entire sky takes on the fog color rather than just the horizon. It is particularly visible during sunset/sunrise, when the fog changes color, as in this comparison.

The issue is still present in the latest update.

Thanks for that information, MADLAD3718 - after testing it, it's true that disabling vsync resolved the issue completely - confirming that this is in fact a software bug. I hope it gets resolved soon.

Same experience on 1.18.10.20. On 1.17, Prior to 1.18 betas, my Nvidia RTX 3070 handled RTX flawlessly - but now it's almost unusable due to lag and choppy frames. Both my CPU and GPU are at less than 10% utilization, often even below 5%, so it's likely some other bottleneck. Render distance seems to have either no or almost no impact - it's roughly the same amount of choppiness at 8 or 24 chunks.

It's possible that by "the way the resource pack stacks", they may have meant the order in which certain aspects within the resource pack are rendered - for example, if RTX textures (ie. PBR, luminosity, etc.) are rendered before texture variants, then it could mean texture variants wouldn't match up with the RTX material textures.

With that said, even if this theory was true, it still would be no explanation for why it's an intentional feature. This might mean that it's hard to fix, but by no means would it be justification for it being intentional or by design.

Given that this bug is a big limiting factor in the work I do, I would love to speak with the developer who gave the explanation for why it's intended (or any developer on the RTX team, for that matter), in order to better understand it - as I cannot comprehend how the stacking of resource packs, regardless of which meaning that has, would render texture variation an intentional feature.

I can confirm that the issue is still present in 1.18.0.21 Beta as well as 1.17.34.

Thanks for that information, Jeffery - that's good to know. I'll add that deleting the texture pack or world file manually in File Explorer did not resolve the issue for me. I personally experienced the issue on Windows 10, and have received complaints from two users reporting the same issue - one on Nintendo Switch, and the other on Xbox.

I think this issue is especially bad given that it impacts paid content, both from the perspective of content creators and users. It unfairly negatively impacts content ratings for the content creator, and for users, it renders content unusable which they paid money for. I'm sure it also deters buyers from purchasing further content from the Marketplace once they've experienced the issue. So, I hope a fix is implemented as soon as possible.