yoda64

The problem in your case is , that the lights in your model are not embedded , they are linked . Under this conditions the reload for the linked lights fails . As a workaround for now , embed all lights into the model .

It's fixed for V15.f

I have the plugin now updated, so it's measured also the curvature distance between 2 cp's .

Both is possible, but I don't suggest to use sprites for filling another object , because they are flat particles , use instead volumetric particles like fluid or blobbies . I have attached examples for both . spritetest.zip

Please do this and attach your MasterPrefs.ini and the lbr file. I will look into this .

First Have you copied the *.lbr files from /Libraries also ? Second Are the location for this copied folder in the same place relative to the A:M main directory (on the mac normaly at /Applications/Animation Master 15.0/) ?

Please open a bugreport on A:M Reports , it's in definition a bug .

As a workaround , don't render the entire view , select a bounding view with to render . It would be interested for me , if users with nvidia gpu's also affected from this issue .

In this case, sharing Your projectfile is very helpfull .

The problem is , that in your model are some bones in the relation , wich have no contraints assigned . I have put a new version for the plugins on my website , they are adressing this problem , so A:M will not longer crash .

Ahh , now I'm see what is wrong . Open the relationship window (action) for the right constraints relationship , than go back to the modelling window , now your able to run the plugin properly.

More input needed. My crystal ball is just not on hand :-) - Pc or Mac (if mac intel or PPC) ? - screenshot from the settings done in the plugin dialog and last but most important the model self

The problem in all three files is a missed token, in this segment <GROUP> Name=Head Matrix=1 0 0 -6.19888e-006 0 1 0 31.3083 0 0 1 1.43247 SaveError=EXCEPTION005 </GROUPS> When You replace the "SaveError" line with "" the files are loading correct . I don't know , why this has happened and I'm not able to reproduce this after same short tests. The corrected files are in the attachment . Deer_Whitetail_c.zip

Hi Caroline Sorry for highjacking Your thread again ... The only issue with the plugin was that I did find that the bones called "right" copied and weighted correctly, but the bones called "Right" copied, but did not weight (I had unticked case-sensitive). I fixed that by renaming the "Right" ones "right". Is now solved , also the rmweight problem .

Make a report please . For the time, before this problem is fixed in A:M , I have added to the mirrorbone plugin package a plugin, that will correct such problems . Redownload the plugin from my pluginpage. It's called rmweight ,but appears in the menu as "Check CP Weight's" (starting from a selected model) (mac v15 version is updated too)

I will look into this again. But , I had think it was solved .

As I had said , first I need model where this error occurs .

After Mirrorbones or TSM ? In both cases please provide a model with such a problem . For me , writing a plugin

Maybe , adding a non case sensitive mode is a easy task . Look at sunday on my homepage for the new version .

Hi Rusty You and David are talking about two different plugins. The one , You have a picture included , is not the mirrorbone plugin, which David mentioned .

A question because a bugreport is opened for the first way (importing model). In which version has this way worked ? I know now where and why this happend (overwriting the existing relationships) , but I'm not sure if it is suitable, to change the actual way , this is handled .

Yes, otherwise You get a secondary bonetree

That's new for mee .... The problem , which occurs in your model is , that some bones are not excact on the x0 axis, like this picture If You have corrected them , (for control main it is needed to change the z-rotation to 0) , it works without problems like the next pictures, You must run the plugin twice , with selected "main" bone and selected "control main" bone Then run MirrorConstraint (start with on the model), and voila

That's true , but there is another plugin , which will do this :-) I don't know why I had'nt release it before (initial build was from early 2007), but now it's included in the mirrorbones download . After the constraints are mirrored , you must work with a new action , because existing actions will not reflect the changes .

The grid settings are changed .... This problem is solved for the next V15 version . In the time between use for Step Width "5" .