That is a mistake.
I mean NOT the Render-Button, I mean use the Render-View-Button on an empty PoserPro-Window.

That was it!
Sincere thanks **bagginsbill

**

In PoserPro I become this Message when I Run RealSkinshader on a V3-Figure:

Traceback (most recent call last):
  File "F:ProgrammeSmith MicroPoser ProRuntimePythonposerscriptsRealSkinShader_all_Figure.py", line 906, in ?
    SkinShader = SkinShaderDlg(tk)
  File "F:ProgrammeSmith MicroPoser ProRuntimePythonposerscriptsRealSkinShader_all_Figure.py", line 688, in init
    Label(self.StatusFrame, text='Selected Figure : ').grid(row=0, col=0, sticky="e")
  File "F:ProgrammeSmith MicroPoser ProRuntimePythonliblib-tkTkinter.py", line 1790, in grid_configure
    self.tk.call(
_tkinter.TclError: ambiguous option "-col": must be -column, -columnspan, -in, -ipadx, -ipady, -padx, -pady, -row, -rowspan, or -sticky

In Poser 7 is work without any problem with the same figure.

In PoserPro is the same problem - the same error-messages.
All my Realism-Kit-Scripts will not work in PoserPro.

PNG Features

PNG has the capability for both binary transparency (like GIF) and variable transparency, more commonly referred to as alpha transparency or translucency. Stored as RGBA (Red, Green, Blue, Alpha), each pixel is assigned one extra byte of data (or palette entry for 8-bit images) that defines its transparency level from 0 (fully transparent) to 255 (fully opaque). What does all this mean? For one thing, anti-aliased images will look good on any background. Imagine, no more ugly image halos or fringing! You can even apply background-independent effects such as drop-shadows and glows.

When you save in Poser 6/7/Pro your render-result as PNG-File you have automatic a Alpha-channel.
In PS 6-CS3 your PNG-File ist 100% with a transparent background.

You have two options in the Queuemanager-menue: QUEUE
PROCESS JOBS LOCALE or
SEND JOBS TO NETWORK

When you have not select PROCESS JOBS LOCAL the program will WAIT for a answer from a Remote Queuemanager.

In the "Attribute-Manager" from C4D you found a Button "Create Material".

But the Plugin has a great Bug.
You can't use DAZ-Figures - alle DAZ-Figure become a blind "Eye".
The Plugin is a Joke.

You must have PoserPro with the QueueManager from PoserPro.
On the Destination-Machine you must NOT have a running Poser only running the QueueManager. The Remote QueueManager starts the FFRender.exe for each Job.

Its work on my Network great .

The problem is, you can't start a Batchrendering. When I send more as one Job to the Remote QueueManager the second job and all next jobs will run parallel not serial.

Sorry for my poor english.

I must contradict ADP with the C4D-Import.
At me Poserfusion with C4D operates perfectly.
It depends naturally on which one would like to achieve thereby.
I want to use only with C4D the substantially better light tools and naturally the excellent Render engine.

For these purposes the interface is completely sufficient.