Stride Game Engine
BEPUphysics
Our great sponsors
Stride Game Engine | BEPUphysics | |
---|---|---|
23 | 5 | |
6,191 | 2,158 | |
1.7% | 3.6% | |
9.5 | 8.7 | |
2 days ago | 5 days ago | |
C# | C# | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stride Game Engine
-
Unity Software plans to reduce its workforce by 25%, eliminating ~1,800 jobs
In general it took me less time to rewrite the code-base then implementing some of the workarounds for missing features in Unity (e.g. HTTP2) in the first place.
[0] https://github.com/stride3d/stride/issues/2069
- 🗨️ Join the Stride Conversation on GitHub!
-
Thinking switch from C++ to C#. Some questions. Part 2
I don't know where you have all these GC problems. There must be a problem with your design. I run real time automation stuff in C#, GC doesn't caused any problem yet. Stride3D docs says, that's if you put a lot of big objects in the heap without reusing them, you will hit big GC pause: https://github.com/stride3d/stride/wiki/On-Garbage-Collection But most of the time it's trivial to reuses those.
- Brought to you by an Electrical Engineer
-
Relaunch of r/stride3d
This could be set as a prominent link somewhere, it is the official stride forums: https://github.com/stride3d/stride/discussions
-
hi i'm new is unity still usable after the whole scandal of the past like 3 weeks or so ? thanks
If you like to develop in C#, the free and open-source game engine Stride is a good alternative. But it really depends on your needs and skill level: https://github.com/stride3d/stride
-
End of the Machinery Game Engine
> ...you are requested to delete The Machinery source code and binaries.
This is pretty weird.
Then again, in regards to the engine itself dying, I feel like this is inevitable for many of the projects out there. For example, there was the Xenko engine which was later renamed to Stride: https://www.stride3d.net/
It's actually a nice project, has lots of great features and feels like it should be a more open alternative to Unity, whilst being similarly easy to use. However, compare the attention it is getting in comparison to something like Godot:
- https://github.com/stride3d/stride
- Why is there a lack of cool repos?
- C# games in Godot, 2022 edition
-
Unity is merging with ironSource
I leave this little thing: https://stride3d.net
BEPUphysics
-
Current state of 2D game code-first frameworks?
The best pure-C# physics library (hands-down) is bepuphysics2, which unfortunately is mainly a 3D physics library, but could be used for 2D if you wanted to get your hands dirty.
- Physics Engine
-
Open Source C++ Physics Libraries for Dedicated FPS Server?
Bepu Physics is pretty good and is written in really optimized C#, the author's blog post are really interesting to read.
-
GJK: Collision detection algorithm in 2D/3D
The usual approach is some form of sweep to get a time of impact. Once you've got a time of impact, you can either generate contacts, or avoid integrating the involved bodies beyond the time of impact, or do something fancier like adaptively stepping the simulation to ensure no lost time.
If the details don't matter much, it's common to use a simple ray cast from the center at t0 to the center at t1. Works reasonably well for fast moving objects that are at least kinda-sorta rotationally invariant. For two dynamic bodies flying at each other, you can test this "movement ray" of body A against the geometry of body B, and the movement ray of body B against the geometry of body A.
One step up would be to use sphere sweeps. Sphere sweeps tend to be pretty fast; they're often only slightly more complicated than a ray test. Pick a sphere radius such that it mostly fills up the shape and then do the same thing as in the previous ray case.
If you need more detail, you can use a linear sweep. A linear sweep ignores angular velocity but uses the full shape for testing. Notably, you can use a variant of GJK (or MPR, for that matter) for this: http://dtecta.com/papers/jgt04raycast.pdf
If you want to include angular motion, things get trickier. One pretty brute forceish approach is to use conservative advancement based on distance queries. Based on the velocity and shape properties, you can estimate the maximum approaching velocity between two bodies, query the distance between the bodies (using algorithms like GJK or whatever else), and then step forward in time by distance / maximumApproachingVelocity. With appropriately conservative velocity estimates, this guarantees the body will never miss a collision, but it can also cause very high iteration counts in corner cases.
You can move a lot faster if you allow the search to look forward a bit beyond potential impact times, turning it into more of a root finding operation. Something like this: https://box2d.org/files/ErinCatto_ContinuousCollision_GDC201...
I use a combination of speculative contacts and then linear+angular sweeps where needed to avoid ghost collisions. Speculative contacts can handle many forms of high velocity use cases without sweeps- contact generation just has to be able to output reasonable negative depth (separated) contacts. The solver handles the rest. The sweeps use a sorta-kinda rootfinder like the Erin Catto presentation above, backed up by vectorized sampling of distance. A bit more here, though it's mainly written for users of the library: https://github.com/bepu/bepuphysics2/blob/master/Documentati...
-
Early Demo of Dynamic Blocky Lighting System
I use https://github.com/bepu/bepuphysics2. I haven't worked with 3d physics engines before so I can't really comment on it's quality but it is definitely an impressive project! The developer is very active and helpful and some of the demo scenes are pretty large and complex.
What are some alternatives?
MonoGame - One framework for creating powerful cross-platform games.
JoltPhysics - A multi core friendly rigid body physics and collision detection library, written in C++, suitable for games and VR applications.
Wave Engine - This repository contains all the official samples of Evergine.
WPF-Samples - Repository for WPF related samples
Xenko
Duality - a 2D Game Development Framework
Nez - Nez is a free 2D focused framework that works with MonoGame and FNA
osu-framework - A game framework written with osu! in mind.
CocosSharp - CocosSharp is a C# implementation of the Cocos2D and Cocos3D APIs that runs on any platform where MonoGame runs.