rossmum

To be fair, DCS doesn't simulate it getting dirty during the flight, so having a canopy that's a little grotty is as close as we're likely to get. No matter how clean it is when you take off, it won't stay that way. Getting bug guts off perspex sucks, they're like concrete :lol:

Every other canopy in DCS is unrealistically spotless. While the MiG's might be a touch too dirty, people really underestimate both how much bug guts ends up on the perspex in flight, and how hard it is to clean off properly. Usually the windscreen gets the worst of it. With that said, the gunsight glass should be pretty close to spotless.

It won't if you pay attention. Don't exceed 33 indicated AoA, don't subject the engine to overspeeds or neg/0 G, watch your rudder coordination. T/O flap and emerg burner let you get away with a lot.

It does move, but the logic that drives the cone is based on air pressure IIRC so you won't see as much movement if you never leave the deck.

AI use their own separate flight models for all aircraft, not just the MiG. What works against actual players won't against AI and vice versa. That said, people chronically underestimate the 21's capabilities in close and especially at low speed, and Hornets are the most satisfying victims :)

I had no oscillation with it today, but did notice it was putting me into a slight climb rather than its previous behaviour before the FM change (dropping the nose for speed, overcompensating once or twice to level out, then sitting dead level).

VNE is 1300 or 1350, you're up around your max dynamic pressure for the airframe there and in DCS your engine will quit somewhere in that range. It can hit 1400 without flaming out sometimes, but I wouldn't count on it - I always try stay right on 1300 and go no higher. 1200 is fine. If you're losing your engine while you still have >200l of fuel in the tanks, one of four things is happening: a) you're overspeeding it - stay below 1300km/h IAS. b) you've somehow compressor stalled badly enough to flame out. This is exceptionally hard to do without first doing something else that would rip the airframe, if overstress was more fleshed out (e.g. ARU override to 'long arm' and then reefing on the stick at >800km/h). It's probably not this, you'd hear the banging from the compressor anyway. c) you've applied 0 or negative G, or flown inverted, long enough for the 80 litre header tank to drain, thus starving the engine of fuel. d) you've overridden and meddled with the nose cone position, or failed to turn the automatic nose cone control on (main right side vertical breaker panel, top row of horizontal switches, it's the switch nearest the front of the aircraft out of those three). It's most likely c) or d) given your speed is below 1300. For the first, pretend you're flying a Spitfire - roll inverted and pull rather than nosing over. Negative G sucks for you as a human being and sucks for the airframe, so avoid it as much as possible - both your body and the aircraft tolerate far higher positive G loads than negative. Don't fly inverted, if you have to be inverted then apply gentle back stick to apply some positive G to the aircraft (so the fuel drains properly rather than floating to the top of the tanks). For the second, don't. You shouldn't be touching that unless you have good reason (and if you have good reason to be touching that, you should be looking to land, because something is very wrong). Make sure the main breaker switch for the cone is on and don't touch the override on the left panel.

I think it's only on that specific one - at least, that's the only one I've noticed it on. Might be worth checking the description.lua file and making sure there's nothing missing/typo'd in there maybe? If I remember I'll poke around myself and post any fixes I find.

Learnt a hard lesson earlier today about my need to brush up on the 29, and just how short-legged it really is. The restriction to 60s make it a bit of a trap almost! Think I'll stick to the 21 next time, especially if I'm already on a roll with it... :lol:

OB here. Like I said, I notice no difference - my framerate is perpetually low in multiplayer and especially any time I go near trees, but I haven't noticed a significant impact from the 21's radar. My friends who have are all running OB as well.

Running any mods? Any traces left of mods from previous installs? Tried a repair? I know they're pretty obvious questions, but never hurts to double check. "Uninstalled" mods have caused me issues in the past.

Awesome, thanks :D Should be a little fairer on the blues now while giving us MiG jockeys our signature weapon back! Had an absolute blast on Sail Ahoy! earlier after a bad false start on Catch Me If You Can (which is usually one of the missions I enjoy most, go figure, I'll blame my lack of skill with the MiG-19). There was some very... creative strategy from one of the blue players, so I actually taught myself to use the Grom after a year and a half of flying the 21, and got a gun kill on a BMP :D

I don't tailstrike often, but I don't think it caused damage last time I did. I watched a friend who only got the module today do one earlier and he seemed fine. I don't think it's modelled, or if it is, it's not working at the moment.

Same backtrim as I used before, stick back 3/4, rotates around 280-300, ease off stick as necessary to keep the nose from rising too much. It's more sensitive than it used to be and it took me a little adjusting to (mainly because of the nose's tendency to bounce) but honestly, if you hold the nosewheel off the tarmac long enough to take the stiffer suspension out of play, the takeoff is pretty much no different.

A mate of mine with a much more powerful PC than me has also reported a drop from 150FPS to 40 when the radar is turned on. My potato PC doesn't seem to register a difference at all, though.

The new AB hasn't been added yet. I don't know why people are saying they 'downloaded' it, as it hasn't been released.

Be aware that the RWR experimental behaviour has to be enabled in the mission. It doesn't work on some servers because they haven't set it to work, even if you have it enabled on your own client.

This is a longstanding issue which I think they're aware of, not 100% sure. I can definitely confirm it happens constantly in MP though.

You might be losing enough speed to stop the engine windmilling enough to preserve the pressure, maybe.

I haven't noticed issues with the module specifically either, running a much older PC (but also at lower settings). Seems the same as most other modules to me.

It can do slow too, it just needs practice. Watch the AoA indicator, 28 is a huge margin of safety. It will comfortably handle 30-32, at 33-34 you're on the edge but with a little finesse you can hold it there. Below 600km/h, drop the takeoff flaps and engage the emergency afterburner - you can pull some absolutely revolting turns, and as you bleed speed the circle closes tighter and tighter. If the wing stalls, let go of the stick and let it correct itself, or counter with some gentle rudder.

The actual flight handling is pretty simple when you get a feel for it - I'd rate it as easier to handle in a lot of respects than the Tomcat. It's just knowing those weird little quirks. It's my most flown module and in the space of the past 2-3 weeks, I've learnt a few things about it that make it feel like a whole new plane.

It's not messed up. The in-cockpit gauge is local AoA at the position of the sensor vane (left side of the nose about halfway to the cockpit). The airflow is already distorted by the aircraft at this point and will read higher than the true AoA (F2 view). This is realistic and happens on the real aircraft. Someone posted a diagram on the forums ages ago but I can't find it right now. The engine is not underpowered, it has a TWR over 1 when the emergency burner is on. What you are seeing is the enormous drag associated with the aircraft's wing design, with flaps lowered. There is a blown flap system which requires >80% RPM to operate, below this level there is no bleed air being provided to the flaps and you will drop like a rock. Keep power over 80% and if you're too fast, tickle the airbrake, don't reduce power. This is a design quirk of the real MiG-21bis. This is why the Soviets added the blown flap system in the first place, to provide for safer landings at lower speeds than the earlier models. AP is working fine now per my experience a few hours ago, but take note that this is a very old, analogue system and it will 'search' with the nose while it tries to find the right airspeed. It exhibited this behaviour even before the FM changes. The MiG-21 is a fantastic aircraft and with a bit of experience, will cream most F-5 players online. I wouldn't trade it for anything, but you can't just come in and expect a 1972 upgrade of a 1959 aircraft to fly itself and require no study, my dude.

That wasn't what he was asking, he's asking why the wheels themselves aren't coming down. The emergency system is pneumatic but the normal system is not, it's hydraulic. All I can think of is that you've somehow damaged the undercarriage in such a way as to prevent the doors opening again, or for some unholy reason the hydraulic system is running at such low pressure it won't drop the gear - but then you'd have flight control problems, too. I don't remember if there's a shutoff valve that prevents any hydraulic oil running to the gear mechanism, as I've never had to isolate it, but that's all I can really think of outside of damage or some really weird bug.

IIRC the gear is hydraulic, it's the wheel brakes and chute which are running off the pneumatic system. Wheels should still come down. Some sort of system damage maybe?