So. After a small investigation, the following results. After downloading and installing the old version 1.18 - everything is installed without errors. When you build a project in version 1.19, you do not automatically create a solution for VS2017.
Run command in terminal: .\lmbr_waf.bat msvs -p game
1.18 - is success
1.19 - is error: Skipping platform 'win_x64_vs2017' because it is not installed properly for this version of visual studio Unable to generate solution for 'Visual Studio 2017'. Make sure it is installed and enabled in Setup Assistant. Skipping visual studio solution generation
Even if I did something wrong, it's likely to go unanswered. I guess I shouldn't be doing anything at all. https://techraptor.net/content/amazon-game-studios-struggling-due-to-lumberyard-engine
So I accepted this answer as the only true one.
Now lmbr_waf configure revived to generate the vs2017 solution file.
I have the same issue as yours after I update to the vs2017 version 15.9.14.
I re-installed vs2017 and Lumberyard but still get the following warning.
So, I decided to go back to vs2015 until they resolve this issue.
My vswhere output.
C:\Program Files (x86)\Microsoft Visual Studio\Installer>"C:\Program Files (x86)\Microsoft Visual Studio\Installer\vswhere.exe" Visual Studio Locator version 2.5.2+gebb9f26a3d [query version 22.214.171.124008] Copyright (C) Microsoft Corporation. All rights reserved. instanceId: 125cbc17 installDate: 2/5/2019 10:59:30 AM installationName: VisualStudio/15.9.14+28307.770 installationPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community installationVersion: 15.9.28307.770 productId: Microsoft.VisualStudio.Product.Community productPath: C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\devenv.exe isPrerelease: 0 displayName: Visual Studio Community 2017 description: Free, fully-featured IDE for students, open-source and individual developers channelId: VisualStudio.15.Release channelUri: https://aka.ms/vs/15/release/channel enginePath: C:\Program Files (x86)\Microsoft Visual Studio\Installer\resources\app\ServiceHub\Services\Microsoft.VisualStudio.Setup.Service releaseNotes: https://go.microsoft.com/fwlink/?LinkId=660692#15.9.14 thirdPartyNotices: https://go.microsoft.com/fwlink/?LinkId=660708 updateDate: 2019-07-13T00:08:19.298205Z catalog_buildBranch: d15.9 catalog_buildVersion: 15.9.28307.770 catalog_id: VisualStudio/15.9.14+28307.770 catalog_localBuild: build-lab catalog_manifestName: VisualStudio catalog_manifestType: installer catalog_productDisplayVersion: 15.9.14 catalog_productLine: Dev15 catalog_productLineVersion: 2017 catalog_productMilestone: RTW catalog_productMilestoneIsPreRelease: False catalog_productName: Visual Studio catalog_productPatchVersion: 14 catalog_productPreReleaseMilestoneSuffix: 1.0 catalog_productRelease: RTW catalog_productSemanticVersion: 15.9.14+28307.770 catalog_requiredEngineVersion: 1.18.1049.33485 properties_campaignId: 1979421144.1544487226 properties_channelManifestId: VisualStudio.15.Release/15.9.14+28307.770 properties_nickname: properties_setupEngineFilePath: C:\Program Files (x86)\Microsoft Visual Studio\Installer\vs_installershell.exe
Sorry for the frustration this has caused, you are not alone and we are actively working to make this process easier (https://forums.awsgametech.com/t/cant-compile-with-visual-studio-2017-15-9/5985/1, https://forums.awsgametech.com/t/1-15-1-16-perfectly-clean-remove-and-newly-installed-but-there-was-a-build-error/5975/1, https://forums.awsgametech.com/t/visual-studio-2017-compile-problems/6794/1). The most likely reason is due to the Visual Studio version you have installed being newer than any version we tested with Lumberyard. @REDACTEDUSER
To resolve this issue we need to modify your build settings file
- Open a command prompt and navigate to your Lumberyard dev folder
- Run the command to generate a build settings file if you don't already have one lmbr_waf configure
- Open dev/WAF/user_settings.options with your favorite text editor
- Find the following line which specifies the valid versions of visual studio 2017 ;win_vs2017_vswhere_args = -version [15.7.27703.2035,15.9.28307.665] Change it to this which allows all of 'em. NOTE: make sure to remove the semi colon at the beginning of the line win_vs2017_vswhere_args = -version [15.7.27703.2035,16]
- Back in your command window run lmbr_waf configure After this, your version of Visual Studio should be properly detected.
Adding new answers, comments, and votes is disabled.
Unable to generate solution for Visual Studio 2017asked 3 years ago
Cannot install Visual StudioAccepted Answerasked 6 years ago
Lumberyard support for visual studio 2017Accepted Answerasked 6 years ago
Unable to create a new projectasked 3 years ago
Help. Lumberyard does not recognize visual studio 15Accepted Answerasked 5 years ago
Visual studio 2017 compile problemsasked 3 years ago
When typing lmbr_waf.bat build_win_x64_vs2015_release -p all i get an errorAccepted Answer
[ERROR] No eligible platforms supported for visual studio solution generation HELP!Accepted Answer
AWS Toolkit SSO on Visual Studio 2022 - Assembly AWSSDK.SSOOIDC could not be foundasked 5 months ago
Failing to make a new project at the Visual studio solution stage. HELPAccepted Answerasked 5 years ago