Eevee materials not working starting from 3.2.0 beta 967f96ee2e2e

[FyiurAmron]

Neither the preview (shows black box for everything apart from hair) not the actual rendering works for me anymore. It still works in 3.2.0 beta bf352df27a6f. Hard to say if it's related to core blender code, or Win7 compat. A wild guess, but maybe 3.2.1 fixed it somehow already?

[nalexandru]

I will upload 3.2.1 in a few hours.

I doubt it's related to the compat layer because there were no changes since 3.2.0 beta cbc024c3cac2 and it doesn't do anything for graphics.

Try running Blender with "blender_debug_gpu.cmd" instead of "blender.exe", go the the preview and exit. After Blender closes, it will open a folder with two files, "blender_debug_output.txt" and "blender_system_info.txt".
Please upload those 2 files.

[FyiurAmron]

@nalexandru here you go:

debug_logs.zip

honestly, I couldn't trace this back to anything sensible. The possible errors/problems in the dump are the same in both versions, and using factory startup doesn't affect this at all (still a black window for all material types different than hair). It happens even with the default "cube" scene and nothing else.

[nalexandru]

I've uploaded the 3.2.1 release.

Both logs are empty. I see that you're using an RX 580 with driver version 21.5.2. The latest version on AMD's website is 21.6.1 (https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-580), you can try updating it in case it's a driver issue.

I found some similar issues on Blender's bug tracker: https://developer.blender.org/T99264, https://developer.blender.org/T98284 and https://developer.blender.org/T98128. I will try to reproduce this on a RX 550 on both W7 and W10.

[FyiurAmron]

Yeah, they are, I guess there's basically nothing to log since I can verify it happens as soon as Blender is launched without doing virtually anything. Still, the bugs you found seem basically exactly like the one I have, so I guess it's 99% unrelated to Win7 compatibility itself. I've checked 3.2.1 (many thanks for shipping it BTW) - it still happens, although in fact it's an Eevee-only bug - Cycles & Workbench still work perfectly. I'll close it here and try reporting it on Blender's tracker, though I honestly suspect they'll close the report due to Win7 being unsupported, even if (which I suspect) the bug is reproducible on *n*x, MacOS and Win10 :D

BTW thanks for the info on the drivers - I've stopped checking some time ago after AMD said they're dropping support for Win7 drivers, and I'm quite surprised they shipped some as late as April/May 2022'. They didn't seem to fix this one (well, they did, a bit - now I have preview of all the "preview render types" apart from Sphere, previously preview worked only for Hair; the main renderer nor viewport preview still doesn't display anything), but it's good to have them updated anyway :}

[nalexandru]

I was unable to reproduce this issue on a RX550 on Win7 with 21.5.2 or 22.6.1.

[nalexandru]

@FyiurAmron there has been another rendering issue on an RX580, #19, which was fixed by this build: https://1drv.ms/u/s!AhpnXywMA4U1mUYW4jtP0GsxlPHF. Can you test if it fixes this as well ?

[FyiurAmron]

@nalexandru what can I say? KUDOS 🙇 🙇 🙇 👍 💯 - it seems that https://developer.blender.org/rBd1340e1bb250f6ec4b9781f4b9c5f01a9e4da9e9 was indeed the thing here, it works perfectly again now!

[FyiurAmron]

BTW @nalexandru - this is the official response from Blender team:

https://developer.blender.org/T99846

Sadly, I'd say this now is a Windows 7-related issue. Since no Win7 GPU drivers work in this setup without reverting the code patch in question, and the patch itself has little positive value for Win7 setups (due to GPU drivers getting less and less support) I was just wondering if you'd be so kind as to include reverting this commit into your fork permanently?

[nalexandru]

I'm not surprised by their response.
I will include it and when 3.2.2 releases it will be applied.

The reason i was unable to reproduce this on my RX550 is that the workaround was left enabled for it. It seems AMD's drivers are not identical on 7 and 10, the same driver version (tested 22.6.1) is missing a few Vulkan extensions on 7, so i assume they've fixed the driver bug mentioned in that commit only in the Win10 version.