Lumberyard Editor Launch: Asset Processor Negotiation Failed

Question

Hey everyone,

I'm brand new to Lumberyard, so please bear with me.

After Installing, going through the Setup Assistant, and setting up the prerequisites for the tutorial at http://docs.aws.amazon.com/lumberyard/latest/developerguide/network-multiplayer-gs.html, I launched the Lumberyard Editor and receive this error:

*An attempt to connect to the game or editor has failed. The game or editor appears to be running from a different folder. Please restart the asset processor from the correct branch.*

I then went ahead and set some other project in the Project Configurator as "default" and launched the Lumberyard Editor and received the same error. The only one that seemed to succeed (1 time that I can remember), was the SampleProject. Also, when I go to the AssetProcessor.exe, I get the same error, but since I can see what jobs are being processed I'm able to see that most of the jobs are "pending", but the same three are always "processing":

1. Slider.slice
1. Test.slice
1. TooltipDisplay.slice
I also re-installed Lumberyard thinking I did something wrong, but that didn't work. I tried changing my %TMP% location temporarily to see if file paths were too long. I also deleted the Cache folder in the dev/ file location and retried. No logs were shoing up in the Cache/PROJECT/pc/user/log/ location either.

Incase you're curious of my file path lengths:

*C:\Amazon\Lumberyard\1.9.0.0\dev*

*C:\Users\AustinK-xxxxxxxxxx\AppData\Local\Temp*

EDIT: In case you didn't notice in my file path, I'm using Lumberyard v1.9

Thanks!

Austin

Accepted Answer

Hi all, sorry for the issues. I've created a support ticket to help get this sorted out.

Answer

Sorry i have the seam problem and that did not help me.

Answer

Awesome! Thanks for the update and so sorry for the issues. Keep me posted.

Answer

It might be worth trying this. Not sure if it is the same issue but it's worth a shot.

*The
current work around is to end the asset processor task, go into your LY dev
folder, then into the primary Visual Studio associated Bin64vc... folder and
run **AssetProcessorBatch.exe**. Once the process within the
AssetProcessor window is complete, go ahead and try the Editor.exe again and
see if it works.*

Answer

Hey @REDACTEDUSER

Answer

Hi Binky_LY. One more the [seam problem ](https://forums.awsgametech.com/t/cannot-open-lumberyard-1-9/2775/1). Maybe this help, in asset processor showing that error.

REMOVEDUPLOAD

Answer

We are still working on a solution to this issue and I *think* we will be deploying a patch in the next day or so. Hang tight and sorry for the delay.

Answer

Hey @REDACTEDUSER

Answer

Alright, cool. Is it possible to link your original answer to a ticket url so I can just mark your answer as accepted?

Answer

The 1.9.0.1 should fix the asset processor issues. Can you give it a try and let us know if it does not help?

Answer

yeah. For sure.

Answer

I just want to say I am having the same problems, but I see you guys may be working on it already.
Thanks for filing a ticket.

Answer

This worked to get me moving forward. I've run into another issue I think having to do with trying to open a new project that hasn't been built yet, so I'm following [https://s3.amazonaws.com/gamedev-tutorials/Tutorials/Programming-Basics-%2802%29_Compiling_the_Engine_Editor_and_Game.pdf](https://s3.amazonaws.com/gamedev-tutorials/Tutorials/Programming-Basics-%2802%29_Compiling_the_Engine_Editor_and_Game.pdf) to get it going. I think it's an old version, but it's working so far.

Answer

Will there be any responses on progress or what the issue may be on this thread? Should I download an older version of Lumberyard for now?

Answer

Hi. This negation error started to appear and now I cannot launch the editor.

Any ETA of a patch ? fix ?

Does the 1.9.0.1 fixes this ?

Thanks and continue the great work!

Nick

Answer

I'm having the same problem, editor always 'hangs' at the line showing slice, line number ( compilation ) 149 .

Answer

Kill the process with AssetProcessor.tmp and restrart AssetProcessorBatch

Lumberyard Editor Launch: Asset Processor Negotiation Failed

Relevanter Inhalt