rendering issue with infinity armor and sword

[xtrux]

my infinity armor on my server is red for some reason but in singleplayer its normal. looks like this when on my server.

but with same modpack on singleplayer it looks normal like this

it only happens on this world too.

[SpitefulFox]

It looks kinda cool like that. Can we call it a feature? >.>

[xtrux]

is it a bug. it happens on my client only, it also looks like this

[SpitefulFox]

Which version of Avaritia is this?

[xtrux]

1.11

im on 1.7.10

[SpitefulFox]

Hm. I honestly don't know enough about opengl to figure out why it's showing showing red in multiplayer like that. Sorry. :c

[xtrux]

im going to try disabling fastcraft and see if it fixes

[xtrux]

k so i updated to 1.13 of avaritia in my custom infinity evolved server and it still happens. the glitch also happens with the cosmic shader in immersive engineering.

[xtrux]

this bug appears to also happen in most packs
happens in project ozone 3 except when im in galaticraft dimensions

[xtrux]

would the fact the server is being hosted off the same pc be relevant?
the bug also happens with the cosmic shader from Immersive Engineering

[xtrux]

i have done some more debugging because everytime i play modded mc i see this and get dissapointed because the sword looks so cool when its not bugged. i have found out that when world time exceeds 65536, the sword turns red. this happens in 1.12.2 and 1.7.10

[SpitefulFox]

Whoa. Good find. I'd put out a fix for the 1.7.10 version, but the forge sdk for 1.7.10 broke a long time ago and I don't know how to fix it.

[xtrux]

ah rip, im learning java at some point so im gonna try to make my own patch for the 1.12.2 version because it drives me mental.

[Dinhhokhanhnhat]

It looks cool. But you played in your own sever and had that rendering problem?

[xtrux]

im pretty sure the rendering problem is caused by the animation tick getting linked to the world time tick or something, which causes it to error once the world tick time reaches the 16 bit integer limit. figured this out by doing stuff like /time set 0 and time set 65536 etc

[Dinhhokhanhnhat]

im pretty sure the rendering problem is caused by the animation tick getting linked to the world time tick or something, which causes it to error once the world tick time reaches the 16 bit integer limit. figured this out by doing stuff like /time set 0 and time set 65536 etc

I think you should attribute the time?