Hmm.

I don't have any insight on the inner workings of Renderosity, here I'm just a regular member, but I can tell you about my experience on the topic.

When Bill released his console I was jazzed because he'd done a really nice job on it. I'd started one of my own back in April but never finished it. I had finished the rest of the console room and all that was just laying
around on the hard drive so I figured I'd pack it up and post it.

When I did, I titled it "TARDIS Console Room Prop". A short while later I got a very polite note from one of the Renderosity moderators explaining that the word "TARDIS" was a trademark of the BBC (which I didn't know) and that
using that title could open Renderosity up to potential legal action even though the post probably fell under the category of fan art. They suggested a couple of other acceptable titles. I picked one, the moderator edited the
title for me, approved it and that was the last I heard. They didn't ask me to change the thumbnail, only the title.

I understand their concern and I'm fine with it. I also thought they were very cool about the way they handled it. The model I posted was 100% original work eyeballed from the old episodes. If the BBC comes to me sometime down
the road and says they want me to take it down, I'll take it down. If they say they want me to add "tm" after the word TARDIS, I'll add "tm" after the word TARDIS. Call me stupid but as a free fan art item, I'm guessing that won't
happen. If I tried to sell it in the marketplace, that'd be a different story.

That said, I did notice that Bill and several others had used the "T" word in their titles but I didn't think much of it at the time. I've never had any issue with any online community (ever) over content I've posted but,
because of my involvement with the GPA project and some others, I'm used to being watched a little closer than most. Again, all fine with me because I understand
what it's like to be a site operator.

Point is, a bunch of people have done some really fine work. It'd be a shame to see it all taken offline because of a lack of communication. Seems better to ask the question rather than assume an answer.

Desaturating in post is easy and will get you a good result. The alternative to simple b/w materials is to copy your maps, desaturate those, then render in Poser. That'll let you retain your detail. Obviously you'll also want to convert all your lights to shades of grey as well (average the RGB values then set all three values to that number). IMHO, a good b/w image is more about lighting, shadows and contrast rather than just the simple lack of color. Don't forget to select an appropriate camera focal length for the style of image you're doing. The photography forums might be of some use to you on this one.

The Script Pak I wrote a while back has a script called Dial Focus that does just about that. It doesn't print but it does hide dials set to zero as well as a few other things. I was doing the same thing as you, for the same reason, it was tedious, I wrote the script, thought I'd share. http://www.castironflamingo.com/tutorial/GPAScriptPak1/index.html Stay well, Craig

Ah, but it was free. ")

There are various options to hide file extensions of known file types. Turn those off (show all file extensions) and you'll get less fuss. Check under Tools/Folder Options/View tab on any open folder. Alternately, I use WinSyntax over notepad or word pad, you can get it free from download.com. It's actually a PHP code editor but it works very well for Poser files and especially Python scripts where preserving the original format of whitespace matters.

Keeper.

You should see "Python Scripts" under Window on the main menu. If not, maybe check Help/About and make sure your pro pack installed ok.

Posted those scripts in me free stuff section if anybody is interested. Sorry for the delay, had lots of unrelated stuff to clear off first.

Yep. That'll work. I'll package it up with the others and post it over at GPA.

I've noticed that too. When you enumerate the options, you'd think that those are the only ones that have an impact on the export. Not always the case.

Grafting in the missing section is a way to go but I wondered if there wasn't another hidden ImEx option you can set to have it include that section. There has to be actually because the internal code would be setting it when Poser exports a pp2. It's not clear however, if that option setting is exposed to Python.

Trouble there is finding it. You could just fling constants at it and observe the behavior but the problem there is that if you give it an integer when it's expecting a float it tends to just die and not raise an error. Ask me how I know.

Either way, seems we might have something that'll work if all the channel info is available.

Here's a code fragment to chew on.

Basically you export anything. It doesn't matter what it is but calling the export method sets the callback that carries over (not that it should) when you call SaveLibraryProp. Just look at the .pp2 though. No channels section. Very annoying.

Later, C