Does not render anything on 3.5 / 3.4 about eevr HOT 15 CLOSED

I have fixed the back image problem on macOS in my b35 branch.
For installation instructions, see
nagadomi@4781816#commitcomment-111058232

I tested that it works with both OpenGL and Metal backends on AWS EC2 mac2.metal instance.
But I have not checked with VR headset.

EDIT:
I confirmed that it is working fine on VR headset (SBS).

from eevr.

For me EeVR doesn't even show up in the latest Blender (3.5.0).
It used to require going to the "testing" category in the addons manager, but now there is no longer such a tab..

from eevr.

@ecations I have posted a fix for that issue in #49, works with only one line change.
@Waldgeister With the above changes, it worked on Blender 3.5 + Linux, so I think the problem is due to macOS.
might be related to https://blender.stackexchange.com/questions/286919/addon-stopped-working-on-mac-metal-in-v3-5-due-to-shader-compile-error-console

from eevr.

@nagadomi Yes I found that one too and checked the source of renderer.py. But it does not use any of the listed glEnable, glDisable or ShaderCreateInfo commands.

from eevr.

Maybe the shader code should be compiled using new gpu.shader.create_from_info() instead of gpu.types.GPUShader().

I don't have a mac machine so I am not sure that is the cause.

from eevr.

I would love to fix it. But I'm only used to develop in Swift. So the stackexchange example is quite cryptic to me. Testing shouldn't be a problem.

from eevr.

I've tried updating renderer.py to use the new gpu module. Not tested in detail. (many of the texture parameters has been lost, so there may be differences from previous versions)
nagadomi@4781816

Note that this commit does not include the changes in #49.

from eevr.

Two things about Mac (M1 in use here):

• Whatever I download here, it still needs a manual change to run with the latest Blender version, like stated above. Unzip eeVR, make the change (replace "testing" with "community") and zip it again. So it´ll show up.
• The render error @Waldgeister reported can be solved by going to the preferences and set the GPU BackEnd to "OpenGL". By default it´s "Metal", but Metal doesn´t work for me.

Anyway, so far I only get complete black images, but at least in 4096x4096 ;) Still exploring.

from eevr.

@Sasatari Just tested the openGL workaround: The rendered output is indeed completely black. But even more, all the objects, camera, etc turn also black in the 3D viewport. I had to change the view port shading several times and back again to get regular coloring.

from eevr.

@Sasatari Just tested the openGL workaround: The rendered output is indeed completely black. But even more, all the objects, camera, etc turn also black in the 3D viewport. I had to change the view port shading several times and back again to get regular coloring.

Yes, same here, but I´m not deep enough into Blender (My main software still is Lightwave 3D) to figure out, why this happens. And actually have a severe lack of time. Will try to find some Blender on Mac users who can help with that.

from eevr.

Just did a View Render (F11) and there I got the expected result. So it seems to work in general, must be a simple setting somewhere I guess.

from eevr.

I guess this is only one of the segments you are seeing in the viewer. Did you activate the "keep temporary work files" in options?

This is how it looks for me. Both in Metal and OpenGL with the new b35 version of @nagadomi

from eevr.

Didn´t check temp, now I did and this is what I get:

Edit: Forget what I wrote, you mean Blender 3.5, don´t you? Just tried that and then updated to 3.5.1 with absolutely same results.

from eevr.

Thank you so much! This works fine on my 2020 13 inch M1 MBP with Blender 3.5

from eevr.