The custom sky is conflicting heavily with shaders. I turned off the custom sky in the config and that resolved the issue only on a local game. The server overrides the config setting of the client. A suggestion for resolving the conflict would be to allow the clients to ignore server settings dealing with the custom sky. I am using the current version of Kuda Shaders (v65.56). I am also using v1.4.5 of Astral Sorcery

Relevant screenshot below.

You will notice the discoloration of the sky at the cross hair. The horizon and celestial bodies follow the cross hair. I can confirm that it is not a hardware issue, both of my friends can confirm same issue and our rigs are vastly different.

I have some more info after some testing. I made a world with the default config in a local world. I closed the client and changed the white list in the config to have the overworld blacklisted.

I the restarted my client and entered the local world again. The sky glitch still persisted. I then removed the mod, and unsurprisingly, the sky glitch disappeared.

The surprising thing happened after closing my client and re-added the mod with the config change. The sky glitch then reappeared.

I looked through the closed issues. (Which were hidden be default.) I am attempting one of the fixes mentioned in the report. I am curious how the above post's result happened though....

The answer to this may be "Doomgull, consume more caffeine, its too early", but I don't follow. You changed the config and the glitch happened, removed the mod an the glitch disappeared, then readded the mod with the same config where it glitched and are surprised the glitch is still around?

Here is a step by step with numbers:

1. New install with default config.
2. I changed the white list in the config to black list the overworld. This resulted in no change in the render glitch.
3. I removed the mod completely, including config. This fixed the rendering.
4. In the same world, I re-added the mod and the modified config. The glitch returned.

The expectation is that once removed, all data from the removed mod is removed. Then the clean re-installation of the mod "should" be loaded with the config changes. However that isn't what happened.

Also, using the weak render option fixed the issue. I suggest putting a note in the config notating the shader conflict and the fix. Or make the current line which reads:

"IF a dimensionId is listed in 'skySupportedDimensions' you can add it here to keep its sky render, but AS will try to render only constellations on top of its existing sky render."

read something like this: (Caps used to denote change, not yelling)

"IF a dimensionId is listed in 'skySupportedDimensions' AND HAS A CUSTOM SKY RENDER you can add it here to keep its sky render, but AS will try to render only constellations on top of its existing sky render."

If you didnt remove the config file when you pulled the mod, it wont regen it. Thats default mc behavior.

And thats what the weakrender option is for.

The config was removed btw.

The server config doesn't override client config for that option by default unless something else is forcing it to do so.

#13