[UPDATE} Possible Fix For Low Level Fatal Error....

[SourceUnknown]

[UPDATE] Unfortunitely the fix has caught up to me and is no longer working! Atelast I got 8 hours of play before it got me....Best of luck to everyone, hopefully Blue Isle gets it worked out soon!

If anyone has any other possible solutions could you please post a link to your thread here too, so others can see it? Thanks!


I ended up with this bug after the last patch a day ago...so I have been scrambling to figure out another way around it...

Through trial and error, I decided to make a shortcut to desktop of the executable for Citadel and start the game from there. The only reason why i did this was because of a game I had last year that did this and a friend suggest this trick....it worked, so I tried it here and with success.

I havent fully tested it out on Official servers as I was just in a hurry to try and get the game going. So I grabbed the first Unofficial Server in the list with a ping of 32.....

It worked. I logged in, created a character and played for well over 3 hours without a hitch. Lag was not a serious issue (couple of burps here and there but very, very playable) and no real problems or quirks. I grinded to level 12 and build a somewhat sized base...

I cant guarantee this will work for you, but its worth a shot if the new patch that was just released didnt work for you....so please try the new patch first!

The executable you will need to make a shortcut to desktop is "Citadel-Win64-Shipping.exe" fire the game up from there and hopefully you can log in! Best of luck, I hope it helps someone!

[SourceUnknown]

Originally posted by emsee25:

did not work crashed soon as doors loaded

Sorry man, Wish it couldve helped....Ive already relogged back into the same server now 3 times with no problems.....except the new patch now has introduced a cooldown bug and Im going to try a work around for that as well....

[SourceUnknown]

Originally posted by emsee25:

alot of players clear spells then take off weapon put on weapon add 2 new spells then replace with spells they had on before

Thats what Im about to try! thanks!

[SourceUnknown]

Bumping just in case this helps someone as it did me....

[Risu Go]

Tried both creating new shortcut, AND clearing spells/unequipping weapon. Neither were effective, either seperately, or in tandem. I do apprecite the suggestion(s), however.

[silaradams]

If you follow what GasTheFanz says, it may possibly work, as it worked for me. You can't just make a shortcut to the main exe in the game directory. This was the path for me of the file that you need to make the shortcut to the desktop of:

\steamapps\common\Citadel\Citadel\Binaries\Win64\Citadel-Win64-Shipping.exe

I've now been in playing for at least 2 or 3 hours without a single crash. I was getting a crash after just a few minutes of going into the server every single time.

[Maric]

Edit: well I was able to play a private server but it still did it on official one after a while. Dunno.

[Risu Go]

Originally posted by silaradams:

If you follow what GasTheFanz says... This was the path for me of the file that you need to make the shortcut to the desktop of:

\steamapps\common\Citadel\Citadel\Binaries\Win64\Citadel-Win64-Shipping.exe

I've now been in playing for at least 2 or 3 hours without a single crash. I was getting a crash after just a few minutes of going into the server every single time.

I did this exactly, and it did not work. Same issue.

[Snore]

Tried this method, while the game seemed to load better (my guy actually spawned where he should on the map instead of spawn), it still crashed once everything loaded in.

[Cadeyrn]

I think it is tied to your GPU (AMD seems to be most affected) AND the number of structures on the server you're trying to play on. If it is over a certain number, I think you're screwed no matter how you fire up the game.

[Zephyrbell]

Originally posted by emsee25:

did not work crashed soon as doors loaded

Doors loading are what do it for me too.

[SourceUnknown]

Weird, after about 2 mins im ok, i can actually play and have better performance than before. Ive played a solid 3 hours and no problems. Logged back in for another 2 hrs and still doing ok.

Im running...
AMD FX6300 black box edition (6-core), 32gb (soon to be 64gb) DDR3 1866 corsair vengeance, AMD R9 380X (4gb)....

As you can see im not running a epic beast, but its not exactly a potato either!

[Risu Go]

Originally posted by GasTheFanz:

Weird, after about 2 mins im ok, i can actually play and have better performance than before. Ive played a solid 3 hours and no problems. Logged back in for another 2 hrs and still doing ok.

Again, your effort and suggestions are appreciated, and although not every AMD system is affected, many are, and the solutions you put forth in your OP do not work for most of us. There are many AMD users with top-of-the-line systems getting this error.

I'm not saying others should not try them, but hardly a pancea for the majority. What we need is a permanent solution in the coding of the game.

[mooks]

Neither shortcut solution worked for me, thanks for posting!

If anyone else has another fix, please update.

[SourceUnknown]

Well, unfortunitely the fix finally caught up to me! I cannot load back in anymore and still getting the error....ugh.

Well, atleast I got about 8 hours of play before it came back. Best of luck everyone. Hopefully Blue Isle will resolve the problem soon!

If anyone has any other ideas, feel free to link your post here so others can see it! Thanks!