The getCurrentScene() command is from the old 210 API, which has been dropped as of Publisher 2.25. Use instead Blender.Scene.getCurrent(). Also, the ribexport.py script has been updated considerably, look for Green's BlenderMan script at elysiun (I have it if you can't download it anymore). Also, Green is currently working on hardcoding a rib exporter (maybe even a direct "Renderman" render button?) into Blender. Look for progress on that in the rendering fourm below.

ray_theray wrote:The getCurrentScene() command is from the old 210 API, which has been dropped as of Publisher 2.25. Use instead Blender.Scene.getCurrent(). Also, the ribexport.py script has been updated considerably, look for Green's BlenderMan script at elysiun (I have it if you can't download it anymore). Also, Green is currently working on hardcoding a rib exporter (maybe even a direct "Renderman" render button?) into Blender. Look for progress on that in the rendering fourm below.

elysiun does not have blenderman script anymore.

Where can I get the latest?

What about the new renderman button that Green is working on? Is that available?

ray_theray wrote:The getCurrentScene() command is from the old 210 API, which has been dropped as of Publisher 2.25. Use instead Blender.Scene.getCurrent(). Also, the ribexport.py script has been updated considerably, look for Green's BlenderMan script at elysiun (I have it if you can't download it anymore). Also, Green is currently working on hardcoding a rib exporter (maybe even a direct "Renderman" render button?) into Blender. Look for progress on that in the rendering fourm below.

elysiun does not have blenderman script anymore.

Where can I get the latest?

What about the new renderman button that Green is working on? Is that available?