Cannot create new project in fresh install of lumberyard

I just installed lumberyard, ran the setup assistant, and once everything looked good, hit the “configure project” button on the summary page. I want to start a new project so I can follow some online tutorials, so I hit “create new”. I give it the creative name of “TestProject”, then it takes a while creating and configuring, and then it reports an error in the “Building Project” step after several warnings.

Here’s the error log – it seems to be warning me that “StarterGame” is the enabled game for this build, rather than the “TestProject” – do I need to do some kind of configuration for my new project prior to hitting the create new button? It then warns that it’s unable to find QT, though the setup assistant reported everything installed – do I need to do some kind of QT setup that isn’t being done by the SetupAssistant? And then it crashed with a python stacktrace, which may or may not be related to the previous warnings. I’ve attached screenshots from SetupAssistant, in case someone can find clues there.

  "C:\Amazon\Lumberyard\1.18.0.0\dev\lmbr_waf.bat" build_win_x64_vs2017_profile --enabled-game-projects=TestProject -p TestProject
[WAF] Engine Root: C:\Amazon\Lumberyard\1.18.0.0\dev\
A custom BuildEnv.json file was not found. This build will be untagged.
A custom BuildEnv.json file was not found. This build will be untagged.
default_settings: using option bootstrap_tool_param: "--enablecapability compilegame --enablecapability runeditor --enablecapability rungame --enablecapability vc141 --enablecapability windows" from _WAF_/user_settings.options (default: "")
default_settings: using option generate_vs_projects_automatically: "false" from _WAF_/user_settings.options (default: "True")
default_settings: using option msvs_version: "15" from _WAF_/user_settings.options (default: "14")
default_settings: using option enabled_game_projects: "TestProject" from command line args (default: "StarterGame,CloudGemSamples")
default_settings: using option win_vs2017_winkit: "10.0.17763.0" from _WAF_/user_settings.options (default: "")
default_settings: using option win_vs2015_winkit: "10.0.17763.0" from _WAF_/user_settings.options (default: "")
[WAF] Executing 'build_win_x64_vs2017_profile' in 'c:\Amazon\Lumberyard\1.18.0.0\dev\BinTemp\win_x64_vs2017_profile'
default_settings: using option bootstrap_tool_param: "--enablecapability compilegame --enablecapability runeditor --enablecapability rungame --enablecapability vc141 --enablecapability windows" from _WAF_/user_settings.options (default: "")
default_settings: using option generate_vs_projects_automatically: "false" from _WAF_/user_settings.options (default: "True")
default_settings: using option msvs_version: "15" from _WAF_/user_settings.options (default: "14")
default_settings: using option enabled_game_projects: "TestProject" from command line args (default: "StarterGame,CloudGemSamples")
default_settings: using option win_vs2017_winkit: "10.0.17763.0" from _WAF_/user_settings.options (default: "")
default_settings: using option win_vs2015_winkit: "10.0.17763.0" from _WAF_/user_settings.options (default: "")
[WARN] Game folder 'StarterGame' configured in bootstrap.cfg is the enabled game for this build. In order to run or debug for the game 'TestProject', they need to be set in bootstrap.cfg under the 'sys_game_folder' entry accordingly
[WARNING] Incredibuild disabled by build option
[WARN] 3rd Party alias 'qt' specified in c:\Amazon\Lumberyard\1.18.0.0\dev\Code\Tools\Woodpecker\wscript:56 (build) is not enabled. Make sure that at least one of the following roles is enabled: []
[WARN] 3rd Party alias 'qt' specified in c:\Amazon\Lumberyard\1.18.0.0\dev\Code\Tools\Woodpecker\wscript:104 (build) is not enabled. Make sure that at least one of the following roles is enabled: []
unable to find QT
unable to find QT
Traceback (most recent call last):
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 226, in waf_entry_point
run_commands()
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 342, in run_commands
ctx = run_command(cmd_name)
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 319, in run_command
ctx.execute()
File ".\Tools\build\waf-1.7.13\lmbrwaflib\msvs.py", line 1943, in override_build_state
old(ctx)
File "c:\Amazon\Lumberyard\1.18.0.0\dev\wscript", line 469, in execute
return execute_method(self)
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Scripting.py", line 696, in execute
return execute_method(self)
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 254, in execute
self.execute_build()
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 277, in execute_build
self.compile()
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 370, in compile
self.producer.start()
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Runner.py", line 307, in start
self.refill_task_list()
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Runner.py", line 209, in refill_task_list
self.add_outstanding_tasks(next(self.biter))
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 818, in get_build_iterator
self.post_group()
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\Build.py", line 789, in post_group
f()
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\build\waf-1.7.13\waflib\TaskGen.py", line 218, in post
v()
File "Tools\build\waf-1.7.13\lmbrwaflib\cry_utils.py", line 894, in add_compiler_dependency
if os.path.isabs( self.env['CC'] ):
File "C:\Amazon\Lumberyard\1.18.0.0\dev\Tools\Python\2.7.12\windows\lib\ntpath.py", line 59, in isabs
return s != '' and s[:1] in '/\\'
TypeError: 'in <string>' requires string as left operand, not list
Process failed with return code: 1

Hi @DeadlyGazebo,

When you run through SetupAssistant, on the get started page, what happens if you click ‘Compile the Engine And Asset Pipeline’ and ‘Compile the Lumberyard Editor and Tools’? To create a new project in Lumberyard, you generally need to have the ability to compile the engine completely. If you are missing a piece, errors like this will pop up. Let us know if changing these settings works for you!

We are seeing the same error here. In our case with the options set for compiling the full pipeline.

This is a fresh install of Ly, using VS 2017 (latest). No prior version of LY was installed on this machine.

Same error also happens attempting to build the StarterGame sample with

lmbr_waf build_win_x64_vs2017_profile -p all

Note: On another machine which previously had older versions of Ly, this error does not happen.

Same error still occurs with 1.19. In this case installed on the machine having issues with 1.18.

@DeadlyGazebo

I was able to work around this bug by setting

win_vs2017_vswhere_args = -version [15,16]

in

dev_WAF_\user_settings.options

1 Like

Same error still occurs with 1.20 but win_vs2017_vswhere_args = -version [15,16] solves the problem.

1 Like
  • Same error still occurs with 1.21.1 but win_vs2017_vswhere_args = -version [15,16]
    as said above, solves the problem.
  • Also the shortcuts pointing to Bin64vc140, when VS 2017 is used instead, are misleading.