Hi Kristy, This likely is a visualization only problem that we fixed already in later versions of OpenSim. That problem was caused by losing track of the folder where the model came from so instead of the application using the MOBL_ARMS custom geometry folder it's using the stock geometry folder whi...

Hello, There's a line in the header of sto (and mot) files that specifies whether the angles are in degrees or radians. Motion files are assumed to have rotational coordinates in degrees (inDegrees=yes) so you can set it to match the data in the file. For OpenSim use the .mot and .sto are interchang...

Hello, This is a visualization only issue due to missing geometry/mesh files, it has no effect on modeling or simulation. If the model uses stock opensim mesh files it should work out of the box as is, otherwise the model authors should provide a set of mesh files in the same folder with the model (...

Hi Nathan, Please open an issue on github or file a bug report so we can dig deeper into the issues/differences between machines/environments that work and others that don't. Not sure if these issues are model specific but I'd try models with built in geometry rather than with mesh files (e.g. an ea...

Hello,

My recollection is that OSX version 11 has been retired by Apple, as such we build/distribute/support OSX version 12+. Please try another mac with a more recent OSX version and let us know if the problem is resolved.

All the best,
-Ayman

Hi Giovanni, The pose of the model in visualization depends on the state/coordinate-values. Some models have coordinates that can be set to move them above/below ground. I think that's what you have, it's not necessarily a bug that a model appears below ground if that's the case. You can also hide t...

Hello,

Please relax the assembly tolerance (first reported exception) to something like and then retry.

Hope this helps,
-Ayman

Awesome, thanks for the update, glad all is working/visible now.

Best regards,
-Ayman

Hi Davide, Thanks for explaining your workflow. The header file for C3DFileAdapter is conditionally included, so you may have to define the preprocessor symbol WITH_EZC3D for the compiler. We probably should define that in our CMakeLists.txt regardless since that's what we do during release, but let...

Hello, The missing files issue can be fixed by setting the search path as explained by Mohammadreza (if you do have the files locally). The last error is caused by using a binary vtp file which is no longer supported since 4.0. You should try to find an ascii version of the file or some online tools...