Critical Error Occurred

[Kuraiko]

Hey Aslain,

 

I have a tiny little problem which prevents me from playing WoWS with your ModPack or playing it at all.

 

After installing the latest version of your ModPack today (Aslains_WoWs_ModPack_Installer_v.5.5.1.01.exe) this error occurrs after clicking "Play" in the WoWS Launcher:

 

 

 

(Want spoiler BB-Code ...)

 

This message still appears if I clear the res_mods folder completly.

This message still appears if I uninstall the ModPack via unins001.exe.

This message does not appear any longer after uninstalling and reinstalling WoWS and starting it without the ModPack.

After I installed the ModPack again, the message re-appeared.

 

Logs attached.

 

I'd especially like to know how to fix this error without reinstalling WoWS again

 

Regards

Kuraiko

_Aslain_logs.zip

Edited May 13, 2016 by Kuraiko

[Quaksen]

Curious. I don't have that resources.xml file, and my game works fine.

Edited May 13, 2016 by Quaksen

[MGIMATTY]

This seems like some mod related issue. As I too don't have resources.xml in my game files.

Edited May 13, 2016 by MGIMATTY

[Quaksen]

As for spoilers...  

 

SPOILERS!

 

[spoiler]Hidden stuff goes here[/spoiler]

 

 

Edited May 13, 2016 by Quaksen

[Grandorf]

Hi

 

Some good oldfashioned updating of drivers and Windows

[Kuraiko]

16 minutes ago, Quaksen said:

As for spoilers...  

  Reveal hidden contents

SPOILERS!

 

[spoiler]Hidden stuff goes here[/spoiler]

 

 

Thought it wasn't available cause it wasn't in the code bar. ^^

[Kuraiko]

22 minutes ago, Grandorf said:

Hi

 

Some good oldfashioned updating of drivers and Windows

Windows is always up to date. Last Updates made yesterday.

Drivers work fine. I updated the GeForce Drivers just today. Everything is fine with it. I.e. I can play any other game without issues.

As for all other windows drivers: Never change a running system. And it is running

[Grandorf]

Hmm

 

Something is making Windows give error. 

 

You could try eliminating the troubled mod 

by testing 1 at a time, start with soundmods 

if sound is the issue in this case.

 

[Kuraiko]

1 hour ago, Grandorf said:

Hmm

 

Something is making Windows give error. 

 

You could try eliminating the troubled mod 

by testing 1 at a time, start with soundmods 

if sound is the issue in this case.

 

I had to reinstall the whole game everytime ...

 

Well, I'll try a few. Maybe Aslain can read something in the Logs?

[BlueKQ]

If I read your logs correctly, you chose to install a UI pack, and other earlier options when the instructions clearly state that could be incompatible.  I would start by selecting the UI pack or other items, not both, and then seeing if you can get it to work.

 

[Kuraiko]

4 hours ago, BlueKQ said:

If I read your logs correctly, you chose to install a UI pack, and other earlier options when the instructions clearly state that could be incompatible.  I would start by selecting the UI pack or other items, not both, and then seeing if you can get it to work.

 

The UI Pack was the one I wanted to test out at first, too.

Gonna let you know what I find out.

----------------------------------------------------------------------------------------------------

Edit 1: It wasn't the UI Pack.

----------------------------------------------------------------------------------------------------

Edit 1: It wasn't the UI Pack.

Edit 2: It wasn't a sound mod.

I've noticed some weird stuff now. 

There is a folder and a text file which are named with crypted symbols as well as some .dds files both in the WoWS main folder which weren't there in previous versions of this ModPack.

I've double checked the Mods and wanted to use and I don't use any new mods which I didn''t used before. Actually, the UI Pack was the only one that I changed since the last version, but I gonna continue research on this.

Here's a screenshot of my main folder:

 

 

 

Marked the folder and files red (obviously).

 

Edit 3: Can't delete attached files ...

Edit 4: It's none of the Mods listed under "Miscellaneous Mods".

 

Edited May 14, 2016 by Kuraiko

[BlueKQ]

Have you tried starting the game in "safe mode" by clicking on the arrow next to the "Play" button on the WOWS Launcher?

 

[Kuraiko]

36 minutes ago, BlueKQ said:

Have you tried starting the game in "safe mode" by clicking on the arrow next to the "Play" button on the WOWS Launcher?

 

Yes.

Didn't work after installing the ModPack even after clearing the res_mods folder.

Edited May 14, 2016 by Kuraiko
Don't like typos.

[BlueKQ]

When did you download the modpack?  Aslain originally uploaded the wrong one as 5.5.1.01.  Maybe you got the original one and it was for the wrong version of the game.

[Kuraiko]

3 minutes ago, BlueKQ said:

When did you download the modpack?  Aslain originally uploaded the wrong one as 5.5.1.01.  Maybe you got the original one and it was for the wrong version of the game.

I noticed that and I think I've downloaded it again ...

 

I'll download the MP again, just to get sure.

[Kuraiko]

There we go ...

 

So the issue came indeed from those weird named folder and file.

They seemed to be related to my two custom mods.

Now, I have to say two things:

1. Those custom mods are just skins.
2. They worked even in version 0.5.5.1 with the previous MP Installer.
3. Everything stopped to work with the newest version of Aslains ModPack.
4. And on top of that, the skins STILL DO WORK when I unextract them by my self instead of letting the installer do so.
5. If I extract them, there are also no folders and files created in the main folder, because there non to extraxt there ...

Why is this happening?

 

PS: UI Pack works perfect

Edited May 14, 2016 by Kuraiko

[BlueKQ]

That explains why no one else was having a problem. :-)  I don't know enough about skin mods to help you diagnose that issue.

[Kuraiko]

Well, the issue appears only, if the ModPack extracts the skins.

The paths within the zip-files are all correct, but somehow it places a few files at the wrong location.

 

Weird ...

[MGIMATTY]

This can happen sometimes because of (en/de)coding issues. Suggested solution is you do it yourself or repack the mod files in a zip you made yourself (pref with windows or 7zip). 

Edited May 14, 2016 by MGIMATTY

[Kuraiko]

7 hours ago, MGIMATTY said:

This can happen sometimes because of (en/de)coding issues. Suggested solution is you do it yourself or repack the mod files in a zip you made yourself (pref with windows or 7zip). 

Made the zip myself and it's .zip files.

But I guess you could be right. Maybe I'll try 7zip next time