stride3d / stride3d/stride-docs
Building GameStudio with different graphics API
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 39
- Forks
- 74
- Avg merge
- 3h 36m
- Merged PRs (30d)
- 2
Description
Some documentation to add for building Game Studio with source.
Problem:
https://discord.com/channels/500285081265635328/500290856532574209/1395829713569579149
Azeno: Anyone any hints on how to debug the Direct3D12 code? I did set <StrideGraphicsApiDependentBuildAll>true</StrideGraphicsApiDependentBuildAll> in Stride.props, Visual Studio says the related code is in play, in my sample I game I set <StrideGraphicsApi>Direct3D12</StrideGraphicsApi> but when running the editor and opening that game with it, no breakpoints are hit. I must be doing something fundamentally wrong.
Solution:
https://discord.com/channels/500285081265635328/500290856532574209/1396105042762928268
Azeno: Ok, had to add <StrideGraphicsApi>Direct3D12</StrideGraphicsApi> to Stride.GameStudio, now it picked it up.
Contributor guide
No contributing guide indexed for this repository
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 reviewing the repository's existing build instructions and the linked Discord discussion, then check how Stride.props and Stride.GameStudio are described. Document that building and debugging with Direct3D12 requires setting the Stride.GraphicsApi property for Stride.GameStudio; done means the source-build instructions explain this configuration clearly.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100