"Shared/Same Context Buffer" LOD Builder Failure
Hi all. I've been using Distant Horizons in Allthemods-10, and have had no issues for around a month so far. However, today I've encountered a bug that no solution a search engine or the FAQ has been able to fix. I've even nuked the config file and restarted computer.
The LOD Builder component will queue jobs but never actually complete them. Every job in that sequence beforehand can complete fine. In debug mode, the "Rendering" to "Same/Shared Context Buffer" will cycle endlessly, along with the CPU limit warning if I walk around enough to get the queue to 1,000.
This problem would occur intermittently over the past week and usually a restart would fix it. However, when I loaded a new dimension via Compact Machines, the problem became consistent and unfixable. I know it is not a compatibility issue as I've been playing for a month and loaded other modded dimensions just fine without issue. During this, no in-progress wireframes are visible.
Error messages are visible in screenshot. Modlist is the standard ATM10 version, as of October 24, plus Simple Clouds, Chunky (not running) and Distant Horizons. Singleplayer world only. No logs, this never caused a crash.
Solution:Jump to solution
Switching to nightly build fixed it, but i'm not gonna mark it as a solution since that involves a more generally unstable build type.
10 Replies
Oh, and: if anybody responds to this and I'm not in-game, do expect a delay as I finish what I'm up to and reload it.
Solution
Switching to nightly build fixed it, but i'm not gonna mark it as a solution since that involves a more generally unstable build type.
(unless a mod wants me to)
The nightly builds are now pretty stable, and will be released as a stable build soon if no bugs are found. So I think switching to the nightly build is a good solution.
Okay then. Should I mark as solved, even if it's just using a different version?
I'll say upgrade to a nightly buld first, see if the issue persist or not before closing this thread as solved.
I did, and the nightly build fixed it. (And also seemed to be much more speedy!)
But I know not everybody updates to newer versions. Feels like a copout of a fix?
Why would updating to a newer version not count as a fix?
I dont get it
Anyway, marking the solution is solved is not that important anyway
Updating to a fixed version is considered a fix. Softwares do need updating to fix an existing issue.
OH! I totally forgot DH updates for multiple minecraft versions.
Okay, marking fix.