4 Answers
- Newest
- Most votes
- Most comments
0
Hello @REDACTEDUSER
Have you tried running the Asset Processor as an Administrator? I experienced the same issue when I was using AppStream 2.0 as well.
Let me know.
Thanks!
answered 6 years ago
0
So, I decided to just straight up try running the Lumberyard Editor as an administrator hoping that the permission would be inherited by the Asset Processor, and it worked :D
Thanks for the help!
answered 6 years ago
This post is closed: Adding new answers, comments, and votes is disabled.
Relevant content
- asked 7 years ago
- Accepted Answerasked 7 years ago
- Accepted Answerasked 7 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago