Stuge

Much respect to all participating pilots. :thumbup: Razer never reads these forums but he was the hero of the day, his flying was way beyond the call of duty, I was just there riding along :) Our 2v2 tacviews have been added to my dropbox: https://www.dropbox.com/sh/hkgrhw0kukoflkn/AADtcIkD22ztrvOhOaWTHJwja?dl=0

This would be nice yes. A simple way would be to have the game give feedback in debriefing. Speaking of that the mission structure in DCS is really too simple. Voice acted briefings and debriefings should be standard, and the missions and campaigns themselves be much more thought through and polished and bug-free and also with more interesting plots than country A goes to war with country B.

I'm looking forward to this GG! Any idea when? 1 year? 3? 5?

Oh yes double elimination is very good!

Sorry, that wasn't very constructive I know. I'll try this time.. Surviving a BVR missile shot in most cases is a combination of high speed and high G. Faster is better and more G is better. Why fast? Because a missile from rear or side aspect must chase you longer. Thus most often it is not beneficial to slow down to corner speed. Corner speed is most important for dogfights! Extra speed in BVR is bad only if you are shot from the front sector and do not know it, then you will fly into the missile faster :) In all other cases of BVR.. speed is life. It keeps you alive, and it gives your own missiles a longer reach.

Lol :) Sorry :)

One way to use the gyro sight is to set it to minimum possible range, then fly close enough so the target fills the pipper completely. This way the required "steady state" time is minimal, and accuracy is good! I use this technique with Mig-15, I find it gives best accuracy for the situation where the cannon is powerful (only a few hits are required) but ammo is very limited so missing a lot is not good :) Also in Mig-21 this is the only way to use the gyro sight. You cannot adjust the range setting, it is at a fixed range.

Improving is a very subjective concept :)

Oh it does, that's the whole point of the gyro sight! You set the target wingspan, then adjust the range to fit the target inside the pipper, aim so the pipper is right on target, and pull the trigger! The problems with gyro sight are a) your range estimation can easily be a bit wrong because you do it visually, resulting in wrong lead. b) you need a stable target. if the target is constantly rolling and switching directions the gyro reacts too slow and cannot calculate proper lead.

My tracks from cockpit: https://www.dropbox.com/sh/u6t0l3tcvqyie7m/AABNe-TRtPwDHHvtzwhLfC0Sa?dl=0 Note that sometimes the view in the replay goes out of sync, you can see this when the view is pointing in a pointless direction, like downwards only looking at instruments, or helmet sight not matching the locking angle etc.. in this case I recommend overriding the view control by using the view keys (numpad default) and looking around yourself ;) Also, as I play with old school 4:3 aspect CRT monitor, the field of view is different when replayed with a widescreen monitor - upper and lower edges are not visible in a widescreen replay.

If you manage in this scenario to lose track of the opponent before merge, you kindof deserve the confusion :P Unclear cases can be instantly verified from the Tacview replay! Night fight is fun, but is not anymore a BFM contest but a test of search capabilities and especially the rod cell function of the retina of the eye :) Also test of how dark you can get the room.. sunlight coming through the window curtains? Too bad :D Glad you enjoyed the dogfights, the more people we have doing it regularly the more fun and rewarding times for everyone!

Guys remember that Flanker needed this fix more urgently than does the Eagle. Surely Eagle's structural limit modeling will come later.. but you can't have everything at the same time! So this is a definite improvement. It's a step towards better realism. You can't make everyone happy, and it may break apart a little too easy in some cases but still.. good job ED!

Umm.. I'm sorry to say but this is not good and actually makes things more difficult because it attempts to force a merge within certain parameters. If this is the case, these parameters must be clearly defined to the details of at the very minimum altitude tolerance (for example 2000m +/- 50m) and perhaps separation distance. Enforcing such tolerances is time consuming, since they should be reviewed from Tacview after every single round to determine whether someone went outside parameters or not. Forcing a controlled merge also removes the possibility of any pre-merge tactics which is an essential part of BFM. Meanwhile, allowing a free merge style is extremely simple. The definition of merge is the point in time where the two fighters reach their closest distance from each other. This is very easy to enforce because if one fighter breaks this rule, you have a head-on shot which is easy to see. So, I really recommend not to artificially make this a problem when there is no problem. Whoever complains about going low before merge clearly has no clue about what BFM is about. If you really want to prevent this, you need to set the fight to start so high and so close that diving all the way to the deck is not possible before merging. Or alternatively, set some SAMs below the combat area to act as a deterrent for low altitude flight. These would be reasonable ways to force the fight higher.

Thank you everyone, flawless organization, refereeing, and many worthy opponents! Special thanks to <51>Teknetinium for an absolutely nerve-wracking adrenaline pumping match!! I haven't been that pumped up for years. Tacviews from my fights can be found here: https://www.dropbox.com/sh/hkgrhw0kukoflkn/AADtcIkD22ztrvOhOaWTHJwja?dl=0 I might post my cockpit tracks too, tomorrow... now off to sleep. S!

Ok guys got it thx :)

Ironhand, I don't understand the part where it describes different weights. 150000 kg?

Ok below is a copypaste from the 104th site to change version number! I believe the previous version number is 1.5.3.51417 Open a command prompt window Type CMD Open Command Prompt. Type: CD\ ENTER Key Type: CD Program Files\Eagle Dynamics\DCS World OpenBeta\Bin\ (this should be your DCS directory) ENTER Key Type: DCS_updater.exe update 1.5.3.51417 ENTER KEY Alternatively just edit your dcs_updater.exe shortcut icon properties and add after the command line "update 1.5.3.51417"

There are instructions on 104th teamspeak server how to downgrade DCS to previous version. It is really simple too, i can post it here in a few moments if someone doesn't beat me to it.

Damned if you do, damned if you don't :) Always someone will be unhappy but... the general direction should be towards realism so.. good job ED!

Haha nice timing with the new patch from ED :D

I'm not watching tracks, I'm performing live testing with external view which shows the G. I managed to go to at least 12.5 G without breaking it. Hmm you're right the pitch CAS off does give a little extra G. May be future tactical applications :)

Short test revealed that Flanker disintegrates at ~13 G. Eagle doesn't seem to be able to reach 13 G under any condition. So in that respect it's all good, maybe a structural limit doesn't need to be modeled for Eagle. However consequences from exceeding maximum speed could be added for all aircraft...

Yeah, it's gonna be 7 seconds now :)

Oh this is gonna be good.. two birds with one stone: 1) Complaining about unrealistic high G maneuvers stops 2) Using S key will still kick ass at slow speed maneuvers but now even less people will bother to learn it :)

I just interpreted wrong the part where Zeus said they couldn't catch the bug in action... It is not unusual for known DCS bugs to go unfixed for years. I don't feel ripped off, I like pretty much everything about the M2000. But basic deficiencies really should be prioritized over the more trivial stuff :)