Something that seems to be overlooked with D|S, which dissipated my enthusiasm for the product early on. It's a closed system.

IMHO the real success in Poser wasn't anything to do with the app per se, but that it used OBJ format and rational (well mostly rational ;-) extensions. I.e. all in TEXT format.

Poser is what it is today because of USERS, users who dug into, understood and EXTENDED Poser to way more than MetaCreations ever anticipated. With the sad recent "We don't support MAT files (even though we ship them in P6)" exception, these new tricks have been adopted or tolerated by the creators of Poser (but maybe that's just a side-effect of Curious Labs aversion to fixing prior-release bugs? ;-)

NONE OF THIS WILL HAPPEN WITH D|S. The formats are binary, proprietary and encrypted. I raised this in early beta in D|S forum, and to RobW, all said not a problem, will be workarounds, people will figure it out, etc., etc. BS! Does anyone really believe that the encoding process is there for any reason but data protection? (Officially it's for speed of loading! - On what, a 486?) Does anyone really believe DAZ wouldn't seek protection under the DMCA? Truly ironic when you consider that the single largest beneficiary of the current open Poser formats, extending them and building products based on that EULA-forbidden reverse engineering, is ... you guessed it, DAZ!!!

BTW EULA text highlighted byAnton is fairly common language for Software Applications, but I've not seen it used on a free app, nor have I seen it used to cover content. But there is one BIG difference here, it's usually written to be the other way around!!! I guess DAZ doesn't want eFrontier to do to them what they did to Curious Labs???

D|S will be a professional app, an adjunct to expensive apps like Lightwave, no doubt. But it'll never be a Poser replacement as we currently know and understand Poser.

DON'T!

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

Remember that most monitor default settings (until you get up into the upper $ pro bracket ones) are pre-set to look good in a very highly lit showroom floor. If you operate under that much fluorescent (or mercury vapour - ugh) light then the settings might be right for you :-) Ditto the colour temperature - 9500K is desert sun equivalent. But note if you set your monitor to a reasonable 6500K (lowest settings of 5000K equates to tungsten light bulbs), then anything done at 9500K is going to look "dark." Then there is gamma (even tougher subject), but be aware than Mac runs at different default gamma than PC, so anything created on Mac is going to look "darker" on a PC monitor (assuming both still at default settings). Finally the brighter the CRT the quicker the phosphors burn out - although these days something else may well fail before the phosphors get too dark t use the monitor. But 3 years is not unknown for a heavily used monitor set to max bright. The above is true for CRT type TVs too. There have been many postings about this aspect in the past.

Hogsoft's QuickMAT builds the mat file and the .png/.rsr (from true renders) from within Poser. It has an option which lets you pick from a heirarchy menu exactly which actors are to be included for each mat. And it's very, very quick.

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

"It's stated in the readme, that P6 handles paths more consistent..." ... but consistent with what? Certainly not earlier versions of Poser!?! Fortunately Correct Reference can undo the damage done. (P.S. New version will build the distribution zip files for you too... )

PXP: Control Panel > Mouse > Motion pane/tab under Cursor Speed and Acceleration. Maclean: I'd agree with you, but as I have their trackball (same drivers) to reduce wrist ache, I do need a few of their parameters. But I agree their installers are pretty pathetic - unloading unwanted "give-aways" is bad enough, but being expected to hand edit the .ini files after install for the trackball is beyond the pale!

Ah, had EXACTLY this problem with P6 - and with some versions of P3DO too.

If you have a Logitech mouse driver, get the latest version, and then on the Motion pane UNcheck the new option "Disable acceleration in games." Apparently this feature - to add acceleration to games - was added several driver versions ago and caused slow downs in 3D apps using OpenGL. It wasn't until the latest version of the driver that they provide an option to revert to the older (pre '03) functionality.

Once I'd upgraded and unchecked, everything was fine in all applications - except my mouse was a little faster everywhere - so I had to reduce it from flat out where it had been forever to about 66%!

whbos "#6 ...When placing figures inside of props, a way to keep the prop from totally obscuring everything that is placed within it... " - Use the camera's Hither dial - clumsy to adjust precisely, but it works. To problems needing fixing, most have been covered, but some of the P5 and earlier ones have not: - Update the delete confirmation dialog to list the actual item which is to be deleted. - Fix the focus problem by elimination - multiple independent windows in an application work on MacOS and OSX, but do not on Windows (where it incurs the Windozes overhead of task switching), so don't use it. No amount of tweaking will cover up the fact that P5/P6 are slower and less responsive in terms of parameter dial adjustment than P4. And good parameter dial adjustment is central to Poser. - Update the whole Mac-to-Windows cross-compile interface code so that it uses current Windows APIs not the venerable out-dated no-longer-supported legacy ones. - Either fix the memory usage (more efficient data structures, load lesser-used segments - e.g. face room - only when needed, etc.) and/or implement a proper memory manager, a la Adobe, etc. Either way, stop Poser mindlessly going over the 2GB limit. - Actually do what the past and current CEO's have promised with P5 and then, amidst apologies for the P5 debacle, again with P6: and actually FIX THE BUGS FROM PREVIOUS RELEASES! Sorry, but fixing just 1 doesn't count as mission accomplished, it needs to be the majority, or something close to it.

Should I post the tutorial here or start a new thread. Either, we'll adapt ;-) We're just pleased that someone has figured this out, and is prepared to put in the effort to share their results. Thanks!

laying back - simple. Comes from a now-defunct email addy. Was enjoying early retirement (from choice), and got cable broadband service from @Home about the same time, ergo layingback@home.com. Alas all good things must come to an end ;-)

Ah, but it's an old bug. And CL/EF has a policy about not fixing existing bugs ;-) During the P5 "public beta" we actually got Larry W to personally fix one of these - in the Morph Load file dialog - by keeping the dialog open for the next load (more of a workaround than a fix admittedly). But such corporate policy transgressions cannot go unchecked, even when the CTO makes them, so this change had to be removed from P6!

Remember Poser's origins folks. Think early MacOS conventions, not Windows, then it will make sense - or at least becomes explainable.

If you always use your own figure numbers (beware a very few figures are set for FII without numbers), and you use them consecutively (no gaps), and you never delete anything other than the last figure loaded (again no gaps), and your clothing is similarly well behaved and you loaded them as you added the figures, then yes, I would think you are right. But 1 little hiccup, and only the prior installation of Nulls would have saved you. I maybe wrong, but my limited testing of the impact of Nulls was that they cost very little beyond the bump in Figure numbers, and the few seconds it takes to load them, so they always seemed like cheap insurance...