Attached Link: http://www.hogsoft.com

I think you meant Ajax

Les, Having researched it, Migal's discovery was similar, close, but no cigar. His was related to making MATs work on a prop by changing the type to actor. Same means, different ends. Here's his post from PoserPros: PostPosted: Fri Mar 05, 2004 4:18 am Post subject: Add User to Ignore List Reply with quote Just as an aside... You can do MATS for unparented props, if you first refer to the prop as an actor in the pz2, like this: actor Sphere_1 { }

I was rasing the non-ERC aspect 'cos it does generally cause confusion. I was not trying to confuse, nor underestimate the amount of research that you've done. > But it shows the basic problem -- load order is paramount. On this we agree! > I am told P5 does not replicate the latter behavior. ["bad" crosstalk between similar figures] Agreed. > I am told, however, that P5 does replicate the former behavior. ["good" cloth to figure crosstalk] This sounds very suspicious to me. Only for simple clothing, it does not work, leastways for me, for clothing using ERC ("super-conforming" clothing). But I do agree that if it did work for ERC clothing it would be strange ;-)

nomuse, Is it possible your "confusion" is because there is more than 1 form of "crosstalk" - or at least more than 1 set of symptoms? (Although I believe that there is at least 2 separate code issues at play). Crosstalk of the "classic" variety was defined by CL as a "bug" and fixed in P5. But Mil3 figures with their readscript based injection suffer exactly the same symptoms at the UI in their FBMs as the "classic" crosstalk. But in this case it is caused by the readscript process. This variety of crosstalk is still present in P5 & 6. The only way to "fix" it that I know of is the FII (Figure Independent Injection) changes to the readscript Delta files. FII support is now available as a plug-in to PBooost, but Stephanie Max is developed with FII built-in, if you want to experiment. SMax was developed by Migal, and is/was a free download from Netherwork's site, but requires Daz Stephanie (1). But there is always JCM Calf Injection morph for V3 from Migal's new site, which was the proof-of-concept for FII. (Migal by the way first noted the "propter" prop-named-as-actor trick at PoserPros as an aside to the FII discourse threads, as he developed it for SMax.) Further potential user confusion follows from application of FII in P4/PP which triggers the "classic" crosstalk on the reload following a save in P4/PP - unless Nulls are employed at creation time. But note that opening such a saved file in P5/6 will work, no "classic" crosstalk present. Ergo "classic" crosstalk and readscript induced crosstalk are different at the code level. (I suspect the readscript variant is due to readscript development predating the multi-figure/multi-figure number implementation in Poser - and just got missed in the update, intentionally or accidentally, because when used as designed readscript never needed to worry about figure numbers at all as by design it only ever loaded a figure into a virgin scene.)

The Hub lets you run all Hogsoft programs from one small "stub" program, which remains loaded all the time. (This is one reason why PBII loads/unloads as usual, unlike PB v1.) It makes it much easier to run things like QuickMat. And with PBII you can switch banks directlyt from the Hub. (Also it is part of the P4PyE Python alternate, that supports plain old P4.)

Attached Link: http://www.hogsoft.com

I think you need to apply the Service Releases (patches) from eFrontier. The 3rd/last one fixes this problem, and avoids the need to force a screen refresh to display the newly injected morph. eF/CL rarely (never?) installs patches in manufacturing, nor seems to give any clue to new customers that they almost have to update in order for it to work!

Have you tried putting Null figures between each base figure (not the clothes) while you create it? This usually forces Poser to go through the same steps during the reload. It seems as if the Null breaks the "chain" of figures, and forces Poser to treat each figure almost independently.

ernyoka1, Skip the details, for now, on what it does and why ;-) Put it this way, when you first bought V3 and encountered the Injection system, you probably assumed that everything else would work as before. Only later did you discover/hear that only the first figure loaded could accept injections. Try injecting any subsequent figure in the scene, and you got crosstalk-like symptoms. Generate the FII bank, switch to it, and then Mil3 Injection figures will work like you originally expected them to. Simple as that!

noggin, Try it and see? ;-)

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12413&Form.ShowMessage=2583804

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12356&Form.ShowMessage=1431670

No longer do you need to either pre-process a Mil3 figure and save it for later use, or worse, use massively bloated Mill3 figures with every morph included, just in case. Instead use every Mil3 figure the way it was intended: inject just the morphs you need when you need, regardless of how many figures you currently have in your scene, even if there are several figures of the same character.

FII works by removing all Figure numbers from the injection poses. This means 2 things: you need to remember to select a figure before attempting to inject a morph into it, which is no real hardship; and crosstalk will no longer work. If you need crosstalk for cloth conforming, in this or any other situation, then simply use Hogsoft's (free) Crosstalker available from his website www.hogsoft.com which will enable crosstalk in a controlled manner - yes, even for Poser 5 & 6.

Attached Link: http://www.renderosity.com/messages.ez?ForumID=12413&Form.ShowMessage=2583804

ynsaen, "available to anyone who wants to use it" - e.g. spammers and other "do-gooders?" :-O Will be interesting to see if anyone EVER completes one of your surveys again. You promised anonymity, and yet included IP addresses, plus personal information. There was an implied contract of trust from participants, no? Also the US does not have a Safe Habour agreement with the UK or Europe. So all entries with UK/Euro IP addresses contravene their Data Privacy Act. Can't remember the penalties off hand... IMHO you should withdraw this database from R'osity ASAP - if only to protect Renderosity from TPTB.