- Newest
- Most votes
- Most comments
I SORTED IT OUT!!!!!!!!!!!! and this may help others with similar issues.
OK If you have an issue like mine you will need to follow these instructions in this order.
-
Uninstall Lumberyard.
-
Go to the C: drive and delete the Amazon folder.
-
Go to the registry location and delete the entire Amazon entry at \HKEY_CURRENT_USER\SOFTWARE\Amazon. Not just the lumberyard entry folder.
-
In the start menu right click on one of the dead shortcuts. select "more" then select "Open File Location." Go up one folder and delete the entire start menu Lumberyard folder. (very Important)
-
Go to your user folder (where the pics, videos, documents folders are.) and look for the folder
LyMetricsCache. If it is still there. DELETE IT! as well as any Lumberyard files that are still lingering such as lumberyard_editor_stylesheet.qss and lumberyard_stylesheet.qss
-
Empty trash!
-
Restart!
-
Download and install Lumberyard again and do not choose the customer option.
When it asks you if you want to start it choose YES!. once it has completed asks you if you want open a level or create one you can do what ever you want at that point!
YOU DID IT!
Every step is important. If you do not delete something then Lumberyard will not over write the old file and it will fail!
Hey @REDACTEDUSER
I've created a ticket to have a tech take a look at this.
You can try this:
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.
Hello @REDACTEDUSER
Can you please include the logs under Bin64vc140\Logs folder? Also if possible if you can include the assetdb.sqllite file located in the dev\Cache{ProjectName} folder?
Thank you!
There are two folders that start with that name. Bin64vc120 and Bin64vc140 I ran the ssetProcessorBatch.exe in the vc120 folder and received the same string of errors. It did not complete so running the editor.exe was not done. When I ran the one in the Bin64vc140 folder and it produced the "system_thread_exception_not_handled" Blue screen of death and restarted the computer.
4704-logs.zip|attachment (1.06 MB)logs.zip
Here are the logs. I have zipped all files into one. A little explanation.
I have included both the sample project and starter game .sqlite files. I have not been able to get to the point of creating my own.
I included all folder and files under the location
C:\Amazon\Lumberyard\1.9.0.1\dev\Bin64vc140\logs
I think I need to include another explanation here. I did have a new project named IRI. However I uninstalled everything and installed the new 1.9.1 hoping to get a better result. However to my dismay it was the same result. So I have not gone as far as creating another one.
Am I becoming obsessed? lol
OK so I am still playing with it. I started using Microsoft Visual Studio to attempt some debugging. What I have noticed is that when I launch from the Lumberyard editor on the desktop it actually ends up attempting to find the AssetProcessor.pdb in the Bin64vc120 folder and if I am not mistaken it should be in the Bin64vc140 folder. Also That .pdb does not exist in either. I also launched the asset processor in the Bin64vc140 directly and got the same error and same debug info accept this time it did in fact look in the correct folder.
furthermore: ready for this? I can now get the FeatureTests and MultiplayerSample to launch and run. But nothing else.
I still say the thing is looking for the database in d:\ly\workspace\PKG_v1_9.........
Probably from the Dev that compiled the thing working from the D drive. And then not giving it a variable to look in the correct directory.
could this be the code causing the problem? The very last line? (from the setup assistant batch file)
SET launchOverrideCommand=%1 SET launchOverrideValue=%2
REM Locate the first available MSVC Built Setup and binary folder
SET workingDir=".\dev\Tools\LmbrSetup\Win"
IF NOT "%1"=="" ( IF "%1"=="-workingDir" ( SET workingDir=%2 ) )
REM Some tooling, like the installer, may pass in extra slashes. SET workingDirStrippedBack=%workingDir:\=% SET workingDirStripped=%workingDirStrippedBack://=/% start /d %workingDirStripped% SetupAssistant.exe
Wow, that's not a very good user experience. I've added these steps to the ticket to get this addressed. Sorry you had such an issue. Thank you for sharing your resolution steps with us.
This post is closed: Adding new answers, comments, and votes is disabled.
Relevant content
- asked 2 years ago
- asked 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago