At this point, please do not apply the hotfix to new installations any more. It was only necessary until the first service release was available. Please download and install the latest service release from http://my.smithmicro.com/win/poser/updates.html - that's all that is necessary. Among other improvements, it will ensure that the Visual Studio redistributable libraries get installed correctly.

Quote - look see

I see you're running ForceWare 178.24, that's an outdated driver known to be problematic in conjunction with Poser. It can be configured to work properly with Poser Pro, but at this point you should just get the latest version from nvidia.com

Quote - I had this problem with Bryce6 on Windows XP Pro 64 but it worked after I used 'Large Adress Aware' (LaaTiDo.exe  -> http://www.musikbanken.se/TechLaaTiDo.aspx). Maybe this little and free program helps in Vista or Windows 7 too (it was released for Windows XP 32bit to trick the 3GB limit, but it works also with XP Prof 64!) ?

Poser 7 and Poser Pro are compiled large address aware, so this tool won't change anything (at best). If they weren't, the Poser process couldn't even use 3GB, it would hit the 2GB barrier. See msdn.microsoft.com/en-us/library/bb147385%28VS.85%29.aspx for details.

Poser doesn't use a z buffer image for depth of field. If you want to refine the DoF effect, you can increase the Pixel samples value on the FireFly tab of the Render Settings dialog (please increase the value carefully though, it increase the actual number of samples taken exponentially; 6-8 should do).

There's another thing you could try (has nothing to do with texture caching for final rendering, but can help if you're short on RAM and your textures are large): Poser 7 allows you to adjust the texture preview size. Regardless of the actual size of the texture, the maximum resolution Poser 7 will load it at for previewing a scene is specified on the Preview tab of the Render Settings dialog. So lowering that value will leave more room for other data while posing, animating, etc.

Joelglaine, please contact Smith Micro tech support via my.smithmicro.com/support/index.html, describe your problem and provide your scene if possible. Tech support staff might also be able to help you with an earlier service release.

Quote - Gah! I just installed it and now I can no longer load from the collections folder. WTF??????

Speaking of discarding preferences... one way of resolving this issue is to delete libraryPrefs.xml in your home directory (C:Documents and Settings[user name]Application DataPoser 7 or C:Users[user name]AppDataRoamingPoser 7 respectively).

If you have a lot of external runtime libraries linked in, or don't want to delete your library preferences for another reason, then you can open libraryPrefs.xml in a text editor and change the location of your main runtime from
    <ContentFolder folder="Runtimelibraries"  index="0" >
to
    <ContentFolder folder="C:Program Filese frontierPoser 7Runtimelibraries"  index="0" >
(assuming that's where your Poser 7 is installed and main runtime is located). This should resolve the issue without deleting libraryPrefs.xml.

Quote - I had no problem downloading it from S M, but if your read the info, it only works on a fresh install of P7. I am not reinstalling all that content I have so I guess I'll wait until my next major reformat.

Poser 7 SR3 does not require re-installing from scratch. While doing so is recommended if you are experiencing difficulties with your installation that can't be resolved by discarding preferences, in most of all cases installing over an existing installation works just fine. Even if you have to re-install the application, that doesn't necessarily mean you have to re-install all 3rd party content.

Quote - So far the SR3 is causing my Poser 7 to act weird.  The Material room is acting retarded. It's reaction to any clicking is very retarded in time. Before it would respond within 1 to 3 seconds, now it's response is retarded to 15 seconds to 2.5 minutes.

Do you have an ATI graphics card or chipset? If yes, then please update your graphics driver. If you deleted your preferences during installation of SR3 and the problem appeared, then you might have previously had the workaround for the driver problem enabled that we shipped in SR2.1. You could still do that, but at this point it's better to just get the improved driver from ATI/AMD.

Quote - Rendering four threads is strange to watch now. Before it would render as normal, now it splits the screen into quarters and render each quarter seperately . Strange but usually gets the job done..

Rendering in four threads was always done in four quadrants, no change there. If you had 'Render in separate process' enabled previously, it might have looked like it did it all at once due to how the results are read back.

Yes, Poser Pro and Poser 7 SR3 both run on Tkinter 8.4.

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.

zollster, there were problems with Tkinter 8.3 that forced us to update that component. Here's a quote from the readme:

"PoserPython

-Updated to Tkinter 8.4. (Windows) NOTE: Please contact script developer if compatibility issues with Tkinter are encountered."

It could be that Occlusion Master and Unimesh Realism Kit use this component for their user interface and are affected by the update.

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.

TygerPurr, thanks a lot for the explanation. In case you want to do this under Vista, the location is c:Users[user name]AppDataRoamingPoser 7

Yes, as stated in the readme, some prefs changed their location: "-Memory dots and custom UI preferences now stored in language-specific sub-directory to facilitate concurrent installation of multiple Poser versions."

MaskimXul, what platform are you on? Mac or Windows?