BurningmyBurner Posted March 6 Posted March 6 So I was just using Aslain installer, I set the folder directory to where my Steam WOWS was, everything was according to the guide, but when I tried to launch the game, it just refused to, no crash, no black out or suddenly pop-up, the game just refuse to open Quote
Administrator Aslain Posted March 7 Administrator Posted March 7 See my post signature with link to the guide, attach zip with logs. Quote
BurningmyBurner Posted March 8 Author Posted March 8 On 3/7/2026 at 2:24 PM, Aslain said: See my post signature with link to the guide, attach zip with logs. oh I see, thanks for letting me know how to properly bug report Quote
BurningmyBurner Posted March 8 Author Posted March 8 So I have a problem with my Steam WOWs, where after downloaded and followed the guide along with the installer to install the modpack, I tried to open the game, and it just refused to open, no black screen, no crash, no 0.1 seconds pop-up, it just refused to open, I tried to open directly via Steam, the Play button went from Running and back to Play without anything pop up, which is quite weird, cuz previously I tried with Modstation, and it worked, granted Modstation is more "official", but most of the mods I installed in Aslain are the same one I installed in Modstation Aslains_WoWs_Logs.zip Quote
Administrator Aslain Posted March 9 Administrator Posted March 9 It's not about the correct way, but the fact that previous post was lacking the logs, without them I cannot check this issue. Installed the same mods as you have and I can log in with no problem, but maybe it's matter of a ship you have in a port. Modstation official or not, it doesn't matter, technicaly it's just different modpack, but the mods are the same, with the exception that I have more of them and mine are more up to date mods, while their not really. I see that the python.log from the profile folder is missing, so I don't see errors you had, therefore cannot check this part. From my point of view it's not the mods, because after installing the same I'm not crashing. Try to reduce the mods number, especialy regarding tank skins to see if they are a culprint for you. There is also a chance that something on your pc interrupted the installation. Quote
BurningmyBurner Posted March 9 Author Posted March 9 50 minutes ago, Aslain said: It's not about the correct way, but the fact that previous post was lacking the logs, without them I cannot check this issue. Installed the same mods as you have and I can log in with no problem, but maybe it's matter of a ship you have in a port. Modstation official or not, it doesn't matter, technicaly it's just different modpack, but the mods are the same, with the exception that I have more of them and mine are more up to date mods, while their not really. I see that the python.log from the profile folder is missing, so I don't see errors you had, therefore cannot check this part. From my point of view it's not the mods, because after installing the same I'm not crashing. Try to reduce the mods number, especialy regarding tank skins to see if they are a culprint for you. There is also a chance that something on your pc interrupted the installation. hm... I tried removing the skin mods, same issue, I also tried to delete all the mod, same issue once again I starting to think the modstations mods leftovers are still there Quote
BurningmyBurner Posted March 9 Author Posted March 9 44 minutes ago, BurningmyBurner said: hm... I tried removing the skin mods, same issue, I also tried to delete all the mod, same issue once again I starting to think the modstations mods leftovers are still there I verified my files and it worked, seems like there was actually modstations leftover 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.