DarkFire

Good kills! Was one of those F-15's trying to shoot at you with his gear down??!! Loved the music by the way, what is it? For smooth control, firstly I'd recommend using control axis curves, somewhere between 15 and 25 units for both pitch and roll. This will help you make precise but smooth inputs. Next, feet off the rudder! The ACS on the Su-27 will perform co-ordinated turns for you, you don't need to touch the rudder. Nearly the only time I ever touch the rudder in the Su-27 is when I'm on final approach for a cross-wind landing. I'd also recommend flying more slowly for conducting WVR combat. The corner speed for the Su-27 is roughly 700 - 770 Km/h depending on weight & load. Flying above 1100 Km/h will give you a very large turning circle & also makes it much easier to over-G the airframe. Finally, the ACS on the -27 doesn't react well to making inputs in multiple axes simultaneously, i.e. roll then pull rather than doing both at once. Hope this helps. Great video!

Could it be that the targets you have locked are reacting and beaming you? Do you see any aspect change jest before they disappear? Medium PRF is better than high for side-on or rear aspect targets but they can still enter the doppler notch & disappear from your radar.

That's very good to hear. Hopefully once the ED team have finished with the initial 2.5 roll out they'll have some time to sort out smaller issues like the Su-27 ACS tweaks.

I've noticed this on occasion, but not only in campaign missions - it also happens in single missions that I've made. I've only seen it myself in 2.0 alpha though, not 1.5 beta or the stable version, though it could be happening there as well and I haven't noticed.

There's a known bug with the Su-27 autopilot. The problem is this: for it to produce stable flight the autopilot must be engaged at an indicated air speed (TAS is irrelevant as is ground speed) of at least 550-560 Km/h, otherwise it exhibits the oscillations described. Altitude is also irrelevant, the IAS is the limiting factor. The reason most people don't notice the oscillation problem at low to medium altitudes is that the IAS is that at most commonly used altitudes IAS is well above the minimum permitted value. Note that the described oscillations will also start if your IAS falls below 550-560 Km/h, even if your IAS was above that when the autopilot was engaged. What this means in practice is that using the autopilot limits you to flight at or below 10,000m altitude. At any altitude above this, unless you're in afterburner your IAS will always be below the required 550-560 Km/h minimum. This is definitely a bug and is not real Su-27 behaviour. The real Su-27 has an autopilot mode that can pilot the aircraft through a landing pattern and in to final approach, where your IAS will be 240-300 Km/h (depending on weight and other things). The DCS Su-27 autopilot can't do this and will exhibit the oscillations as described, which at that sort of air speed and very low level can be fatal. With regards to the autopilot, what you need to remember is that unlike some aircraft the automatic control system of the Su-27 operates by adjusting trim settings within the flight control system, rather than directly adjusting control surface position. Disengaging the autopilot does exactly that - it simply turns the system off. The "ACS reset" function is slightly different. While one of the autopilot functions is turned on, if control surface deflection exceeds 20% of maximum value, or if the aircraft exceeds 80 degrees of bank, the ACS will drop in to manual mode. As an example, imagine that you're motoring along in altitude hold mode when you suddenly notice an incoming missile. You grab the stick to carry out an emergency max-rate turn to avoid the missile. Under these circumstances the ACS will drop back to manual mode, but the ACS actually works using the trimmer system so giving it a manual input while it's in automatic mode (i.e. autopilot turned on) causes the system problems. You can try this for yourself: fly around in alt hold mode, do a snap roll to drop the system back to manual mode and the ACS reset warning light will probably illuminate. Try re-engaging the ACS and see what happens :) Even if you don't re-engage the ACS you'll likely notice that the controls have become quite sensitive and twitchy. When the system has dropped back to manual mode due to a drastic manual command input, to restore the proper function of the system it needs to be reset, hence the reset command being different from the ACS on/off command. Pages 44-45 of the Su-27 flight manual give a description. Hope this helps...

This is a very useful thread for mission building. Could one of the mods sticky it please?

Accurate as it is now. The MiG-29 does not have the head-down-display & datalink systems that the Su-27 has. The HDD on the MiG-29 (at least all the versions in DCS) is purely a HUD repeater.

That's much too fast to taxi. Keep it under 35 Km/h and you'll be fine. The real Su-27 has an automatic braking system (I suppose like anti-lock brakes on a car) that unfortunately isn't modelled in the game. To help avoid popping tyres when you're braking after landing dab the brakes quickly on and off.

I used to be able to reliably crack bunkers with 2 x Kh-29's from my Su-25T. I'll have to check it again to see if anything might have changed.

I was going to test this very thing today when I got up :) So, maybe it's more accurate to say that bunker resistance has been corrected vs non-penetrating munitions. Looking forwards to playing through Heavy Sky again - really enjoy that campaign.

I don't think it's an issue with the mission per se, I think a possible bug was introduced in the last patch whereby bunkers have massively increased damage resistance. Thanks for your continuing efforts to fix the campaigns though, much appreciated :thumbup:

That's probably the cause of the issue. I'd imagine that destroying the bunkers are a mission success condition and under the circumstances they aren't being fully destroyed by the bombs dropped by the mud hens. I wonder if this is a bug? There's a thread in the A-10C forum that's vaguely about the same topic.

Did the F-15E's actually destroy the bunkers? There seems to be a bit of an issue currently in that bunkers take an insane amount of HE to actually destroy.

That's a real shame. ED and 3rd party dev teams have done absolutely amazing work with maps and various aircraft - obviously these are their core competencies. Esim on the other hand have done what is at this point by far the most realistic tank & armoured warfare sim that's ever been available, very much the "DCS Ground Warfare" game. From a lay person's perspective it'd be amazing to see ED sub-contract ground warfare development to Esim. Make Esim '2nd party' developers. ED could develop maps and then leave Esim to develop modules, or a module, for ground / armoured warfare. Given that both DCS World and Steel Beasts are grounded in the same hard-core realism, subcontracting ground warfare to Esim would seem like a very good fit for ED's concept for DCS world. I really hope this decision gets revisited in the future, good things would come of it.

The altimeters on all the DCS aircraft under-read as altitude increases, even if you calibrate for QFE on takeoff. The effect gets larger as altitude increases. Take a zoom climb for example, something I do occasionally in my favourite Su-27: at the top of the climb the HuD (and altimeter) are both telling me that I'm just over 27,500 metres altitude, whereas the F2 view says that I'm above 35,000m altitude. I gather that the atmospheric modelling in DCS probably needs a little bit of tweaking. Good luck with the exam!

Yep, at anything over ~1,450 Km/h IAS.

Interesting result: when I un-installed the game from my mechanical disk it didn't delete the saved games directory. Result: when I did the new install on the SSD it had preserved my log-in details, key bindings, game settings etc. Worth knowing for anyone intending to re-install the game...

Thanks, I'll make sure I save that :thumbup:

I'm about to re-install DCS World in order to move it from my mechanical drive to my SSD. What files do I need to keep in order to copy across my log book & bey bindings?

Instantly donated. Incredible work!! Waiting for the link to work again :)

Ah, you're absolutely correct, my fault entirely for mis-reading your post. This is probably a better example of what you're looking for: [ame] [/ame] USAF Thunderbirds display team routine from 2015 which includes both group formation and solo elements. Fast forwards to 19:45 for the start of the action.

Great stuff, thanks for posting the links :thumbup:

When you say loss of control authority, what exactly do you mean? You will (technically) overspeed the Flanker going full AB at sea level, but I've not noticed a lack of control authority except for the hydraulic force limit of the control surface actuators. Is that what you mean?

The -1 (non-classified flight manual) for the F-15 is publicly available, though the only one I've been able to find is behind a paywall :(

The head down display on the Su-27 is scaled like a map - in vertical scan mode 2Km represents the scale of the little line underneath, not the entire HDD display, so the entire display is covering something like 16 Km which should be more than enough for any WVR mode. Vertical scan and helmet-mounted-sight modes will only start to lock targets under ~15Km range anyway (depending on target size, aspect, radar or EOS or both etc.) so until you approach this range you should probably be using one of the BVR modes anyway. To answer your question, I don't think it's possible to change the initial default values for the range scale settings on the HDD. They might be in a lua file somewhere though I suppose.