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