Please only select 'Remove existing preference files' or 'Backup existing preference files' during updater installation if you intend to do that. Yes, those options will return Poser to the factory state, including the runtime library setup.

If you want to continue with your current preferences, please choose 'Use existing preference files' instead.

If you experience difficulties downloading Poser 7 SR3, please contact Smith Micro tech support via my.smithmicro.com/support/index.html and let us know what updater you were trying to access, and what your serial number is. We'll try to address any issues there might be as quick as possible. We apologize for the inconvenience.

BladeWolf, we might have a different understanding of what a memory leak is. To make sure we're on the same page - I go by this definition: http://en.wikipedia.org/wiki/Memory_leak

Again, I'm not aware of the problem you are experiencing. If you want us to do something about it, we need a very detailed description (what render engine, what app preferences) and a scene that reproduces the problem. If the problem occurs with any scene, it might make sense to go over your system settings with tech support (virtual memory, user rights, etc.).

Quote - I installed all the updates including SR2.1, now I'm having all sorts of problems, is there any way to uninstall the updates?

There is no direct way of uninstalling just one update. Please contact e frontier tech support and describe the problems you're experiencing. They will also be able to tell you how to reinstall with minimal effort.

At this point (SR2.1), we're not aware of any memory leaks. If you have a scene that exposes one, please submit it to e frontier tech support via www.e-frontier.com/go/emailtech and specify what action (posing, simulating, rendering) leaks. We'll then investigate the issue.

Quote -
Has anyone else had the Poser to Photoshop CS3 Extended script not work?  Since I installed the last 2 patches it doesn't work at all.  Even when it did work, I've gotten mixed results.  Oh, BTW, node based shaders (or procedurals) aren't really accepted by Photoshop--it doesn't know how to interpret them.

You might want to check this knowledge base article: www.e-frontier.com/article/view/2302/1/861/

If the exporter doesn't load, the updated file from that article will help. If textures don't show in Photoshop it might be that they are larger than what your graphics hardware supports. In that case you would have to shrink them a bit to get them to show.

Hi all,

we beg to differ. Here's a comment that I made in a similar discussion:

"The default is filtering because Poser 7's tiled texture loading technology relies on Mip Mapping to save resources and improve performance at the same time. With 50 MB total used for texture memory on rendering a Poser 7 scene, texture filtering resource use becomes irrelevant. We do not use summed area tables any more like in Poser 6 (that's what needed 3x as much memory as an unfiltered texture), and we're not holding the entire texture in memory at render time any more either. However, to make that possible without slowing the renderer to a crawl we have to use filtering. That's why there is no render setting for filtering any more, it's always on.

The option on the node is provided for those cases where you really need the aliasing effects that sometimes are considered "crisp" and you don't mind taking the performance hit."

If you feel your renders are blurry, you should reduce the shading rate. That's the single most important parameter when you want to increase detail on shaded surfaces.

Since some were wondering what "Quality" means in this context, here's an excerpt from the Reference manual:
"Filtering: The Filtering attribute allows you to select one of three options for texture
filtering on the selected image map. These options are: None--no texture filtering;
Fast--high-speed texture filtering; Quality--high-quality texture filtering."

stewer elaborates on the subject in http://www.renderosity.com/mod/forumpro/showthread.php?thread_id=2679119

Uli

Poser 6 and 7 scale up the universe roughly 1000x for rendering in FireFly (Poser 5 scales up ~100x).
I would assume that the problem described is an oddity in shadow camera behavior and can be resolved by adjusting shadow cameras.

If you're running Poser under Vista with an NVIDIA chipset, please go to NVIDIA's website and download the latest driver. The issue with Poser freezing when showing modal dialogs (such as render progress or delete confirmation) is known and resolved by the latest drivers.

If you encounter XML errrors on launch, please zip up your knownFaceRoomHeads.xml and contact e frontier tech support (http://www.e-frontier.com/go/emailtech). Some SR2 fixes rely on a properly updated version of that file. We did extensive testing to ensure that the update process goes smooth, but apparently there are cases where it still can fail. We would like to find out what the source of the problem is and fix it.

Thanks,
Uli

P.S.: We looked at the file that gets distributed with Apollo's Face room module. There are some inconsistencies in that file that might throw off add-on installers (like Miki2 or the G2 males). SR2 itself should not have problems with these inconsistencies. However, if you installed one of e frontier's Face room add-ons after dropping in Apollo's file, please mention that to tech support. Lastly, the Apollo file should not be needed for Poser 7. The Poser 7 version of knownFaceRoomHeads.xml contains all necessary information already.

Quote - But have the Content files been updated too since the last patch?

There are currently no new versions of the content updaters. The only new release this week is the SR2 application updater.

Quote -
Same problem.  Maybe this is another one of their fixes.  After all, according to UliK, all previous versions of Poser were not handling the alpha channel correctly when rendering over background and saving to TIFF.  The Render Police strike again.

Read this thread again, especially the last posts of beryld and me. Thanks.

Quote - Has anyone tried saving a background render in .Tiff?

Works fine for me here. There is one change in SR2 though - by popular demand, Poser now does not discard the alpha channel any more when rendering with FireFly over a background image. So depending on what software you use to view the TIFF, it might look like the background is missing. The reason would be that that software applies the alpha channel before viewing (Microsoft's built-in viewer does that for example, whereas ACDSee and Photoshop hide the alpha channel)

Quote - This update forced me to reinstall Poser from scratch... somehow one of the XML files got corrupted and it doesn't say which one.

This really should not happen. Was your Runtime/heads/knownFaceRoomHeads.xml modified in any way? Most likely that's the file that caused you trouble. Please contact tech support via http://www.e-frontier.com/go/emailtech and send them your broken version of that file (if you still have it, if not please explain whether or not your version of that file was likely to be modified).

Like I said, it's a bit confusing. Let me try to be more precise. "PF Usage" shows you Total Commit Charge, or the sum of all virtual address space currently in use. The virtual address space for each process spans across physical memory and your page file on disk. Look at this paragraph:

"Commit Charge (K)

Memory allocated to programs and the operating system. Because of memory copied to the paging file, called virtual memory, the value listed under Peak may exceed the maximum physical memory. The value for Total is the same as that depicted in the Page File Usage History graph."

There is further information in http://msdn2.microsoft.com/en-us/library/aa366914.aspx (MSDN articles are a little hard to digest for non-technical people, but can provide good background information). This is the key sentence:

"The total amount of virtual address space available to a process is limited by physical memory and the free space on disk available for the paging file."

cspear's screenshot is a good example. If there were 2.5 gig of data swapped out on disk, there would be no way how both CPU cores could be pegged. 2 out of those 2.5 gig are probably physical memory, so both CPU cores get enough data to run at full speed.