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

Windows:

• v14.0 Installer (2007 - Oz CD ) (11m)
• v14.0 Network Installer (Hasp - Requires 2007 subscription) (15mb)

OSX (Universal Binary):

• AMv14Installer.zip (23.6m) Up shortly

Fixes since the last release:

• 0004420: [Composite/Post Effects] buffershortcuts and posteffects saved absolute paths, now they are relative paths allowing files to be in different folders (Noel)
• 0004418: [_ Not Selected _] Simcloth sometimes simulates more than once. (bobcroucher)
• 0004413: [_ Not Selected _] simcloth does not work (johnl3d)
• 0004417: [_ Not Selected _] SimCloth crashes upon simulate. (bobcroucher)
• 0004412: [Images/Animations/Rotoscopes] Cp settings dialog opened when it shouldn't (Noel)

Make sure when you report bugs to A:M Reports, that you pick the v14 project in the upper right.

Just thought I would ask so I will: is the multi-processor/core thingy working OK now? I heard that it was proving to be a bit of a pain…

No Mac progress yet.

Thanks for the reply Martin, I recently upgraded my PC to Core 2 Duo E6400 2.1ghz thingies so is the PC version working (please say yes! Please!!!)

Well, give it a spin, Gary, (keep your fingers crossed). With a few people using the multicore version once-in-awhile (until we feel comfortable with it), things should move right along. (Then I can look at the Mac.)

I can't wait till multicore is working on the mac, I have a Mac Pro just waiting for its 4 cores to start chugging on some renders..

Is the Dual Core A:M implementation on the PC set as 'active' by default or is it part of a setting within v14 ?

As of the latest Beta it is set to Inactive.
Change it within TOOLS/OPTIONS.

I think this is the right forum to post my ideas for A:M. If it's not you can move it.

Maybe there would be a auto-saving devices built into A:M.

So if it crashes you will not loose all your work.

Maybe it would save it every 5 min's and save it when you start to render. But you can alter the settings.

Elliot

I think this is the right forum to post my ideas for A:M. If it's not you can move it.

Maybe there would be a auto-saving devices built into A:M.

So if it crashes you will not loose all your work.

Maybe it would save it every 5 min's and save it when you start to render. But you can alter the settings.

Elliot

EDIT: Sorry about posting twice

You can download an AutoSave plug-in here:
http://www.sgross.com/plugins/
There's one for V13. I don't know whether it works in V14.

I tried to send this QT movie to A:M Reports but it wouldn't upload. When I attach the movie it causes an error on A:M Reports and my window fills with red text, ( a text version of my QT movie ).

The movie is a CamStudio capture of a problem that I have been having with A:M for quite a while now.
The problem, which I have seen mentioned by others, is that when I select the rotate tool,( R ), and follow with the turn tool, (T), my model seems to be displayed in reverse. The back facing patches are drawn over the front facing patches, or something like that. It makes it difficult at times and impossible at others.

Click to view attachment

--------------------
Edit:

Actually the "Turn" command might have nothing to do with the problem. This occurs even when I simply select the "Rotate" manipulator,

Did you put it in a zip file for AM:Reports? It should accept it then.

No, I just tried to upload the QT movie but I have sent this jpg image now instead:

Click to view attachment

This shows just how impossible it is to see what you are doing when this occurs.

I would like to know if there is anyone, who is using the rotate manipulator on bones, who never sees this glitch, and if so what graphics card they are using.

Anyone?

I do remember such 'happenings' but I would place that more in category v12, I do remember hitting spacebar 'solved' it... I have an NVidia XL card b.t.w.
Something you probably thought of yourself; you did try to switch drivers as test...(openGL/DirectX)

I saw this anamoly several weeks ago while troubleshooting my graphics card.
I haven't seen it lately and just tested a simple file with negative findings.
Could it be related to the size of the files?

All clear here on a Intel Graphics Media Accelerator 950 running in Vista.


Whoops... typed too soon.
See below for a shot of reversed bones (still not seeing reversed surfaces).
Animating still works fine *if* you can animate in reverse.

Definitely send that off to A:M Reports.

Workaround:
In my case Saving the Project immediately corrected the screen.
I did swap from OpenGL to Direct3D immediately before that as any time I get a display issue that seems to work for me.
In this case it didn't and was set to close A:M and see if all was well after reloading.
Didn't need to go that far as saving popped everything back into proper perspective.

Note: The correct perspective doesn't stay that way for long when working in multiple windows.
I'm still waiting for Intel to release better drivers for their GMA graphics cards.

Not as far as I can tell. I get the same thing with a simple 900 patch model, (with no textures or decals), as I do with these TWO models.
Hitting the Spacebar doesn't clear it. The only way to clear it is to click away, deselecting the bone, but as soon as I start using the rotate manupulator again it is back. This is the norm. It is rare for it not to happen.

I have two machines and it happens on both. One has an ATI Radeon X1300 Pro card and the other has an nVidia GE Force FX 5600XT. I have tried running A:M with OpenGL and Direct3D and it makes no difference.

If other people are not seeing this then there is something very strange going on in my machines or in the way I work. Could this be related to having too many windows open in Workbook mode? That is something that I haven't tested yet. Hmmm.

Rodney, that little glitch that you have found looks like something completely different. I haven't ever seen reversed bones.

Thanks for the feedback, guys!