Game stuck on loading Screen (....Battles....)

[Hadscho]

Hi there,

After installing the newest Patch (1.2.5 Live R) I started the game up and did some Refits.

While refitting a Armoured Cruiser I Hull the Game gave me a notice about not being able to construct since it's obsolete. Since I wanted to do a refit I ignored this warning and saved the Design.

Now the save doesn't load anymore. Every Time it tries to load .....Battles..... the music restarts and doesn't leave the loading screen.

Which is strange since I was in the middle of the round and not at war. I tried updating the drivers and a fresh install of the game (which gave me a UI Bug)

System Specs:

CPU: AMD Ryzen 7 3700X

GPU: AMD Radeon RX 5700XT

Operating System: Windows 11 Pro

 

Attachments Photo of the Loading Screen where it gets stuck.

[Nick Thomadis]

Hello, can you please check if the bug has been fixed in the latest repaired version that is uploaded?'

Unfortunately, saves that have been corrupted may be impossible to become repaired fully.

[Nick Thomadis]

If possible, please attach your save files so we can check them out. You can search in windows with this term:

%HOMEPATH%\AppData\LocalLow\Game Labs\Ultimate Admiral Dreadnoughts

and find the files save_0.json, save_1.json etc.

[ituralde]

I had this same issue on two save files both on the latest patch.  I attached them to this post - that is actually a .7z file archive (change the extension) that contains both save files.

[ituralde]

Clarifying that the most recent patch just now fixed this.

[Hadscho]

I can also confirm that the latest Patch fixed the issue.

 

Thank you and good work on the quick fix 😁👍.

 

Kind regards and I wish you all a nice weekend 👋.

[Kerbo]

On 3/3/2023 at 1:09 AM, Nick Thomadis said:

If possible, please attach your save files so we can check them out. You can search in windows with this term:

%HOMEPATH%\AppData\LocalLow\Game Labs\Ultimate Admiral Dreadnoughts

and find the files save_0.json, save_1.json etc.

Hello, I'm playing on 1.2.5rx2 and this issue persists

[flaviohc16]

I have the same problem now, in 1.31, first time I have seen this happen

[Berring117]

Having the exact same issue on version 1.3.4