Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: updated with recent changes

...

A common installation issue especially on Linux when having purchased the game through GOG is a missing Vulkan runtime. Details how to solve this can be found here.

A second issue you might experience is related to a missing (or incompatible) OpenSSL library on your system. Again, this only applies to Linux and only when having installed the game through GOG as the Steam runtime ships with a compatible version. We are working on changing this dependency in a following patch to remove this problem for good. Please refer to this troubleshooting page for an workaround.

Exitcodes

When you try to start the game, it performs some early startup checks and if it determines some a setup issuesissue, will provide you with an a popup like the following one which provides you with instructions on how to resolve the startup problem yourself:

These instructions are provided specifically for the issue which the game identified so you are not presented with random and pointless FAQ steps which might apply to resolve other situations but won't help with the specific issue at hand. In 90% of the cases the instructions on these popups will solve the issue. Important to recognize here is that at the end it states the exitcode of the startup error (Exitcode 212 in the screenshot above).

...

ExitcodeDetailed Troubleshooting Page
2
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-267
8
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-293
9
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-294
113
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-325
201
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-82
202
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-80
204
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-274
205
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-131
211
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-352
212
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-81
220
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-1
221
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-273
222-231
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-275
233
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-271
235
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-371
1003
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-454
1009
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-465
1012
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-452
1021
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-453
1026
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-455
1028
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-275
1046
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-464
1062
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-457
1065
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-463
1069
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-462
1079
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-458

Startup issues without exitcodes

...

If you followed the instructions on that page and figured out these didn't apply to you, you can either also give it a blind shot and look at the following list of troubleshooting pages which don't have an exitcode assigned:

Startup ErrorDetailed Troubleshooting Page
Missing Vulkan Runtime
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-313
Avest 3rd-party tool incompatibility
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-104
Generic Vulkan engine issue
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-2
Unsupported Intel graphics card issue
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-18
NVIDIA driver startup error
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-272
Steamoverlay related startup error
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-277
Steamoverlay related startup error (type 2)
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-278
Steamoverlay related startup error (type 3)
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-355
Vulkan specific startup error
Jira
serverEgosoft JIRA
serverId9d4eeb41-d1c2-3d89-8ea6-0964f358c464
keyX4-353

...

If you still end up being unable to start the game, please send a mail to prioritysupport@egosoft.com with the Subject: "Undefined startup issue" and attach the crash dump file to your mail. The file is located in the same directory as the X4.exe file resides. Make sure to pick the correct one with the timestamp encoded in the filename corresponding to the time you tried to start the game and point whether/that you didn't get redirected to another troubleshooting page and that you also didn't see a popup.This page explains how to locate the crash dump file: Crash Reports and Crash Dumps

Please be aware that this support channel is solely intended to resolve issues with starting up the game. If you run into any other type of problem, please use our troubleshooting section in the official forums to tackle the issue you have.