Breakshot

Great stuff! :thumbup:

Gentlemen, please note the registration deadline is extended to 15th Sept to allow some of our Russian speaking friends who might want to join time to register their teams!

Mig and Mirage is fine, no 33s. Simple reasoning being: Mig and Mirage offers unique challenges. Su33 is just an 'easy mode' 27 clone... Blue Flag has the same policy. And it's so for a reason. Sent from mobile Android via Tapatalk

I second every word ^ It is frustrating and as a result I have seen whole squads disappear from MP scene. Quite frankly I myself have been semi retired (only fly squad events sometimes) from DCS in the last few years for this very reason. It's just not fun tweaking and fixing and testing, ALL the time, instead of flying... Sent from mobile Android via Tapatalk

I think in the interest of fairness the 33 is out of the picture. Seriously, how can it be a competition if there is an option to fly one aircraft in hard mode and another version in arcade mode. Cmon guys! As for Mirage and Mig, Stuge is spot on, they have severe fuel/weapon limitations, and can only serve an intercept/support purpose, needing to score kills quick and RTB early. They would however add some tactical options for some squads in combination with ASF fighters. Making things unpredictable and interesting. Such as a sneaky flanking maneuver, etc. Remember, aircraft selection is not fixed for any match. Just the pilot roster is fixed with minimum of 6 per team. And yes, it is true that F15 in this format has a significant advantage (doesn't it always? ... even in guns). But it makes for wrecking F15 only squads all the more pleasurable as the pressure is on them! But to take Su-33 is a big no no. So guys, use that energy instead to write to ED to get 33 a PFM, everyone wants it here just as bad... But for now, let's stick to SATAC ROE discussion here.

^^ guys take note that Su-33 would not be possible in this event as its SFM is not compatible with other modules. It would be advisable to take the 27...

Just tested on 104th. Works great. Back to normal. Good stuff Sent from mobile Android via Tapatalk

Very interesting. So you're saying one can use it while everyone else around are on new code... I wonder how that affects everything... Seems like a big discrepancy on the part of ED. Sent from mobile Android via Tapatalk

Is this setting server enforceable? If so, I would strongly suggest it to be used for SATAC, unless ED actually fixed it before then... Sent from mobile Android via Tapatalk

The net code is simply an evolution of the existing code from LOMAC days... The new algorithm removes an old problem by introducing a much worse one, IMO. I rather have someone going to the moon and back once in a while (it really only happened in extreme cases of server instability), rather than having completely false representation of where everyone is.... Sad but, it is what it is. I hope they find a good balance soon! Sent from mobile Android via Tapatalk

The 51st also have noticed this in our recent flights. The problem is extremely severe, especially on a populated sever! What I don't get is why ED made this new model if the old one had it right! Could have just added some sort of smoothing algorithm to prevent warp spikes... As it stands now BFM is a joke, you can't trust ANYTHING that you see... Sent from mobile Android via Tapatalk

The 51st PVO Regiment are reporting in with a full roster of pilots to defend our title! Flying strictly Su-27S. This time we are putting up only 1 "A" team, with pilots rotating in-out to meet the mission requirements. Up to 8v8 might be possible on some match dates (should both squads agree). Confirmed Roster as of 19 Aug: Breakshot X-Man Frostie Teknetinium Rage Holimoli Chimanov Seetricks And possibly more to make a return or fresh appearance... Looking forward to the event! S!

Netcode and pingtime does. Especially on the angle limits of RWR. This has been the story since LOMAC 1.02 Remember, the launching platfrom records the impact for kill (ranges and angles can sometimes be affected by server delays on the receiving end). We have seen cases where it looked like the missile passed by missing the receiving target (visual), only to be "killed" a sec or two later... Rule of thumb, react at least 3 seconds earlier than in SP. Example: if you can orthogonal roll an Aim 120 from say 2 bars from full on SPO. You have to start the maneuver at 3 bars from full in MP. <-=== though doing this in NEZ is a bad idea anyway, unless you like broken wings. LOL

Based on the latest word from ED, that ownship export will be a server enforced option that would stop any such mods from functioning in the upcoming patches, once disabled. :) So everything has been documented and brought forth to the developers... Including the lack of IC at this point, leaving the sim completely defenseless from any sort of exploit. Therefore, in the future, I'm sure any serious event or public server will make a decision whether such mods are allowed or not. Until that moment however, it is my beleif that such 3rd party 'enhancements' even if done in the name of realism or whatever, will always be used as an exploit in combat by some individuals.

It is a known fact that SARH missiles are completely porked due to ground/sky clutter and chaff over modeling since a couple patches ago. You can look it up on the bug report threads in the general section. The big question is though, is ED planning to do anything about that...? Sent from mobile Android via Tapatalk

Any update on this? Guys, the ground/sky clutter parameters need fixing. It's not really the missiles that are the problem... Has this been reported for a review? Sent from mobile Android via Tapatalk

Good stuff! Though some feedback on the stream from yesterday: It was impossible to watch for me due to the very high data rate... Buffering every 2-3 seconds... Even our guys in EU had constant buffering. Perhaps slightly lower quality and bit rate for the next one?

Of course they each have their strengths. But when you box, there is a ring... not a football field, if you get my analogy. There should be no situation whereby some one should just run circles around and out fuel the other guy without really taking the fight. Clearly at the hands of any good F15 guns pilot, with the current rules, the flanker has little chance as the 15 doesn't even need to commit to the fight and stay out of range all the way until the other guy is out of fuel, or has to start saving thus unable to keep up. This is different as to something like hammerhead, corkscrew or other vertical tactics you see in Mig 15, Sabre and WW2. This is not really BFM, IMO but rather a sort of intentional cat and mouse fuel game, Flanker simply can't win. You should at the very least review the fuel load for the next one. Sent from mobile Android via Tapatalk

Fun 1v1 event and good BFM training guys. Thanks for the hosts for setting it up... A couple of suggestions for making the scoring and perhaps the fights a little equalized given the big performance difference of the aircraft: Given I was the only Flanker in the top 4, the F15 is certainly much more potent, obviously, thus the final scoring should be broken down into 2 categories, Best Flanker/ best F15 pilot, etc. (for SA points awarded - not the final gift prizes). Of course the overall winner receiving more bonus points regardless of aircraft. Which also means, pilots should not be allowed to change aircraft once they have submitted their entry into the main draw! Actually I had no idea this was not the case... Once you take a bird, should stick to it, IMO. As for equalizing the fight, 3 possible proposals: 1. Fuel calibration should be done not at seal level but at say 7-8,000m, because as it stands now, the F15 simply out-fuels the flanker in the vertical chase. All my SF rounds I had basically big fuel issues while being on his 6 for like 5-10 minutes and had to conserve by not going gate (its hard enough trying to keep up with the 15 going vertical already). F15 can into space :D OR 2. Simply script a top deck of say 8,000 m for the fight forcing the ranges to stay close and avoiding the 10minute cat and mouse fuel chasing... it should still allow energy fights, just not the kosmonaut training flights. OR 3. Add two SR missiles for all aircraft types for more realistic type BFM scenarios (though I reckon flanker would be a tad more dominant here given the ACS override - as in the real world scenario assuming both planes get into the merge) Looking forward to 2v2s and more BFM events to come.

Guys just out of curiosity, are you positive we can finish the whole event this coming weekend? Given the proven difficulty from last weekend ... I think it's really asking much from some to fly 4 matches on the trot till potentially 6 am, then same thing again for doubles next day.... I'd suggest maybe stretching it out for another week? Just a thought... Sent from mobile Android via Tapatalk

Okay, no worries. Sent from mobile Android via Tapatalk

Much better! Thanks Sent from mobile Android via Tapatalk

@Flankerator, In the brackets and results, is it possible to correct all [51] tags to their appropriate format: <51>?

Well then it is clear to me that there was no reason to postpone in the first place. Just for reference, as some should know, any event or tournament, once the draw is posted it should never be alterted or manipulated under any circumstances. Basic sporting code 101. Now, I could understand postponing due to severe technical concerns, given the 1.5 beta is indeed in quite a sorry MP state at this moment, but to reinstate just a week later, when a more unstable patch just came out, sounds more like a move out of convenience for some, rather than logic...? My two cents on the matter.. Отправлено с моего C5502 через Tapatalk

Honestly guys with the current 1.5 build memory leak, and 20 sec constant freezes in any MP mission, I think it would be safe to say DCS Beta is currently unflyable. Most of the 51st guys are seriously reconsidering our participation as the latest patch made things much worse in terms of stability. Any event should probably wait till release version is out.... IMO.