weird wakes happened with Comp Reimagined r2.3

[KA1N3o]

https://youtu.be/VcWEWiFlWQ4
here's a video so you can check it out.

[Goby56]

Is this only happening with shaders? If you turn them off I think you may see something similar but less pronounced.

I think this occurs when using the "vibrant" style in combination with age decay. In the mod's config, could you either try disabling age decay or change the style to "subtle"?

[KA1N3o]

Hey, thanks for responding me !
It's happen even i turned off shaders, plus only when i change wakes style to "Vibrant"

[Lafolie]

I'm also using Wakes, vibrant, with Reimagined 2.3 and not experienced this. Perhaps it could be GPU/driver specific?

I am on Arch Linux, GTX1060 6GB, proprietary driver in case that helps.

[Lafolie]

Okay, after some more playing I can confirm I have experienced this too. Can't say for sure what triggers it, because it doesn't happen all the time. I noticed the glitchy wakes after returning from the nether.

[Goby56]

Does disabling "Age decay" change anything?

[Lafolie]

So I tried playing around with that value (at least I think it was the right one, think you got the name wrong). If I set it to 0 I can't see any glitchy tiles, but anything other than that makes them visible again. The effect is really noticable if you set it to highest, with the long trail.

Speaking of this slider, could you change it to be logarithmic or some such? Anything lower than the default .9 results in a very short trail, and there's only one more notch until it maxes out. I really like the longer one, but would like to set a value of .95 or something.

Back on topic, I tried a bunch of the settings, nothing seems to have any effect other than making the wakes decay really fast, so the trail is so short you may as well not use a fancy mod like this.

[Lafolie]

Perhaps unrelated, but I have encountered weird yellow wakes in certain areas too. Related to biomes/temperature perhaps?

[Goby56]

Speaking of this slider, could you change it to be logarithmic or some such?

That's a good idea. I'll add that in the next version.