Darth_Clicker

This problem does not exist in the current modpack version.

It should work ok now. It is for me.

Damocles Sword custom sight is not causing the esc/ctrl problem any longer. Thanks Aslain. Now if we could just get ProArty sight back......

yes, those crosshairs have the mod_sights.pyc file which is apparently a cause of ctrl/esc issues. J1MBOs is one of the sight mods that does not use that file. There is a list of the ones using the file in this thread...I think from September 2.

apparently some people are having the sound problems with vanilla...no mods at all. So, it is at least partly a WG problem.

Is this esc/ctrl issue the same problem as before with the same cause: the mod_sights.pyc file that some custom sights use? I tried Damocles Sword yesterday (it has the mod_sights.pyc file) and esc/ctrl did not work same as in previous versions. I went back to J1MBOS which is one of the sights without the mod_sights.pyc file and no problems. I would choose a sight that does not use this file and see if that solves your problems. There is a list a few responses ago (September 2) that I copied from Aslain a couple of weeks ago that lists the sights that used the file at that time. I do not know what the current info is on this subject.

Logs? What are logs? How did you use Google to translate the text in the screenshot? I only used CTRL to get rid of the message after it pops up but not before. I switched custom sights to J1mbos and found out it is not working with my setup. Switched back to my original sight choice and now i do not have the message. If it happens again I will Google what logs are and get some for you here.....

Everytime I return from arty strategic view back to normal view I get this little popup message. I can not understand the language (Russian?). I would like to remove it if I knew the source. Any help is appreciated.

For now, if you install the modpack without XVM your mods will work. To do this, make sure the entire XVM section is unchecked in the modpack. You will have to change the 0.9.15.1.1 folder that the modpack creates to 0.9.15.2 . Also, make sure that you do not have an XVM folder inside the configs folder in res_mods. This is important in case you have xvm changes in your Aslain Custom folder. As I stated above, Sirmax (XVM Developer) has stated that there is not yet a working version of xvm for 0.9.15.2. So the problem is definitely in XVM and is due to the changes that WG made with this micro patch. Good going WG!!!! Please don't blame XVM for this problem. http://www.koreanrandom.com/forum/topic/34535-9152/

Sirmax at XVM has stated that there is not yet a working version of xvm for 0.9.15.2. So the problem is definitely in xvm and is due to the changes that WG made with this micro patch. Good going WG!!!! http://www.koreanrandom.com/forum/topic/34535-9152/

I have renamed my the 0.9.15.1 folder to 0.9.15.2....hoping like hell that everything would work. But, it doesn't....I guess the guys at WG are smiling really big this morning....haha. The game starts perfectly in safe mode, so no problems on WG side. With mods it starts slow and gets stuck at updating vehicles. I have classes to teach this morning so I can not help by removing things from my modpack config....sorry. If any other logs or help is needed, let me know. python.log _Aslain_logs.zip

I am pretty sure he attached them earlier in this same thread concerning the same problem.

I think that it is a real shame that the nightly builds are put out and the information on what has changed in them is not readily accessible. I have learned how to make some of the same changes I used to make before AS3 and others are either not available or I have not figured out how to do it yet. If I knew these features were not available I would not waste my time or yours by requesting them so early. To be clear Aslain, there is absolutely nothing in this post that is directed in any way at you. Just a bit of frustration with some of the people over at the Korean Random forum.

Thanks for adding the option to see or not see dead tanks on the mini map. I am continually impressed by what you do. I fought with xvm files for about 15 minutes trying to turn them off and had no luck at all. Thanks again Aslain.

it is in the game client settings under general.

More info to #2 above. I can disable the expanded mini map features in settings, but this also disables spotted but lost tanks. At the moment, with expanded mini map features enabled I have two markers for spotted but lost tanks and one marker for dead tanks. I would like to have one marker for spotted but lost and no marker for dead. Here is what I see now:

Here is my wish list for the modpack. I know some may be dependent upon XVM developers but here they are: Larger mini map size when using ctrl for a centered mini map. More control over mini map icons: ability to have player names on mini map colored by wn8 3. Darker lines on the mini map, the current ones are a bit difficult to see. 4. A circle showing the range of artillery when playing with spg. Maybe I could ask Santa Claus for them for Christmas....

I figured that out a few minutes before you posted this. thanks. I was hoping to make it larger than 5. looks like you can only make it smaller. Edit: I just realized what the "(0..5)" means....it is the range of zoom adjustments....duh. Oh well. Maybe some miracle will happen in the future. A larger mini map would be better in my opinion. Now, the standard mini map can be larger than the zoom. Thanks for trying. I think that was in the old system. using the +/- keypad keys will toggle the zoomed minimap through the 5 different sizes. Similar to the same you can do with the normal mini map. It is just that the normal mini map has larger sizes.

Has anyone figured out how to increase the size of the alt mini map that is centered on the screen? I may be blind, but I do not see any pixel settings in the xvm file....maybe I am looking at the wrong file.

I forgot....you can choose extra aim info in the mod pack and it provides shell travel time to any sight.

Damocles Sword does, but it is one of the crosshairs that uses the mod_sights.pyc file that I think causes esc/ctrl etc problems. So I am not currently using it. ProArty sight also has it but I do not think it has been updated for 9.15.1 and is not currently part of the modpack. The change from Action Script 2 to 3 really caused a lot of problems with custom sights. I assume that many sights will either be reworked or disappear. I really hope we will see a return of more custom sight choices in the future.

In order for you to get help with your issue, you at least need to post the required logs. It would also be best to post your request for help in the "Issues and Bug Reporting" section of the forum. If you are unaware of the logs required, everything you need to know to get on your way to help is contained here http://aslain.com/index.php?/topic/9-how-to-report-a-bug-or-issue/ Good luck with your problem. I have not experienced the problems you are having.

I do not know how to do this in the current version, but in the next version (9.16) WG is making it very easy to add your own 6th sense sounds in the form of a normal mp3 file. Unless it is very easy for someone to make it work in the current version, I do not think I would waste any time on this and just wait until early next month when 9.16 is predicted to be released. We should have a CT server of 9.16 in a few days so you may be able to test out the new functions concerning 6th sense sounds.

You are welcome. Happy hunting on the battlefield!