Project Rebuild Error when Compiling The Starter Game

Lumberyard Discussion Other Support
,
#1

Hi, I’m new to Lumberyard, I selected compile the game code in Setup Assistant and installed all required SDK’s. (Also I have the Visual Studio 2019 Installed with required tools). But when I try to compile the Starter Game I get this error message in the log. I hope you can help me. Thanks

Build failed
Traceback (most recent call last):
  File "E:\Lumberyard\1.27.0.0\dev\Tools\build\waf-1.7.13\waflib\Task.py", line 242, in process
    ret = self.run()
  File "E:\Lumberyard\1.27.0.0\dev\Tools\build\waf-1.7.13\waflib\Task.py", line 86, in run
    return m1(self)
  File "E:\Lumberyard\1.27.0.0\dev\Tools\build\waf-1.7.13\waflib\Task.py", line 86, in run
    return m1(self)
  File "E:\Lumberyard\1.27.0.0\dev\Tools\build\waf-1.7.13\waflib\Task.py", line 86, in run
    return m1(self)
  [Previous line repeated 4 more times]
  File "<string>", line 24, in f
  File "E:\Lumberyard\1.27.0.0\dev\Tools\build\waf-1.7.13\lmbrwaflib\msvc_helper.py", line 257, in exec_command
    return self.exec_command_msvc(*k, **kw)
  File "E:\Lumberyard\1.27.0.0\dev\Tools\build\waf-1.7.13\lmbrwaflib\msvc_helper.py", line 239, in exec_command_msvc
    ret = self.exec_response_command(k[0], **kw)
  File "E:\Lumberyard\1.27.0.0\dev\Tools\build\waf-1.7.13\lmbrwaflib\msvcdeps.py", line 325, in exec_response_command
    sys.stdout.write(os.linesep.join(out) + '\n')
  File "E:\Lumberyard\1.27.0.0\dev\Tools\build\waf-1.7.13\waflib\Logs.py", line 52, in write
    self.stream.write(txt)
  File "E:\Lumberyard\1.27.0.0\dev\Tools\Python\3.7.5\windows\lib\encodings\cp1254.py", line 19, in encode
    return codecs.charmap_encode(input,self.errors,encoding_table)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\ufffd' in position 320: character maps to <undefined>

Process failed with return code: 1
#2

Hey there @Selim_Sandal,

To help me better understand your issue, can you answer a couple of questions about how you got here?

  1. What command did you run that led to this output?
  2. In the SetupAssistant, did you check the box for Visual Studio 2019 on the first page of options?

Thanks