Hey there Ockham.

I don't ever recall Poser installing a C++ resditstributable before.  Daz Studio runs that installer as well, and has a version of that DLL (its the only place it shows up on my machine).

I'm concernced that that might not be the only thing missing.

I'm betting that tcl84.dll and tk84.dll have been compiled against MSVCR71.dll and not MSVCR80.dll, just like the P7SR2.1 and before tcl83.dll and tk83.dll are compiled against msvcrt.dll

This sort of thing can lead to instability, especially with memory allocation (which Python does a lot of).

Well, copying the file from elsewhere on the pc into the runtimepythondlls folder has solved the issue for the moment.

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.

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 - 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.

@nruddock: Yup, you're right.  A quick view of the tk84.dll code shows a reference
to MSVCRT71.

I'm on a Dell 1.8 Ghz, with 1 gig of RAM. No ATI cards or such and the Firefly render engine is so slow, it's taking days to finish renders that HAD taken 8 to 9 hours to finish. How do I uninstall the SR3 update?  I'm through with it. It's crippled my ability to produced fast renders in a timely manner.

Quote - I'm on a Dell 1.8 Ghz, with 1 gig of RAM. No ATI cards or such and the Firefly render engine is so slow, it's taking days to finish renders that HAD taken 8 to 9 hours to finish. How do I uninstall the SR3 update?  I'm through with it. It's crippled my ability to produced fast renders in a timely manner.

Well unless things have changed with this update for poser you have to totally uninstall P7 and do a fresh install to get rid of SR3. The SR will not show in add/remove programs in the control panel.

Just run the SR2 updater.

The only SR 2.1 I can find are the French and German. If it changes the language, it might not be worth it. If there is NO alternatives, I'll learn GERMAN instead of keeping SR3 as it is!

After rendering for over 36 HOURS it crashed to the desktop only 75% completed!  Oh man, I am so POed about this!

Any English SR2.1 floating out there?

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.

I've tried several different scenes and only one out  of five even rendered. I already contacted customer service. I have never EVER needed to contact Customer Service to get a previous SR to restore function to ANY software before! In that Poser is crippled right now, I would say I am a disgruntled customer. :cursing:

I'm seeing some marked changes in the rendering in SR3, possibly connected with ambient occlusion, maybe? The most obvious effect I've seen where a water surface intersects a skin surface which has had a shader added using this Unimesh Realism Kit.

According to Smith Micro iin an official tech support response: "One thing you could try is reducing the irradiance caching down to zero. This shouldn't lower your quality, as the SR3 updater has improved the quality of the renders in general."

LazyLeopard--that might be what you see in your renders.

Quote - > 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.

Last time I reinstalled P7 it overwrote my entire library (deleting all previous content) half the  geomotries and many of the textures.

Quote - According to Smith Micro iin an official tech support response: "One thing you could try is reducing the irradiance caching down to zero.

Thanks. I had tried reducing it to 50, and looking closely now I can see a very slight reduction in the over-shaded interfaces, but I'd put it back up to 90 because reducing it increased the render time dramatically. I'll give zero a go, and see whether it improves matters while still rendering in a finite length of time.

I just finished backing up my runtime, deleting poser, and re-installing it, and uploading SR2.1.

I just reloaded my scene and hope to god to render the bastard before I die from frustration! :cursing: This should have finished by LAST SUNDAY DAMMIT!

WIth SR3 it took 28Hr 40Mn and then crashed to the desktop at the 80% mark. I'm going to start it up and see what happens right now! 

Wish me luck.:rolleyes:

I asked Tech Support at SmithMicro Site for help to get SR2.1 , have not heard anything yet though.
I made a fresh install of Poser 7 and waiting.
SR3 really messed up my Poser which was working fine.

They should take the SR3 off their Site and test it before releasing it.

They did test it.. for about 3 or 4 months, but no one can predict every single hardware and software combination out there.

Just finished my Render that SR3 had at 28Hrs40Mn.

With Sr2.1 installed it was 5Hrs 22Mins.  No crashes to the desktop, no hiccups, no monkey bussines!

If your Poser installation is crashing and shaky BEFORE you install SR3, it may fix a lot of problems.  If your Installation is already rock-solid and you're not having problems--I recommend holding off on installation until more beta-testing on it is done.

It certainly has some effect, but it's not the whole story. Here's the same (double-sized) render section with the irradiance cache set to 90, 50 and 0 respectively.

Right after I installed SR3 my render times deteriorated from about 3-5 minutes to 30-40 minutes.  Naturally, I assumed it was due to SR3. 

I was wrong. 

My problem had to due with a hair prop which I discovered by trial and error.  Once I deleted the hair prop by render times went back to the normal 3-5 minutes.  I wish I knew the name of the prop, but I changed it when I loaded it and my runtimes are too much of a mess to search.  When I come across it again, I will know it.

In the process of researching I got the following input from SmithMicro
 - SR3 should facilitate faster loading and about the same render time.  That is my experience.
 - Number of runtimes loaded to the library bar should have no impact on render time.  Impact on load time is an open question.  This has been my experience also.
 - Increasing the render threads to match the number of cores was a big help.
 - Irradiance caching will have no effect on Poser 7 render time.  Apparently, it is related to Poser Pro render time.

Yeah, I'm doing a scene with a nasty hair prop as well. My usual render times with everything cranked are a few minutes.. I'm looking at 5-15 minutes now JUST because of that ONE hair figure!

Multiple overlapping transmaps really kills rendertime.

That is one of the things I found out through experimentation.  Some hairs that had been fine to render in SR2,1 were suddenly 'radioactive' under SR3!  Since I have a LOT of hair, I almost exclusively use trans-mapped because it usually renders quicker. Under SR3 that is NOT true.  Some render the same, some cripple render times.

Same with some nodes. Reflection raytraced is slow, where the gather node seemed to cripple my machine. (Literally. It hit a patch of Gather and always crashed to the desktop!)  Ray-traced glass sometimes rendered slow, or crippled speed or caused crashes randomly.

Since I didn't want to try to re-invent the wheel with SR3, I had to roll back to SR2,1.  I'm used to what will do which foible in Poser 7 SR2,1,  But SR3 in some ways makes Poser act like a different application altogether,IMO.

Yeah.. it's fixed and works properly now. Your solution is much like peopel hanging on to poser 4 for 10 years after it should be dead n buried.

there were some nasty bugs tiny reported to SM as far as hair rendering and developement , and SM worked REALLY HARD to fix trhings properly.

Rather then a roll back, I suggest an additional poser 7 sr3 install, so you can relearn the proper way to do hair in the fixed P7 sr3 hair room?

That way you have all your older hair you worked on, but can take advantage of the new fixes in place as well.

Ummm, but he said 'trans-mapped hair' - ala helmet hair, hair prop.  How does that work in the Hair Room again? ;P

Quote - I almost exclusively use trans-mapped because it usually renders quicker. Under SR3 that is NOT true.  Some render the same, some cripple render times.

He said most, not all.

But the quoted inference is obvious: trans-mapped hair DOESN'T render quicker under SR3 (than SR2.1).  I've read it about ten times, and, yes, that is the inference. :)

So sue me?

you'll be hearing from my Lawyers, Bludsucker, A Chaser and Creep forthwith!

Quote -
 - Increasing the render threads to match the number of cores was a big help.

Interesting? How does one go about doing that?

Quote - you'll be hearing from my Lawyers, Bludsucker, A Chaser and Creep forthwith!

Might I recommend the firm of Dewey, Cheatum, and Howe?

LOL!

Maybe someone said it, but you can turn the raytracing for transmapped hair "off" under its properties, and the render time reduces. I usually do that until the final render, but to me I don't see much difference either way. Maybe some improvement around the edges..

Good luck

Quote - They did test it.. for about 3 or 4 months, but no one can predict every single hardware and software combination out there.

well here people have more problems then not. which means that something is wrong with the SP3.

people are reinstaling poser because of this. something is 100% not right here.

Quote - people are reinstaling poser because of this. something is 100% not right here.

Folks seem to be in a variety of positions, and I can quite understand why going back to SR2 looks like the best solution for some of them.

1. If you plain can't get something important to work (like the "wrong version of tkinter" problem which hit PoserPro) then you've not got much choice. It's a simple case of "the old one works, the new one doesn't."
2. If you try to re-render something but the result is just so different that you can't even begin to figure out what needs to be changed to get you back where you want to be, then you probably don't have much choice either.
3. If your new renders seem to have improved in places but have also developed isolated but unaccepable new artefacts then it's a choice between figuring out how to set things straight in SR3 and going back to SR2. Here, other folk who've already figured out changes can help.
4. If your new renders work just fine and look better than they did before, then you're not likely to be coming here for help. ;)

I've had one or two scenes that fall into the fourth category, but most of mine fall into the third or second. I want to stick with SR3 if I can, but at the moment it's like trying to paint with a brush which squirts inappropriate splodges onto the canvas apparently at random...

Does Poser Pro physical version includes a new manual?

Quote - > Quote - They did test it.. for about 3 or 4 months, but no one can predict every single hardware and software combination out there.

well here people have more problems then not. which means that something is wrong with the SP3.

people are reinstaling poser because of this. something is 100% not right here.

People that have issues WILL post, because they are seking solutions.

But people without issues are just working as usual, without reason to post. Thee will always be a few people with some issues with any new program update for any program.

As I've said, theres no way any company can test for every single hardware and every single software solution, and there's never a perfect bug free update for any program from any company as a result.

Quote - People that have issues WILL post, because they are seking solutions.

...though it's hard to know where to post to stand a chance of getting a useful answer. When a thread's more than a page or two long it's increasingly difficult to find useful answers, especially when the thread also fills up with meta-conversation like this. Maybe it's time for a new thread specifically about the effects of the changes between SR2 and SR3...

Well, this thread was originally announcing it's release, and was not a torubleshooting thread at all. Thread drift is commonplace, and people with sr3 will most likely find a solution in an associated thread.

Quote - and people with sr3 will most likely find a solution in an associated thread.

...if they're lucky enough to find the right associated thread in the first place. So far this is the only thread I've found here which seems to be dealing specifically with SR2/SR3 issues in any way at all...

There aren't a whole lot of sr3 threads at all, so there aren;t a lot to choose from.. ;)

Plus Smith Micro themselves have also replied here as well.. when you actually have the guys who worked on it replying in a thread, odds are you'll find the info you need here whenever they pop in again. Good reason to stick around, eh?

If you have a particular issue that hasn't been discussed you have two choices.  Post your issue here and hope that the SM people see and answer it or start a new thread specifically for your issue and hope someone who has the answer in the community will have your answer.

3 choices.. also contact SM direct, which is always the smartest option on new releases.

Well, the first choice should be to contact SM directly.  Secondarily, users can inform each other of their experiences which may help others having similar issues.  Any time something doesn't work as expected (whether from the source or the user), the dialog between the company and user should help to resolve the issue or at least illuminate it. :)

hey, download went fine, installation went fine, but:

AnAn does not work any more ( none of them)

The hip detafches from the figure and places itself about 3" back.
Also the texture goes missing.

Any sugestions? The rest of the figure is OK, and the problem is not solvable.

Thanks, Tony

hmm iam gettings render speed problems too after installing SR3.
Mainly even though ive choosen 4 threads only 2 of my procs are used (using alt-ctrl-del) and only at 15% CPU usage!!! (before i was getting a 90% CPU usage from all procs). I tried playing around with the adaption Threshold and memory limit buffer but very little difference. it takes me now almost twice as long to render O.o !!!

quote/  AnAn does not work any more ( none of them) / end quote

You scared me a bit there, added my Anan runtime when i saw your post (deleted all prefs in the upgrade) and loaded AnAnR2 (new Judy), worked fine for me.

Sorry I cant give you any solution for your problems with AnAn just wanted to say that the character works ok here even with SR3

The only problem I have is that P7 now have troubles identifying some textures as valid jpg's (textures called on when loading some hair models), when i load the same textures in P5 or P6 they work rigth away.

I do however find the application more stable now as the random crashes are almost gone.

Regards / Jonny