You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steam versions use the Documents directory to store saves and other configuration information. This directory cannot be moved or renamed. If the username has a character that's more than 8 bits, FFNX can't read anything from a path containing it.
To Reproduce
Steps to reproduce the behavior:
Have a local username with a >8 bit character in it that is in the user's home directory in c:\users\ .
Install Steam FF7 or FF8.
Run it once.
extract FFNX to installation
Run the game exe
FF7_en.exe immediately crashes with an unhandled exception because it can't read metadata.xml and doesn't even check for this case, just as if you've never ran it on steam. Because there is no exception handler, nothing even gets logged past [TRACE]Metadata: Initializing manager.
Expected behavior
The game starting.
Screenshots
from a foreign person with this issue on his desktop.
GPU
Irrelevant, the crash has nothing to do with graphics.
Additional context
This was a real pain to track down, because there is no exception handler for this particular case. And users can't simply rename their home directory to work around it, so at the very least an exception handler should be placed it to reveal this happening, so the user can create a symlink to what FFNX thinks the path is.
The text was updated successfully, but these errors were encountered:
Describe the bug
Steam versions use the Documents directory to store saves and other configuration information. This directory cannot be moved or renamed. If the username has a character that's more than 8 bits, FFNX can't read anything from a path containing it.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The game starting.
Screenshots
from a foreign person with this issue on his desktop.
GPU
Irrelevant, the crash has nothing to do with graphics.
Additional context
This was a real pain to track down, because there is no exception handler for this particular case. And users can't simply rename their home directory to work around it, so at the very least an exception handler should be placed it to reveal this happening, so the user can create a symlink to what FFNX thinks the path is.
The text was updated successfully, but these errors were encountered: