It will affect the character some, but you can reduce this effect by using the ShldrSml morph (under Muscularity) to slim down the shoulder. If you think this is bad, take a look at M3 shoulders...

Capsces, No problem. Also Insomniawork's implementation of the actual injection files looks a lot easier to replicate for a simple project, without all the indirectionm files and hidden folders of the method employed on V3.

See Insomniawork's recent posting here on MayaDoll and also in Poser Tech. You may or may not be keen on the actual morphs he's applying - you've been warned ;-) but he's just recently solved exactly the issue you have - how to add empty channels for injection without having to touch the original.

Sounds like the ERC morphs aren't working. Are you sure that V3 was the FIRST character loaded into the scene since you started that scene? If not, then the ERC/FBM morphs will not have been injected correctly. Deleting earlier loaded characters won't fix it either. Either start with V3 as first figure, or, implement Figure Independent Injection (see post in Poser Tech).

_A/_D, I knew of the poser syntax script, but didn't reference it here, as I thought _D's site was still down. Not aware that it was on vim site. Thanks. BTW, is there a way to mod my script easily to work on the current directory? As IPB builds non-FII pz2 files, the script will need to be used more frequently, and editing teh script first is a pain. It's a shame that gvim doesn't have the directory selections on the gui as BBE does; I realize that on a real OS it wouldn't be an absolute need, but it could still be handy.

Yes, Ockham developed a python equivalent to DialCleaner, and a second one that hid dials set at Zero. However it doesn't look as if it actually removed the morph's deltas, if that was what you were looking for. You'll need to attract Ockam's attention if you want to explore a more complete solution.

No need to worry about the extra RAM until/unless you hear Poser transfering data out to the hard drive's paging file. It all depends on scene complexity, e.g. Jim Burton's CPU Perfoance test exercise (there is a thread about it some time back) showed that for that scene 512MB was sufficent. If you have system instability with large page files and very, very large scenes, it may be because Poser is getting close to the hard 2GB memory limit (of any 32-bit app). In which case consider setting your page size such that 2GB can't be reached (e.g. for my 1GB real mem system I have Page size set to 960MB).

I think you'll find if you disable your network access entirely at the OS level, then Poser will not attempt to access the net, and your performance loss - whatever it is - related to multiple-copy testing will be restored. But remember to keep Zonealarm running to correctly analyse Poser's contributory role in this - as ZA is a pretty heavy resource hog. (However if all you do is unplug the cable, then of course, Poser will still see a network capability, and attempt to use it.) So I wasn't saying remove the network to reduce the OS resource component, but in order to fool Poser into thinking you have no network connection to check out. But like everything else in Poser, you have to try it to find out what really happens... Either way I was only offering a suggestion to possibly permit the poster to further progress into analysis of an area in which they seemed particularly interested. I'm not interested enough to do the actual analysis for them! I have no other ideas on how else you can persue. Even if OSX doesn't do this what will that tell you? The variation caused by 2 different Poser builds, OS's and even system designs, has to wash out all other findings.

If you want to get a measure of the wastage, use the trick that's used in video editing - disable the Network Interface to your Internet connection temporarily. Time a render before and after, and see if the savings are worth disabling NI every time. Watch for caching effects though. You'd really need to run Poser from a fresh reboot each time, and do exactly the same steps - as Windows and Poser cache everything they can to save load times.

Ah, to stop it... Only way is go grab a disassembler and start digging in the code to find the call. Very hard, esp. as this is a ported Mac app. Pro'ly falls under the d**n DMCA too, as it's to prevent potential infringement of the license.

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

Here ya go ...

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

Orio, Re rsr files, see my posting of last week - link above, Item #17. You should be able to search for more info on Resource Forks in MacOS related literature. The font you referenced is the standard Windoze system font (try right clicking it and Open in Win Explorer). Why it's there I have no idea - perhaps it dates from the days of early Windows versions, when this font wasn't always present - just guessing as I can't remeber when this font became the default one in Windows, possibly Win95. I'm also not sure what it's used for by Poser - that's a very basic font. Wait, is it the camera name displayed in upper left corner of the main scene window? As for the asi32_12.dll I have no idea - perhaps to connect a piece of MacOS code to Windows font handling API? As to the I/O dll's beging in the "wrong" place, that seems a small error compared to some issues in Poser - e.g. memory and fiel management. Hope thsi helps some.

Please read my prior post (#13) regards the issues with running those 2 morphs backwards - or try it for yourself. Unless a morph is designed to run backwards it will almost always have negative consequences, esp. if you need to go all the way to -1.000.

Caly, That's hardly the point I was trying to make. I was trying to compare the M3 model to real bodies. But yes, M3 shoulders if you place M3 right in front of M2 (fully zeroed pose, Front camera), are FRACTIONALLY larger - but M2's biceps are nearly DOUBLE the size of those on M3. (Indeed all other major muscle groups on M2 are larger to some degree.) It's the RELATIVE proportions (within M3 itself) that are off IMHO - shoulders & pecs to biceps & calves etc. And yes I realize that this is subjective, but I was trying to point out to Daz that while these proportions may be fine for some applications, they are not fine in ALL applications. And to date there are no options/morphs to adjust that ratio - other than by beefing up the rest of M3 muscle groups individually (a huge number of dials) to match the essentially fixed shoulders and pecs. But that still doesn't give you a slimmer guy. The NoPecs morph suggested earlier should produce an essentially 'flat' chest area, and the DeltoidsSmall morph should reduce the bulk of the shoulders, reduce the front-to-back depth of the deltoids, and move the center of radius of the shoulder out slightly for a sharper curvature to the shoulder looking from the front - representing exposure of the bone structure of the shoulder in the ascence of little covering muscle. Adding those 2 morphs would increase M3 flexibility at the slim end (whereas the "Freak" is clearly to address the massive end). BTW, both of these morphs are effectively available to V3, and thus to some extent to V3M, and so are presumably technically feasible in M3. Trying to put it another way: Let the range of muscle sizes for flesh-and-blood males spanning Emancipated to Muscle3 be represented by 1 at the low end, and 10 at the high end, then M3 Base has Deltoids at 5 and everything else set at about 4. Additionally individual morphs for Deltoids are available for a range of 6 thru 10, Pecs are available at about 3 thru 10, and all other major muscle groups are fully adjustable through the entire 1 thru 10 range. I'm past comparing M3 to M2 - or even V3 - having purchased M3 I'm looking for the model to COMPLEMENT M2 - not replicate it. An obvious use for M3 is slimmer bodies than M2, which would be fine, except I keep ending up with a Gray Davis with Arnold S' shoulders and pecs. That's not right! :-)

JaMaCoVe, I complete agree with your concern about the roundness and "massiveness" of M3 shoulders. It appears in the default pose, and all poses supplied by Daz with the M3 package in which the arms are down to the sides (which is not that complex a pose, and if Daz can't hide it...). Raising, lowering or twisting the collar has no noticeable effect. Trying to steer well clear to all references to morph origins, mesh design, and other "sensitive" issues, let me please put it this way along with a constructive solution or 2: For each of the Full Body morphs supplied by Daz - Base, Muscular 1/2/3, Skinny, Young and even Emancipated, the muscle development necessary to have shoulders like that is disproportionately large to the muscle development in the rest of the arm and the body. No one can have shoulders that look as if he single arm curl a weight heavier than he has biceps and leg muscles with which to lift the same weight off of the ground using both arms! This is particularly noticeable in the less-than-Base settings, eg, Skinny, where M3 has very little biceps - which is fine for Skinny - but still has massively developed shoulders, viewed from the front and the side, particularly in the upper arm area. Can Daz please consider a) toning this muscle down in the Base setting, and b) proportionally increasing/decreasing it 's size in the Muscular/Skinny type of morphs? Otherwise as it stands today, there is no way to have an M3 character without well-developed shoulder muscles - and simply faking it by posing will not change that. Applying the Deltoid at 1.000 does help with the shoulder size, however it introduces an unrealistic flatness to that area, as it only affects the center of the muscle when run backwards, so the front-rear curvature of the shoulder is lost. But perhaps a true DeltoidsSmall morph is an alternate solution to all this? A similar but smaller problem also exists with M3 pecs - M3 always has pec muscles all the way through Skinny and Young, even though all other muscles (bar the aforementioned shoulders) correctly atrophy away. This just doesn't happen in the real world, you have to develop other muscles before you can possibly develop pecs! Again perhaps a NoPecs morph is in order at this point in the development of M3? (The supplied Pectral morph wont run backwards without raising the sternum). Thanks.