So Smith Micro's ad campaign stated clearly that when you purchase Poser Pro you could install it on 2 machines so as to take advantage of network rendering.

But if you install it on two machines one of them says "somebody else is using this serial number" and shuts down.

What am I missing?

Yep, looks like I did.  so only the queue manager can be running on the other machine- but it doesn't seem to be starting automatically for me, is there a trick to it?

thanks!

Attached Link: http://poserpro.net/King_Tut/vids/img/RenderQueueSWF.swf

Mazak

LOL wow i just got around to watching that tutorial finally... its so basic that I'm not sure who he made the tutorial for.

My machine is a BEAST and render queue simply does not work.  it sits on WAITING forever- and the tutorial did not shed any light at all on how to use multiple machines to render.  It also failed to mention that you are NOT supposed to use the render queue at all if you only have one machine... which apparently is what Smith Micro says.

I'm not sure why it's such a mystery here, seems like it should just WORK, and it don't =/

I've also noticed Smith Micro support is utterly absent  (have yet to answer a question I submitted to a "technician" on their site 2 weeks ago).  Also there is not a single question or answer with the word "queue" in their knowledge base.  Are there any comprehensive tutorials for it yet? 

Maybe I'm just too early and we're all waiting for the instructions...  the manual sheds no light on the subject either.  I can read labels on buttons by myself, I need to get the queue working lol

 I've had answers back from their techsupport.
Love esther

well you are a lucky duck then =P   maybe they don't like me asking how to use the render queue since there are no guides anywhere.  or it could be known bugs they have no fix for yet. 

and  try looking up motionblur in the poser pro manual
love esther

motionblur?  what does that have to do with the render queue lol- actually i've never used motionblur i use photoshop for all of that

My thought exactly, Darkworld.  There is no obvious link between motionblur and rendering queues except maybe that motionblur is a render effect.  Sounds like another poor Poser manual.  Render queues SHOULD be under rendering - duh and doh.............

 Oh I was just mentioning motionblur  because it is one of the options in one of the menues at the top of the poser screen and absent from the manual. Just another example of how the manual is deficient.
Love esther
PS sorry for the confusion

gotcha... i agree and that might be part of why i've never tried it!  oh well, im sure i'll figure it out eventually.  it all looks so easy right?... select "send to queue" and then name the file.

that's TWO steps.  but it doesn't work for me.  it wants to "Talking to Poser" until the sun goes supernova.

  i have dual geforce 9800 GTXs, 8GB ram, and a hefty quad core chip so im pretty sure its not my system.  unless there is some prohibitive bug on Windows XP x64

Are both applications (Poser Pro and Queue Manager) allowed network connections in your firewall? If there's anything blocking communication Poser can't hand the job to the queue.

XP x64 is a great platform for the render queue (most of the queue processing happens in 64-bit under that OS). We run jobs under XP x64 here daily.

hmm well im running kaspersky net security so it always asks me when something is trying to get out.  but this happens even trying to do it locally

You should permanently allow network access for those two applications (please keep in mind that Queue Manager is independent from Poser). That applies whether you're using the queue locally only, or whether you add network nodes to mix. If it asks you every time to permit a connection, the connection might have timed out by the time you get around to allow it, and whatever was supposed to be communicated would not happen.

I think I see the problem.  Look at the order number on that project in the queue.  It's set to render as the second process for some reason (I'm assuming you may have canceled the first process), and it's waiting for the first one to finish.  However, since there is no previous order number in the queue, it's just gonna sit there and wait forever.

I must assume you already tried rebooting your machine to reset the queue, and starting over again.  I had the queue working, and it works pretty good.  What I did was open a PZ3, send it to the queue, then after it's in there, go and open another, do the same, etc. The first one you sent to queue should be order number 1 of course, and once you have a bunch in there, you can change the order numbers around for all the other processes, but never change the first one from being first, or it might screw everything up.