Fatal Error Crash :/

Conan Exiles General Discussion Players Helping Players
1

Game mode: [Enter game mode here: ( - ]
Type of issue: [Enter one of the following: Crash ]
Server type: [Enter one of the following: - ]
Region: [Europe]

[Describe the bug here]
when i try to open a game by steam its loading but after few seconds i get a crash. i dont have anything from workshop subscribed i also tried to reinstall Conan but nothing changed:
Fatal error: [File:C:\B\branch_exiles-live-roh-p2\code\UE4\Source\ConanSandbox\ConanSandbox.cpp] [Line: 364]
Mounted paks num(53) not equal to expected paks num(52). Please verify your installation

!0x0000000000000000

Please provide a step-by-step process of how the bug can be reproduced. The more details you provide us with the easier it will be for us to find and fix the bug:

  1. You open a game
  2. Game crashed after few secounds
2

Hi @Peacereaver!

  1. Did you try “verify game files” in Steam? Try to play after that.

  2. There is also a chance that your antivirus is blocking your game. Try playing with your AV off or add exception of game location to your AV.

  3. … to be continued if 1 & 2 do not solve the problem… :smiley:

3

I’ve tried 3-4 times.
and i dont have AV

4

Have you ever been able to play the game before (on this computer/settings) or is it a fresh game?

Either way, did you check if your drivers are up to date?
And if its fresh purchase, does your computer meet minimum (recommended) specs?

5

Of course i have like 500h
i dont think drivers are problem as you can see

“Mounted paks num(53) not equal to expected paks num(52). Please verify your installation”

6

I apologize if I seemed to state some “random and obvious” suggestions.
Somewhere in back of my mind I recall that error but can not place it.

So I did a search on forum for related threads.

some of the more direct hits:

Also, here is official FAQ:

My humble opinion: If this problem started after game patched, it is very possibly a game related bug. If it started sometime after last patch, then I would guess that an update of Windows/AV/driver… must be causing the situation.

On that matter, a completely personal point of view: sometimes a completely fresh install of items like GPU drivers, distributables ect. does wonders. (and sometimes even that does not help…)

If you would be so kind, please reply if any of those links or my additional comments helped.

7

well… not

8

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.