Attached Link: http://www.e-frontier.com/filemanager/list/updates/0/0/0?sbss=300

Good Lord, why not just call it SR2?  This is going to be confusing for
users.  Oh well, maybe it will help, if it fixes the tendency to render
pretty portraits of "Bedtime in the Coal Mine".

Oh my goodness - It really IS another upgrade for bugfixes on top of SR1.

Groan.....  tomorrow....  I shall get it tomorrow....

I'm confused as to what I should install from all those updates.   I updated with SR1 but now I see content updaters for Poser 7 and content updater for Poser7 SE.  I got the SE so should I go with just that??  It's a smaller size and I feel maybe it might not be complete?   The SE update is 17MB while the Poser 7 Content Update is over 140MB!!  And if I do need both is there a specific order in which to install them??

Tomorrow I'll write support, just don't have the energy to deal with all this on a lazy Sunday evening :)

I'm assuming the SE updater is simply that - an update for the SE content. You don't need it if you don't have it, or if you don't use the stuff. The Content Updater should be an update to ALL the content that the program includes except, of course, the SE update - why update SE content for people who don't have it anyway? Thus the Content Updater should be for everyone. I haven't been able to download it though since it's never worked when I try, but I'm just using my experience with past release.

Then, there are the Service Releases. These are supposed to target aspects of the software itself and as such, they are much more important than the Content Updaters. And if there's an SR 1.1 update, well, be glad ef is tackling the aspects of Poser that need fixing. Maybe what's fixed is something minor and thus it doesn't justify a full SR number so they added a .1.

Anyway, that's not unheard of in the software industry. I use XSI at my workplace and I recall that about 4 months after the release of XSI 3.5 they released the ill-designed XSI 3.5.1 update. That update broke a lot of render options so they had to hurriedly release an XSI 3.5.1.1 update. Pretty absurd huh? But it happens, even in the highest end segments of the market (and XSI's a heck of a piece of kit - used to be $14,995 for the Advanced package back in those days, it's around $8,000 now).

Quick report:

Installed nicely.  The separate-process Firefly render is fixed.

But I'm still getting Bedtime In The Coal Mine for an animation
using the P4 renderer, separate process or not.

o.k., we'll be awaiting any reports on what it breaks/fixes.

ITS CRAPEEERR
instaled it yesterday with content updater and it takes toooo bloody long to render, so will uninstall from new computer, hell update even made poser 6 slower god no's how they did that.
i have instaled poser 7 on old system and am going use content update, screw sr 1.1, save external drive and put on new comp.
Dont mater what they do the patches wont fix the main bug's as talking 1 chapie in shop he heard from his mate in america, a hacker looked at core code of 7, and his report it the program has to be remade again.
What it means they gota reprogram again then send new program to registered users, even though i bought it in states the most important thing for me is morph tool a bloody life saver.
so will use poser 5 and 6 set up stuff, poser 7 morph tool, and render in carerra pro 5.

P7 starts faster now (unless I'm imagining things)
Not tried the "Render to separate process" yet but I reckon normal renders are a touch faster too, especially with some hairs that take forever to render.  Not tried it with the cloth room or volumetrics yet but I'm impressed so far

Just instaled content updater and se content updater and program still runs fast, on seperate install of 7 on hard drive installed 1.1 on top of content updater and ya guesed it crasho wamo, program bombs.
So im copying 7 with content updates to external drive to put on new system and no way on gods green earth will patch 1 or 1.1 see light of day in poser 7.
Thank god for carerra 5 pro.

man you get some grief from P7.  Dunno why some have no problems at all and others it's hell on earth

If I haven't installed the first patch, do I have to do that before this, or can I just jump ahead to this.

I was never game to install the first because so many had problems with it & I figure as P7 worked well for me, don't fix what aint't broken LOL

Works great on my end :)

There's really not enough fixes in it to call it SR2.  People would expect more and be upset.  That said, It fixed my biggest issus w/ P7: "Fixed case where rendering in separate process would fail, producing a blank image" and "Fixed case where applying MAT poses would change a figure's pose."

@Anniebel:  Whenever there is a SR for Poser, you need only install the most recent one (in this case 1.1).  It's not necessary to try to find and install previous versions first.  SR1 fixed a lot of issues w/ P7, you should definitely install this (SR1.1).

Edit:

It does seem to boot up noticeably faster, but it could be in my head.  here are the release notes for 1.1 specifically for those curious but too lazy to go click through and enter their SN:

ENHANCEMENTS AND BUG FIXES IN Service Release 1.1

FireFly Render Engine

• Fixed case where rendering in separate process would fail, producing a blank image.
• ColorRamp node does not cause artifacts any more when rendering multithreaded.

File I/O

• Fixed instability on reading certain images.
• Fixed PICT image reading problem (Intel Mac only).
• Fixed texture loading problem causing certain figures to preview black.
• 3D file format import now working when decimal separator is set to ',' (Windows only).

Library

• Fixed case where applying MAT poses would change a figure's pose.

Cloth Room

• Fixed case where Cloth simulation would corrupt scene.

Misc

• Adjusted install log to avoid removal of content installed after Poser 7 upon uninstalling.

o.k., it appears they're saying they fixed the comma thing that screwed up european versions in sr 1.0

Quote - @Anniebel:  Whenever there is a SR for Poser, you need only install the most recent one (in this case 1.1).  It's not necessary to try to find and install previous versions first.  SR1 fixed a lot of issues w/ P7, you should definitely install this (SR1.1). > Quote -  

Ok, thanks I will see if I can get up enough courage to install it LOL

So far, I'm liking it.

I just checked some of my scene files, and they've apparently fixed my recurring issue with the Cloth Room that caused some of my cloth sims to literally explode.  Now I won't have to run the simulations in P6 first.

I had another problem with materials (particularly on Victoria 4), where they'd initially load completely black, requiring me to reload the textures.  SR1.1 seems to have fixed this, also.

Haven't noticed any new problems yet.

Also fixes the PICT image reading prob on Intel Macs.

SR1.1 installed smoothly and so far so good - haven't noticed any problems yet. 

But then I don't seem to have anywhere NEAR the problems other people have reported with P7...from initial install to SR1.1.

Well took just under 2 hours uninstal from new system with ashampoo and clean out registry, even carerra 5 pro locked.
After i cleaned system poser 6 ran bloody smooth, so took p7 instal from old comp and put on ext hard drive, then put onto other system without instal, program ran smooth.
Od character install with body parts invisible till render but seems from content update happen, but ran smooth as a baby's ass, did a test put patch 1.1 on and program slooow as asses.
So deleted and put back on again and i will run p7 without the bloody patch as long as i can use me morph tool im happy, if i wanted render in p7 would have to put on other section of hard drive.
Load stuff poser 6 save scene load in to patch 7, hell poser 6 ran bloody better with patch 1 after they realise program slowed down, nope patch 1 and 1.1 loadsa crap as causes to many other problems.

What exactly does "render in separate process" mean anyway? Is it an advantage over the usual way of rendering? Still trying to decide on upgrading to P7 here.

It means that you basically start off the render engine in a separate process so in theory it gets more memory/processor time than if you render within poser itself.  You need to set your firewall to allow poser and ffrender.exe to talk to each other though

Sounds worthwhile; if it works right another mark in favor of upgrading. Been waiting to see how many bugs get squished before buying P7. On the minus side it doesn't play nice with Carrara, so they tell me. But I can still use P5/6 for that.

Poser
has gone with vue as thier will be no support for cararra or even cararra 6, though dont matter as i can load from 6p6 into cararra 5 pro, and anyway independant programers will be able make a 3rd party bridge for p7 work with carerra 5.
though at moment you cant render big poser scenes in vue 6 wont handle it.

Heh, the Vue 6 PLE I have crashed its ass off trying to load 1 clothed M3. Nothing else, not even a 1-poly backdrop. I hate to think what it considers a big scene.

well, I'm just about to load a scene with 3 complete sets of VAP GRIM armour and a backdrop into VUE so we'll see how well it copes

Byrdie, Vue is a HUGE memory hog, especially when it comes to importing things from Poser.  The latest beta patch has seemed to improve the issue somewhat, but given that it's beta, I doubt it's applied to PLE (currently exists for Espirit/Pro Studio, Infinite, xStream that I know of).

As for Carrara, it will actually work just fine, but you must have Poser 6 installed in order for Transposer to work correctly.  Once you install Poser 6, add your Poser 7 runtimes to its library and everything should be good to go.  You can use the (crappy, IMO) Carrara native import w/o P6 involved at all if you wish.  

The reason the eovia come DAZ3D folks were denied a Poser 7 SDK hasn't been officially stated, but it's assumed that since eovia (makers of Carrara) was bought out by DAZ3D since the time Carrara 5 came out, and DAZ makes a cheaper, yet nearly as robust and intercompatible direct competitor to Poser, DAZ|Studio, e-frontier decided to thumb their noses at them and say "NO SDK FOR YOU!".  One side effect of this is that eovia/DAZ3D is promising vastly improved support for DAZ|Studio imports in the upcoming Carrara 6.

UPDATE

Well the scene loaded and I could even render it - I need a lot more RAM though - took 10 mins to just load it but then again, that particular scene causes Poser more than a few problems so I'd say it worked pretty well.  If anyone is interested, the scene is "Fireteam" in my gallery

What is Poser 7 SE?  I just bought poser 7 for $180 on
Amazon.  I hope that's not it.

Well, I'm about 90% happy with SR1.1, but I noticed on my system that the DELETE function is broke again. It worked well enough under P7 SR1 but now it;s back to freezing the system again when you try to delete anything. Anyone else notice this?

mike

Well
Im gona instal bryce 6.1 on me other system and import poser stuff even though bryce accepts direct  from studio, and studio is still a bloody superb program.
I dont use it much as when i import some poser characters done it moves some clothes ect, but still great program, and when render in cararra 5 pro i have noticed it's quality is better than poser 7, though im bloody angry about the bodge job they did with vue 6.
They were told from vue 5 about vue not being able import big poser scenes, but it seem's they tottaly ignored that part people mentioned, and i did a test i took a poser prop 200,000 polyons and destroyed 140,000 polygon's and saved and exported, ya guesed it vue 6 still recognise it as 200,000 polygon's, not 60,0000.
Vue 6 is a bloody major disapointment as we in 21st century and can make processor the size of a pin head, and now soon ya can use water to save info on.
With all these advances in science these bloody idiot programers still cant do a bloody simple pc program properly.

Quote - What is Poser 7 SE?  I just bought poser 7 for $180 on
Amazon.  I hope that's not it.

Oh I get it.  Ok, the special edition thing is gone, no biggie.

Quote - Good Lord, why not just call it SR2?  ......

...uh, because they still haven't figured out how to fix it all??

Quote - Well, I'm about 90% happy with SR1.1, but I noticed on my system that the DELETE function is broke again. It worked well enough under P7 SR1 but now it;s back to freezing the system again when you try to delete anything. Anyone else notice this?

mike

Works fine for me. I am on a mac PPC
Everything seems to load a ton faster. Shoot I used to wait just to create a new blank doc. Not any more. Like the fact that two items that loaded as black in preview problem is gone. Granted I have only been doing this for about 100 days. But sometimes P7 would collapse right at the end of a render using firefly. Did a bunch of reference renders of my inventory and it was quick and no problems at all. (so far). One big file with both M3 and V3, walls, tables, a couch, standing lamp, rocking chair, used to take ages to render using IBL. Now it is reasonable to my expectations.

1 V3, No clothes, No hair
DAZ Jester Hat
2 P4 dogs
1 tent CR2 (Sixus1's circus tent)
3 lights (I IBL, I spot, 1 Point)

Original scene had 1 IBL, 2 Infinates, 1 Spot, 1 Point set to Spec only but:

Scene rendered in Both P6 SR3 and P7 SR1
Installed SR1.1 and nowP7 almost instantly gave message "Problem with Raytrace, try reducing...yadda yadda yadda)

hmmm, used Python Script to remove all lights and revert to 3 lights described above:

Also noted that Shadow Cameras no longer show you the 'angle' of your spot lights (ie, change angle and shadow cam no longer updates)
And after deleting lights the original Shadow Cameras did not delete. Even after applying a different light set from library, however after I manually deleted and then added a light suddenly POP the correct Shadow Cameras suddenly showed up...
Also noted that light controls seem 'wackier' and now harder to control
Also noted the delete thing again as well (noted by earlier post)
Still does not load any Bump maps (not displacement, not gradient bumps - "bump" node maps) and instead it loads only a small preview of the original and appears that is was actually gets applied during render (perhaps how they lay claim to "faster render" by forcing a reduced resolution map...? go figure)

I conclude; its still broken, unless the "Render in separate Process" is an issue then stay on SR1, better yet, use Poser 6 that has far less issues and better stability compatability.

Oh, Speed.....reduced to only three lights and it still could not render the scene in a single night; previously the scene did render in about 5 hours (yes, I like Quality over Quantity, I use high settings and I reject the idea of "duh, turn off Raytrace if you have problems..." - duh, like Raytrace is part of what I Paid for, isn't it....or is Raytrace a "future feature not yet implimented but just there to look cool"?)

I upgraded to SR1.1 last night.

After upgrading -- using 'render in separate process' -- I was able to render out a scene which prior to the 1.1 upgrade had always rendered to around 90% and then stopped with a memory error message.  But now, it works.

One other matter of note:  the scene rendered more slowly than it did pre-SR1.1 (not using 'render in separate process'), but the final rendered result now looks better than the earlier '90%' results did.  This was somewhat surprising to me.  But IMO -- the better result is worth a longer wait.

The scene has 4 characters -- 1 V4, 1 V3, 1 off-brand male character, and one M3.  All of the characters have full clothing, plus hair on the two female characters.   They are set in a background scene inside of a restaurant with lots of props & reflective surfaces all around.  Raytracing is on.

Windows XP, Core 2 Duo, 4G's of RAM.

Finally got the scene to render, took better part of a day, had to reduce the ray bounces from 6 to only 3 (ok for this scene but lousy if I intended to have any reflections...) and had to lower samples from my usual choice of 25 to only 10.

guess Poser 7 is ok for the Animae makers...but its loosing the race for "fine art" creators, DAZStudio renders the scene in under 20 minutes, and that's WITH a fully clothes David 3 character and his props added and my original light configuration...and only one cpu with just 756meg of ram