LOL....Mine too---->(My problem is in making and transmapping the "skullcap" and "tuft" at the ends). I tried a hair model once and it came out like Vicki was balding! LOL! Just wisps of hair here and there..it was quite laughable heheh. The mesh itself was pretty full and thick, so I guess it was my transmapping that sucked to hell. :) I didn't use a skull cap either and that was another part of the problem, I guess.

Valandar, what proggy are you using. I use rhino. I was thinking that perhaps I could do something similar using multiple strands per hair segment. I don't have access to my machine right now, but will give it a try later. I was thinking perhaps "piping" a number of splines which are already in the proper shape and order. ...and piping each with slightly different diameters... oh, and without end caps :). By usings different diameters, I hope to cause some of the strands to intersect slightly which would close some of the gaps (hopefully all). It would be most similar to how DW creates his hair models. I've never done hair before either, but it will be a nice little challenge. I was playing around doing organics the other day and came up with a nice grass model which I placed in the FREE stuff section. Did a nice little ornamental tree too :)

Aye, I've never really tried to model anything like natural braids. Most modelers create braids from deform spherical objects or cylinders I would guess. Doing it in the same fashion as true braids would be a difficult chore but not impossible. I'm guessing that the poly count would be higher as well.

LOL! Gebe, I was thinking the same thing ;)

Ooops... The last example I made didn't have the dial values which would be seen in a normal MatMor pose file. These values would come after "k 0 1" in the file. MatMor and Morph Injections aren't the same, of course since the indexes and deltas are included in an injection pose :). Glad that this was of help to you :D ----Will

Mahna, If you are just creating a pose file without the deltas, then there is no issue over copyright. :) The violation would occur only if you include the deltas as an INJECTION as well. Pose files should only include info that sets up the parameters of your characters. In other words, the pose file would contain only the values for the pose (dials); there shouldn't be any info in the pz2 file which says "indexes" or "deltas". Example: channels { targetGeom HdVictoria2 { name Elena initValue 0 hidden 0 forceLimits 1 min 1 max 1 trackingScale 0.02 keys { static 0 k 0 1 } interpStyleLocked 0 indexes 9772 numbDeltas 10041 deltas After "deltas", there would be a list of data which defines the morph. I took this example from a custom made morph injection that I created for Victoria 2, hence you'll notice the name change of the dial from "HdVictoria2" to "Elena" The only info that you should see in a morph pose file is this: channels { targetGeom HdVictoria2 { name Elena initValue 0 hidden 0 forceLimits 1 min 1 max 1 trackingScale 0.02 keys { static 0 k 0 1 } Of course this example only shows one channel :) Hope this helps. ----Will

Hmmm wouldn't be too hard to go over the thousand mark if you have about 20-30 products and only half do well. I find that the market does fairly well enough. I agree with Kromecat, however, that the actual figures are nobody elses business. I, myself, don't care but many other merchants would rather not have that info divuldged unless they divuldge it themselves.

Another interesting discovery I made was while I was working on a kit (not yet released) for Victoria 2. The kit is designed as a way for users to remove unused deltas from a loaded V2 figure to free up memory. There are also options to hide and show dials. However, when the user removes a particular morph I have it set so the dial hides automatically. I discovered that when this is done and the user saves to a new Cr2 the dial is forced to remain hidden even in the new Cr2! It does not return "unhidden" as would normally be expected. I'm not sure, yet, as to why this occurs but it does. I even tried saving the cr2 again and again under different names and the dials still remained hidden. From what I know and from my experience I don't think this has ever been accomplished. Typically you can hide the dials from a pose file, but if the user saves to a new cr2, the dials are forced to become unhidden by default. I've toyed around with hiding dials before and never was able to get them to remain hidden. Now that I've accomplished it while removing deltas at the same time, I'm wondering what is forcing Poser to keep them hidden. In retrospect, the "Hide Dials" option in my kit remains the same as before. If the figured is saved to a new cr2, the dials become unhidden when the cr2 is reloaded. Go figure. It only seems that if you remove the deltas and then hide the dial that this applies, but perhaps I'll take a closer look at my code when I get a chance and see if there is something different there that is causing this much wanted effect hehehe. Just thought I'd relay this tidbit of info from my journeys through readscript :) Ps: How I remove the deltas is through morph injection. I simply inject a value of zero to the deltas of a target. indexes=0 deltas=0 That's pretty much it. Pretty simple but a lot of work and a lot of files to keep track of. So far, I have about 1600 files in the kit and these just pertain to V2's head. I'm configuring a good way to structure the body targets at the moment. ---Will

I am thinking that they can, but the organisation is important since they execute in the order they are read. For example, if you want to remove deltas then hide the dial in respect to the morph you just removed you'd have to have the "readscript" line that removes the deltas come first in order. I also discovered that readscript will read any file extension! You can rename the pz2 to anything you wish and readscript will still read the data inside as long it's still in the proper poser format ;). Cool. ----Will

Oh yeh, I forgot to mention this, but certain versions of windows (XP being one) limit the max page file size to 4.1gb if you use the control panel utility to set the VM. This applies to the max on the MINIMUM setting as well. This was done, I'm sure, because of the threshhold limit by many programs. However, the max setting can be overridden with a few registry hacks :). I still wouldn't suggest setting the minimum value above 2gb though. And logically there is really no need to go above 3 or 4 gb on the maximum unless your an impatient bastage like me who likes to run two or three high end apps at once (while surfing the net)heheh but, of course your always risking a system crash when running too many high end apps at the same time :(. I'm pretty satisfied with XP pro and is memory handling capabilities and stability. It rarely crashes even under the heaviest of loads. ---Will

Take notice that they are talking about the MIN setting. If you look at my earliest post, I mention setting the minimum between 1-2gb. The maximum setting doesn't apply here because that is changed on the fly only if windows needs it. The problem occurs when Poser is first executed and the amount of VM, at the time a figure is loaded, exceeds the 4gb threshhold (better chance of winning the lotto unless you've set the min at or above the threshhold). The threshhold can be exceeded without a problem while, let's say, Poser is rendering which would happen if physical plus available VM is exhausted (not very likely). A lot of programs would have a problem if the page file is larger than 4gb at execution. Some have a problem when it's only 2gb. My recommendation is always set the min at about 1-2gb. There is always an issue with older windows versions, however. Let's say WIN 98. On occasion (hehehe OK more than just occasionally) win 98 will not dump the page file like it should. However, if you set the minimum to 2gb when the system is rebooted and windows restarts, the page file will be resized back to 2gb. Server versions of windows handle this much better.... NT, 2000 PRO and XP or XP Pro

My maximum for VM on my machine is at 10GB (I have a BIG BIG HD heheh). I have never received a crash while using Poser even under a heavy load. But then again I have 1GB physical ram also. The OS I use Poser in is Win XP Pro on a multi boot system. The other OSs are WIN ME and Suse Linux.

Yes, video cards won't do so much for Poser renders but the increase in overall system performance for the display is dependant on hardware. Regardless, display throughput performance increases with more video ram which is only available with today's sophisticated video cards. As far as VM and Poser goes, chances of using up to 4GB would be rare (you'd have to have one heck of a busy scene going on). It is better to up the VM and take the risk of a crash than to not up it and certainly risk crashes more often.