esb77

Tried it in the latest version of 1.5 and had no problems, aside from only hitting two trucks. You might check your control configuration, make sure things aren't double bound, or incorrectly bound. Entered air to ground mode, pressed V four times to get to the KMGU/bomb rack release mode, flew through the gates at about 780 km/h, put the pipper about 50 m ahead of the nearest truck, pulled and held trigger until I heard the last of the submunitions release. Are you using 1.5 or 2.0 by the way? Just because something works in 1.5 doesn't mean the same is true in 2.0.

Hm, I dunno. If we're simulating here, I'm surprised they even got the airframe inspection done in just 32 min. I would think that an over-g resulting in airframe damage would be more like, "Come back next week if you've finished the paperwork by then, and remember to bring us[the ground crew] a case of vodka when you do." "More realism," is a doubled edged battle cry in some cases. ;)

F key view controls stopped working for me in current (as of today) version of 1.5. F1 through F6 at least, don't normally use the higher number ones. Numberpad in cockpit views still work fine. This was in the base Su-25T module, have not tried payware modules or payware FC3 planes. Edit: in further testing I was unable to reproduce the effect, even in the Mozdok landing mission where it originally occurred. Restart of DCS and/or removing and reattaching HOTAS controller possibly fixed issue?

I had this happen to me when trying to configure controls for the Su-25T on a thrustmaster X flight hotas. It took long and/or repeated presses to register keybinds. Also had an issue where none of the F key view commands worked, even when rebound several times.

I can see at least two potential technical problems with implementation of this without good source materials. As far as we know the Su-25 and Su-25T don't have a means of displaying JTAC lasing dots for the pilot. This creates a challenge, as the JTAC and Pilot must establish the precise target, the azimuth of the side of the target that is painted by the lasing, and then the pilot would have to launch the laser guided munition with incomplete information as to whether the launch was well within good launch parameters. Depending on the coding of the missile seeker logic (in real life), and whether the ground lasing unit has an ID built into the designator system, there also might be problems convincing the missile to accept the dot as a target, or even to launch at all. Source material for Russian systems seems to be generally harder to obtain than source material for NATO systems, so if it's not implemented it may just be due to lack of details about the specifics of how it works.

So, what I'd really like to see is some posted flight plans from these flights where wings came off. You did have flight plans, right? I'd especially like to see the source or authority that was the basis for entering combat or performing BFM training at loads massively beyond what the manual states is allowable. Who signed off on that as an acceptable practice? This is aviation, there has to be traceable documentation somewhere, so where's the authorization for the overweight maneuvering? The Russian Airforce typically does not load up every possible station with R-27 E versions. I'd guess that they also don't start pulling high g turns with full tanks. The mass and speed for which the Su-27 is rated to pull 9 g is about what one would expect for a well planned and executed air combat mission that had closed to WVR. Are we supposed to be assuming that this is purely coincidence? I mean really when it comes to problems with the aircraft simulations in DCS, the biggest most glaring flaw is that completely unqualified people are allowed to operate the aircraft with no qualified supervision. On the other hand, having pilot error be the primary cause of aircraft loss means the folks at Eagle Dynamics must be doing something right. ;)

I don't have FC3, just the stand alone modules for the Su-25, F-15, and Su-27. The old training missions, or at least some of them are definitely MIA. Easy to confirm using a file search for the ".miz" extension. They may reappear or be replaced at some point. The Su-25T training missions vanished briefly before their most recent revision.

A relaxed stability airframe with damage to its control systems is not an ideal aircraft for safe gliding. In a stable airframe, flight changes are resisted, so the plane tends to self correct to stable flight. The airbus you cite as an example has a classic stable airframe design. In an unstable airframe, this does not happen, so the correct active controls must be constantly applied by the FCS and/or the pilot for flight to remain stable. If the controls are damaged enough so that this correction does not occur, rapid loss of aircraft control is the expected result. The Su-27 has an unstable airframe, the benefit is great maneuverability in combat. The downside is that control system malfunctions or damage are potentially unrecoverable situations. This is a common problem with advanced FBW combat aircraft. If the system is sufficiently complex even things like an airspeed sensor failure can cause a crash that may not be preventable by the pilot(s). The scripted behavior Ironhand describes sounds suspicious, and may well be improperly modeled. However, once the hydro was fully gone the plane would be uncontrollable in any case, so I'm not sure how much that matters.

So what mechanical backup system are you talking about? As far as I know, once the fluid is gone you loose all control authority, and I've never seen a source that says differently. I've seen lots of sources saying that the control system is purely FBW hydraulic, i.e. no mechanical cables for backup.

Not at all improbable. Overloading a tire and then subjecting it to lateral forces is an excellent way to rip a tire off of the wheel rim. You're trying to land at 168% of the base recommended weight for those tires. Adding large lateral loads to that is a bit crazy. You're not flying like a professional pilot. A professional would be dumping excess weight as fast as they safely could to get to an allowable landing weight. Try your experiment again with a gross aircraft weight of 12000 to 14000 kg. You should be able to land successfully if the plane isn't overweight by a huge margin. That would mean reducing fuel to about 800 kg and jettisoning 2000 kg worth of stores from pylons. Or keep the fuel and jettison everything on the pylons. Edit: In real life they wouldn't put a really heavy load of weapons on the plane unless they expected to use them during the flight. They're already accounted for as expended in the budget, so dropping them is a small price to pay for getting the airplane down in one piece. Saving the pilot is important, saving the plane is not quite as important, the fuel and weapons just go up in flames if you use them, so it's not much of a waste if you have to drop them to save the pilot or the plane.

I was curious about whether your loadout was too heavy, and couldn't find a definite answer. According to Sukhoi, the normal landing weight for an Su-25K is 11020 kg, and the maximum is 13200 kg. Your fuel and weapons loadout gives a gross aircraft weight of roughly around 18500 kg in DCS. The Su-25T supposed to be rated to take off about 2 - 4 tonnes heavier than the Su-25K, but even so, an 18000 + kg plane is probably over maximum allowable landing weight limits. Unfortunately I couldn't find official numbers for the T variant's maximum landing limit and the landing weight limits are not included in the manual. If you dumped or burned fuel until you were down to something like 500 to 800 kg of fuel, it should be much closer to a good landing weight, maybe even within the proper limits for a T variant. Edit: I'm pretty sure that the official landing weights for the 25T are greater than for the 25. I've never seen anything mention of improved gear though, so it's entirely possible that the amount of force needed to cause gear failure are the same in both variants. Without more official information I'd recommend always being extra gentle when landing the 25T.

Well, apologies for the tone. It was a tone for a pilot who didn't read manuals, not a tone for a gamer asking a simple question about a game. In terms of the crosswind significance the force on the chutes is proportional to roughly the third power of the relative airspeed. So IAS^3. That's a LOT of force at landing speeds. The chute is attached to the tail of the plane, so there's several meters of airframe acting as a lever that the chute is pulling on. It all adds up pretty quickly. I am a bit nicer than my posts sometimes indicate so for your benefit I present: and I told you to look in Docs, but really it's in DCSWorld/Mods/aircraft/Su-25t/Docs, so I figured I owed you the effort of going and finding the full text, since I pointed you at the wrong location the first time.

You're missing the section in the manual where it explicitly states that for landings with significant crosswinds the procedure is to NOT use the drogue chute because it causes the plane to weathervane (turn into the wind). The chute in real physics is an aerodynamic control surface not all that much smaller than the wings that will try to point you directly INTO the relative airflow. That means that in a crosswind it's going to exert a very, very powerful pull that can exceed the ability of both the gear and the plane's control surfaces to counter. If you think you're going to go off the end of the runway, say on an 1800m runway that's icy, and for some reason you can't divert to a field with longer runway or one with a smaller crosswind component, you can try waiting until the last 500m or so to deploy the chute. Once you're below 100-125 km/h the chute is a bit less likely to pull hard enough to force you off the runway. It's also worth noting that if you're landing with a heavy load, you have to land faster (which makes the chute more of a problem in crosswinds) and you're placing an additional load factor on the landing gear, which of course increases the risk of failure. Basically your problem was a combination of multiple pilot errors: Failing to read aircraft documentation (Check out the manuals in your Docs folder in DCS). Failing to follow weight recommendations for landing. Failing to divert to a field with landing conditions appropriate for pilot skill level. Failing to follow crosswind landing procedures. Given those failures, if the plane was still in a more or less salvageable state, you actually did fairly well. Aside from making all the easily avoidable pilot errors that is. You also might want to learn how vector math works. Predicting crosswind components and how to correct for them is vector addition. Most calculus texts cover that, some trigonometry texts cover it, and of course you can always look it up on Wikipedia. At any rate the only bug is in the pilot training procedures. There's a reason they don't just hand out a pilot's license to anyone who walks into airfield and asks for one. Practice and education. The Su-25 can be a bit tricky in crosswinds because of its big tail fin and narrow gear stance (and improper chute deployment makes it a lot worse), but if you read the procedure and practice, you'll get it right soon enough. :thumbup: I'll also note that having a HOTAS or Pedal axis bound to the rudder really helps a lot when landing the Su-25. Keyboard can be a bit rough, as it lacks fine control. Edit: I did the math, and the wind would have been pushing you across (off) the runway at about 24 km/h, and the relative wind direction would have been 6.5 to 14 degrees off of the runway centerline depending on aircraft speed at chute deployment. Pretty much what you described.

If you're in a plane that's short on fuel in low vis conditions an instrument useful for flying IFR patterns is about as useful as aircraft avionics can ever get. Or to put it another way, since our lives and our hardware aren't on the line, we virtual pilots have some serious distortions when it comes to evaluating importance in aircraft features and flight procedures. ;)

If by FPM you mean decent rate in feet per minute, well the Flanker is organized in metric so it gives readout in m/s both on the vertical velocity indicator and the ascent/decent rate display on the right side of the HUD. If that's a typo for PFM (professional flight model), then be aware that the Su-27, Su-25, and Su-25T have fully developed aerodynamic models, while the Mig-29 and Su-33 do not.

Assuming you are not in the A-10 C and just forgot to turn on nose wheel steering and your plane is not damaged (check the hydraulic pressure gauges) the problem may be input configuration or hardware. It is not always the case, but the most common reason for strange input responses is having multiple controls bound to the same function. So check your keybinds and controller binds as a first step. Be very thorough, for example check mouse, stick, throttle, keyboard, etc. Some of the controls can be accidentally bound to things that you wouldn't normally think to check. Faults in the input hardware is probably the next most common cause. Once those have been checked and eliminated as causes it's time to start thinking about trying a repair of DCS, digging around in relevant LUA files, and possibly reporting a bug.

According to this thread it's W for the pullthrough of the soft limit. http://forums.eagle.ru/showthread.php?t=154301 Of course, it's quite possible that there are multiple keybinds available for this, or that things have been changed in a recent patch. Lol, it's a thread by rami about the override function. So they already knew about it. Yeah, in that case it's just a matter of max instantaneous turn rate being, well, for an instant. That and being at the flight parameters for peak performance as shown in the relevant performance charts.

The Su-27 can pull 9 gs or possibly a bit more (which is more than most pilots can really handle). There is a "soft limit" in the FBW system, that on the real plane you can override by just pulling back really hard on the stick. I believe that this is modeled in DCS only instead of pulling harder on the stick you press the wheelbrake key. There's a thread about this floating around on the forum somewhere. This is a separate function from disengaging the ACS in order to do airshow stunts like the Cobra. edit: As a lot of others are pointing out though, there's a difference between instantaneous max turn and sustained max turn.

Read your mission briefings and look at the map in the briefing very carefully! There are triggered units that pop up out of "nowhere" but the majority of enemy air defenses will have a rough location on your briefing map. It makes life so much easier. You can do things like just fly to your target on a route that completely avoids 75% or more of the air defenses. Or if you insist on taking foolish risks, it at least suggests where you should start popping flares in self defense. It also helps if you decide to clear the air defenses before going in for your attack run. The MANPADS are really hard to see, so knowing their general area is a gigantic help in finding them so that a Vikhr can be dropped on their heads. If you do your own SEAD, make sure you positively identify every unit in a group before getting within 8 km or so, or else fly a pass at 7 to 8 km to bait a SAM launch that's long range (and therefore easier to avoid), and then swing back around and kill whatever is parked or standing where the smoke trail started. It helps a lot to learn the shape of the various IR SAM units, being able to pick the SAM carrier out of a column of APCs is really useful. Use terrain, IR SAMs can't see through hills and mountains any better than radar guided ones can. For the Su-25T flying above the engagement range is pretty useless most of the time. The weapons available in DCS generally won't hit reliably if you're that high up. It also makes you and easy and obvious target for medium and long range air defenses. Generous preemptive flaring, and throttling down the engines are both pretty effective in DCS when it come to spoofing IR SAMs, as long as you also maneuver. The fundamentals are planning and observation though. Used properly, they can be so effective that you don't even need any countermeasures. The other nice thing about planning and avoiding the SAMs is that you don't waste munitions that you could be using for your primary mission. That said, for the default campaign, unless it has changed significantly, it's not a bad idea to have 90-100% of your countermeasures loadout be flares. Most missions don't have enough serious radar threats for chaff to be of much use.

There is no Mig-29 forum, as there is no separate Mig-29 module. Both the Mig-29 and Su-33 fall under the general DSC:Flaming Cliffs 3 forum, at least until they get their own stand-alone modules in the way that the A-10A, Su-25, F-15C, and Su-27 have. The best we can do is hope that happens soon, and use the forum search tool to look for Mig-29 as a keyword.

This sort of thing is almost always caused by a problem with input hardware configuration. Most often due to more than one input being assigned to an axis. Clear the axis controls for the aircraft module in question and then reassign, and it usually takes care of the problem if you remember to do it for all of your input devices: mouse, keyboard, stick, throttle, pedals, Track IR, etc. Rarely, it is a problem with the physical hardware. Worn or misaligned sensors in a stick, sticky key on a keyboard, that you can troubleshoot by plugging/unplugging one controller at a time to see if there's a correlation with the problem. You can also check the ground level wind speed and direction in the mission editor, or just test in different missions. Extremely unlikely to be the cause, but more likely than a bug. Of course, a bug is possible, but it's pretty much the explanation of last resort in this case.

Convince 100 million people to purchase and download DCS World and all of the modules. Then it will be commonly downloaded. :thumbup: This is a consequence of security software that uses user behavior statistics as a "risk predictor". Anything with an insufficient number of downloads triggers a flag, unless the publisher contacts (and pays) to get on the "good list." They have other stronger warnings that pop up if a program is a KNOWN security risk. You could scan the file for malware if you're still worried. I expect the result will be, "nothing dangerous was found in this file," though.

Blueflag Registration for round 4 Faction preference: Redfor (I know the geography flying from the North a lot better). Callsign: Auger Aircraft: Su-25, Su-25T, Su-27, Mi-8, Redfor CA ground units as JTAC/Driver.

There are several techniques, I'll list them in order of importance: DO NOT OVERLOAD THE PLANE FOR THE MISSION PROFILE PRIOR TO TAKEOFF! This accounts for 100% of your landing with a heavy load problem, but DCS doesn't include crew chiefs or commanding officers to yell at players when they do it. As a result overloading planes is one of the most popular stupid and unrealistic mistakes you see people making in DCS. If the mission calls for burning the fuel and expending the stores, then the loss is already factored into the budget. Replacing the plane and/or the pilot because the pilot ignored the maximum landing weight limits is generally not in the budget. Dump fuel. This is the cheapest way to lighten the plane. Jettison stores. More expensive way to lighten the plane, but still a lot cheaper than trying to fix an airframe that deformed due to overstress or treating a pilot injured in a hard landing. Increase landing speed. Helps some, and on a medium length runway you can push the 25T up to around 300 km/h + whatever the headwind is without problems, but this is really a step to use after the above methods have already been employed. The autopilot exercises it's authority mostly by operating trim settings. If you get the plane trimmed and throttled so that it stays on glideslope with little intervention before turning on the AP then it's very well behaved when it turns off. If you fly a poor approach and the AP has to do a lot of work to stay on glideslope, or if there are strong or variable crosswinds, then there can be rather extreme trim settings when the AP turns off because it does not automatically reset the trim to a neutral setting when it reverts to manual control. This is when the plane can act like a horse or bull trying to throw a rodeo rider. In general I like to turn the AP off at least 2 km out from the runway threshold.

So I never actually answered the question. I set up a mission I named Arcata Rules IFR training with a 150m thick fog bank with 75 m visibility, and a 100% cloud layer from 1000m to 2000m. Goal was to follow waypoints set up to resemble navigation by radio beacons and fly from Krymsk to Mineralnye and land. I did quite nicely until on approach to Mineralnye when I had the first nice controlled flight into ground that I've had in quite some time. So despite this being intended as a worst case scenario training mission, I'd have to say I'm not proficient. I thought to my self, "wow, I can barely see enough to taxi (very unsafely), I'd have to be sort of nuts to try takeoff," especially without knowing that there's an airport and a divert point with better landing conditions available. I still took off despite this, so no, definitely not proficient. I navigated over 400 km, primarily using time elapsed, heading, and TAS in non-flyable conditions, but a proficient pilot would have gotten out of the plane, closed the cockpit canopy, and gone to wait for better weather conditions (or edited them in the mission editor in this case). 0 modules, even the Su-25T which I have more than 400 hours in. Re: the mission name, if you've lived in the Pacific Northwest and experienced the coastal fogs you know why I named the mission after a town on the Northern coast of California. Probably should have named it Arcata - ACV IFR Training.