However, the fix preventing crashes won’t work and, most importantly, any integrity check will bring back the issue with loading screen, and it will require reinstalling the mods again. In this case, the anti-crash fix will stay in place. Do not install mods after doing that, because the loading screen issue will be back. Right now we can offer two possible workarounds for this situation:Įither fully remove all mods and then conduct an integrity check. It is happening because of the conflict between mods and the latest fix deployed to remove an issue leading to client crashes. If you copy the Aslain_Modpack folder into the new install folder the mod installer will install all the mods you had without issue, game launches correctly.Some of you using mods could have encountered an issue which prevents you from entering the battle after the loading screen. Aslains Mod Pack 10.3.0_03 was able to install without issue. The issue seems to be with the preference files. Reverting the two preference xml files and relaunching I was able to enter port. At this point the the "Logging In." issue resumed. After closing the game through the menu I went back to the folder to swap out my preferences.xml and user_preferences.xml file into the new "World of Warships" folder, backing up the existing xml preference files. After reinstalling the game I was able to launch and log in to the client. It was the update that broke the login and caused the game to stick at "Logging In." I was able to resolve the issue by uninstalling the game then moving the the "World of Warships" folder in my steam library to another name to backup my preferences and settings. For those using the Steam client, I was able to fix the issue.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |