This is a minor update. The changes are mostly usability improvements. The main changes are improvement of error handling and addition of a context sensitive help.
For Blender 2.64 pre release:
You can open the Help for any Avastar function button by:
Right Mouse Button -> Online Manual
Your Online browser should pop up and guide you to the relevant Help page.
Changeset:
FIX: fixed an error message text in the exporter
FIX: Parent to armature now preserves child location regardless of Avastar location
IMP: Make Error messages for unweighted vertices more consistent uand less confusing
IMP: Added Warning and optional Online Help Button to message popup
IMP: Some functions would change the selection State after terminating. This has been fixed. (No more unexpected flickering on the 3D View when calling a function)
IMP: Weight utilities now only show up when they can be used.
IMP: Added message box to Bake T Pose (when unweitghted vertices are found)
IMP: Added reports to status line for all tool shelf operators.
IMP: Check for attempt to reparent an already parented mesh and added a detail message box.
Highlights:
Help messages are now context sensitive. Most message popups now contain a button to the correct Machinimatrix help pages.
We added an example startup file which has built in materials for new Avastar characters. Just Add -> Avastar will now create a skinned female Avastar character.
Limitations:
This update is not compatible to Avastar-500. The compatibility fix is still pending.
More Questions ?
Ask Gaia Clary in Second Life, or send email to mailto:gaia.clary@machinimatrix.org
I already purchased Avastar-1: You find the new update in your Jass Download folder.
I want to buy Avastar-1: You can buy directly from Paypal (see left column of this page), or go to the Jass-Shop in Second Life and purchase from the Avastar-1 vendor.
Important notes:
We believe that we have fixed most issues with Avastar by now. However please continue reporting any issues. Every test case can help us to isolate new problems.
We have tested the new Avastar update on the development version of Blender. Avastar should now run on all Blender 2.6 version.
(Using Blender 263) I upgraded from Avastar 432 to 636. Can you explain the workflow differences. In 432 I would select the mesh and avastar then copy weights. Lastly – click Bake to T-Pose. Export to SL and upload to SL with the weight and joint options available in the SL importer.
In 636 some functions seem to have been modified – I’m not sure how to export to SL with weights correctly. I can’t seem to export with the weight/joint data. I select both the mesh and avastar – click copy weights. Then I see rigging with Parent to Armature or Bake to T Pose.
I tried each one and them both. I then export to SL but don’t have any weight data – cant check weights or joints in the SL importer.
What is the correct way to export to SL with all weight/joint data in 636?
(Using Blender 263) I upgraded from Avastar 432 to 636. Can you explain the workflow differences. In 432 I would select the mesh and avastar then copy weights. Lastly – click Bake to T-Pose. Export to SL and upload to SL with the weight and joint options available in the SL importer.
In 636 some functions seem to have been modified – I’m not sure how to export to SL with weights correctly. I can’t seem to export with the weight/joint data. I select both the mesh and avastar – click copy weights. Then I see rigging with Parent to Armature or Bake to T Pose.
I tried each one and them both. I then export to SL but don’t have any weight data – cant check weights or joints in the SL importer.
What is the correct way to export to SL with all weight/joint data in 636?
Thanks
In 432 – Parent to Armature was checked and then you click Bake to T Pose.
In 636 – Parent to Armature is a separate button above Bake to T pose button.
Based on 432 I assume I would click Parent to Armature then click Back to T Pose.
One thing I noticed – after I click copy weights and click Parent to Armature – the mesh and avastar seem to shift/move – no longer aligned.
Actually re-tested with imported obj model file and 636 and 639 work correctly. Must have been the dae model I used. All is good!
Dave
Thanks!
“The Collada exporter currently does not export Material settings. This means your exported objects will have only one texture face”
Has this been fixed in later releases?
Hi, Dave. This issue has been fixed a few months ago.