You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am seeing your RFtoolsUtility uses some kind of screen shader that disables any other shader from making the screen function properly. This causes some minor issues and graphical glitching that unfortunately makes working with the screen very bothersome.
Result with shaders
Expected result with shaders
The entire screen block is seethrough except for text.
Reason I could "fix" hack it is by putting black concrete behind the screen so its "circumventable" for people who are looking for a temporary solution
The real fix is either for the shaders to support said block, which I am not sure if that'll be done, or to create a seperate shader like Botania does for your block so the shader mod doesn't automatically modify the block and will not touch it.
Look at botania's internal shader support in their config. If you could add this I would be extremely happy! And I can definitely see others appreciating this as well!
Thank you for all your great work thus far and continued support @McJty :-) 👍
I wish you a wonderful day!
The text was updated successfully, but these errors were encountered:
Hmm, a PR fixing this would be nice though as I'm really very bad with shader stuff. Wouldn't even know where to start and pointing to another source code doesn't really help as that's hard to adapt to mine
I see, is there anything I could possibly do to get a fix for you? Excuse my inexperience but how does referencing a source that hosts a potential fix not do anything for this mod? Is it coded that much differently? They use the same language and API correct? Meaning you can reference the same things within limitations of course I do know there are substantial differences in mod creation within minecraft, forge, neoforge and fabric, but this is mostly the same tree is it not?
I could ask botania's creator if he might have a potential insight? I don't really know if I can see sourcecode openly as it is inside a jar file. Are they encrypted or can you mostly unpack them with sourcecode intact? I might be able to tinker around if you give me permission and a tiny how to what programs to use to get an insight on it.
Not saying I can fix it myself, far from, but I can always dedicate quite a bit of time and effort to finding the right people and looking into the issue myself long enough.
@McJty thank you so much for your quick reply by the way :-) It goes a long way!
Hi there!
I am seeing your RFtoolsUtility uses some kind of screen shader that disables any other shader from making the screen function properly. This causes some minor issues and graphical glitching that unfortunately makes working with the screen very bothersome.
Result with shaders
Expected result with shaders
The entire screen block is seethrough except for text.
Reason I could "fix" hack it is by putting black concrete behind the screen so its "circumventable" for people who are looking for a temporary solution
The real fix is either for the shaders to support said block, which I am not sure if that'll be done, or to create a seperate shader like Botania does for your block so the shader mod doesn't automatically modify the block and will not touch it.
Look at botania's internal shader support in their config. If you could add this I would be extremely happy! And I can definitely see others appreciating this as well!
Thank you for all your great work thus far and continued support @McJty :-) 👍
I wish you a wonderful day!
The text was updated successfully, but these errors were encountered: