robcat2075

That's fabulous, Roger! A little urban noise and wheel squeaking would go well with that.

Looks like a good result!

I hope you'll bring this to Live Answer Time. i think it would be easier to do this interactively. I haven't read the Paries or TAoA:M recently so i'm not sure on the distinctions between the two.

Yes, contact hash. i believe Jason has created an additional .lic file for Mac users who run windows.

I've discovered that unless you explicitly pick a forum in the drop down list you will get no results. Maybe Rodney or Jason can shed more light on that.

Now if there were some way to export the small details as displacement map and place that back on the A:M model...

Short version... First you make an image series of random gray scale blobs. It should have as many images as a multi-pass setting. (9, 16, 25, etc...) Apply that to your model. Set it as a displacement map. In the chor, Set the frame property of the image sequence to cycle through the series in the first 0.2 of the first frame and set that to repeat for every frame Render with multipass, 20% motion blur All the different displacement maps blurred together make a fuzzy look. sample PRJ... scratchWhiteTest.zip

Hey Serg, if you were looking for fuzzier look for the cloth parts of your character there is a multipass technique using displacement maps that the SoulCage guys showed a while back. These are some experimental tests I did to try it out. With the right pattern and right settings it might give a good felt look. FuzzyClothMultipass Sampler.mov

that is very cute!

A URL will be posted just before the start time. You click on it to go to the Hangout. Your browser may ask you to allow a plugin. Have your mic plugged in before hand.

I don't think you need to change rigs because that won't change the need to weight CPs or use smartskin appropriately. Come to Live Answer Time! i think it would be useful to talk about this interactively.

This would be a good case to bring to Live Answer Time.

Inkscape SVG contains just the points you created. It's curves between control points, rather like A:M.

We've had .ai (Adobe Illustrator) import for a long time. You can make an outline in a vector art program and A:M can import the .ai file and bevel/extrude it to make a 3D shape. That is great for making mechanical parts. However, inexpensive programs that can export a .AI file are still not common. V19 will add suport for SVG. SVG (ScalableVectorGraphics) is another vector format and is supported by free programs like InkScape. InkScape appears to be a full-featured vector graphics editor and should work well for A:M purposes.

I was initially confused by that different location also.

Welcome back! Glad to have you!

Can you show your start and result?

That's a good toon-line result

Thank you for your detective work on this! This may be a correctable bug. I recommend you submit your findings to hash.com/reports when when v19 becomes available (presuming the behavior continues in that version.)

Here's my old thread... How to randomly set a value ONCE?

I believe it can be done. On TWO I created a generic crowd character that would assume different sizes and colors and hats (?) each time it was dropped into a chor. There was a small bit of manual key-framing involved but most of the randomization was handled by the character. i suspect the same concept could be re-used to make a value reset when the chor repeated. hmmm... how did that work? I think an expression could be used to check IF the current frame is the first frame and if it is THEN use the random function to set a value. After the first frame, the random thing never happens so the value stays stuck.

V10.5 has the interface we see today with the PWS outline in the left pane and the PWS timeline in the right pane. Some previous versions experimented with elements like that but 10.5 was when they got it right and it has stayed that way since. Of course, many features and speed/stability improvements since then but v10.5 was when it got the GUI it has now. Prior to that, v5 was the big leap to a unified modeling/rigging/animation environment. Prior to v5 they were all separate apps and prior to v5 you had to break your model into .seg files for every bone and rejoin them back together in the rigger. V5 also added most of the constraints we need for modern rigging. But if i ran v5 today I wouldn't know where to start, it looks so different.

Save those for posterity! The last OS I had that ran that early version was Win 2K. It was so different from modern A:M that I couldn't make any sense of it.

Here is a post with a tut on Surface Constraint

Welcome back to A:M, kazagruma!