Prey 2017 hard crash on level load: memory issue 0x00000000000000

**Game information**
Prey 2017
Arkane Studios

**Distribution name and version where applicable**
```
Fedora release 33 (Thirty Three)
NAME=Fedora
VERSION="33 (Workstation Edition)"
ID=fedora
VERSION_ID=33
VERSION_CODENAME=""
PLATFORM_ID="platform:f33"
PRETTY_NAME="Fedora 33 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:33"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f33/system-administrators-guide/"
SUPPORT_URL="https://fedoraproject.org/wiki/Communicating_and_getting_help"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=33
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=33
PRIVACY_POLICY_URL="https://fedoraproject.org/wiki/Legal:PrivacyPolicy"
VARIANT="Workstation Edition"
VARIANT_ID=workstation
Fedora release 33 (Thirty Three)
Fedora release 33 (Thirty Three)
cpe:/o:fedoraproject:fedora:33
```

**Flatpak info**
```
Flatpak 1.8.2
nvidia-455-28
default
host
```

**Problem description**
- Configure Prey 2017 to use Proton 5.0-9
- Starting a new Singleplayer game
- ```Attempt to read from address 0x0000000000000000 The memory could be "read"```

**Does this issue reproduce with native Steam**
No, native Steam works.

Reproduce the reported crash by starting a new Prey 2017 single-player game with Proton 5.0-9 on Fedora 33 and the listed Flatpak/NVIDIA setup. Compare the result with native Steam, which the report says works; done would require identifying and resolving the level-load crash, but the issue names no files or tests.

Written by the indexing model from the issue text.