Lumbeyard 1.9 and Asset Processor hanging. Editor not opening

Have you tried turning the machine off and then on again?

If it dosnt work try uninstalling, restarting and then reinstalling

Checking in with our techs as well — sorry for the issue!

REMOVEDUPLOADcapture2.pngcapture.pngI'm having a similar issue when I make a new UI canvas with or without using the sliced assets. I did try the recommendations from the post about running the assetprocessorbatch executable. I don't want to run lumberyard on my C drive but that's seems to be the only difference between me and others that I see that have fixed the issue.

Hey @REDACTEDUSER

@REDACTEDUSER

But it was sad... we had migrated to 1.9 and fixed all the issues in the lvl... suddenly the LY/assets processor stopped... in all machines... so, we had to roll back...

We are using 1.8.1 now and the lvl is pretty full of entities. It is going to be hard to migrate from 1.8 to the 1.9 or maybe version 2... but we are going to do it, do not worry :-)

But now we cannot take the risk ...

@REDACTEDUSER

As we have an event coming soon we are going to wait the event and then after we are going to upgrade the version.

Hey @REDACTEDUSER

4535-rc-log.zip|attachment (3 KB)rc-log.zip@Aman_LY

Ran the batch.exe about 8 times always says it passes. I have attached the RC logs

Good Afternoon,

  I wanted to chime in on this thread for a quick follow-up question. Before you run the AssetProcessorBatch.exe, have you completely stopped all other Lumberyard processes, including the Editor.exe?
When the processor fails the editor may still hang. I would ensure the assetprocessor in the system tray and the Editor.exe are both completely stopped before running it.

@REDACTEDUSER

Looks like I have to keep running assetprocessorBatch until there isn't anything more to process, even though it may say successful. That could be any number of times. Last time I did it, it took me 3 tries. Also I have to do this on ever edit of a canvas. But hey it works. :)

@REDACTEDUSER

Good morning! With the release of 1.9.0.1 this issue should be resolved, please let us know if this is correct!

Good morning! With the release of 1.9.0.1 this issue should be resolved, please let us know if this is correct!

@REDACTEDUSER

New version seems to work like a charm, also feels like the asset processor is running faster

Thank you

That's excellent. Thanks for verifying and letting us know.

New version works for me. Thank you.

After three weeks (vacation) I returned to Lumberyard only to notice my 1.9.0.0 install was broken just like described in this post and several others in this forum. The asset processor breaks. I did a fresh install of 1.9.0.1, but nothing changed. I see randomly all of those errors described in this forum, so I feel I do not need to repeat them again here now. Also, there were several tips to overcome this issue, I think I've tried them all. For example, running the asset processor manually from the command line does not fix the problem.

Sorry for hijacking the thread, but I think this was the most relevant discussion on the topic. I'd be delighted to deliver any logs or what not, just let me know what should I post. I'd really like to continue working with Lumberyard. Thanks.

I respond to myself.

After yesterdays experimentation and debugging I think I found an/the issue. First of all, I do not know why the asset processor fails in the first place. It it able to process a random number of assets and then fails to asserts or timeouts. The key thing is that once it fails, it leaves a dead process in the background named "AssetProcessor_tmp.exe". If this process exists then no further actions can be done with the processor, they are all failing. This process needs to be manually killed and after doing so the next run of the processor has a change to succeed.

I was monitoring this and by making sure there are no bogus AssetProcessor processes in the background, I managed to build all assets by re-trying and now finally 1.9.0.1 editor launches again.

Hey @REDACTEDUSER

Try last answer from this thread: https://forums.awsgametech.com/t/what-is-this-error-in-lumberyard-1-9-does-not-work-1-9/2750/1

Hi @REDACTEDUSER

https://forums.awsgametech.com/t/lumberyard-beta-1-9-0-1-release-available-now/2852/1

Just wanted to give you a heads up!

I posted a question about this a while ago as well. A ticket was filed.

Here's my thread: https://forums.awsgametech.com/t/lumberyard-editor-launch-asset-processor-negotiation-failed/2745/1#comment-15999

Hey @aridias the asset processor (AP) issues you mentioned are a top priority for us and we hope to have a solution for you soon. I definitely understand your reasoning for rolling back and realize that was a tough decision. Please let us know how else we can be of assistance to you - I'm looking forward to seeing what you all are up to =)