LostOblivion

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

Last one there reminded me of one I have taken hehe.

I was just wondering why people are allowed to have tens of lines of text in their signatures on this forum? All the other forums I actively post on have a restriction of between 4 and 6 lines maximum that is enforced by moderators, and with small text at that. I often find myself being distracted when trying to read what people say when their signature contains 15 intrusive lines of computer specs or a huge image compared to the five words in their post. What gives? Lost.

Does TS really change plugin interfaces that fast that TARS will simply not work with newer releases of TS? It's kinda weird...

Also, the F-35 is really easy to get detailed information on. I mean, ask any hill billy aviation enthusiast that has this aircraft in his garage hobby collection. :)

Maybe the BS INS/DTS has erronous terrain data in BS2. Something that differs from the terrain we see. Maybe there is an 'invisible' hill that is obstructing the INS to calculate the distance correctly from what we actually see...

Glad to help. Lost.

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.

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? Which part exactly? Which voiceover message? :) 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, and we did not have any crashes at all when we tested it in DCSW .9. 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... 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. Thanks again. Lost.

Also, sometimes, ground crew will not re-arm, until right after you have started moving, they re-arm and say "Hey! What are you..." all at the same time. Like if there is a bugged boolean check somewhere...

It is just very basic. :) No fancy stuff going on there. All I do is let the edge of the unit symbol align on the ruler, or on a road, or similar. Another good way of aligning units quickly is putting them on a road with a "onroad" WP and then make it "offroad" and then make them face the right direction...voila, perfect alignment for a roadside parking column. ;)

Thank you so much!! It is good to know the hours of work are appreciated, and I am happy that you had fun playing it! :) On the topic of alignment, etc., I tend to use the ruler in the editor to align units, and then check the units in the game with F7, yes. It would be very helpful if they added the ability to have the ruler sticky, i.e., not disappear when you want to move units and align them according to the ruler.

You are only supposed to add thrust after turns, then idle throttle until after next turn again. This usually works 90 % of the time.

Good tip. I'll try not to kill the SA-11 with my 30 mm next time. ;)

There are no enforced options in this mission. Lost.

Wow, Speed, thank you for the kind words! It is always difficult to tell if a mission is ultimately any fun to play when we have tested it for so long and changed things along the way, but it is good to hear that you enjoyed it. :) Your thoughts on it being a busy mission with a lot of units has also come to our mind when making it, and we have several times wondered if we should attempt to reduce the number of units in it. Unfortunately it is much harder to remove units than to add them, and we decided not to seeing as how masterk's relatively old computer (GeForce 8 Series) ran it fine once he lowered his graphics settings a bit (especially turning down visibility range). Having said that, I tried cutting the overhead as much as possible by doing things like avoiding demaning trigger logic and increasing group size while reducing the number of groups (which is Dragon's tip IIRC?). In addition, the fact that this mission is close to Krymsk and Novorossiysk cities probably adds a lot of overhead for many as well seeing as how these are relatively big cities with a lot of complexity.

There is a new fully fledged A-10/BS compatibility mission available. "Taking Krymsk" features 4 slots A-10 and 4 slots BS. Enjoy. http://forums.eagle.ru/showthread.php?t=81622

V1.1 RELEASED! The .miz mission file is now available straight from the forums by following the link in the first post! :) Changelog:

I will do that, deephouse, thanks for the tip! You obviously know what you are talking about when it comes to voiceovers! :)

Ah, yes, I put up the post as I was waiting for the ED website admins to accept the new download on the DCS website. It is now available by following the link on the mission name in the beginning of the first post.

Will do. Had some trouble having Audacity output .ogg files correctly (it always cut the last 0.5 seconds off the tracks), but I will defenately give it a go if the DCS user downloads website has a slow download service for some of you.

Nate, that old dusty lawn-mover in your garage does not count! :P There are many lucky bastards who own one of the WW2 era aircraft are there not? All ED has to do is contact one of them, or better yet, become one of them, or even better yet, if what Nate says is true, then that is already the case. :)

Yea, and as masterk stated, getting access to detailed information on old planes is a piece of cake compared to modern aircraft under classification, etc.

You have to be joking? I enjoy playing BF3, it is a genius game and I have played it for many hours, but IT IS NOT A COMBAT SIMULATOR! On the topic of the announced DCS: Flying Legends. I doubt ED's intention was to put this into context with the other aircraft that will currently be available to fly once all the titles have been made compatible. Rather, it is a great addition to the ranks of legendary aircraft that makes up the history of flight aviation. Adding an aircraft such as the P-51 to DCS would mean that they are now aiming even higher for what a true simulator is, namely a virtual real world where players may do things they would not otherwise be able to, which includes flying events like airshows. Many of us have found that DCS is not just a great combat simulator, it is also very able to give us the immersion into plain flying, which cannot be found anywhere else with the same level of detail and flight model fidelity. Modern day real world combat does not see a flying legends aircraft in action, but they are such an important part of tradition and history that modelling such an aircraft with all the fidelity of the DCS standard would be a great addition to DCS in its own right. I think it is a great idea, and I am looking eagerly forward to flying any aircraft that is labeled a flying legend. Besides, you could always put some T-55s down in the desert around Nevada and have some fun with them -- they are WW2 endwar era tanks. ;) Lost

Mission: TAKING KRYMSK COOP8 v1.1 Aircraft: 4 slots A-10C, 4 slots Ka-50 Approx. length: 2-3 hours Me and masterk have been working on this mission for almost a month now with the ultimate goal of making a large scale airfield assault type of mission that involves both the Ka-50 and the A-10C in an operation that requires close cooperation between both types of aircraft. The mission features voiceovers done by masterk (Hammer 1) and myself (Command One) as well as thoughrough pre-flight briefing imagery in an attempt to add to player immersion. Although some aspects of this mission are unrealistic (e.g. the lack of SEAD), they were so chosen in favour of fun and diverse gameplay rather than 100 % authenticity. These features may be changed in future versions if the requests are many. :) The mission has multiplayer slots for 4 A-10C "Warthog" as well as 4 Ka-50 "Black Shark", although it may be completed with as little as two or three good pilots. General mission design, image work, and trigger logic done by LostOblivion, with a huge contribution from masterk on voiceovers, thoughrough testing, and as the Ka-50 player experience quality supervisor. Scenario Description: This is a joint operation between US NATO forces and the sovereign state of Georgia against Russian forces stationed at KRYMSK. The US 74th F.S. "Flying Tigers" is currently stationed at GELENDZHIK with 7 currently operational A-10s, the only combat ready A-10 squadron in the northern Kaukasus. The OP is spearheaded by a flight of A-10s from the 74th, callsign Hawg 1, as well as a flight of Ka-50 from the Georgian Army, callsign Dodge 1. GELENDZHIK houses the CAOC for this mission, Command One, with NOVOROSSIYSK currently supporting continuing insertion of NATO forces into northern Kaukasus. NOVOROSSIYSK may be used by Hawg flight to re-arm and re-fuel if needed during this mission. For the past week, allied forces have seized control of the suburbs south-west of KRYMSK and have established a forward operating base serving as a middle-station between the coast and KRYMSK. Housing a FARP, FOB MADRID may be used by Dodge flight to re-arm and re-fuel during the operation. Hawg & Dodge Tasking: You will be part of one of two flights for this mission, a 4-ship section of A-10s, callsign Hawg 1, or a 4-ship section of Ka-50s, callsign Dodge 1. This operation consists of three phases: 1. SEAD in the vicinity of KRYMSK. 2. Attrition of SOUTH SCREEN, two lines of defense screening the entrance to the airfield: point IMPACT, a hostile FARP compound south-west of the airfield consisting of mainly MBTs and light armor, and point COVER, an artillery bty. directly south of the airfield supported by AAA and light armor. (See photos.) 3. Covering the advance of Hammer 1 cav. assaulting KRYMSK airfield from FOB MADRID. HAWG FLIGHT will take off at 0710 and proceed to WP1 where they will anchor and assess the situation at and around KRYMSK, with the initial task of suppression of enemy air defenses (SEAD) near the city. Hostile SA-3 MERAD has been reported in the area defending KRYMSK, as well as SHORAD threats in close vicinity of the airfield. The favourable position of the mountains between WP1 and KRYMSK will allow Hawg flight to determine the position of any SA-3 sites from a safe distance at WP1 before ingressing the AO and engaging them from IP BANKS near FOB MADRID. Stay below SAM detection altitudes and use the ridges near the IP to mask yourself from fire until all SA-3 sites have been destroyed. Hint: When engaging SA-3 sites, destroying their tracking radar (see photos) will render the site effectively useless. Once all MERAD threats have been destroyed, continue with the suppression of any SHORAD threats, if present, such as Tor or Tunguska SAM, around the airfield. DODGE FLIGHT will take off at 0710 and proceed to and hold at point BANKS, near FOB MADRID, using the ridges to mask themselves from potential SAM engagement. Once Hawg flight has confirmed the destruction of all SAM threats near KRYMSK, Dodge flight will fly east to IP EDSEL and ingress the target area using the city as cover, assisting Hawg flight with the thinning of SOUTH SCREEN (point IMPACT and point COVER) as well as remaining force reserves stationed at the airfield, including grounded air assets. The compound north of the airfield contains most of the enemy reserves. (See photo.) This will enable our assaulting armor groups, callsign Hammer 1, to advance on KRYMSK with minimal losses. Hammer 1 cav. will follow the A-146 highway into KRYMSK and assault and secure the airfield, paving the way for Pontiac, two flights of chinooks bringing troops and equipment to build up defenses once KRYMSK has been taken. Hammer 1 is currently stationed at FOB MADRID, close to point BANKS and will begin their assault once SOUTH SCREEN has been sufficiently thinned for them to advance. Expect medium air defenses around the airfield area, including MANPADS. Note: Hammer 1 must survive and at least one chinook must land for this mission to be deemed successful. (Playable) Hawg 1-1, CAS, 4xA-10C "Warthog", UHF 251 (Playable) Dodge 1-1, CAS, 4xKa-50 "Black Shark", VHF AM 127.5 Dodge 2-1, standby CAS, AH-64D "Apache Longbow", VHF AM 124 Pontiac 1-1, Transport, 2xCH-47C "Chinook", VHF AM 124 Pontiac 2-1, Transport, 2xCH-47C "Chinook", VHF AM 124 Colt 1-1, CAP, 2xF-15C "Eagle", VHF AM 124 Overlord 1-1, AWACS, E-3A, VHF AM 124 Taking Krymsk Coop8 v1.1.miz