Help - Search - Members - Calendar
Full Version: v13.0e
Hash, Inc. Forums > Forum Archives > A:M Forums Archive > (2007) > A:M v13.0
WillP
Here are links to the v13.0e Installer.


Windows:OSX (Univeral Binary): -fixes
  • 0003448: [Relationships/Poses] Bone relationships created in version ‘c’ do not work in version ‘d’ (rwilliamson)
  • 0003458: [Animation] CP weighting problem when cp controlled by the same bone more than once. (kattkieru)
  • 0003372: [Rendering] AM crashes when rendering with animated surfaces. (rkaneko)
  • 0003441: [Decaling] Continued problem of crashing when rendering to file --- movie or image sequence only (mike b.)
  • 0003450: [Modeling] #001 crash after making a hook (KenH)
  • 0003454: [Materials] annoying visual glitch with models that have Emmitter Materials (raillard)
  • 0003411: [Decaling] #001 unhandled exception crash in pose windows. (KenH)
  • 0003414: [Relationships/Poses] Unhandled Exception #001 with specific model/action (Emilio Le Roux)
  • 0003390: [Constraints] Compensate mode does not work on a pair of crucial bones (raillard)
  • 0003387: [Materials] Normal tweaking material nodes had no effect when material.bump percent was set (Jack West)
  • 0003351: [Plugins] Properties are not correct saved (sgross)
The hair shaders mentioned in this thread are included in in this release.

Examples prj's to play with: hair.prj and hair_oirg.prj (r-click and select save-as)
mouseman
Does the Reference.exe actually get updated with each new release?
T-Dogg
QUOTE(mouseman @ Jul 27 2006, 10:01 PM) *

Does the Reference.exe actually get updated with each new release?


I had been downloading reference.exe with each new version, and labeling them as 13.0a, 13.0b, and so on. Then one day I ran a duplic8, and it said they were all the same. So I'm guessing it only gets updated with each new major version release.

To check again, I just now downloaded the reference.exe file linked to in this thread, and it is also the same as the previous version.

Hope this helps save you some download time.

Hopefully WIllP will let everyone know if the reference file gets updated along with A:M itself. smile.gif
Shelton
Installed 13 e and the system came to a crawl. Uninstalled went back to 13 d and back to normal. Can't explain it any other way. Same project used in both version but with e I would select a cp and it would take up to 10 seconds to move it. The pose sliders would work only part of the time. In fact I moved one slider and it lagged some 20 seconds before the mesh moved in the pose. Then the system appeared to lock up. Some 35seconds later I was able to move the slider back and had to wait once again.

Steve

WillP
QUOTE(Shelton @ Jul 28 2006, 11:03 AM) *

Installed 13 e and the system came to a crawl. Uninstalled went back to 13 d and back to normal. Can't explain it any other way. Same project used in both version but with e I would select a cp and it would take up to 10 seconds to move it. The pose sliders would work only part of the time. In fact I moved one slider and it lagged some 20 seconds before the mesh moved in the pose. Then the system appeared to lock up. Some 35seconds later I was able to move the slider back and had to wait once again.

Steve


Please report this to www.hash.com/reports and attach a file that is showing this behavior.
Dhar
I haven't updated since V13 made it out of Beta; I'm wondering if anyone has this problem or if it has been fixed by the updates (or I need to report it).

This capture is in Action window in Shaded mode, the bones turn black when I try to move/animate them and it is quite annoying since they don't let me see where I'm positioning the hand or what have you.

Any ideas or similar experience?

Shelton
Version 13 e is doing something wierd stuff. I can not render in a chor window. If I try to quick render in the chor it locks up, If I try to output anything it locks up. I can render in a modeling window no problems. Anybody else have any problems

Steve
T-Dogg
QUOTE(Shelton @ Aug 1 2006, 04:13 AM) *

Version 13 e is doing something wierd stuff. I can not render in a chor window. If I try to quick render in the chor it locks up, If I try to output anything it locks up. I can render in a modeling window no problems. Anybody else have any problems

Steve


I just did a basic render in choreography as a test and it worked fine for me. It was just a head with a texture map... no particles or hair or anything too fancy.
PF_Mark
I have made a report for 13 e but I have not seen any activity in the report status I was wondering if I reported correctly the number is 0003481
Rodney
QUOTE
I have made a report for 13 e but I have not seen any activity in the report status I was wondering if I reported correctly the number is 0003481


Mark,
You can add reminders to the reports.
That will.... then... um... remind them. smile.gif
PF_Mark
QUOTE(Rodney @ Aug 10 2006, 12:33 AM) *

QUOTE
I have made a report for 13 e but I have not seen any activity in the report status I was wondering if I reported correctly the number is 0003481


Mark,
You can add reminders to the reports.
That will.... then... um... remind them. smile.gif


Ok then to remind them I remind them which indeed should remind them laugh.gif


Well I was too late to remind them I guess my last post robbed me of that experience biggrin.gif
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2012 Invision Power Services, Inc.