Hi, Id like to update everyone on the status of SR3. You can expect this service release before the end of the next 10 days to which its availability will be announced on the forums as well as our web site: www.curiouslabs.com Below Ive listed the items addressed within the SR3 release. With kind regards, Katherine ------------------------------------------ Enhancements and bug Fixes in SR3 ------------------------------------------ General Application Speed ------------------------- - Poser start-up times noticeable reduced. When launching Poser for the very first time, some system files are loaded and cached by the system, and hence are not loaded on consecutive starts. Some details on start-up times on selected test systems follow: first start : P4 1.600 Mhz : PIII 650 Mhz ----------------------------------------------- SR 2.1 : 42.0 secs : 65.0 secs SR 3 : 31.0 secs : 45.0 secs second start : P4 1.600 Mhz : PIII 650 Mhz ----------------------------------------------- SR 2.1 : 28.1 secs : 45.0 secs SR 3 : 16.5 secs : 28.0 secs - File loading speed improved. Loading speed in general (both compressed and uncompressed) has been doubled for large files when the app is running. E.g., loading Don Casual from the library yields: load Don : P4 1.600 Mhz : PIII 650 Mhz ----------------------------------------------- SR 2.1 : 20.0 secs : 32.0 secs SR 3 : 9.0 secs : 15.0 secs The improvement tends to be between a speed-up factor of 1.2 and 2.2 on current hardware. These results may differ with various hard disks and CPU configurations. Walk Designer ------------- - Walk Designer has been adapted to the Poser 5 figure proportions. The walk styles now work better on the P5 figures. The number of frames will be set based on the frames necessary to walk along the path with natural speed. You can change this number to change the speed. For example, if the calculated frame number is 160, and the user types in 320, then the generated walk will be half the normal speed; typing in 80 doubles the speed. FireFly Render Engine --------------------- - It is now possible to enable smoothing on a per object basis. - Firefly Draft and Production settings with one infinite light, ray trace shadows on now works. - Some render bugs for global 3D textures have been fixed. Material Room ------------- - Import background image: Fixed a crash bug when the loaded image was too wide (>=4096). - The Global setting on shader nodes now works. - Loading AVIs to the Background Movie shader node now previews and renders correctly. - When reloading a saved pz3 file, AVI movies used as texture or BG Movie are not discarded any more. Face Room --------- - High quality texture support. When exporting or applying a texture to a figure, it's now possible to choose between using the maximum resolution of the inputted image or photo(s) instead of the current default resolution (512x512). If there are no input texture(s), the resolution is read from "Poser.ini". - "Apply Shape" button replaced by "Apply Shape" check box. Allows photo matching (feature point dragging, rotation, translation, scaling) with interactive geometry change. - Higher visible resolution when zooming into the input photo image. - Improved memory handling when loading textures from file. - Ability to adapt the face color to figure color when applying a face to a figure. If the face and the body colour differ, Poser lets choose now to have an automatic color update of the face color to match the body color. - Fixed rotation point for eye morph targets (spawn morph target bug, origin of eyes wasn't adapted correctly) Cloth Room ---------- - Enabled changing the ignore collisions settings after a simulation was created. Python ------ - New functions exposed to configure FireFly render options on actors: * RayTraceShadows() - Query wether this light is using RayTracing for shadows. * SetRayTraceShadows() - Set wether this light is using ray tracing for shadows. * SmoothPolys() - Query wether polygon smoothing is enabled for this actor. * SetSmoothPolys() - Set wether polygons smoothing is enabled for this actor. * BackfaceCull() - Query the actor's backface culling flag. * SetBackfaceCull() - Set the actor's backface culling flag. * VisibleInReflections() - Query wether this actor is visible in reflections. * SetVisibleInReflections() - Set wether this actor is visible in reflections. * VisibleInRender() - Query wether this actor is visible in renders. * SetVisibleInRender() - Set wether this actor is visible in renders. * DisplacementBounds() - Get the actor's displacement bounds. * SetDisplacementBounds() - Set the actor's displacement bounds. * ShadingRate() - Get the actor's shading rate. * SetShadingRate() - Set the actor's shading rate. * ShadowBiasMin() - Get if this light uses ray tracing for shadows. * SetShadowBiasMin() - Set the max shadow bias for depth map shadows on this light. * ShadowBiasMax() - Get the min shadow bias for depth map shadows on this light. * SetShadowBiasMax() - Set the min shadow bias for depth map shadows on this light. * ShadowBlurRadius() - Get the shadow map blur radius for this light. * SetShadowBlurRadius() - Set the shadow map blur radius for this light. * AtmosphereStrength() - Get the atmosphere strength of this light. * SetAtmosphereStrength() - Set the atmosphere strength for this light. Misc ---- - Morph Putty: Clear pins now removes the red dots on figure. - Added a ?Set Parent? button in the Properties palette for hair groups - Solved problems with hair playback and highlighting. - The comma (',') on a keyboard's numeric block now works for numeric input. - Disabled parenting body parts with IK switched off to props. - When an .obj file which is referenced by a .pz3 is moved, the user has to locate the missing geometry file. The new path the user specified is now saved to the .pz3, removing the need for loacting the file on every subsequuent loading of the .pz3.

All sounds good, loading speeds is a welcome addition, hope all goes well for SR3.

Great, what about the software's complete inability to process a "file not found" from the operating system. Main issue here, all those falsely or improperly referenced .bum files or .jpg textures that have been moved/deleted/didn't come with a packaged freebie/etc. Why does P5 still take forever to realize the "file not found" message has been sent back by the operating system and it should stop looking. 5-10 minutes wasted in la-la land waiting for P5 to even ask "do you want to keep looking for files" is pathetic. This should have been one of the first things on your list of "MUST GET THIS FIXED".

Great! Thanks for the update. BTW I was wondering if a few other things got fixed? 1. Currently selecting a material completely obliterates a current material. Any chance we can have it like poses where we can save just partial materials and have them combine? 2. Material room sometimes defaults you to full preview mode instead of your settings. Also it always brings up the pose menu even if I selected a different menu. 3. When using AVIs as materials and combining this with a multiply output the AVI plays back black, horizontal lines, especially if I have 2 or more AVI materials running. 4. The Show Selected option for magnets doesn't work. 5. An info box for materials and items. Basically, if I select a figure and click info in the figure menu the dialog will show me the paths for where the obj is, the path for the cr2 etc. Also the same for materials. Some way to show the path for the bitmap. 6. Magnets don't save right when two figures posses the same magnet prop. For example, if I load up two figures using the same named magnet on the head for each figure then save one of them, the saved figure will get two magnet channels instead of one for each body part assigned to the magnet. Then upon subsequent loads and save of the figure I get an additional bogus magnet channel which adds to the original. 7. Any chance you could add Morph Target manipulation routines to Python so I can write scripts to copy, combine, flip etc morph targets. I'd like to not have to keep updating Morph Manager and a lot of the functions MM does I think should be in Poser somewhere. At least if there were script commands to get the array of delta verts and a way to add the array to another object, that would be cool.

In the list there isn't the hair room, that has many bugs (e.g.: "do collison" that not work!)... none fixed?

Fixing the file not found problem would be a massive bonus.

Don't get me wrong, any fixes to P5 are welcome, but many of the things I'm still having problems with (and I see a lot of complaints about) aren't in you fix list above. Here's what really seems to need fixing: The "File not found" error dialog box hides under the program. It's difficult to bring it up. "File not found" does not always recover. Sometimes the program dies no matter what you do. I have to save my file every time before I use a MAT file because I have to worry about Poser crashing if there's a reference error. Excessive delay time in switching rooms. (10-20 seconds to get into the Material Room is annoying.) Allowing the user to clear the unused textures would be great. Poser keeps all the texture info in memory and if you try to load a new texture with the same name as a currently loaded texture, no matter where the new texture is located, Poser will not load it, even if the original texture is not being used. You have to shut down Poser and open it back up. Even if you close a project and open a new one up, Poser still keeps the texture information from the old project in memory. I see some potential issues with Poser caching system files for subsequent start ups, but I'll give that a "wait and see." Thanks for the update.

Pose room An ability to have user specified cross-talk would be nice. At our present level use, not having this hobbles us.

Cresent, I think Katherine's reference to caching files on first load is just a description of Poser 4 & 5 normal behaviour. Dunno what it does, but both 4 & 5 always load faster on 2nd load per OS boot. My concern is there's nothing mentioned about returning reaction speed of the dial manipulation to Poser 4 levels, or fixing the dials "roulette wheel" selection of the final value after you release it. Perhaps that's addressed but not considered important enough to list??? I'd even take an undocumented poser.ini option to switch back to Poser 4 hard-to-read dials, BTW. (You see, I can get better lenses, but I can't speed up time :-) Nothing about the 4MB memory leak either... I more than agree with you on the often fatal file not found error, but hey, it's only been about 4 years so far, so I would assume the non-EVM will ask us to be reasonable, and give them time to address it ;-) To TalonGE, the delay seems to be related to another memory leak at that point in its execution. Look at the memory usage during that period and you'll see it steadily climb throughout - on P4 as well as 5.

Very nice, some excellent stuff there. Face Room with large texs, love it. Would also like to see: 1. Fix for 'file not found', preferably a popup that gives the value expected: in other words, where Poser looked for it but didn't find it (I have several apps that do this, like Sonic Foundry Acid Pro and Vegas for instance, also Adobe Premiere, so it's not impossible). This makes it a LOT easier to go and look for it. Even The Tailor does this. 2. Smarter 'Open' window when loading a file. The tiny unexpandable window for finding a file is a leftover from Win98 and Poser 4. None of my other modern apps have it, they ALL have a fully expandable and configurable popup window. If I have 250 PZ3's in a folder and a TINY window to search in, it takes a long time and is a hassle. And it behaves very strangely too, the mouse pointer goes nuts nad changes behavior as I drag and search. This looks like some basic programming to me to fix it, really basic. But nice with the enhancements and fixes fixed so far. :] Fish

Would have liked to see some work done in the hair room instead of the face room, but then someone else may feel otherwise. How much testing has been done???

Thanks for fixing the faceroom. This is most welcome, Thanks. Can I use it on Posette now? Tony

well I am happy that SR3 is on its way but a little peeved to say the least about nothing of consequence really being fixed. the "File not found" dialog problem is an ongoing frikkin' nightmare that would be rather easy to fix if the developers would just look at it for more than 2 seconds. the damned ~4MB leak is rediculous. There is NO WAY that can be thought of as acceptable. I mean c'mon 2GB od memory should be WAAAAAAAAAAY more than I would need, but to render anything decent at 3200x2400 @300 DPI I typically see poser's memory usage at 1.3 GB +, so don't try to tell me it's a problem when I render something (no matter the size) and watch about 4 MB disappear each time. the fact that poser is not smart enough to UNLOAD unused textures from memory is just plain dumb. This ties into my last note about the memory leak. Screw poser loading 10 seconds faster, I would rather be able to create one damned thing in it without it crashing like a mofo. Luckily, I am a "save" nazi now because of Poser ... but hey whatever I guess.... the fact that the dials, as where pointed out, are much like a roullette wheel ... unacceptable when considering it used to work fine, and is now broken. and these are a few of my gripes. I wish they would stop fixing the stupid shit and get to fixing the CORE. As a programmer myself I cannot fathom why the hell some of the most basic things are still non-functional. If my company had written something like this .. I would imagine we would lose quite a few clients due to lack of quality. I understand it was a "We have to get this out the door" kinda thing, but really if you would suffered for your product a little longer in order to do it right ... you would have made boatloads more revenue from the release instead of what happened. If Curious Labs needs programming help I am willing to do so. Anything to make it better because as it is it is almost unusable for me. I am proficient in C/C++, Java, VB, you name it =) end rant ...This rant was brought to you by the number 6 and the letter J --fretty

P.S. thanks for the update tho :-)

Any fixes to P5 are appreciated and I certainly don't want to diminish what's been done. It could be that CL has discovered that there were just too many issues to try and deal with them all. Fix some now and do the rest later. They are probably right about that. I guess if I had my druthers, I would have prefered to see them focus on some of the most basic and troublesome issues first....things that affect the basic operation of the program (like the memory issues and "cannot find texture x" issues). The memory thing is huge. It's very difficult to create high resolution images involving multiple characters. Even on a fairly competant computer I still get the "virtual memory" message when trying to render images with multiple characters, large textures, etc., even though I can render these types of images effortlessly in Vue. The only thing that saves me is that I use XP and it will make adjustments for the memory problem. The "file not found" is also huge. I echo what someone else said that you have to save constantly and before making any changes in the event Poser can't find some file that's referenced, ignores your command to "ignore" or "cancel", freaks out and locks up. The speed issue is helpful, especially the character loading....but only if it applies to all characters, textures, etc, regardless of room. The biggest speed problem is encountered when you have very large runtimes or are working across multiple runtimes. Hopefully some of the python fixes will resolve the lockup when using non-poser light sets? At present, I use the clear lights python utility and "start-over" each time I add a new light set, to avoid the "lock-up" problem I was experiencing. It would be nice if this were "built in" so that old lights were cleared automatically when a new set of lights was added. The adjustment for moved .obj files is a good fix, as is the background image fix in the material room. That one not only caused crashes, but wiped out an entire .pzz of mine once! I don't use the face room much at all, or the walk designer or any other animation features, so these will not affect much of what I do. But I suspect those who have been frustrated with these areas will be grateful. I share the concern about "caching system files". Sounds like "an accident waiting to happen", especially on the Win 9x OS's. Won't this make the memory issues worse? I'm not a computer whiz, but it would seem that if files are cached in anticipation of a subsequent loading of the program, you are retaining it in memory. I could be wrong. I plan to wait for those braver than me to install this fix and give some feedback on any "dominoe effects" that might occur.

"...any update is a good update...so I'll take what I can get, take what I can get. When I look into my monitor and it still renders...yeah, I'll take what I can get. Katherine... take what I can get." Katherine, will this be the last SR release, or will CL continue on the other problems noted above? Thanks for the info though! Nice to be informed.

Thank you, Curious Labs, for the upcoming service pack. Could one of the next future packs help with the problem of Poser 5 accessing V3 Injections from the Poser 4 Runtime folder? I saw the posted message about installing the injections to the Poser 5 Runtime folder instead, but I like being able to access multiple Runtimes. I currently can't (just for V3 injections, though) since it kills my Poser5. I'm not trying to bash Curious Labs. I'm really happy they are trying to fix the problems and appreciate all their work. I understand that it takes time and patience. There's no way they can wave a magic wand and fix everything all at once. But I hope they eventually work on this one problem too, as I love my Poser.

While we're all talking about bugs we'd like fixed, I'd like to see the display origin for props fixed. Currently the origin displays, but the dials to re-position the origin don't, which means I have to go back to P4 if I want to change the origin of a prop.

I'm hoping the 4MB memory leak will be fixed too, and there seems to be a 300K leak when Python scripts are launched/terminated as well :-( There's no way they can wave a magic wand and fix everything all at once. Unless they really want to avoid spending another 3 months on SR4. If this is going to be the last projected SR, then please take as much time as is needed to address the issues. Seriously, I wouldn't mind (and I suspect I talk for many others) waiting another month, if the alternative is never. Oh yeah, and it would be nice to see cross-talk/conforming-morphing clothing finally connecting in the manner intended. Bill

Ajax - I think you can get those dials to pop up if you bring up the joint parameter box while you have display origins on. Its a bit of voodoo like bring up the joint box, click off the prop then click back on and origin dials show up.

Thank you! It is better to concentrate on fixing each area than try to cover it all. No matter what you fix, or how hard it was to isolate the problem, somebody will complain that their pet peeve wasn't addressed. It took 9 patches before Poser 4 got to its last configuration (and it is not perfect), so I'm patient. With the limited crew left at CL, some of us are glad that the software wasn't simply adandoned, others are glad that it is still being improved and pounded into shape. The "file not found" error seems to cause enough irritation across the board, as well as generating too many crashes, that working on the internal searching routines probably should be a focus of the next release. Meanwhile, fixing the face room to allow for better and bigger textures should help artists get more lifelike models. Getting more scripts to adjust light and shadows and atmospheric affects should yield better renders. (I don't mind if the image takes longer to render, I just want it to look like what I imagine without doing so many renders.) So... hooray and a big {HUG}! (would you like brownies with that?) If there is anything we can do to encourage you folks to continue working on it and to get the Mac version released? Carolly

Hi all, I apologize that I won't be able to address all inquiries over the additions people would like to see. But pdxjims asked a good question on what - if any future service releases are planned. We have a Japanese version due out and of course the Macintosh release. Both releases will also address parts of the product to be improved within reason, so I persionally feel that you can expect a additional SR release in the future. But I won't make that statement on behalf of Curious Labs until we get through the development of the next few months in order to know more on what form the next release will be delivered in. It's likely that there will be a addition or two to the final SR3 release that were not listed in my original post as an FYI. Kind regards, Katherine

Nobody has mentioned the rendering quiting in mid action bug???!!!!

a ibrid version for both on OS9 or OSX ... ? a 2d tracking marker option for motion capture..? a internal lipsinc advice...? a good batch renders ... ? a real and speed HDRI option.... ? a speed global illumination option ...? a number poligon preview setup...? "good for preview in realtime and better of group of CUBES ;-)" ......hmm

Just curious.....why would you want to release a MAC and Japanese version on the poor MAC people or for that matter, on the poor Japanese people, without first working out all the quirks, bugs, shortcomings, whatever?

So, fixing memory leaks is considered an addition??? I think it is a necessity.

To answer sandoppe: $ ? sandoppe, don't get me wrong, there's nothing wrong with your logic at all, except perhaps... the logic of raising this with the very same vendor who shipped Poser version 5.0 in the first place! ;-) And before someone jumps down my broadband connection, I know this is reportedly a different crew at CL, and these fixes may very well be very well tested, and tested in private at CL's expense as they should be. But in terms of what the fixes are (e.g. includes enhancements to the detriment of fundemental bug fixes), it sure looks like dvu all over again. The more things change, the more they stay the same.

That does appear to be the case. You know as I thought about it, I guess the bottom line is "the bottom line"! I suppose it's difficult for them to go much further without putting something else in the market place. I guess that's where the Mac and Japanese release come into the picture. They are really between a rock and a hard place....a position that is not at all the fault of this new team....maybe not even the old team. Just plain "bad luck"! and biting off more than they could chew with the design of this program.

"The file not found" problem is not a Poser problem, it is a problem caused by the artists who put together stuff with incorrect texture references. Why not tell these artists to fix their stuff!? Or you can fix everything yourself, using CorrectReference. Of course, you will spend many hours working on the project.

Whoa, I just posted about going back to Poser 4...sounds like it was a good decision on my part. I would have to kill the program when it hung up on loading, 2 or 3 times. Each time it would get a bit further. After using it once, it would start up nicely most subsequent times so I imagine cacheing is already there. K said there might be a further sr after 3? Well, that's nice considering most of the issues everyone mentioned aren't addressed in the proposed 3. I agree with someone elses comment about why do mac and japanese versions while there are still bugs? Ach, what happened to quality workmanship in this country? Make alternate versions with same bugs to just make more money? Shame! Ah well, not my problem, I am out the bucks for 5 but I can use 4....

Good news, glad to see some work on the face room and some color matching...BUT...do we still have to deal with that portion of the neck that won't take texture from either the faceroom or the body texture?

That's not the answer. Whether the file is incorrectly referenced in the pz2, pz3, cr2 or whatever, isn't the point. There is no excuse/reason/mandate of God that could excuse the sloppy code writing that allows a misrosecond response from the operating system and five lines of code to handle to take ten minutes and lock up the system in the process. THIS FILE LOOKUP PROBLEM MUST BE FIXED. For COBOL's sake, just delete the damn file search routine entirely and stop at "File Not Found", dump to a dialog and ask what to do,... then frikkin' do it!! Its amazing to me that I can click "Stop looking for files" and it still takes ten minutes to understand the response,.. incompetent code writing,... evil, pure and simple, from the eighth dimension!!

I'm not saying a thing... by the way, how long does that NDA stay in effect? or did all that paperwork go out the door with the old crew ?

Thank you, Katherine, for the quick response. Pay attention people, it ain't quite over yet, but close. SR3 will probably have a couple of extras added, we just have to wait and see. After that, no major service releases planned (or so I read) other than things that can be done as part of language or platform conversion. In other words, if it ain't in SR3, don't expect it.

I have to agree with TalonGE. I'm not a programmer, but my word if something can't be found and you say cancel or stop or whatever, that should be the end of it! It certainly works that way in Vue and Bryce! I also just re-read Katherine's post: "I apologize that I won't be able to address all inquiries over the additions people would like to see...." "Additions"???? "Fixes" would be a better term I think. It seems like no one listens. They just go ahead do what they want regardless of the problems that people have addressed over and over again. How old are these people? I'll bet there's no one over 50 on this crew! Maybe the combination of programming folks, marketing folks and arts folks just makes for a "big mess". I've seen this sort of thing happen at my work when you mix programmers with service delivery people to design a management information system. You end up with a lot of "bells and whistles" that don't work worth a damn :)

.....I really don't have a clue....what is it??

Thanks :)

Katherine thanks for taking the time to update us and keep poser 5 users in the loop. Hard sometimes being the messenger, but I think most appricate the hard work that you do, again thank you.

So, we're gonna get a buggy Mac version?!? Is that what she said? Somebody tell me she's kidding. Somebody... anybody... helloooo...

Only if you choose to "buy a copy" Elfwine! :) The more I read her second message, the more it sounds like "double speak" or, as it's called in my field, "bureau-crap" :)

Good to see that we will get some fixes. Thank you CL. What about the development of plugins like for LW, Max or Cinema? Any news about that? Chris

Fix the hair please that is one of the reasons I bought Poser 5, and I see NO mention of fixing it. How can you still advertise this product with these bugs still there? Isn't that fraud? Film at 11, Marque

there is word on som MAC site that DAZ will have Studio out this summer..at least the first step... maybe all isn't lost yet :) Hopefully CL is actually working on the REAL problems....maybe this will be in Version 6....which better be a FREE upgrade to all us 5 people that got the big hefty one inserted.

There's no LW or Vue plug-in yet (like there was for Pro Pack), but loading a character takes 15 seconds less. Hmm... The "file not found [please wait 10 minutes as I search in vain for the texture]" bug (that's been around since Poser 4.0 and wasn't corrected in 4.03, Pro Pack, 5.0, 5.01, 5.1, 5.2, or SR2) isn't fixed, but we can enter a comma into numeric fields. Hmm... While any fix is appreciated, where is CL getting their to-do list? Has anyone requested faster loading time? (Not that I've read.) Has anyone requested fixing the "file not found" bug? At least 5 times, in this thread alone. Has anyone requested a fix for loading images larger than 4096 pixels? (Maybe, but I haven't seen any in these forums.) Has anyone asked for plug-ins for Lightwave and Vue? Ever since Poser 5 came out! Maybe CL should fix the features that the customers WANT and USE rather than what's on their corporate "would be nice to fix" list.

Y'know.... It might be wiser to actually -see- what SR-3 does before chewing the walls again. Until we have it and have it installed, we don't know =WHAT= may be fixed. Those resolved 'playback' issues for the hair room could very well -be- the collision problem. Half of that list could very well have been the source of one or more memory leaks, and now they are fixed, no more leak. Some of those 'little' problems working in concert could have been the cause of what appeared to be a major FUBAR (HOW many issues that were attributed to 'rotten, incompetent coding' went away when the InterLok protection was decoupled? Remember?). And the last code monkey I knew who professed to being able to 'fix a problem' with a few lines gave up at around 700 lines and embarassed himself horribly. It wasn't his source, he'd never met the original coder, and got bitten by the different work style and code structure. Thank you for the info, Katherine. It is -very- much appreciated. ;)

Hi,

I have to step in here. There's too much speculation being generated in this thread when SR3 has not had a chance to release or be used. Ive explained that my list of items within SR3 exclude a couple of items. I understand the anxiousness (as Casamerica notes of 8 months from the original release though a couple months after SR2.1) but please let me correct some assumptions.

#1, the Japanese and Macintosh release will have the development work WITHIN these release(s). Our partner in Japan has a staff of engineers that work closely with our team to double up on development work needed for localization as one example. A comment above makes it sound as though J and Mac will release without further development. I thought what I wrote was clear, but I think maybe too vague. Any further type of service release of Poser 5 PC will INCLUDE the fixes that both the J and Mac installers will have (again from the development in affect now).

What I wrote to address future service releases after SR3..... I gave you my personal view that there will likely be more service releases ahead. I hope Ive been able to maintain not making company statements until I felt it was factual which I will continue to do. The absence of making the statement for future service release on behalf of CL does not mean that it's due to the absence of thought within the company. In other words.. the release of the SR3 will not mean that the development work for Poser will stop.

We appreciate your feedback but I please ask that you let us get SR3 out, and allow yourselves the time to have the chance to use this release to see improvements many want and need. The issue's reported in majority will continue within development of Poser if you find they are still present after using SR3.

With kind regards,
Katherine

I forgot to add that the ProPack offered the plug in functionality for Poser into other product such as Vue, LightWave or Maya rather than it having been a functionality within the Poser product. The development for plug in support is also in process and you will see status and statements for these separate from any Poser-SR release. Kind regards, Katherine

a ibrid version for both on OS9 or OSX ... ? a 2d tracking marker option for motion capture..? a internal lipsinc advice...? a good batch renders ... ? a real and speed HDRI option.... ? a speed global illumination option ...? a number poligon preview setup...? "good for preview in realtime and better of group of CUBES ;-)" ......hmm

Andy, if I can spend the bucks to upgrade a wheezing circa-1995 7500 to OS X, you can too. There is no plausible advantage to developing for 9 and the user base is shrinking. The user base of legacy Macs that cannot be upgraded to X is even smaller, and I doubt much of them are using 3D software intensively. Let's leave this issue behind and not hamstring CL's development cycle. If you're having trouble upgrading your Mac let me know and I'll offer some advice on solutions.

My question would be if the mac types are just getting a straight port of the PC code, or if they're actually getting a re-write. I think it's the former, but I'd love to be wrong... later jb

praxis: Neither. From what Katherine has said, the Mac version will be a further development of the existing code. As such it would seem likely that the Mac product might actually feed some additional bug fixes back to the PC code-base. Ditto, potentially at least, for the Japanese version. Katherine: Many thanks for the update. Apologies for the attitude of some of our members but, hey, we DID pay for this program along time ago. I for one am delighted that the face room texture limitation is to be addressed in this service release, even if I am distinctly saddened by the apparent shortness of the fix-list (the bug-list of new problems with Poser 5 - over Poser 4 - was somewhat longer IIRC). But most of all, thanks and good on yer :) Cliff Bowman