- Newest
- Most votes
- Most comments
Hello @REDACTEDUSER
I've seen this behavior before. It is usually due to the use of symbolic links or shortcuts which the AssetProcessor does not handle properly. I would recommend against using symbolic links.
Hope that helps.
Thanks, looks like that is the case. The project folder was indeed a symlink; placing the real directory in the dev' folder fixed it. I remember finding a post on these forums stating that that is the approved way to have a project live elsewhere than the
dev' directory (unfortunately, cannot find it now) but it was quite old - possibly outdated, possibly never worked.
I've posted a follow-up to this question (hoping to finally achieve my goal of having game projects outside of the dev directory): https://forums.awsgametech.com/t/how-to-use-functionality-which-allows-creating-your-game-project-directory-outside-of-the-lumberyard-engine-directory-with-an-existing-project/4755/1
This post is closed: Adding new answers, comments, and votes is disabled.
Relevant content
- Accepted Answerasked 7 years ago
- Accepted Answerasked 7 years ago
- asked 7 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated a year ago