Bepu: Default values for constraints.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Is your feature request related to a problem? Please describe.
Bepu: by default the servo settings insert magic number values, which don't help much.
Describe the solution you'd like
Insert default values from the Bepu lib + some explanation/example for the stride editor.
Additional context
(https://github.com/bepu/bepuphysics2/blob/master/BepuPhysics/Constraints/ServoSettings.cs) - in Bepu, Norbo assigns new ServoSettings(float.MaxValue, 0, float.MaxValue); as default. I propose to do the same.
Extra suggestion
There is different order of values in some of ConstraintComponents. E.g. in BallSocketServo and AngluarServo spring settings come first, then come servo settings. In LinearAxisServo and PointOnLine servo settings come first, then spring settings. Proposal is to order them consistently in all components.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the constraint components named in the issue with Bepu's ServoSettings.cs reference. Review BallSocketServo, AngularServo, LinearAxisServo, and PointOnLineServo, then inspect the Stride editor handling for their defaults and descriptions. Done means matching the requested Bepu defaults, consistently ordering spring and servo settings, and adding the requested explanation or example.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- game-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100