Duplicate Shader Key Files
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 7.8k
- Forks
- 1.2k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 49
Description
after upgrading from xenko 2.1 all custom shaders in visual studio 2017 have duplicate key files. at least game studio thinks so, although they are not actually present on disk. is there any order of things i can do to fix that? or how would i upgrade my project that this doesn't happen? i could reset the git repo and start the upgrade process again, but in which order should i open/upgrade/save the project files in game studio and visual studio?
EDIT: i have to add, the project was a VS 2015 solution. the errors occurred with 2017. currently trying to get the 2.1 version of the project running with VS 2017 and then i'll try another upgrade.
these are the errors:
then on build:
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 reproducing the upgrade from a Xenko 2.1 project created with Visual Studio 2015, using Visual Studio 2017 and Game Studio as described in the issue. Compare the reported duplicate shader key-file errors with the project state on disk; done means the custom shaders no longer appear duplicated and the project builds successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- build-system, game-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100