Links to all modules are broken because of renaming

Version:

• v2.x.x
• v1.x.x

Issue type:

• Bug
• Proposal/Enhancement
• Question
• Discussion

Hey all,

I am curious if support exists, or will in the future, for the loading of URDF, SDF and/or MJCF model files into nphysics. This functionality would make nphysics highly desirable for simulating robotics and help Rust expand into the robotics world in general. This is something I could potentially help with if there agreement to support such model files.

Perhaps the library is still

Multiple constructors in TString can drop segfaults with formally valid arguments,
e.g.

Ssiz_t l=-5;
TString* a= new TString('a',l);

Expected behavior

No segfaults. Create an empty string if meaningless arguments are given.

To Reproduce

Ssiz_t l=-5;
TString* a= new TString('a',l);

At this time I was not able to provide physic to a Heightfield.

We have quite a few common booleans we use in many places of the code.
Some of them are very simple, like checking for compressible vs incompressible, or for FSI.
But when we want to express something more complicated like is it SA or SST, is the mesh moving or deforming, is this FEM or FVM or FEA, and so on, things are not so simple anymore and we end up with long conditionals repeated in many

Exchange a package that is marked as deprecated.
Seen in CI as warning in the apt install step with CUDA 10.1.243.

To Do:

• double check this works with CUDA 9.2 (current docker image; check minimal version constraint for Nvidia NGC) or...
• update Docker image to newer CUDA

Hello,

There seem to be an issue in template recognition when creating mappings involving Rigid3d DoFs.

Namely, when creating a BarycentricMapping or a BeamLinearMapping between a mechanical model and a collision model of connected beam elements, I receive the following error messages:

`[ERROR] [InfoComponent(Not created (BarycentricMapping))] Object type BarycentricMapping<Vec3d,Rigid3