Here are links to the v13.0 Beta 2 Installer.


Windows:
v13.0 Beta Installer (Yeti CD)

v13.0 Network Beta Installer (Hasp)

OSX (Univeral Binary): v13.0 Beta


See the SVN Instructions

-fixes

• 0002735: [Interface] Quit does not work from the menu on the first try (Steve)
• 0003020: [Timeline/Channel] Faster exit when many muscle channels exist. Fewer timeline draws on object select. (bobcroucher)
• 0002992: [_Other] AM will not quit. (GazzaMataz)
• 0002993: [_Other] Failure on launch due to athlon cpu conflict with newton plugin (AlphaScorpious)
• 0002999: [SDK] Missing Prototypes for HCPWeight (sgross)
• 0003015: [Relationships/Poses] Circularity issues (KenH)
• 0002183: [Rendering] Rendered Images not the same as in V11.1i (ddustin)
• 0001917: [Materials] Materials Rendering oddly (John Keates)
• 0002991: [Hair] magnitude property data (alweb)
• 0002833: [Interface] Some keyframes being deleted in a "stealth" manner (ArgleBargle)
• 0002982: [Modeling] Creating invalid hook caused crash (a1amatrix)
• 0002970: [Hair] The appearance of hair is strange. (jenpy)
• 0001316: [Relationships/Poses] circularity found, unexpected (TempleTiger)
• 0002968: [_Other] Chors, Objects and Actions vanish from V12 project when it has old style hair materials. (rwilliamson)
• 0002836: [Bones/Rigging] Infinite Loop of Circularity Errors in Squetch Rig (jandals)

Back this one up. Timeline speed is sweet now.

This is a problem?!?

Just Kidding Gaz... I know the issue.

But think about this for a moment.
If that isn't a sure sign of stability... I must not know what one is.

I can hear the discussion in the future. It goes something like this:

Master: I bought A:M back in 2006.
Newbie: Wasn't that the one that wouldn't quit?
Master: Yeah... it was the darnedest thing. I had to just keep on animatin' until they fixed it.

Hash & Co.
You might want to let people know that the Beta2 of the Universal Binary version is available now
Rodney
AM not quiting meaning I had to keep on animating? Now there's a thought…

Has anyone tried to render with Beta 2? If I open the toy project and attempt to render... things do not go as I'd expect them to go. I'm wondering if it's just something with my install as I had hoped to test some of the new features.

Rusty

Beta 2 throws up a bunch of circularity warnings whenever I try to open a project. I have to stick with Beta 1 for the time being.

Have not see this but than we are not opening the same project files.

Rusty

I'm getting a strange thing going on ,it seems as though its not updating the model in the cho ,as when I alter some splines in modeling window the cho is not changed even when I replace the model ,heres a screenshot to show what I mean.If you look at the under breast [attachmentid=16749]

Hard to tell what's what. From what I see and what you say... this looks like a pose (or constraint within a pose) has unwanted key frames on a bone. Do you get the same thing in an action? A quick way to tell is to save a copy of your model, delete all the relationships from the copy and see if it still happens.

Rusty

My bad! I had some render shaders set and this caused the problem I saw.

Steve, you may have to press the spacebar to get it to refresh the changes. But send the data into Hash.

Yes, Just placing a model on a path gives a circular reference error. Create a new chor, draw a path, add Knight and contraint Knight to the path. When you try to play, you get this message.


Animation Master 2006

Circularity Found: "Balance Point Rigid" Shortcut to
Relationship1 / Kinematic Chain To Left Foot Target

Yup, that's the error I was getting. Did you submit it to http://www.hash.com/reports/main_page.php ?

I just added it to the v13 Beta 2 reports. That's a good reminder, too, that we should all use the reports to give feedback on errors so Hash will know what needs fixing.

Cheers Ken ,sent a report in

Is there a 2005 Beta 2 Version?

By the way, I didn't see it up there, but did you guys add in the Toon Render updates?

Yes

I know that when you make the move to v13 that it will change the model to were you are not able to go back to v12.
I know the model file is changed.
I heard the bump percentage has changed but on conversion from v12 to 13 it is suppose to do the conversion for you. Is this worked out now or will we need to manually adjust all bump map image files on models?

What other changes will take place to a model?

Are there any changes made to the material files pertaining to specularity, reflectivity, ect. ?

Will there need to be any adjusting to Dark tree materials?

Steve, I had a similar problem once, and after a couple hours of frustration, I figured out that the CPs were not associated with the bones I thought they were. Things looked fine in the model, but then in Chor or an Action, when the constraints were applied, the CPs were with incompatible bones and things were off.

I'm not saying this is your problem, and I haven't even tried A:M 13 Beta 2, but it's something to check.