![]() tup_image_filter(image_filter_settings)įile "/home/dez/Blender/blender-2.80/2.80/scripts/addons/rprblender/engine/engine.py", line 203, in setup_image_filterįile "/home/dez/Blender/blender-2.80/2.80/scripts/addons/rprblender/engine/engine.py", line 269, in _enable_image_filter ![]() The blender closes with an error if you enable denoise.įile "/home/dez/Blender/blender-2.80/2.80/scripts/addons/rprblender/_init_.py", line 65, in updateįile "/home/dez/Blender/blender-2.80/2.80/scripts/addons/rprblender/engine/render_engine.py", line 416, in sync Tonight when I get home from work I'm going to poke around with the python portion of my installation, to see if I can get it working but I think that adding the argument for depsgraph to these functions and adding the called functions to take that depsgraph object and use it instead of the context object will get it working again. I've traced it down to that change, linked above Blender added the view_update and view_draw methods to take a depsgraph object in addition to a context object. ValueError: expected RenderEngine, RPREngine class "view_update" function to have 3 args, found 2 With the stock Prorender when trying to use a very recent Blender 2.8 build and enabling the addon I'm getting this traceback:įile "/Applications/blender.app/Contents/Resources/2.80/scripts/modules/addon_utils.py", line 384, in enable mod.register()įile "/Users//Library/Application Support/Blender/2.80/scripts/addons/rprblender/_init_.py", line 111, in register() _class(RPREngine) This change has been made to the Blender API, breaking Prorender (and potentially other renderers): ![]() Hi, I've found an issue with the build of AMD Prorender with the current Blender 2.8 beta builds after.
0 Comments
Leave a Reply. |