microvax

That was unexpected what happend there. :D Thats great, there was a call who can help the groundstrikers and them beeing bounced at bulls and I was like "Well If I am not helping them, I am not doing my job.". So Yolo dive, it was. 2 Aim7 and 4 Aim120s. :D Well, I guess stuge was wrong on "he cant live through that", because the two AIM120s he fired actually were dodgeable, but the epic last ditch aim120 salvo Knight pulled off after beeing splashed, well roughly 2,5NM from inside the turn is not really dodgeable anymore, expecting the Wreckage to mean "its fine". :D Realized to late that I just should have continued straight on through, pursue Maverick and use the Afterburner sustainability to my advantage running from the rest of the bunch but hey, I really had great fun rate 11/7 on IGN. Goal was 1 Kill, survive as the last mirage, if possible degrade the Aggressors SA by beeing the constant high guy and ditch advantage if the strikepackage needs protection. All achieved, even if the advertised to be protected strikepackage wasnt there. :D [And maybe redeem myself a bit after the last plans horrible failure and show that its possible to be succesfull in the Mirage even in a Redflag scenario. ;)] Anyway really great fun flying with/against you guys I am enjoying the challenge a lot and look forward to the development of the event and possible cat and mouse play which is going to develop with tactics and strategy. :) Flame was telling me 24/7 that the Mirage is a bad Idea and I will achieve nothing and die early again. Having watched Tigers video [faboulous Merges !!! gotta deploy more presents ;)] I am happy to see that I at least occupied and divided your SA a little and surprised you with some Mirage TWS fox2 action. ;D Looking forward to what situations next Redflag will bring up. Thank you guys for hosting the Event, If I can be helpfull in any way, let me know. :)

You get status updates if a asset is under attack and basically that is all you would get I guess. And not who in what, with what killed what and exactly when. :D

Pretty sure it wasnt, but will check back with the guy which did the testing on it.

You gotta replay the track first, since exports are restricted.

thx for le kind words. If you really want to, give me a shout and we can set up some kewl stuff. ;)

Note: its a Magic2, not a 530 as the track says. Just found this gem, I have to say I was only aware of Mustang, my energy state was high enough to probably defend anything thrown at me from the ground up, but still was kinda funny when I noticed that situation while looking at the tacview. :D Pity commentary for this bit is lost. ;D I am kinda surprised this worked out so well for me having run the numbers just 2 days before the event, which also lead to me beeing a little over cautious sometimes. There is optimisations to be done I guess. :D

lel You guys even havent found the best reference one could make for my nickname. :D Try harder.

Ahhh, pity. :D Ran into the same kind of thing myself already, doesnt even work if one does turn on the archival function during the stream unfortunately. I think a post event analysis by the commentator or whoever is qualified, [which is absolutely not me for an exception ! ;D], would be even better to watch it afterwards in some ways, but tbh doing a highlight video is just way to much work to do everytime. Looking forward to what you guys make of it. :))

https://forums.eagle.ru/showpost.php?p=3064080&postcount=1235 There is at least one. :D I totally get that the FC3 missiles are garbage all together pretty much. The ER and ET and AIM120 pretty much only work because they have a higher booster output. I think datalink really would be the best option. I personally do not mind flying against ER and ET or AIM120s with a Mirage, but I think a lot of other people would not like it and the ranges we fight over in blueflag are to small for that kind of ranges imho. Same reason for the kinda low end Airfield defences. BTW afaik the AIM7 does have a lower topspeed then the r27, guidance should be the same AFAIK, dunno about chaff resistance.

soon TM :D thx for le news transport

Yeah difference is that the Mirage has a real track memory but doesnt guide SARH while no LOS is established, while FC3 track memory magically CW's a target beyond gimball limits. ;D

You can disable the D2M server side since a kind of a what if feature in terms that it has the capability, but no airforce used it. Imho E* and AIM120 simply have a to big F-pole for the distances we are fighting over. Same reason for not higher end base defence SAMs.

I dunno, the Mirage already doesnt have its datalink in game, asking for le flanker family datalink and disabling the D2M is a little odd. :D I know the 2000c didnt carry the D2M in any airforces service, even with it beeing technically completely capable of it, its just that nobody bought the option for the C, just the N. I mean bring it, but you will probably notice that if the Mirage pilot is doing his job correctly, removing it will change nothing in A2A, and will only remove the manpads warning functionality its really inteded for, when you are doing A2G. The ET cant even pick up the Mirage headon before a properly launched 530 reaches the flanker, and in combination with ERs you are defensive while supporting the shot in anyways and you can not rely on the D2M because its only lower hemisphere. So you assume Ts in the air and flare anyway. So please, if you think thats going to make the flanker great again, bring it, even if I find it mildly funny that people think, that is going to give them the edge. The numbers, as far as I have seen, did recover from the complete rubbish state. If possible datalink could be a dynamic feature at the start of a rotation. So if redfor was massively outnumbered last rotation, so they could not afford someone on GCI, enable it. If the numbers are not worse then 2:1 keep it disabled. Just that nobody does GCI, doesnt justify datalink. Oh and BTW. Flanker and F15 completely unrealistic feature, because of which ER and R and AIM7 would have to be removed like the D2M, to achieve more realism. SARH missiles from FC3 are actively guided within the target track memory even outside gimball limits. I am fine with D2M disabled, I am fine with D2M disabled and Datalink dynamically enabled. I find it pretty topkek to ask for D2M disabled and datalink enabled, feels a lot like the wish to have it easier to kill mirages, while its not even of balancing concern, since both sides have Mirages.

No news from VKB europe, super sad. :((((

You can acording to the manuals iirc, its just not working atm in dcs.

It was great fun participating. Bushmanis plan worked really well and we had some very good experience with consolidating flights after losses were taken. I will stick with my luminati baguette launcher I think its still very viable to take on the F15 with it, its more the mutual support on aggressor side that makes a fox1 a pretty risky maneuver then the aim120s of the targeted F15. I take the 3-4 AIM120s at once in the endgame kinda as an compliment, the push to save as much of our strikers as possible, definitely was the right thing to do over staying alive imho though. Really compliments to the 104th guys protecting each other from the 530s NEZ launches. Next plan is already on the drawing board. ;) Really hoping a recording exists somewhere. Even audio only would be surpreme to overlay it with le tacview. :) Allways interesting how other people perceive your flying, gives a lot of input on how to improve. :) The commentary I got to hear in the last minutes was really nice. EDIT: One GCI per team would be super duper cool, it really enhances air to air so much. Imho it basically goes from fighters shooting each other to fighters controlling airspace and gives you so much more SA its simply amazing. Also declare on visuals you do not want to scare with radar is such a usefull tool.

Bold claims for not checking your tack file m9. You can just run the track and verify and it would be nice to know how you distinguish an intentional from an unintentional TK.

Signing up for le 104th forums atm. Will coordinate with Flame what we will bring to le table. We are reorganising internally atm so its all little ad hoc but I am sure we can come up with something. :)

Okay, now for the explanation of my question about the methodology behind the 104th statistics functionality. :D The "lets make a quick video" escalated pretty quickly to become a 35-40 hour editing job and my first bigger scale video. Its far from perfect so criticism is very wellcome. The first 3 Minutes is just dramaturgy wise matching intro made of footage I had lying around, the rest is a compilation of a sortie =RvE= had on 104th earlier this week. :D I hope someone has fun watching it, I definitely had fun making it ! :D And yes, Sovietwomble kinda had an impact on the tone here and there. ;D

_fould langue_ YEAH !

Yeah blue efficiency is at a historical low as well tbh.. Lots of people in hibernation. Greg etc. are just very busy and said that more then once, that they just let the server run for a) testing and b) having at least something up while they dont have the time to support an actual round of blueflag. We are running red again next testing round btw.. ;D There is really no point in flying on blue atm.. A10c would be noice on red side, give blue ka50 would be nice as well. I think that setup before round7 was really the most fun one.

Btw, how are the airkills counted vs the total airkills ? Didnt wrap my mind around it yet, is the k/d airkills by missile type used, or by target hit ?

Yeah, it is true that quite a few of us came together via BF and that flying on BF is a pretty big part of RvE. We had quite some internal discussions before we did go red the first time, because exactly that, we are a pretty big block of reasonably well organised people which has the potential to turn the tables in many situations. For testing we agreed on 50/50 red/blue, but atm even with us not beeing on blue for that long its back to pretty onesided numbers. Major part for us not flyin red more is really the A10c. For CAP we are pretty much evenly distributed Flanker and Eagle fanboys. I mean you guys would probably have a hard time choosing to fly f15s on blue as well, if red was in the favour all the time. One does that for so and so long for the goal to balance the thing a bit, but after certain amount of time you want back to your favourite airframe. :D The lacking messages imho make the thing a whole lot more fun, you dont know if the SA3 TR is really down, you dont instantly have feedback on what is taking off and landing where, more specifically, you dont know who it is. I like that a lot, especially for the a2g aspect thats a huge plus. You can actually pull off sneak attacks without instantly beeing swarmed. I agree whole heartedly that friendly rivalary is a lot of fun, but I think in BF we are better off with them off, since the aspect is less on a2a, than on flying an operation with multiple roles. Just as an example, in 104th I think they make a lot of sense, the a2a part is way more emphasized there, and there is a lot of space for that friendly rivalary, without limiting other aspects. On the topic of friendly rivalry, Toss bombing on the viggen is a marvelous anti runway tool. ;) No need for 50 000ft dive bombing anymore. :D

I am not speaking as or for the event organisers, I just employed the we as speaking for a group of people believing that the amount of intentional TKs is ignoreably low atm. I indeed know the problems of borderline imbalanced numbers. And I wish we would have the opportunity to bring balance to the force without shooting ourselves in the foot, but thats basically not possible as long as a10c and ka50 stay this way. For the kill messages, I do not think they are a bad Idea in every situation, there is missions and servers where its perfectly reasonable to have them on and it would be counterintuitive to turn them off, but in Blueflag, where the focus lies with operational thinking, I love the non feedback approach. Having to keep the SA without the messages is way more fun imho then having a text history tell you. Unfortunately, as you pointed out thought, thats kinda getting overrun atm by the massively stacked numbers.

Hmm, current variant of blueflag has 2568 units overall. With the nonexistant documentation on the DCS engine its basically a big guessing game and unit amount could be a factor, could be none in this scenario. Given DCS is basically running everything but audio in a single thread AFAIK, there _has_ to be a scaling factor with the number of units. Might be worth trying the whole thing with just half the map actually beeing part of the mission and see how that goes. Also it might be the way DCS handles zones, again something that might be worth testing, putting all units in 40% of the Area. Ideally with 50 players especially the first _should_ not make any difference, since 50 players are not going to make high frequency of data processing on many unit [groups] necessary, but knowing how DCS is optimized in general, I would just guess the optimising employed, if at all, is not reducing the linearity that much. For the second test scenario it should perform considerably worse, given DCS is single threaded, and more units _will_ require higher frequency data processing. If it doesnt, zoneing is probably the issue. I want just to remind everyone that basically the terrible lag came back with an DCS patch, not with any changes in the scripting. So I doubt its something the Buddyspike team is doing wrong. Problem, even if one can find a good performance metric to measure performance, its probably not going to change things. Because ED undoubtedly knows the state of DCS MP and its simply not their priority atm.