Inserting Interaction Screen Modules into screens causes render issues with nearby chests. The render issues stop when the modules are removed from the screen.
(Shaders are enabled in the screenshots, but the issues persist when shaders are disabled. A potential clash with something like Rubidium or Oculus, maybe?)
Interaction Screen Modules' labels do not show at all, nor does the button text
Adding any text at all to the "label" field reduces the size of the button (shown above) but doesn't display the text.
Variable Screen Modules do not display anything when inserted into a screen (while linked to a processor with a defined variable).
The Text Module is functional, but the Variable Module isn't.
Versions:
Minecraft: 1.19.2
Forge: 43.1.55
CompatLayer (only if on Minecraft 1.10 or 1.11):
McJtyLib: mcjtylib-1.19-7.0.6
RFTools: rftoolsbase-1.19.1-4.0.4
RFTools Control: rftoolscontrol-1.19-6.0.1
Possibly incompatible mods and versions: Rubidium, Oculus, Radon
Issue description: screen render issues
Steps to reproduce:
Inserting Interaction Screen Modules into screens causes render issues with nearby chests. The render issues stop when the modules are removed from the screen.
(Shaders are enabled in the screenshots, but the issues persist when shaders are disabled. A potential clash with something like Rubidium or Oculus, maybe?)
Interaction Screen Modules' labels do not show at all, nor does the button text
Adding any text at all to the "label" field reduces the size of the button (shown above) but doesn't display the text.
Variable Screen Modules do not display anything when inserted into a screen (while linked to a processor with a defined variable).
The Text Module is functional, but the Variable Module isn't.
Versions:
Possibly incompatible mods and versions: Rubidium, Oculus, Radon
Relevant logs, if any: