Smith Micro Software, Inc. and the Poser team are pleased to announce that the Poser Pro Service Release 1 (SR1) is now available for both Macintosh and Windows. SR1 will update Poser Pro Full and Poser Pro Base to the latest versions. SR1 offers several enhancements and addresses known issues present in the following areas:

• General performance and stability updates and improvements
• FireFly and Preview Rendering
• PoserPython updates and improvements
• Material Room, Face Room, Hair Room, Cloth Room and Setup Room updates and improvements
• Improved & more compatible COLLADA export
• Improved & more robust PoserFusion hosting plugins
• Parameter/Properties, Talk Designer and Animation palettes
• Queue Manager improvements

In order to download Poser Pro SR1 or receive technical support for the product, you must have registered your Poser Pro application serial number. If you have not yet done so, please register now.

With your registered your Poser Pro serial number, you can access and download SR1 for Windows or Macintosh.

In closing – we are making significant progress on the Lightwave PoserFusion hosting plugin. This plugin will be made available free of charge to registered Poser Pro Full version users as soon as development is complete.

7/24/08

This soon after the release? Wow! GOOD JOB!

Is there a more detailed list of changes in the "readme" files?

Thanks!

LMK

Sounds good! Serial was accepted. Download now

Mazak

ENHANCEMENTS AND BUG FIXES IN Service Release 1

General

-Now keeping focus on Graph palette while clicking & dragging beyond palette boundaries.

-Poser Pro Reference manual PDF now accessible via Help Menu.

-Making QuickTime movie with 2D Motion blur now works properly (Mac OS X only).

-Enabled 2D Motion Blur for Image Sequence rendered in Poser (Mac OS X only).

-Memory dots and custom UI preferences now stored in language-specific sub-directory to facilitate concurrent installation of multiple Poser versions.

-Improved reliability of memory dots (Mac OS X only).

-Fixed case where problems with shadow camera parenting would prevent depth map shadows from getting rendered.

-Fixed case where polygon group got accidentally discarded if there were > 32 groups in an OBJ file while multiple group names were specified in the same line.

-Cmd-S shortcut for saving scene now more reliable.

-Improvements to texture map location for preview and rendering.

-Improved user interface performance.

FireFly Render Engine

-Fixed case where custom gamma values weren't stored properly.

-Improved reliability of rendering in a separate process when 3D Motion Blur is enabled.

-Improved reliability of FireFly render engine when rendering complex scenes.

-Fixed case where HDR images were discarded from render cache early (Windows only).

-Fixed case where certain shader would cause render to fail.

-Fixed case where small-scale features applied to bump or displacement channels would produce rendering artifacts.

-Improved stability of 64-bit render engine.

-Improved stability of rendering in background.

-Enabled replacement of texture with different texture of the same name. Please note that simultaneously referencing more than one texture of the same name with different content remains unsupported.

-Fixed case where running out of memory during raytracing database setup would cause instability.

-Fixed case where switching off texture filtering would cause artifact to appear at seams of high-res tiled textures.

-Fixed case where depth map shadows weren't cast when rendering in a separate process.

Queue Manager

-Now storing Queue preferences upon exit.

-Improved stability upon canceling job.

-Improved stability upon deleting job.

-Fixed case where adding more than ten jobs and dragging the Document column title would cause instability.

-Improved Network Render Queue stability.

-Enabled 64-bit file parsing (Mac OS X only).

Preview Render Engine

-Fixed case where line segment geometry could cause instability in OpenGL preview.

-Improved line width (Intel OpenGL only).

-Improved transparency map resolution in Preview mode.

Library

-Fixed a problem with popup menu awareness of newly added content collections.

-Fixed Content Collection display issue.

-Enabled creation of PNG thumbnails from resource fork (Mac OS X only).

File I/O

-COLLADA: Improved head position when exporting rigged figure with tilted head bone.

-COLLADA: Fixed case where re-importing scene exported from Poser would cause instability.

-COLLADA: Improved bending for figures exported with rigging.

Talk Designer

-Improved stability when applying to conforming figures without head morph targets.

Parameter/Properties Palette

-Now preventing instability when recursive value operations on an object's parameters are present.

Hierarchy Editor

-Enabled creation of figures from Hierarchy Editor.

Material Room

-User_Defined node now handles its parameters properly.

Face Room

-Fixed case where repeatedly undoing changes would cause Face Shaping parameters to become inaccessible.

Hair Room

-Improved quality of dynamic hair simulation results for Bend Resistance values >0.

Cloth Room

-Corrected text field locations (Mac OS X only).

Setup Room

-Fixed case where adding the skeleton of a figure with dynamic hair from the library would cause instability.

PoserPython

-Now using the standard content search method for finding referenced Python files, depending on the user's specified search policy preference.

-Now accepting any type of value to specify scale factor upon import.

-Improved stability by preventing reinitialization while script-based dialog is showing.

-Now accepting any type of value <= 0 to disable scaling upon import. Omitting kImOptCodePERCENTFIGSIZE will result in import at the last size specified.

-Added PoserPython script to facilitate setup of custom gamma values.

-Fixed case where Collect Scene Inventory script would omit certain referenced files.

-Enabled script-based cloth dynamics calculation for scene with multiple simulators.

-Added Scene.RenderToQueue().

-Added Poser.Quit() method to enable script to terminate the application.

-Added MovieMaker.SetMovieRenderer() and MovieMaker.MovieRenderer().

-Added Scene.SetRenderDimAutoscale().

-Added Scene.Resolution() and Scene.SetResolution() methods.

PoserFusion

-Improved reliability of missing file search in hosting plugins.

-3ds Max: Fixed case were failed file search would cause instabilities when manipulating Poser object.

-3ds Max: Improved stability and fixed case where Poser figure would disappear after a series of manipulations.

-Maya:  Now prompts user to find missing files.

-Maya: Improved stability when hosting scenes with missing files.

-Maya: Fixed resolution of colliding shader names (e.g. 'skin' material on two different figures in a scene).

-Maya: Enabled installation to updated Maya version.

-CINEMA 4D: Enabled Frame remapping.

CINEMA 4D: Installer now correctly installs libfreeimage.dylib into the CINEMA 4D app package (Mac OS X only).

KNOWN ISSUES

• Poser Pro generally runs fine under Windows Vista. There are a few issues that might require workarounds. Please refer to our Windows Vista knowledge base article for details.

• We strongly recommend saving hair groups to the Hair library with their underlying prop. This is because hair is grown from vertices and must be associated with vertices on its underlying object in order to function correctly.

• To save hair to the Library palette, select a hair group (or its underlying prop) then click the ADD TO LIBRARY button. You will be prompted to select your desired hair subset(s). Clicking the SELECT SUBSET button opens a hierarchical display allowing you to select the hair groups that you want to save. Be sure to save the parent object!

• When saving a subset of props to the library only the currently selected object will retain its morph targets. To save morph targets on all members of the subset choose Edit->General Preferences... and uncheck "Use external binary morph targets" temporarily. Once the subset has been saved to the library, "Use external binary morph targets" may be reactivated.

• Adding a prop to the library: When adding a prop with morph targets that is parented to a figure, the prop might not retain its morph targets if Poser is set to write external binary morph targets. In case you encounter this problem, please choose Edit->General Preferences... and uncheck 'Use external binary morph targets' temporarily. Once you're done adding figure-parented props with morph targets to the library, you may reactivate 'Use external binary morph targets'.

• Texture search: In previous Poser versions, textures were occasionally specified by their file name only. Since in that case the search mechanism has to search with just the name, it will find the first texture with a matching name. Please keep your texture names unique to avoid loading the wrong texture when opening legacy scene files. Poser Pro always attempts to store an application relative path or an absolute path (whichever is appropriate) in the scene file. Also, the Poser Pro Texture Manager always displays the full path of all loaded or previously loaded textures. This will aid in determining the location of any texture file.

• Rendering in separate process: In some cases, Area Render might fail when rendering in a separate process. If you encounter this problem, please retry, render a full frame, or consider rendering internally.

• Color on the alternate diffuse channel of a root node will not preview in the document window.

• If you have difficulties using the Face room's photo matching feature due to the rotation of the head in your photos not matching the selection outlines, please consider rotating your photographs in an image editing application.

• A note on using the DivX codec when making movies: the DivX codec can only be used with standard aspect ratio (4:3).

• Some 3D file formats have restrictions in output size. In 3D Studio (.3ds), an object can consist of no more than 65,000 polygons. In Lightwave 5 (.lwo), the maximum size of a scene is 65,000 polygons. Please use the LWO2 export option if you want to export LWO files of objects larger that 65,000 polygons.

• Using the Auto Install feature in the Content room might leave temporary files behind. Please delete the files in the temp folder if you want to conserve disk space (Windows only).

• There is an incompatiblity with Unsanity's Window Shade X potentially causing an undesired Window Shade effect on Poser palettes. Please add Poser to Window Shade X' list of excluded applications if you encounter this problem (Mac OS X only).

• Library thumbnails in PNG format that contain both data and resource fork can cause instabilities. Deleting the resource fork resolves this issue (Mac OS X only).

Mazak

PoserFusion: **Still no 64bit support!
**

Has the Poser to Vue issue been fixed?

There seems to be some issues with updating the Queue Manager on render nodes.  The original Queue Manager had an internal (windows) version number like 7.xx.xx.xx(this wasn't/isn't visible in the about box but is on the properties in the file explorer) but the new QueueManager claims to be 1.0.1.220

The problem is the installer they have doesn't overwrite that old queuemanager with the higher (but wrong) internal version number.  As a result updating render nodes doesn't work. 

Well I should say didn't work for me.  Maybe I'm the only one seeing this, can't really tell.  You can fix this a bunch of ways (uninstall, install to new dir, copy the right files) etc.  If you don't have a matched set of QueueManager's the render nodes won't be available for rendering.
 

Quote - Has the Poser to Vue issue been fixed?

What issue? I work with PP and Vue Infinite since release of PP.

Mazak

 Mazak you obviously do not have external runtimes.
Love esther

Mazak

 you probably haven't tried to import a scene with content and figures from the external runtimes as yet.
Vue doesn't like relative paths and preferred absolute paths that poser used to save in the pz3s before poser pro came about.
Love esther
hehe Mazak  - not by a looooooong way do you have as many as me.

Figure loads
Morph loads
Texture loads
Dynamic cloth loads (Single frame #30)
Hair Prop loads

Mazak

btw the Hair prop and the dynamic cloth come from my Poser5 runtime. V4 and all textures is installed on my main. The textures I always store in my main runtime since Poser5 start with multiple runtimes.

Mazak

Not many runtimes there and I'm guessing they are on the same drive as your P7Pro? I was having issue with Vue not finding everything. I have all my runtimes except main P7/P7pro on a different drive. It all works in Vue from My P7 but I never updated it with SR3. Vue has a bad time with P7Pro.

So far my tests with SR1 have worked. Will try the Pz3's that didn't tomorrow when I have time. I'll try them again first I'll reload them into P7Pro and resave them out and see what works and what the differences are.

I am sorry to hear all your problems. The only thing I can tell is how I handle my files.

With the start of  Poser5 I discovered some problems with missing textures. So I decided to migrate always my textures to my main runtime. Also I move the python scripts to the main. And yes all Poser runtimes are on my drive D: (my luck). The geometry files and cr2 files I store in same runtime. For example the hair and the dynamic cloth is in Poser5 runtime. Vicky4 is in PoserPro runtime. I keep always complete sets. I never used the localized German version of Poser I always use English version. And finally I duplicate the PoserPro.exe and renamed it to Poser.exe. (Even some python scripts work only with a pose.exe in main runtime (and DAZ installer search for P.exe some time)

I don’t think the creators of poser had in mind to create hundreds of runtimes. With Poser 7 now you can create collections. I think that came much closer to what esther and you will need. (I hope my English is correct and you are not :scared: )

Mazak

 Hi Mazak, I looked into collections but it is too much like hard work as things have to be added one at a time.  Runtimes I can just add to the XML library file by adding from within poser.
Love esther

It seems textures are loading quicker on initial render. Can someone else verify this?

 that's probably because the update reset your poser preferences to no longer do a deep search hehehehe.
Love esther

 damn, there's a rendering problem in poser pro that still exists.
Some transmapped hair, and I'm told other things, comes out all whispy in firefly.  I tried the exact same pz3 in poser 7 and it rendered normally, but in poser pro it is bad.  And it's still not right. I was so hoping the SR1 would fix the problem.
Love esther

 and the prom pics for the hair show nice bangs (fringe) at the front of the forehead too.

I have problems with PoserPro Pz3s and Vue6i too - it doesn't import one thing, the scene is always empty. I have to resave my PoserPro Pz3s in P7 (haven't updated with SR3) to get them into Vue. And I have lots of external runtimes. I only keep Python scripts and  the default Poser stuff that comes with the installation in my main Poser runtimes - everything else is savely stored in external runtimes.
 
I noticed the render problem with some hair as well. I wanted to use Hebe hair in my last image and the hair looked great in preview and horrible once rendered. It was all transparent and see through allthough all textures were applied correctly. Doesn't look like that at all in P7.

Attached Link: http://www.renderosity.com/mod/forumpro/showthread.php?message_id=3237861&ebot_calc_page#message_3237861

I am told smith micro knows about this problem and are working on a fix, which is why i was sooo disappointed just now when I tried Sr1.
Don't upate your poser 7 to SR3 or you won't be able to import into vue.
If you create a scene in poser pro and want it to import into vue you will need to run this python script:-

see this thread to your import into vue problem and a solution

Love esther

 Incidentally if you render with the poser 4 renderer the problem is gone.

Hebe hair render fine on my PoserPro. Please think about to restructure your runtimes.

Mazak

 that would really be a totally last resort.  i have more content than you can possibly imagine, and i can find it all really easiy and install it easily with my current runtime.
The problem with hair is not all hair, and I haven't got that hair, but the problem, as you can clearly see from my renders is present with olessas hair.
Do you want to try that one Mazak.  I highly recommend it.  it seems to be a really nice hair.
Love esther

 Mazak, what settings do you render at usually?  Maybe I am doing something differently.  In the preview mode the hair looks fine.
Love esther

Give me a moment I download Olessa Hair. I come back with render results.

Mazak

 I hope you like the hair.

 the problem is improved when I turn off gamma in the render settings.  I seem to recall that before the SR1 that turning this off didn't help.
The problem doesn't appear totally resolved and in any case I like my gamma.
Love esther

estherau, thanks for the link to the other thread. I've downloaded the Python scripts and test them. And if all things fail I'll resave in P7 until E-on had updated Vue. From the email you've got from SM in May I saw that they have provided E-on with a new SDK to fix this issues. Hopefully E-on will create an updater now.

 taps foot impatiently.  I check their download section everyday but nothing new at eon.

 mazak, I will be surprised if you don't get the same result.

Mazak

Mazak

 Esther, you can try setting the gamma of just the transparency maps of the hair to 1.0 and leave the rest as they are. Then you should get gamma correct rendering with the transparencies as they look in P7.

I agree, not all new features of PP are useful in any circumstances. The transmap of Olessa is very fine and thin, a killer for any render application. If you GC that transmap in Photoshop nothing survive, it is like you kill the texture. Give PoserPro and you some time and learn the new features.

Mazak

Quote -  gamma on

Based on that, it seems obvious what the problem is.

Go into the material room, and look at your trans map.  Odds are if you check what the gamma is, it will say "Use render settings".  Change it to "custom setting" and set to 1.

Any texture file that's used for anything other than colour (bump, displacement, mask, transparency) should all have their gamma set to 1, no exceptions, all the time.

Quote - > Quote -  gamma on

Based on that, it seems obvious what the problem is.

Go into the material room, and look at your trans map.  Odds are if you check what the gamma is, it will say "Use render settings".  Change it to "custom setting" and set to 1.

Any texture file that's used for anything other than colour (bump, displacement, mask, transparency) should all have their gamma set to 1, no exceptions, all the time.

Hmm sounds like we need one of the python guru's to wip up a script to do just what you are commenting about.

Might I make a suggestion, that you determine the name of the texture for the hair and or trans map and then search your hard drive to see if you have a hair from another poser artist anywhere on your drive with the same file name? For safety sake I have all my textures and geometries located in my PoserPro runtime. characters, etc, are all out on separate runtimes by character name, buildings, plants, you get the idea. I wonder if at render time it is loading the wrong texture or trans map. Long shot, but might be worth looking at.

The new version didn't fix the problem with non-rendering content.

If I load content from an external runtime and click the render button or choose render in background its fine.

If I render on the queue then all content from the external runtimes is completely ignored leaving a very naked and embarrassed V4.

Smith Micro said it would be fixed in SR1 but it wasn't :-(

Thanks for the heads up & for the active support -- it's good to hear.

The progress with the Lightwave plug-in is especially good to hear.

7/25/08

I notice that with SR1, when I export an image, it now retains the quality setting last used. Before SR1, the setting always defaulted to 75%.

LMK

I don't have any rendering problems with P7Pro, I only have the problems between pro and Vue. No need for me to rearange my runtimes, they are very organized. Most of my pythons work or I have hacked them to work fine in Pro.

The P7 sr3 and P7Pro issue is known and documented by both e-on and microsmith. It will in time be fixed. I had hoped it would be this sr1 but maybe it need to be fixed in Vue instead.

In the meantime, I just use my P7 that does not have sr3 to build scenes for my Vue6I. because it is not the runtimes, it's how Pro and sr3 write the paths.

 "
Based on that, it seems obvious what the problem is.

Go into the material room, and look at your trans map.  Odds are if you check what the gamma is, it will say "Use render settings".  Change it to "custom setting" and set to 1.

Any texture file that's used for anything other than colour (bump, displacement, mask, transparency) should all have their gamma set to 1, no exceptions, all the time.""

thanks everyone - and i wrote to smith micro telling them - they eemed surprised
love esther

My figures palette isn't there now...lol
Great should have done a restore point
 

Ok, found them they were on my other monitor and it was off, joke is on me....lol

When I render Blackthorn Rose I get seams, so far she's the only one I've checked.