I'll tell you all after it's released and out for a bit, how's that? Hey, gotta keep the occassional hand held close to my shirt B^)

shakes head I'm going to have to make a posable Eddie figure, aren't I?

Attached Link: http://www.dodger.org/friv

Oh, yeah, my UVMapping skills have by necessaity improved B^) B^P

BTW, my colo is screwing up so my site and email are down atthe moment,and so is xfx3d.com. In case anyone was wondering.

I had 'Tshirt' right before 'trouser' in the list -- I just didn't want to say 'shirt' because it might imply the projection would somehow deal with the collar ot the front of the shirt's opening, both of which would be beyong scope. sigh I wish my fucking Co-Location provider wasn't such a ghetto ISP, though, or I'd be actually able to USE the tools I put online at the moment (seems they just sort of 'vanish' every now and then from the Internet, and show back up hours later with the message on their phone system stating that they have 'no known service interruptions in the Portland area', as if denying it would make people say 'Oh, I guess it was just me').

Freedom of speech doesn't guarantee being listened to.

Grins Thankses. Though as the creator who did it last October, looks down sheepishly I think it could be better. I've come a long way since. Mike 3's Biker Jacket will be better! B^)

Theoretically (though I don't think anyone has done it), one could easily make a NULL MAT pose, wherein you'd load a Null loader, then apply a MAT pose to that NULL loader and load in a whole bunch of JPEG BUMs (or other BUMs, if you wanted). That would put all that stuff in your dropdown menu for selection and not clutter up a 'real' figure with material blocks that don't exist in the figure.

If all the M3 products come out all at once, please keep the sales/discounts a little longer It's not our say. DAZ sets prices (with our input) and length of sale duration for DAZ brokered products, as well as release dates (which in this case will all be coinciding with Mike 3 intentionally as long as we make deadline). DAZ doesn't work like it does here where we individually assign sales and prices to products.

I think that the rise of D|S will promote some healthy competition between the two developers Personally, I'm hoping that both can come to use a standadised plugin format and that one or both will release an SDK. For instance, some things I'd like to see, whether included in a package or as plugins: Perl support: You have Python there, but I don't program Python, and I'd like to be able to script things without needing to learn a second language. Postwork Displacement: It's theoretically possible to use the concept ot a bumpmap not only to change highlighting or displace the mesh, but to determine angles with which to 'smudge' the output in seperate, object-based layers automagically, to allow for a low density mesh to be given a high quality displacement effect based on a bumpmap. COnsider that in a standard postwork/painting program like Photoshop one can seperate out a layer and 'smudge' it or displace it based on a map, and it's only a flat bitmap at that point. Theoretically, postwork displacement maps could be full colour with value (brightness) indicating height/depth, and colour indicating direction. Displacement (postwork or true) masking. Being able to mask displacement based on another map so that two maps combined can be used. Omnidirectional lights. Nuff said. 'Shaped' lights. Basically omnis or directional lights that take a given shape, like flourescent light tubes. Alternately, the ability to make an object actually glow, rather than simple ambience, such that it illuminates other things. These would be the same concept approached from different angles. Radiosity (the concept, not the renderer) capability. A shader like the 'Illustrate!' shader for Max. Something that can do comic-book style and maybe even comic-book quality drawing.

Conceptually it wouldn't be all that hard, really, algorithm-wise. 1) always remove any polys not visible to an active camera (including shadow cams). No point in processing polys no one will ever see. 2) By interpolating the angle of vertices, remove any polys that would not come out at least 1px x 1px in the render and weld/smooth around them.

No worries. The only 'tricks' to the Embedded Geometry Extractorator would be 1) delivering two return files instead of one and 2) The reference path. I think I can do this relatively easily by storing a temp directory which is a mockup of a runtime directory and then zipping it and returning a tempfile. Like so:

/tmp/randomMD5IDcode/Runtime/
                             Libraries/
                                       Props/
                                             Extracted/
                                                       Input_Prop_filename.pp2
                             Geometries/
                                        AutoExtracted/
                                                      Input_Prop_Geom.obj

/usr/bin/zip inputFilename.zip -r /tmp/randomMD5IDCode

So.. I have to expiriment with what happens when a poly belongs to more than one body part This might be yet another way to acheive the whole skirt and bat wing thing. Maybe.