Skip to content
This repository was archived by the owner on Oct 4, 2022. It is now read-only.
This repository was 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

@sainimu78

Description

@sainimu78

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions