Talk:NieR: Automata

About this board

Debug build (dated March 22, 2017)

Aemony (talkcontribs)

This information is not really relevant to store on the main article page itself seeing how it is even more distance from the latest version of the game than it was before, so it is instead documented here for a semi-easy way for possible modders or users to access it if they so desire.

Owners can download a debug build of the game dated to March 22, 2017 10:31:47 UTC. This version includes separate and more extensive debug menus, with an event teleporter along with achievement and save editors. Achievement removal is also possible. This version is outdated and should not be used for regular play. It is included here for completion's sake as it might be relevant for modders or some players.
A full additional game download is required so 50 GB free space is required on the drive the depot build gets downloaded to.
Controller is required to access some of the debug menus.
Use DepotDownloader to download the debug version[1]
Disclaimer: The tool requires your Steam username, password, and Steam Guard authentication token to function. PCGamingWiki cannot make any guarantees regarding the safety of the tool. Use at your own risk!
  1. Download the latest version of DepotDownloader and extract it to any location.
    • By default downloads will be stored in a subfolder of DepotDownloader so be sure to extract it to a drive with enough space to download all files (50 GB).
  2. Navigate to the extraction target folder where DepotDownloader.exe is located.
  3. Hold down Shift and right click in the folder itself, without selecting any specific files.
  4. If done correctly a few new option will be available in the context menu
  5. Select the Open Powershell window here option.
  6. Enter the .\DepotDownloader.exe -app 524220 -depot 524221 -manifest 1677719970409151957 -username <username> -password "<password>" -validate command with relevant info:
    • <username> is your Steam username (not to be confused with your profile name).
    • <password> is the password of your Steam account.
    • -dir <installdir> can also be used to specify a custom download target folder.
  7. If the account is protected using Steam Guard, the window will prompt for the two-factor authentication code displayed on your authenticator app.
  8. If executed properly the console will say:
    Downloading depot <depot-id> - <depot description>
  9. Wait for the download to complete. Do not close the window or shut down the computer as this will terminate the download!
  10. When the download is finished the following line will be printed in the console:
    Depot <depot-id> - Downloaded <size> bytes
  11. The downloaded files will be saved in the specified folder, typically in a subfolder called depots\<depot-id>\<build-id> below DepotDownloader.
  12. Open indicated download folder. You can now move the contents of the folder to a more proper location.
  13. Run NieRAutomata.exe from the folder to launch the debug build.
  14. After the intros have played use RB+Back on a controller to open the debug pages. Some settings requires the A button to be held down while using +++ on the controller to change the value. Others use the keyboard and +++, PageUp+PageDown, or Enter to navigate.
  1. Verified by User:Aemony on 2018-04-01
    I found this.
Reply to "Debug build (dated March 22, 2017)" (talkcontribs)

"Display driver crash (white/frozen screen)" "ERROR: Graphic::Startup () FAILED No Graphic Memory" "Game crashes during ending E on the 21st death"

All of these appear to be purely technical issues reported for the old PC port, and should no longer be relevant for the current version of the game, unless proven otherwise.

Aemony (talkcontribs)

Display driver crash (white/frozen screen)

This is still being evaluated.

ERROR: Graphic::Startup () FAILED No Graphic Memory

This is something I've still heard users experiencing.

Game crashes during ending E on the 21st death

This needs actual testing before we remove it since QLOC so far haven't bothered implementing any gameplay related changes, so it's unlikely this bug has been fixed.

Reply to "Issues unresolved"
Aemony (talkcontribs)

Contrary to what one might assume, a game whitelisted by Valve/Steam for use with Steam Play/Proton does not constitute official support by the developers/publishers, and as such Linux support should not be listed on the PCGW article.

> Q: I'm a developer; my game got whitelisted in Steam Play; does this mean I have to support an additional platform?

> No; if a game was whitelisted as a result of our testing, we've assessed the experience to be identical (save for an expected moderate performance impact). Users playing through Steam Play experiencing Linux-specific issues should be directed to Steam for support. Keep in mind users were most likely already playing your game using Wine; you just have better visibility into it now.


PCGamingWiki currently does not include any form of flagging whether a game is supported by Steam Play/Proton yet or not, but that sort of support does not replace proper official Linux support, same as Wine does not replace proper Linux support (unless the publisher/developer themselves ships a Linux build of the game that includes Wine, that is). To see whether a game is supported by Steam Play/Proton or not, should be used instead.

Perhaps in the future PCGW will implement some form of listing what level of support Steam Play/Proton have for a game from Valve's side of things, but right now it's an entirely separate thing from the platform seen as "Linux".

Reply to "Re: Steam Play/Proton support"

FAR main thread was removed. A new thread have been created

Aemony (talkcontribs)

I've already updated the main links pointing to the old thread with the new link, but 8 or so references seems to be broken. I'm going to have to think of the best way to solve those.

Aemony (talkcontribs)

Wayback Machine haven't captured any URL from the whole domain, so that's out of the question.

Aemony (talkcontribs)

Over the past months I've went through all broken references and either found new ones or removed the references I deemed unneeded (mostly unnecessary references made after occasional tidbit of info that didn't change the main subject). Most references where changed within the last hour as I replaced a ton with a reference to my tweak guide which covers a lot of the missing references.

All references to the old thread is now gone.

Reply to "FAR main thread was removed. A new thread have been created"
Link Satonaka (talkcontribs)

Not sure where to fit this into the article, but setting DX10+DX11 SLI compatibility bits to 0x080002F5 is a significant tweak of note. I have 2x GTX680; in order to get 60fps on just one, I had to lower most settings and lower the resolution to 720p (down from my native 1080p). With SLI enabled, I get 1080p@60 with most of the settings set to their highest values. Fullscreen required to work. My reported results are without FAR.

Aemony (talkcontribs)

I've added a new section under "Issues fixed" for now with clear information about the unsupported nature of the SLI fix.

Reply to "SLI Compatibility Bits"
There are no older topics