Game crash after load in 5-10 seconds

[D00]

Simply exit to desktop after load, no messages, reason is unknown. Do support need save file? Crash is stable, continue to play isn't possible. Version 1.5
When will be patch?

[Alan Phipps]

Are you on the beta version of Steam (not meaning the X4 beta); if so try with the normal Steam version. Have you verified the gamefile cache (if Steam) since the 1.50 release? Is your game modded and does a fresh vanilla start save load and play properly?

If that doesn't help then please see the first Announcement on this forum as without some useful info we really cannot help you properly.

[D00]

Are you on the beta version of Steam (not meaning the X4 beta); if so try with the normal Steam version. Have you verified the gamefile cache (if Steam) since the 1.50 release? Is your game modded and does a fresh vanilla start save load and play properly?

If that doesn't help then please see the first Announcement on this forum as without some useful info we really cannot help you properly.

Steam version: from 4 jan 2019, 15:26:19, Steam api v018
Game files verified, all ok.
Game isn't modified.

Ver 1.5, rus

DxDiag:
https://drive.google.com/file/d/1h34iVT ... sp=sharing

Vulkan info:
https://drive.google.com/file/d/1C6d90X ... sp=sharing

Save file:
https://drive.google.com/file/d/1djz-KK ... sp=sharing

[Alan Phipps]

Hello. Looking at the DxDiag, you have two sound devices and drivers running at the same time, Nvidia and ASUS. I would disable whichever you do not use in Device Manager, Sound/Audio Devices (right-click on a device in the list there to get an enable/disable pop-up).

You have several ASUS gpu fan manager app crashes reported. I would try to find out what is going wrong there. Otherwise, you have no critical X4 crashes being reported in the DxDiag.

There have been slightly similar issues reported (random game freezes or issues on loading/launching) with Nvidia 1070/1080 or 2070/2080 graphics cards and drivers. There is an example thread here.

Good luck.

[D00]

Hello. Looking at the DxDiag, you have two sound devices and drivers running at the same time, Nvidia and ASUS. I would disable whichever you do not use in Device Manager, Sound/Audio Devices (right-click on a device in the list there to get an enable/disable pop-up).

You have several ASUS gpu fan manager app crashes reported. I would try to find out what is going wrong there. Otherwise, you have no critical X4 crashes being reported in the DxDiag.

There have been slightly similar issues reported (random game freezes or issues on loading/launching) with Nvidia 1070/1080 or 2070/2080 graphics cards and drivers. There is an example thread here.

Good luck.

DxDiag does not necessarily show exceptions.
Exception is there:
https://drive.google.com/file/d/1LQc5kp ... vpcHL/view
An exception was thrown at the address 0x00007FF3AD185220 in X4.exe: 0xC0000005: access violation during execution at 0x00007FF3AD185220.

Disabling nvidia audio did not help.
Asus 2080 rtx currently run on default freqs, reports may be caused when i find out max speed about month ago.

Access to deleted object is possible.

[stefanEgo]

Could you check in the game folder (where the X4.exe resides) whether you have files with the .dmp-extension? If so, can you send the one which matches the in the filename encoded timestamp with the time the crash occurred to crash@egosoft.com (stating a reference to this thread in the subject/mail)?

[D00]

Could you check in the game folder (where the X4.exe resides) whether you have files with the .dmp-extension? If so, can you send the one which matches the in the filename encoded timestamp with the time the crash occurred to crash@egosoft.com (stating a reference to this thread in the subject/mail)?

Yes, email was sent. When Egosoft planning next patch?

[Alan Phipps]

Version 3 of 1.60 beta is available and discussed in the public beta forum now. Release will depend upon these and other fixes/additions that make it into 1.60 and their testing requirements and outcomes.

[D00]

Version 3 of 1.60 beta is available and discussed in the public beta forum now. Release will depend upon these and other fixes/additions that make it into 1.60 and their testing requirements and outcomes.

Saving up bugs is nice, but in my opinion, the frequent release of patches will have a better effect on user favor. If you stop in the middle of the seizure of the sector, then the risk of having to seize it twice due to possible intolerance to the preservation is completely reluctant.

[stefanEgo]

Retrieved the crashreports. According to these you are running into this crash: https://www.egosoft.com:8443/jira/browse/X4-174

As stated in the issue (note that I just updated that information), the crash has been resolved in the current beta (1.60 Beta 3) and hence is expected to also be fixed in the upcoming 1.60.
Any updates regarding this particular crash will be provided on the linked page.

[D00]

Retrieved the crashreports. According to these you are running into this crash: https://www.egosoft.com:8443/jira/browse/X4-174

As stated in the issue (note that I just updated that information), the crash has been resolved in the current beta (1.60 Beta 3) and hence is expected to also be fixed in the upcoming 1.60.
Any updates regarding this particular crash will be provided on the linked page.

Big thanks.
What is the probability that the save from 1.6 beta 3 will be compatible with 1.6?)

[CBJ]

We always try to maintain savegame compatibility between versions, even public beta releases. We can't guarantee it 100%, as implied by the password used to access the beta, but so far there hasn't been a case where that compatibility has had to been broken.

[D00]

We always try to maintain savegame compatibility between versions, even public beta releases. We can't guarantee it 100%, as implied by the password used to access the beta, but so far there hasn't been a case where that compatibility has had to been broken.

In the beta for an hour did not fall, it's good.
From the big minuses - the ships are still not undocked, just hang out with the status of undocking ...
I think I'm teleporting myself undocking. Here's what happened:
https://drive.google.com/file/d/1tIyfoU ... sp=sharing