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

Adding multiple ContactMaterials to the World is useful for unique contact equation properties between two specific Materials

const material1 = new CANNON.Material({ name: 'ElasticMaterial1', friction: 0, restitution: 1 })
const material2 = new CANNON.Material({ name: 'ElasticMaterial2', friction: 0.2, restitution: 0.9 })
const contactMaterial = new CANNON.ContactMaterial(material1, ma

RAEairfoil_AUSM_issue.pdf
Describe the bug
I was trying to run RAE2822 rans case with AUSM scheme (SU2-7.0.1). I observed some issue while using Venkatakrishnan or Venkatakrishnan-Wang limiter, spurious pressure distribution over the surface along with pressure contours in the field are observed. While with Van Albad

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