Known Issues

Selection not working for all display modes in Maya 2016.5 & Maya 2017

Because of important changes in Autodesk Maya APIs, selecting a character may not work in Maya 2016.5 & Maya 2017 depending on your display mode.
 
See the below matrix of all the possible Viewport / Render Engine combination for each version of Maya.
Cells in bold are the default setting when installing Maya. Gray cells are combinations not available in a particular version of Maya.
 
 * env var: for Visual Debug / Cache Layout selection to work, the MAYA_VP2_USE_VP1_SELECTION environment variable needs to be set to 1
 
To change your display mode if needed, go to Maya Preferences / Display / Viewport 2.0 and then restart Maya

On Linux, Maya 2017 Update 1 or later need to be installed to be able to load Golaem

Between Maya 2017 initial release and the following updates, and only in the the Linux version, Autodesk changed the Maya API.
Because most studios prefer to update to benefit from bug fixes, we decided to compile Golaem only with the latest API.

Therefore, on Linux, loading Golaem from Maya 2017 with no updates installed will result in the following error. 

// Error: line 1: Unable to dynamically load : /home/golaem/Golaem/Golaem-5.3.4-Maya2017/plug-ins/glmCrowd.so
/home/golaem/Golaem/Golaem-5.3.4-Maya2017/plug-ins/glmCrowd.so: undefined symbol: _ZN21MMeshIsectAccelParamsC1Ev // 
// Error: line 1: /home/golaem/Golaem/Golaem-5.3.4-Maya2017/plug-ins/glmCrowd.so: undefined symbol: _ZN21MMeshIsectAccelParamsC1Ev (glmCrowd) // 

The solution to this problem is to install Maya 2017 updates. Although the latest update is recommended, installing Update 1 is enough to fix the problem.

Rearranging Behaviors in the Outliner

Moving behaviors in the Outliner in order to arrange them in a different way (e.g. re-parenting behaviors under other behaviors as in Figure 15), may induce errors and failures in your Golaem Scene.
 
Example of Invalid Rearrangement of Behaviors.

Physics Simulation is not 100% Reproductible

Due to the use of the a physics engine (and the difference of CPU usage at each simulation sample), the ragdoll behavior does not produce EXACTLY the same result between two simulations with the same set of parameters. Nevertheless, notice that the differences will be very slight, even sometimes unnoticeable.

Ramp Control in SetBone Behavior does not save Control Points at (0;0)

Due to a Maya bug, creating a control point at position 0 with a value of 0 will not be saved within the Maya file. Putting any other position or value different than 0 (even really small) will fix the problem:
 

The CharacterMaker Geometry Tab does not react when clicked

It may happens that when clicking on the Geometry Tab to switch the CharacterMaker to geometry mode, it does not react, as if it were grayed out.

It is caused by a bug in the UI library Golaem is relying on. Usually clicking at the very top of the Geometry Tab is enough to make it works. In other cases you may need to change the Character Maker mode (Character / Motion / Motion Mapping) and get back to Character Mode to make it works.

Because this is not 100% reproducible and apparently happens very randomly, we could not fix this bug yet (or asked the UI library to fix it). If you know how to reproduce it reliably, do not hesitate to drop us an email!

Other Issues

For any other issue, please contact us