AeriaGloria

What’s wrong with FM? I quite like it now the 2.9 brought damper changes and ground effect

No? But some had a dedicated light for it with priority. But the whole threat database is programmable with cartridges

The MiG-23ML does accomplish, pretty amazing. I was confusing it with this aircraft, I should rename the thread “Biryuza”

9.13 no, but yes for S upgrade. There is 9.12S also when you apply S upgrade to 9.12. A stock 9.13 is only different in humpback of fuel compared to 9.12. A really doubt a 9.13S will be possible until maybe a MiG-29 2 upgrade in 5-10 years

Please go beyond FC3 and model the Beryuza data link system. It is so wonderfully integrated with the HUD, would make an awesome feature to entice buyers, and gives it a unique and very dynamic ability to target with exterior guidance. Being able to have intercept path shown to you, radar/KOLS scan automatically and lock, and tell you when to fire. Being able to change the over 20 channels to select different targets. Being a radio link also brings the side effects of flying low and with obstructions from valleys/mountains. Opens up more team play allowing people to assign different targets to wingmen. Thank you!!

While talking about stealth, we’ll see if the IRST sets off RWR with its 0.25 hz radar pulses when it can’t use the laser to range beyond 3-6.5 km…….

Optimum cruise for MiG-29 is almost always around Mach 0.79-8. I believe the manual also says 4.5 degrees AOA is for best range, and 6 degrees for next endurance Idk where this about FC3 not doing RCS come from. They all have detection range that depends on it. Anyone can plop a F-117 or a cruise missile with a b-52 and see themselves. Hell, the MiG-29/Su-27 BVR search mode even shows different target sizes depending on RCS/IR signature!! They are limited by the same limits as all other ED modules, RCS being a single defined number for a unit with an aspect modifier. 3rd parties can tweak their radar models to account for aspect changes differently, loadout, but it has nothing to do with FC3 not doing such a thing.

Picture is from Su-25, where things are in different places

Also China, Belarus/Uzbekistan (if you count ex SU), and Vietnam Surprising how many rook operators there are

Note that this manual section is outdated, it’s 7.7 seconds note not 17. This means they release flare at 3.8-4.5 km depending on speed. I only need 10 degree pitch up if firing at low altitudes. Once I’m at 400-500m AGL, I can fire mostly level. The flare has to be about 300m or more above the ground when it ignites

Clarification, Is it the light shining through the body the main reported issue? From what I can read, the FPP-7M landing light should be able to rotate continuously through 360 degrees in any position retracted or extended. But of course, the light shouldn’t shine through the body. I have also noticed it able to shine through the periscope housing and other places it shouldn’t

I’m sure with Rhino SW you can. With SimFFB software, setting any effect automatically disables any input from DCS I could get it so trim still works the same, but not sure I can program it so that the trim hat works the same as in DCS

Yeah with FFB force goes away with trim button, making precision hard. Easier with Ka-50 where autopilot stills dampens with trim held

I don’t like holding trim button down becuase I use FFB, I prefer to just trim 2-3x in quick succession to get rid of “nodding.”

Becuase with the seat in place it blocks certain buttons and switches, like AP panel. In order to do it, all three positions would need to be selectable

Yeah, and improving on Mi-8 which only moves the attitude hold with the cyclic based off where the cyclic was when autopilot turned on (cyclic when turning on AP = 0 movement, any movement from there moves AP with cyclic), the Hind trim button also resets this. So while if you turn AP on in hover in Mi-8, and transition to fast forward flight without messing with it, it will think you are wanting it to dive rather then hold that attitude as your cyclic is now more forward of where it was initially. And be giving left input thinking you’re trying to roll left (since cyclic needs to move left as speed increases). So with the trim button on Mi-24 you can both tell AP “I want to hold this attitude,” but also “this is where the center of my cyclic is right now, and if I move it from here then I actually want to manuever in that direction.”

Mi-8 has different trim system, its trim button doesn’t interact with AP at all. The only way to set the attitude the AP holds in Mi-8 is to turn it on at that attitude or use adjustment knobs When designing Mi-24 the Mil bureau realized why not combine the job of the engineer in resetting the AP channels to be done by just pressing the trim button, which the pilot needs to do often. Ka-50 does the same thing

It it’s realistic, the trim resets the attitude hold of the autopilot. Let’s say you turn on AP on ground, becuase nose angle is +3.5 degrees it holds that attitude. When flying you pitch down to -5 degrees, and pitch AP gives nearly full authority to fight this and bring you back to +3.5 degrees. You are then fighting pitch AP to books that negative angle When you press trim button, AP deflection goes to 0. You release trim button and now it wants to hold current nose attitude of -5 degrees. That means the AP your were fighting to hold -5 degrees is gone, and your forward stick is too much now So you kinda have to remember that when you trim, you are also telling pitch/roll AP what attitude you want it to maintain Solutions are 1. trim after every major attitude change 2. hold trim button while you manuever before releasing trim, when holding trim pitch/roll AP will be nuetral 3. trim multiple times to get rid of the “jumping” I do a combo of methods 1 and 3 personally

200 kmh is only when the phenomenon begins to happen. It only gets severe at 250 kmh, and gets its worst above 300 kmh. Its severity directly correlates with airspeed. Dutch roll is the same I believe the blade stall here isnt from overspending blades, the rotor tipsgo about Mach 0.6-0.7 at the tips at full rpm. I believe this rotor stall is from positive AOA. The rotor needs air to come from above it. When the air comes directly from the side, it is more difficult to have smooth airflow but still often okay. But as AOA increases and the air from the airspeed is hitting the rotor from the bottom, then it will really begin to stall as air hits the blades from higher angles.

It still happens to me, it's just more smooth the transition. You hear the blades begin to flap, sometimes some shaking. You will see AOA rapidly increase per G load. It should be a range of 1.6-1.8 G at low altitudes, and 1.4 G high up. I still find maintaining those numbers to avoid the rotor stall (rotor flapping noise) and to keep speed the most efficiently. Not sure how you are testing, but a huge part of the phenomenon is rotor stall, so the higher your rotor pitch, the more aggressive it will happen. Sometimes I still find just decreasing collective 1-3 degrees is plenty to stop it when it happens, which is accurate. Before the patch you speak of, it would "snap" forward in an oddly quick way when you reduced collective during it. Now it is much more smooth

The manual warns you to raise collective 1 degree/second to stop rotor droop (rotor rpm decreasing). This usually works unless you have collective near bottom (1-3 degrees), you want to gently increase it until engine rpm is 90-95%, then you have more freedom to be rough with collective. In normal conditions you can pull 13-14 degrees without rotor droop The engines themselves take 8-9 seconds to spool up from idle, and the governor only commands this when rotor rpm is below 95% (unless you mess with turbine rpm adjust.) So a other way to raise collective when it’s really low is just raise collective until rotor rpm is below 94%, then your engines will start accelerating

There’s also the 740-8,000 PRF range in addition to 7.5-16.6 GHz carrier frequency For fan song for SA-2, I see it in E/F/G band, which is below the 6.6 GHz minimum frequency.

MiG-21 SPO isn’t modeled with the limit of frequency range, it sees everything that is radar When I looked it up, SA-2/SA-3/SA-5 radars are all too low frequency to be in range. But these SAMs almost always used very low frequencies because frequencies that are lower travel farther Patriot radar is definitely out of frequency range For SA-13, its radar isn’t modeled, if it was modeled it would still be out of range. Shilka radar is in Ku band, which means it could be in range or not depending on what side of the band it’s on. Idk about Vulcan, hard to find info on its radar, same for SA-15 Tor

They could also add SPO-15…….Give me thermobaric S-8. Single ATGM loaded racks. Maybe a few years after official release……

The MiG-15 manual (IRL) also speaks about elevator being very light until you get to Mach 0.85, at which point the force increases from 1 kg per 1 G, to 25 kg per 1 G at Mach 0.92