I asked earlier if there are any particular objects on-screen when this bug happens; let me change that question. It seems to me that this bug happens to particular objects. Can you identify which kinds of objects it happens to, and also whether, when it happens, it affects all object of the same type, or only some particular one among them (like, say, whether it happens to all mulberry trees at once, or only one particular mulberry tree while five others are unaffected)?
"Object-oriented design is the roman numerals of computing." -- Rob Pike
epicbuds wrote:just got this game a bad review on my website and will post on every forum and game page i can think of to tell people to stay away from this site this game is a joke
viruseg wrote:Kill all new players for no reason. Polish scum came running and killed me with a crowd. Suck fuck fucks..
In my case, it happened to all the dandelions during that game session, whether on-screen or just nearby. Given that i could click and pick them, it could said that their model essentially "exploded". Maybe some shader goes haywire when certain parameters are involved, some that are constant per every one of them (like, the ones dependant on the time of the day). Guess i'll try to light a fire near one of them next time, so that i can see if changing their lighting (as the time of the day does) can influence said bug.
In my case it was apparently caused to cliffs? And they stick to the screen after moving around
W16 ??? W15 Lame road-builder of Eyjafjallajökull W14 Proud defender of Kakariko Village W13 Sporadic member of Ravka W12 Occasional member of Lake Town W11 Inactive member of Yggdrasill W10 King of The Northern Kingdom W9The Revenant of Wulf's Retreat W8 Lawspeaker of New Thotoshire W7 Lawspeaker of Esteldín
Jeff wrote:In my case, it happened to all the dandelions during that game session
Do you remember if there was a point where the dandelions worked, and that they broke sometime later, or were they broken from the very outset?
Nah, they were broken from the get-go.
Maybe it is due of some graphical element that gets processed, cached and reused during the session - but ends up having some fault during the processing phase?
I had this happen last night to a fireplace and a blueberry forageable. Different areas, same client session. I didn't take screenshots and unfortunately there weren't copies of the same object around to compare.