Screen going black (but not crash) when interacting with any aspect of the mod

[ozitm]

Direwolf20 1.12 version 2.5.0

Tried version 2.7 of this mod, selecting any build mode, as well as attempting to change any part of the array or mirror settings makes screen go black, but game is still running.

Haven't changed any settings in the config, just downloaded DW20 pack and installed this mod.

[Requios]

I am not able to replicate it. I have installed the modpack and tried version 2.7 and 2.8, and everything seems to work as normal. What block were you trying to place?

[Cameron Osbourne]

I can confirm this happens outside of Direwolf20’s pack. Although I cannot provide exact modpack details at the time, I can say it’s not from the placing of the block, but specficially when highlighting anything in range with the cursor. The block placed had no effect (was tested with wood planks, logs, stone)

Everything is still functional behind the black, too. I’m not sure how it happens but its definitely some sort of conflict with rendering. No optifine was installed. Though seeing as how Direwolf20’s pack seems to work fine without any changes to it outside of adding this mod to it, perhaps it’s something else that ozitm added? Possibly some sort of performance mod, like VanillaFix or BetterFPS? In the mean time, when I get the chance I’ll test it out with some of those mods to see if it’s a specific conflict, as I really do like this one and would love to see it fixed for my personal pack as well.

Edit: Curiosity got the best of me, so I stuck it in a pack with just vanillafix and betterfps. No black screen, but I do have a problem where sometimes blocks don’t place, but leave the inventory until I mine that same type of block again

[Requios]

Temporary workaround: set useShaders to false in the config. You can do this ingame by clicking ESC > Mod Options > Effortless Building Config > visuals > useShaders = false. I will continue to investigate.

[Requios]

Tried to fix it today but only broke more stuff. Will try again next weekend.

[Requios]

I cannot replicate this exactly, but I did fix a shader issue, so this is probably fixed as well. Try version 2.11, if it still occurs recreate this issue. Otherwise its considered fixed.

[Bradley]

Updating to version 2.11 fixed this for me. I’m curious because you couldn't replicate this, do you have an Nvidia, Amd or Intel GPU. I had this problem on an Amd RX 480.

[Requios]

Nvidia GTX 970 (x2). I could try on my laptop which has an AMD but if its fixed its fixed.

[Bradley]

That's fine I was just curious, and seeing as you do have a non-amd GPU, it was probably just an amd issue.