Quote - And for folks who don't own renderman there's the option of aqsis

RenderMan is a generic term for any renderer, including Aqsis, that conforms to RiSpec, the Pixar RenderMan Interface Specification. So, as well as Pixar's Photorealistic RenderMan, there is also :

• 3Delight
• Air
• Angel
• Aqsis
• BMRT
• Entropy
• Lucille
• Pixie
• RenderDotC
• BMRT and Entropy are discontinued. BMRT's author, Larry Gritz, now works at NVidia and develops Gelato. He, Matt Pharr and colleagues at Exluna also developed Entropy. Matt Pharr since then developed PBRT. LuxRender is a development of PBRT. These are not RiSpec renderers.
• Gelato
• PBRT
• LuxRender
• Hence the list in my previous post, of several different programs for exporting scenes from Blender, to RenderMan. The Forum's news group is for announcements, discussion, questions and answers on all of these methods, the blog is for more detailed information from the developers of them.

There are a number of links in the blog's sidebar to various tools and resources for Blender, RenderMan and generic 3d. 

Quote - are there pictures of this exporter around?

There are several different tools for exporting from Blender to RenderMan and there will be screenshots posted by the respective developers that are members of the blog.

The Blender to RenderMan export tools at this time are :

• Blenderman original
• Blenderman patches
• Neqsus/BToR
• Blender Pixie
• Blender Lucille
• RIBKit Ribber Sler
• SVAT
• RIBMosaic
• Blender Gelato
• Blender PBRT
• LuxBlend

A good page on how Neqsus/BToR is used with Blender and Aqsis can be seen here :

http://wiki.aqsis.org/guide/blender_pipeline

Quote - Good luck with the new one.

Thank you.

We chose a distributed HTML rendering approach this time :)

dvdcdr

Quote - And I watched the tutorial, I did everything, I just plain don't understand Blender.

If you haven't done this already, read the Blender wiki. It has the manual, tutorials and examples. Blender is difficult at first because it's complex.

mediawiki.blender.org/index.php/Main_Page

I'm not completely used to it myself and I've been using it since before version 1 and still have an ancient copy of it on one of my PPC's as well as the current version on my Thinkpad.

Give youself time to learn it before trying to achieve anything, like practising a musical instrument or martial art. Take a couple of hours a day to do a set exercise until you know it, then move on to the next exercise, and so on until your are comfortable with the necessary functions for what you want to achieve.

Tenzin

This is quoted from Cambo/ideasman42, the author of Blender's BVH handling,  :

"Hi, Blender 2.41 is able to import, edit bvhs and export them, but only as a hierarchy of empties.

I wasnt happy with only supporting empties so I removed the scripts for 2.42 and they also needed re-writing.

Recently I rewrote the BVH importer.
which should work with 2.42.

projects.blender.org/viewcvs/viewcvs.cgi/blender/release/scripts/bvh_import.py

But the exporter has not been written so far.
expect to get to it in the coming months.

• Cam"

This was in August, he and others are working on restoring the export functionality.

Tenzin

Jestmart, sorry, I mistyped your name as Jetmark.

Tenzin

As Jetmark says, the Close button will close Blender. Use the Continue button.

You might also to modify exported Obj files as is advised, but I've only opened Blender exported Obj in Ayam3d to apply RMan shaders and had no need to.

Some old Blender scripts don't have the BPy header section that's used by modern Blender to automatically register them in the scripts menu.

I do it the old way, which is :

Open the Bpymenus file in the .blender folder above the scripts folder in a text editor,
and the .py files you want to add to the scripts menu in another tab in the text editor,

Then you need to find in the Bpymenus file the section titled Import  and add a new line containing the data it should have been given by the script's registration header :

Import  {

'OBJ...' 232 objio_modif232.py 0 'Import Wavefront File Format (*.obj)'
}

Then save the Bpymenus file, and restart Blender.

This must be the exact same information as in the scripts header if it has one. The current Blender API syntax for that header is :

#!BPY
#"""Registration info for Blender menus:
#Name: 'OBJ...'
#Blender: 232
#Group: 'Import
#Tip: 'Import Wavefront File Format (*.obj)'
#"""

Note the Bpymenu entry is the data from the different fields from #Name: and #Blender:, with the name of the script added inline then a 0, then finally the #Tip: section.

Some older scripts instead have only the # before !BPY and are not recognised, other scripts have no registration header at all.

Since I prefer all scripts to be in my menu, I add this data for the ones that have to be started from Blender's text editor with Alt+P or File Menu > Run script, or are run from opening .blend files, by saving the text of the script from Blender's text editor as a .py in my .blender/scripts folder and manually adding them to Bpymenus in the same way above.

Also because since the auto registration function has been added to Blender, I have never known it to work in SuSE so I will continue doing things the old way :)

Tenzin

Quote - Is this it?

Yes, that's the one.

These might also be of use :-

Cr2bone import, PoserIO, and Poselib,

which is discussed here A pose-handling script.

If this is stating things you already know or were discussed earlier in this forum, my apologies :)

Tenzin.