BlueKQ

No one else is reporting a problem with this crosshair. I was able to install all the mods listed in your log files and was able to see the crosshair in the settings under static Type 1. I am trying to help you, but since I am not there on your machine, I have to ask you questions and ask you to show me things. We could try a remote desktop style tech support tool where you can watch me while I control your computer and check things, but since you don't know me, you may not be comfortable with that. In the meantime, please open WOWS, go to the settings menu, click on the Controls tab, then the Select Crosshair button, select Static and Type 1. Then take a screenshot to share in this thread. I wan t to see what option one is after you have installed the mods.

The ModPack installer doesn't run on the Mac natively. The actual mods are usually zip files that are placed in the res_mods directory. If Wargaming kept the same file format and you have access to the res_mods directory, you can place the files in manually and use the mods. See the original mod authors posts for instructions.

We can unpin this post now.. Most of what is being asked for is in the game and there are a couple of ship names mods.

The default setting is on Static Crosshair type 2.. did you switch it to Type 1? Can you post a screenshot of what your type 1 looks like?

I just installed the exact same mods as you have listed in your log files and the custom crosshair shows up as Static option 1. _Aslain_logs.zip

Rerun the ModPack installer and "un-check" the box of the mod you don't want to use.

I can't tonight, but tomorrow I will install the same mods as you did and see what I can find.

Did you go into the crosshair selection in settings and look to see where your installed mod was set up and then select it. For example, the description says it is installed as static crosshari 1, but it might be installed as Static Crosshair 3 or Static Crosshair 8. Check all the static options until you see the one you installed.

This needs to be moved to the World of Tanks "Bugs & Issues" forum. @Quaksen or @Aslain

I have tried each of the three options you chose independently (one at a time) and received the same results as you. The ModPack hangs after clicking on the Finish button. The window disappears, but the processes are still running, the program icon still shows on the Windows task bar and the final log file and zip file are not created. I noticed that all the mods you are trying to use are by the same author so there may be something related to how his put together. I switched back to my mods and everything worked as normal. I also tried a different "full package" where this same problem happened before "Blue Steel" and had the same problem of not completing the install process. I am going to appeal to @Aslain for a higher level of support because I can't dig any deeper. No zip files were created. I only included the .inf file from the final test of Blue Steel, but the original log file posted by OP showed the other three options I tried separately. I used ver. .04 for my tests. _Aslains_Installer_Options.inf

If you don't have admin privileges already, you should be prompted to grant them when the ModPack starts running. I am testing the installs with your options right now.

No. It should only take that long if you are downloading large mods and have a really slow Internet connection. I just wanted to make sure you were not running the ModPack installer while the previous one was still running.

In between each of these attempts, did you manually kill the running process in the Task Manager?

His ModPack is a windows executable. The ModPack is a simple way to install multiple mods at one time. Until someone creates a MacOS X app that does the same thing, you will need to manually install the mods you want to use. The mod author usually describes how to do that where they posted the original mod files. You can check the mod forums on the World of Warhips Official Forums to find the original files.

Running Lights is not an illegal mod. I searched and read through pages and pages of forums posts where it was even mentioned and it was never declared to be illegal. And it fits within the acceptable mod because it only displayed information that is available by looking at the ship.

Please upload the Aslain_logs.zip file as described in this post:

The post it references sending Aslain_logs.zip. Do you have that in your WOWS directory. Please send the .zip file after you run the ModPack with the all the options you want, including the mod you think isn't working properly.

Three thoughts.. First get the updated ModPack and see if it still happens. Aslain will not spend time on looking at fixing something if you are using a version older than the current one. (I know, it may have been the current version when you posted this, but there is a newer one now.) Secondly, you selected a "full package" that states it may conflict with previously selected mods, and in fact, you also selected two standanlone Kancolle mods and the Kancolle full package. Try only selecting the Kancolle "full package" without any other mods to see if your install can finish properly. Lastly, There was a bug with the installation of the "Blue Steel" full package a few mod versions ago and Aslain had to fix a bug. There may be one in this full package as well.

Please include your log files as described in the linked post so that we can help you:

You use very similar mods to me, except that I don't use a camera mod. Try selecting the in game damage without the minimap ship names and see if that brings the colored kill messages back. The minimap names options seem to conflict with several of the other mods and that is the first one I would remove.

It sounds like Aslain is familiar with the problem you are experiencing, but here are a couple of items that will help us help you. First, if this is continuation of an existing, already reported problem, please continue your updates in the thread already started instead of starting a new thread. Secondly, if you are reporting a problem, please include the Aslain_logs.zip file as described here: It sounds like Aslain is familiar with the problem you are experiencing, but here are a couple of items that will help us help you. First, if this is continuation of an existing, already reported problem, please continue your updates in the thread already started instead of starting a new thread. Secondly, if you are reporting a problem, please include the Aslain_logs.zip file as described here:

Please upload your log files as described in this post.

Logs also list every mod you installed in case there is a conflict between some that are causing your problem. They also list the version of ModPack you are using. Maybe Aslain spent all day fixing your problem and released an updated version, but you are still using an old version. Many reasons to include a the log file zip with every bug report.

Please follow the directions in this post when posting about problems you are having so other people can look into the problem for you.

hmm.. no logs. Please see the link in my post above about posting issues. With just the information you provided, it is impossible to track down.