[Linux] Issue tracker for Stride Engine Samples
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
Description
Commit hash at the time of verification : 76572689ca71c733eebcdd84e5ea5e6ae148a7cd or 4.4.0.2
Context
At the current state Stride 3D enables you to build you games on Linux...kind of. While is possible to build your game it may not be possible to run it because of many different runtime issues. The goal is to make clear which samples can be run and which do not work.
List of Samples
-
Audio
- Simple audio - App crashes on image click
-
Graphics
- AnimatedModel
- CustomEffect
- MaterialShader
- SpriteFonts
- SpriteStudioDemo
-
Games
- JumpyJet
- SpaceEscape
-
Input
- Gravity Sensor
- Touch Inputs - not sure about GamePad though
-
Particles
- ParticlesSample - Game crashes
-
Physics
- Physics Sample
-
Templates
- Platformer2D
- First Person Shooter - Works but animations are glitched
- Third Person Shooter
- Top Down RPG
- VR Sandbox - "Shader Texture2DMS could not be found"
-
Tutorials
- CsharpBeginner - Game freezes for a few seconds and crashes
- CsharpIntermediate - same as above
-
UI
- GameMenu
- UIElementLink -
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt - UIParticles -
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
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 checking out commit 76572689ca71c733eebcdd84e5ea5e6ae148a7cd (4.4.0.2) and running the listed Stride samples on Linux. Recheck the unchecked samples and the noted crashes, freezes, animation glitches, and shader or access-violation errors. Done means the checklist clearly records which samples run and which remain broken, with current failure details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, linux
- Domain
- game-dev, operating-systems, testing-qa
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100