Stride samples/4.4.0 Released
Stride samples/4.4.0 ships alongside Stride 4.4.0-beta8 and reads like a major maintenance release for the engine’s sample ecosystem. Stride’s GitHub release notes show a wide sweep of template, build, and test work aimed at making the samples easier to generate, validate, and keep in sync with the engine.
The headline addition is a new 2D Platformer template, plus asset packs for New Game as dotnet new item templates. The template system was reworked around a transform-based -devN flow, and the legacy template system was retired. In practice, that should make sample creation and version bumps more predictable for teams building on Stride’s starter content.
There’s also a substantial project-format migration: solutions move from .sln to .slnx, Stride.Sdk is renamed to Stride.Build.Sdk to reserve the former name for future user-facing use, and the samples are updated for .NET 10. The release also cleans up packaging and asset handling, including git-lfs tracking for binary art files, package-prefix fixes, and skipping empty collections when saving .sdpkg files.
On the sample side, several demos were fixed or stabilized, including AsyncCollisionTriggerDemo, LoadingContentDemo, SpaceEscape, Material Shader Demo, and BepuSample. The test pipeline got a major overhaul too, with screenshot comparison harnesses, AOT publish/run coverage, Linux/macOS host support, and hang-dump capture on teardown timeouts. For developers, this release is mostly about smoother onboarding, fewer sample regressions, and a more modern build/test workflow.
- what
- Stride samples/4.4.0 released for Stride 4.4.0-beta8 with major sample, template, build, and test updates.
- what
- Adds a new 2D Platformer template and asset packs for New Game as dotnet new item templates.
- what
- Migrates solutions from .sln to .slnx and renames Stride.Sdk to Stride.Build.Sdk.
- impact
- Teams using Stride samples/templates may need to update project files, template workflows, and .NET 10 compatibility.
Big usability and workflow improvements, despite migration churn
Follow stride updates
See relevant stories in your personalized news feed.
Discussion