[Graphics] Clarify exceptions from selected API lacking support to run effects and other logic
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.
See title, loads of issues relate to this be it when the asset compiler runs or at runtime. Implementing this whole thing won't be pretty but we could at least catch and inspect exceptions to provide more info based on that.
See #524 , #459, #51, #584, #198
Describe the solution you'd like
See https://github.com/stride3d/stride/issues/524#issuecomment-543786768
Describe alternatives you've considered
git stash :)
Additional context
See issues mentioned above.
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 reviewing the linked issues #524, #459, #51, #584, and #198, especially the solution discussion in #524. Trace the selected API failures during asset compilation and runtime, then define what additional exception information should be exposed in both cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- computer-graphics, game-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100