Page MenuHome

Pov Ray 3.7 renderer does not parse with Pov Ray 3.7 and shows dark checkerboard
Open, Needs Information from UserPublic

Description

System Information
Operating system: Windows 10
Graphics card: Nvidia GeForce GTX 1050 Ti

Blender Version
Blender 2.79b

Short description of error
I am using the Pov Ray renderer and all its doing is showing me a dark checkerboard for a render. When it normally works it parses with Pov Ray but for this .blend it does not. It just goes straight to the render window wit ha dark checkerboard

How It looks now.

The window that comes up when it parses with Pov ray. (when it normally works)

Exact steps for others to reproduce the error
I'm sorry but I dont know the exact way to recreate it but from what I remember it started when I accidentally pressed one of the buttons near ctrl-z or A when trying to select all or undo something in edit mode.

Here is a copy of the file with all the ugly textures I made included. It also carried over the bug I am talking about.

Thank You.

Details

Type
Bug

Event Timeline

This comment was removed by Tyler (Tylerm8101).
Sybren A. Stüvel (sybren) triaged this task as Needs Information from User priority.

Please do some more investigation. Without clear steps on how to reproduce this issue, it's hard for us to fix it.
Also try with the latest version of Blender (2.80) to see whether the issue has been fixed already.

Tyler (Tylerm8101) added a comment.EditedThu, Aug 1, 4:23 PM

Hello Sybren.

I was messing with the bugged .blend to just find ANY way to fix this, and I saw the info tab and clicked on it and had no idea what it does. As it turns out it might be the answer to my problem.

It brought up this text (when I attempted to render the scene):

(This is what it says if the picture is too small.)

Traceback (most recent call last):

File "C:\Program Files\Blender Foundation\Blender\2.79\scripts\addons\render_povray\render.py", line 4147, in render
  self._export(scene, povPath, renderImagePath)
File "C:\Program Files\Blender Foundation\Blender\2.79\scripts\addons\render_povray\render.py", line 3837, in _export
  write_pov(self._temp_file_in, scene, info_callback)
File "C:\Program Files\Blender Foundation\Blender\2.79\scripts\addons\render_povray\render.py", line 3648, in write_pov
  shading.writeMaterial(using_uberpov, DEF_MAT_NAME, scene, tabWrite, safety, comments, uniqueName, materialNames, material)
File "C:\Program Files\Blender Foundation\Blender\2.79\scripts\addons\render_povray\shading.py", line 251, in writeMaterial
  if(t and t.use and validPath and

UnboundLocalError: local variable 'validPath' referenced before assignment

location: <unknown location>:-1

That makes things a lot clearer, thanks. Can you now also test with the latest build of Blender (https://builder.blender.org/download/) to see if this is still an issue? You're still reporting with an old version of Blender, which we don't support any more.

The povray add-on included in 2.80 isn't working for me when trying to render the BMW27 demo with povray -- I'm also dropped to a checkerboard background:

***INITIALIZING***
Official POV-Ray 3.7 feature set chosen in preferences
The name of the binary suggests you are probably rendering with standard POV engine
Traceback (most recent call last):
  File "/usr/x86_64-pc-linux-gnu/share/blender/2.80/scripts/addons/render_povray/render.py", line 4160, in render
    self._export(depsgraph, povPath, renderImagePath)
  File "/usr/x86_64-pc-linux-gnu/share/blender/2.80/scripts/addons/render_povray/render.py", line 3841, in _export
    write_pov(self._temp_file_in, scene, info_callback)
  File "/usr/x86_64-pc-linux-gnu/share/blender/2.80/scripts/addons/render_povray/render.py", line 3588, in write_pov
    exportCamera()
  File "/usr/x86_64-pc-linux-gnu/share/blender/2.80/scripts/addons/render_povray/render.py", line 550, in exportCamera
    tabWrite("aperture %.3g\n" % 1/camera.data.dof.aperture_fstop*1000)
TypeError: unsupported operand type(s) for /: 'str' and 'float'

The fix is tabWrite("aperture %.3g\n" % (1/camera.data.dof.aperture_fstop*1000)) but after editing that, another issue reveals itself:

***INITIALIZING***
Official POV-Ray 3.7 feature set chosen in preferences
The name of the binary suggests you are probably rendering with standard POV engine
Traceback (most recent call last):
  File "/usr/x86_64-pc-linux-gnu/share/blender/2.80/scripts/addons/render_povray/render.py", line 4160, in render
    self._export(depsgraph, povPath, renderImagePath)
  File "/usr/x86_64-pc-linux-gnu/share/blender/2.80/scripts/addons/render_povray/render.py", line 3841, in _export
    write_pov(self._temp_file_in, scene, info_callback)
  File "/usr/x86_64-pc-linux-gnu/share/blender/2.80/scripts/addons/render_povray/render.py", line 3588, in write_pov
    exportCamera()
  File "/usr/x86_64-pc-linux-gnu/share/blender/2.80/scripts/addons/render_povray/render.py", line 555, in exportCamera
    if camera.data.dof_object:
AttributeError: 'Camera' object has no attribute 'dof_object'

Here the fix is apparently if camera.data.dof.focus_object and after that is fixed, yet another error shows up.

I talked to the guys in #blender-coders and @Pedro A. (povmaniaco) suggested that the povray add-on in the 2.80 tarball is perhaps somewhat outdated and needs an update?

EDIT: Tagging @Maurice Raybaud (mauriceraybaud) as he's apparently the povray plugin maintainer.

EDIT2: Just tried cloning the blender-addons.git tree and symlinking the render_povray folder from said tree into my blender-2.80 install. I get the exact same bugs as with the official 2.80-tarball, suggesting that the official povray add-on in git is in dire need of a push with updates from the add-on author.

Just a quick note that @Maurice Raybaud (mauriceraybaud) (the povray plugin maintainer) has gotten in touch with me and stated that, while the povray plugin doesn't currently work with 2.80, he and his team are working on getting it functional again.