Skip to content
This repository has been archived by the owner on Oct 4, 2022. It is now read-only.

Asset Processor launching failed if run Editor from vs2017 debug mode #503

Open
sainimu78 opened this issue Jul 20, 2020 · 1 comment
Open

Comments

@sainimu78
Copy link

Describe the bug
Asset Processor launching failed if run Editor from vs2017 debug mode. There is no this issue if run Editor from SetupAssistant.bat.

Steps to reproduce
1.Create a new project in Configurator, and enable PhysX Sample Gem.
2.Rebuild Project in Configurator (I don't know which project the Configurator was bulit)
3.Open dev/Solution/myproject_vs2017.sln and select [All] debug configuration then build it.
4.Start debugging Editor, few minites later, Asset Processor pop up this error

Expected behavior
Please provide a concise description of what you expected to happen.

Screenshots/Logs


Status: Initializing Gem...Gem.StarterGame.0c2c51b1d69d4700a3c078f9d52dd37f.v0.2.0
Error
X An error occurred while loading gems.
..........
.........
.........
.........
Full error text:
Failed to load dynamic library at path "f:/Fts/Proj/Test/lumberyard/lumberyard_1_25/dev/Bin64vc141.Debug/Gem.GameState.1a557ac19dc34f5697fe03f30be5b6e4.v0.1.0.dll".

Lumberyard version
v1.25.

@AMZN-puvvadar
Copy link

Hi @sainimu78 ,

We typically see this type of error when a project's configuration specifies a Gem but it is not built. Is the GameState Gem enabled in your Project Configurator?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants