MP Mission: Taking Krymsk Coop8 (Ka-50 + A-10C)

[Speed]

Hi, Speed, thanks for looking into this for us. It is appreciated. Although you could always blame the DCS engine for crashing, etc., you could also say that there is simpy too much to do for the poor sim in this mission, and that it makes it crash. However, I agree that this should not be a problem. It can run slow, but not crash.

 

We know there is a pretty big lag spike for about 5 seconds at each of the ambushes when everyone fires all at once--lotsa ballistics calculations, but only for about 5 secs. This only happens for the host though, parhaps for clients seeing all the tracers. Does it crash at the same time always?

 

It is strange you mention the shkval problem where it hops off target and will not lase properly, we also had this problem, both of us. Though none of us have played enough BS2 yet to know whether there is something bugged with the mission, or in general.

 

When we tested the mission, I hosted it every time using the DCSW MP executable while playing myself--no dedicated. I have a fairly sturdy computer. i7 overclocked to 4 GHz (it is stable), 6 GB DDR3, HD 5870, Intel X25 SSD. We connected using VPN LAN. Although it does crash a lot for us as well, we have been able to finish both ambushes without any. We figured it was a bug with the latest patch since there have been other people with the same problems, according to masterk (he stalks the forums quietly :P). I noticed that DCS ran faster with a lot of units than what it used to before the latest patch, maybe there is some heuristic that went too wrong and makes the game crash or something, I dunno.

 

Btw, if you are going to test it, I suggest...

setting the "TEST Set Test Flag" trigger "SetFlag" action to flag 99. It will turn on some practical radio cheats to speed things up in the mission timeline. ;)

 

 

Another thing: this mission was originally created using DCSW 1.1.0.9, and I had some trouble making it work properly. When I tried running it in BS2 for the first time since DCSW .9, all the GroupDead triggers would always be true, even though the group was alive. I found out that there is a bug in BS2 where if you put periods in a group's name (e.g. Hammer 1.1), some (all?) of the triggers that work on groups will not work. You can try this yourself creating a fresh BS2 mission, Nate has looked into it. So a quick fix for me was to just change to Hammer 1-1. Anyway, might be related, might not.

 

Lost.

 

Thanks LO. I was thinking of testing it by blowing up all the SAM sites and just spawning myself in the air within missile range of the enemies. That should take care of all the hard work and just allow me to focus on testing. I will also try out that test flag.

 

As far as group names go, that is an interesting bug. I'm trying to figure out how the hell it could happen. Thanks for sharing it. I've always used the underscore for separating names/numbers, and no spaces or periods. Underscores are VERY rarely used as special characters in computer programming. However the period IS- in Lua for example, it separates a table and a table element with a string index. Maybe that's where the bug comes from. Still, it's very odd. The dash/hyphen/minus sign is going to be pretty safe too. You don't want to use spaces in group/unit names because two spaces can look a lot like one space... that will matter a lot if you ever try Lua scripting in your missions.

[LostOblivion]

Setting it to 99 will add the radio options "Destroy MERAD + SHORAD" (destroy all the SAM), "Disable Fronts" (trigger south screen dead), "Schedule Ambush 1" so that it is guaranteed to happen, and "Schedule Ambush 2" so that it is guaranteed to happen and not ambush 1, and "Disable Ambushes" to disable ambushes alltogether.

 

Edit: During the ambushes, some HMMWVs appear next to the main convoys including some infantry. In the next version I will probably remove the infantry, at least some of them, as they are more than likely causing fruitless lag with the tracers and all.

 

Lost.

Edited November 16, 2011 by LostOblivion

[HiJack]

..... Another thing: this mission was originally created using DCSW 1.1.0.9, and I had some trouble making it work properly when moving to the BS2 editor. When I tried running it in BS2 for the first time since DCSW .9, all the GroupDead triggers would always be true, even though the group was alive. I found out that there is a bug in BS2 where if you put periods in a group's name (e.g. Hammer 1.1), some (all?) of the triggers that work on groups will not work. You can try this yourself creating a fresh BS2 mission, Nate has looked into it. So a quick fix for me was to just change to Hammer 1-1. Anyway, might be related, might not.

OK! So thats the problem with my resent mission! I am using 1.1 2.1 3.1 .... in a lot of unit names as this worked fine in 1.1.0.9. Thanks for that information.

 

(HJ)

[LostOblivion]

Glad to help.

 

Lost.

[masterk]

I also got a consistent problem with my Shkval too- the second I would launch a Vikhr, my Skhval range would jump from the correct range to a range value that was like 2-3km short of the correct range.

 

Indeed interesting that you had that problem too. I've actually spendt some time trying to recreate it in other missions, my theory being that it had something to do with ins alignment, or something like that. It never occured to me that it had something to do with the mission, although I can't remember if I had the problem while playing the campain as well.. I'll try to find out, and maybe make a post in the BS Bugs forum.

[LostOblivion]

Oh, I mentioned ambushes earlier. There are no ambushes...really...sssh. All Hammer 1 does is attack the airfield... :-)