[#3904][FREEZE][7.5] Freeze on clicking "Get Up" during Graph 2 final mission - Fixed in 7.60 Beta 6

Ask here if you experience technical problems with X4: Foundations.

Moderator: Moderators for English X Forum

Insurgo
Posts: 11
Joined: Mon, 5. Aug 19, 22:19
x4

[#3904][FREEZE][7.5] Freeze on clicking "Get Up" during Graph 2 final mission - Fixed in 7.60 Beta 6

Post by Insurgo »

I've got the game frozen currently and am avoiding closing it in case I can extract more info.
For that reason I've had to extract game version numbers etc. from files by alt-tabbing.

Version and language (e.g. 7.10 Hotfix 1, English, etc.).

Steam App ID: 392160
Buiild ID: 17442116
version.dat: 750
X4 file version: 7.5

Whether or not your game is modified using any third party scripts or mods (see note below).

Nope. I have never even installed one.

The game start you originally selected for the game in which the problem occurred.

Timelines Graph 2 final mission defending the Hatikvah Station.

Exact nature of the problem, where and when it occurs and what you were doing at the time.

In the above mission, I have just fended off some Xenon waves. I am contacted by the station to help move research off station. I select "sure, let's get started."
After a few moments, I go to collect some missiles from around the station. Next I want to repair the ship, as it's slightly damaged. I click "Get Up" from the top bar in the GUI - the game instantly freezes.

I have waited for at least 10 minutes by this point - no progress. The game is using almost no CPU and about 2GB of RAM.

NVidia SMI reports this:

Code: Select all

+-----------------------------------------------------------------------------------------+
| NVIDIA-SMI 576.28                 Driver Version: 576.28         CUDA Version: 12.9     |
|-----------------------------------------+------------------------+----------------------+
| GPU  Name                  Driver-Model | Bus-Id          Disp.A | Volatile Uncorr. ECC |
| Fan  Temp   Perf          Pwr:Usage/Cap |           Memory-Usage | GPU-Util  Compute M. |
|                                         |                        |               MIG M. |
|=========================================+========================+======================|
|   0  NVIDIA GeForce RTX 4070 ...  WDDM  |   00000000:01:00.0 Off |                  N/A |
| N/A   46C    P8              2W /   52W |    6534MiB /   8188MiB |      0%      Default |
|                                         |                        |                  N/A |
+-----------------------------------------+------------------------+----------------------+

+-----------------------------------------------------------------------------------------+
| Processes:                                                                              |
|  GPU   GI   CI              PID   Type   Process name                        GPU Memory |
|        ID   ID                                                               Usage      |
|=========================================================================================|
|    0   N/A  N/A           17808    C+G   ...s\Win64\EpicGamesLauncher.exe      N/A      |
|    0   N/A  N/A           20640    C+G   ...\common\X4 Foundations\X4.exe      N/A      |
+-----------------------------------------------------------------------------------------+
Any possibly relevant changes you have made to your game, system, or software before the issue occurred.

I updated my GPU drivers in the last day. I played through some other Graph 2 missions just fine since though.
I also enabled the venture extension yesterday, not realising it was not currently active.

Where appropriate, additional symptoms, error messages, links to saves *, screenshots and crash dump files (see this Wiki entry).

I believe Timeliens doesn't have save files. That said, it must have _some_ way of tracking what's been completed. I found userdata.xml; see attachments.

Your system specifications in the form of a DxDiag report and vulkaninfo (see this Wiki entry).**

> vulkaninfo > "Desktop\vulkaninfo.txt"
WARNING: [Loader Message] Code 0 : Layer name GalaxyOverlayVkLayer does not conform to naming standard (Policy #LLP_LAYER_3)
WARNING: [Loader Message] Code 0 : Layer name GalaxyOverlayVkLayer_VERBOSE does not conform to naming standard (Policy #LLP_LAYER_3)
WARNING: [Loader Message] Code 0 : Layer name GalaxyOverlayVkLayer_DEBUG does not conform to naming standard (Policy #LLP_LAYER_3)
WARNING: [Loader Message] Code 0 : windows_read_data_files_in_registry: Registry lookup failed to get layer manifest files.
WARNING: [Loader Message] Code 0 : Layer VK_LAYER_AMD_switchable_graphics uses API version 1.3 which is older than the application specified API version of 1.4. May cause issues.
WARNING: [Loader Message] Code 0 : vkGetPhysicalDeviceSurfaceCapabilities2KHR: Emulation found unrecognized structure type in pSurfaceInfo->pNext - this struct will be ignored

(see attachments for stdout)

PS C:\Program Files (x86)\Steam\steamapps\common\X4 Foundations> Get-FileHash -Path .\X4.exe -Algorithm SHA256

Algorithm Hash Path
--------- ---- ----
SHA256 290EE32F3D082380A3E433E66623466BB012DA58D4C6715759EDAB3BB9F36AD6 C:\Program Files (x86)\Steam\...


Attachments via Google Drive

- DxDiag.txt
- vulkaninfo.txt
- userdata.xml
- Screenshot of frozen game
- Performance analysis from attaching a debugger in VS 2022 for 30 seconds

https://drive.google.com/drive/folders/ ... sp=sharing
Last edited by Tranxalive on Fri, 9. May 25, 15:58, edited 2 times in total.
Reason: Editing the title to say it's fixed.
Insurgo
Posts: 11
Joined: Mon, 5. Aug 19, 22:19
x4

Re: [FREEZE][7.5] Freeze on clicking "Get Up" during Graph 2 final mission

Post by Insurgo »

It appears to be a soft-lock, as sending a quit via Alt F4 instantly exited the UI.
Steam still thinks the game is running, and indeed I can see X4's executable sat there still.
Tranxalive
EGOSOFT
EGOSOFT
Posts: 690
Joined: Mon, 14. Dec 20, 01:49
x4

Re: [#3904][FREEZE][7.5] Freeze on clicking "Get Up" during Graph 2 final mission

Post by Tranxalive »

The issue should be fixed now in the Public Beta, in Beta 6.

Return to “X4: Foundations - Technical Support”