CL recently sent out a $50 off coupon if $100+ is purchased offer to (some?) existing customers. Interestingly the coupon does not expire until June 30, 05. So does that indicate that P6 will be out (just) before 6/30, or not before??? Personally I'm not up for an early purchase from CL ever again, either way ;-)

randym77, IM'ing you, as if I respond here I run the risk of demoting this thread to Product Showcase, which would really hijack it ;-)

randym77, Yes, QM will do all MATs, including P5 (as long as you have P5 of course :-) There is 1 caveat, to quote Howard from his website: "There is, unfortunately, one extra thing to remember when making MAT poses with Poser 5 material nodes with QuickMAT... If you have some Poser 4 content in your scene (you usually will have!) then the nodes themselves don't actually exist unless you've looked at them in the material room once. If they don't exist, they're not exported to QuickMAT and they don't end up in the resulting MAT file. So to ensure the materials you want have P5 nodes, just look at each material in the material room before firing off the MAT save through QuickMAT."

Vendors, as well as others, should consider QuickMAT from Hogsoft. It makes MAT's for you directly from within Poser so the references are taken from a Poser-created file. It will also capture an image (even a rendered image), and builds both the .rsr and the .png - and all "on the fly." Even if not using QM, then simplying running CorrectReference Pro before zipping the product, would find and fix any malformed references... Many of Hogsoft's products are designed as much for vendors' use as for end-users. [ Full disclosure: I'm a beta tester for Howard of Hogsoft, and originator of a few of the conceptual ideas implemented by Howard in CRPro and QM/Hub. ]

support@hogsoft.com

All Windows 32-bit operating systems applications are limited to 2GB. The 32-bit addressing will handle only 4GB, and 50% is assigned to the OS side of the application, and 50% to the part of the application the user sees. So 2GB is it. CL are clean on this one. CL's sins are a) using .6GB of "other Stuff", and b) getting so little value out of 1.4GB left. 2GB oughta be enough for any Poser scene really... But as Poser 2 or (whichever came to Windoze first) through 5 still seem to use the same memory model as they did in the original version (Windows 95 or was it 3.1?), and still loads everything into memory whether you want or use it or not... So only solution besides a simpler scene, is Poser 4 as it has less to load, both code and options. It seems to me that it should be trivial for CL to not load some features, but it cannot be, or they surely would have done so by now. (As well as fix some very basic Windows file dialog issues, lost textures bugs, etc.) But as they have avoided all such efforts for all versions and SRs for Poser 4, Poser Pro Pack and Poser 5, one might have to assume that they are unable to access that part of the code source for some reason or other...

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=1438921

The only fix at the moment requires significant editing - simple edits, but many, many files to edit. The details are at the link provided.

However, I have reasons to believe that one of the future Hogsoft utility products, building on this new technology that Howard's mentioned (and some of which is still being finished ;-), could be an FII utility! However I know that there are a couple of other exciting things ahead of it. Crosstalk being one of them.

And with corresponding enhancements to PBooost to let you switch between normal and FII injection as you need/want, FII could be just as easy to use as the current injection method.

Bobbie, We need to be careful with the term "crosstalk", it's been used in Poser to cover more than 1 thing. The crosstalk that Hogsoft Crosstalk addresses follows Jim Burton & FyreSpiryt's latest discovery and addresses the "classic crosstalk" that we all know and hate. The similar symptoms in Daz Generation 3 figures and any other figures that use readscript injection, is actually a different phenomenon, with a different root cause, and although the symptoms are similar in effect, the method of avoidance is very different. The fix to readscript injection was discovered by Maveris, for which I coined the term Figure Independent Injection or FII, and is quite a bit more complex than the classic crosstalk fix Howard is currently beta testing.

maclean, Go check hogsoft.com forum again, Howard thinks he has addressed your problem by generalising the solution to all dials. Also re your question on readscript loading mutliple figures, I suspect that readscript does not support figure numbers at all! It is such an old function, intended only for initial load of a single figure into an empty scene. Thus there would have been no reason to update it to be compatible with the multi-figure capabilities which were added in a later release. If this is true, then readscript would always load figures into the "Figure 1" slot, whether or not it's full/empty, because it's the only slot it knows off. (This behavior - being blind to figure numbers - is also the only rational explanation I could come up with as to why the V3/M3 injection issues could possibly work when the FII fix was applied: readscript was fooled into using old legacy code which didn't have the Figure # - and thus the Figure # bug - in it.)

Attached Link: http://www.renderosity.com/messages.ez?Form.ShowMessage=1438921

You say SR4. If you really mean SR4 rather than SR4.1 then you need to upgrade. SR4 was meant to speed up P5 over SR3, but for some of us (not sure of the common cause, but suspect the early release CD for P5 as it had some differences in the XML fles) SR4 was slower than SR3 and even SR2. But for me SR4.1 speeded up P5 way beyond anything in any earlier release - still slower than P4 or even ProPack, but at least usable (with CP removed of course). I don't use sub-folders, so can't confirm that aspect.

For reviewing your uninstalled zips, P3dO will browser .zip folders, it dislays an image available in the first item in the zip as the icon. In the event that the first item isn't a graphic, you can click on the zip item in P3dO and it will expand the zip file, displaying icons for all items within the zip. Granted that's not the best solution that you could possibly think of, but it requires zero effort on your part, just open P3dO and point it at your folder of uninstalled zip files. No preparation needed. That was a good enough compromise for me ;-)

Bobbie, You have a valid point - but I never store anything where the creator tells me anyway ;-) I store items including textures by category - usually the base figure - therefore every one of the references are wrong for me!

Bobbie, it's not me to defend Windows, but the "issue with PBooost" is actually a Poser bug. The symptoms are as you describe, but the root cause is Poser. When Poser can't find a texture, it opens every folder under Runtime in a wild search for the texture. And it leaves every one of those folders open - never closes a one! Windows 9x couldn't care less about open folders, but Windows 2K/XP keeps track of such things, and won't let anyone else access them until the requesting application - in this case Poser - closes them. Which it nevers does. So PBooost can't get to them, because Windows has them locked (to Poser) as you say. Only known solution to date is - as you indicate - to run CRPro to correct the links thus ensuring that Poser doesn't have to run its buggy shotgun approach to finding a missing texture. And a by-product is much faster loading of figures/props/etc too. I'm sure that Howard would be more than happy to receive a freebie Mac, aalthough there would be a lot more involved to port Hogsoft utils to MacOS or OSX. And you are most definitely right about Howard being pretty busy at the moment. But hang in there, there are some amazing new technologies coming...

The copy protection can cause these sorts of problems, although it doesn't for everyone. As Stewer says it was removed in SR4.1 (in fact any SR > 2.1). But you can still install the copy protection "inadvertently" if you start Poser 5 - particularly an old copy of P5 - BEFORE you apply the SR. The copy protection scheme is executed when you first start P5, so apply SR4.1 first after installing P5, then start Poser 5, and all should be well. If you have already got Interlok code running on your system, then you'll need to scan the Web for instructions on how to remove. (There were some here on Renderosity, but Pace have removed some of the tools used in that method used.)