robcat2075

load the alternate version of your character into your Project. (I presume it has a different name.) Select the old character in the chor, then in its properties use the drop down list to the right of "Shorcut to" to select the new version of the character. You might need to save your PRJ (with a new name of course) and reload it to get any complicated constraints made in the chor to awaken to this change.

Basically, I'm not sure what is causing the problem you have.

Here's what i get with the v16 PRJ...

Here's what i get when i load the v15PRJ in v15, v16 and v17 They look OK

I edited that to fix the link, it was missing a colon and a www

I sat down to make a quick demo of it and found that Snap to Surface wasn't working right, so I've sent a note back to Steffen on that for him to look at. I see it sort of working like this: First you use Snap to Surface to get your CPs close to the intended targets and then you select them and Choose Snap to CP to bump them all in place exactly.

i imagine one could do something like that in A:M. Put your hand drawn animation on a flat and place it in your 3D modeled background. If one can hand-draw animation...

I'm impressed they were able to light those to look right.

Hi chariev, I don't think A:M directly supports a FCP motion format. Biovision BVH and Polhemus DAT and Polhemus Network are the formats mentioned in the motion capture device list. Of those, BVH is the only one i recall people making use of. That has been done successfully. I don't know if there is a way to convert.

Bobby, could you also post a chor made in v15 that uses that Thom and animates the arms from the default position to the position that causes that bad shape?

I'm surprised to hear that. Can you post that Thom you show there? I'll try it out.

Lovely work. She needs a sister named "Ima".

Review of "The Wind Rises" in the NYTimes http://www.nytimes.com/2013/11/08/movies/t...ne-creator.html

OK, i didn't realize that Boolean was important. Yes, i think that's a bug to report. Show the case with Boolean OFF that works and the same case with Boolean ON not working and I think that would make it clear.

Here's a sample PRJ that seems do do everything that Stefan wants, (except one thing)... SimpleEyeTestSurfCon04.prj -The pupil properly floats on an irregular eyeball -The aimer bone follows a target null outside the eye -there is no jumping or flickering -the one thing that doesn't quite work is that the pupil bone bone doesn't follow the aimer bone while you are manually moving the target null. However if you flick the frame counter back and forth one frame it will go to the proper position and if you drag the time counter or press play the animation will work properly. The failure to immediately follow an aimer bone that is constrained to a target may be a bug or it may be a limitation of how constraints are evaluated in real-time when you are moving stuff around without actually advancing the time counter. There is one other case of this where things don't fully calculate without advancing the timer. However you can pose and animate properly with this mechanism, just remember to check your results by tapping +- to force A:M to work through all the constraints.

Hi Bobby, Select your model and look in the Property Window. The relationships you added will appear under User Properties on User Properties>New Property>Folder That will make a folder in User Properties (you can rename it) You can drag Poses into and out of folders with the little cross icon at the left of the Pose name

The Wayback machine still has "Dem Bones" Part I Part II It's quite old, I haven't examined it enough to know if it represents what are still best practices today in A:M or not but I imagine it would all still work. You may have to do a bit of mental translation from the interface screenshots in the pictures to the interface today

Stefan, I think this is a bug we can report. i notice that the constraint properly positions the pupil on the 1st, 3rd, 5th, 7th etc, frame but not on the ones inbetween. That is odd. I'll look at this some more. In the mean time... could you add the pupil as a separate model in the chor and do the surface constraint there? Does that not work? I believe a distortion box can do this although it's a bit fiddly to work with.

I'm not sure about the tut, but with your current license you can install and run v15 or 32-bit v16 and use it to rig with TSM2 Just copy the master0.lic file from v17 to either of the other installs.

Yes. After you've looked at enough of them you start to recognize when something is seriously malformed. It helps to have one that works and one that doesn't so you can compare.

Here's another case where text editing was able to resurrect a file damaged by a power outage... Model "disappeared" after power failure, Model won't appear in Project Workspace Post #6 has screen caps comparing damaged and undamaged versions of the file.

The first thing i did was compare the beginnings and ends of the two files. The beginnings looked fairly similar but the ends were very different Junkman07.mdl (the older file) ends normally with a tag, but Junkman_full_02.mdl (the new model) doesn't get that far. It looks like it died halfway through writing a tag: I copied the missing text from the first file and pasted it onto the end of the second file. Try this. It looks like it loads OK. I didn't test it beyond that. Junkman_full_02x.mdl We're lucky that it died at the very end of the file and that only basic housekeeping info was lost. And we are lucky that A:M stores its files in human-readable text so that this sort of repair is easy to do!

Probably the only final render element that might be graphics card dependent would be the Screen Space Ambient occlusion effect in v18, but that would not have been in play in your test anyway. Looks like about an 18% penalty on render time for the mac which isn't too bad. it used to be many x worse in the Power PC days, i think.

I f you want to send me the two versions of the .mdl file I can look at it. You can attach them in a private message if you don't want to post them here.

Thanks, Rodney!