Charly_Owl

Can a moderator add a forum for OctopusG? Now that their I16 is live... I believe they deserve a place to gather feedback.

Wasn't aware of this difference between the SA342 and the SA341. I find it rather strange that we'd leave the starter switch on (I've never seen that on any helicopter... but stranger things have happened). I will update the manual.

Enjoy! https://chucksguides.com/aircraft/dcs/mig-19p/

MiG-19 guide added in first post: DCS MiG-19P https://drive.google.com/open?id=1gXePAywvO6fnq6JdN-7HP-Lp7nfafwoi

Cool beans!

I don't think so. Open Beta should work well with both modules. How did you start the training missions exactly?

Will be available shortly. It's 99 % done, only missing three minor items.

MiG-15 and F-86 guides updated to be more readable. Added some missing information as well and various quality-of-life improvements. MiG-19 guide is almost complete.

It's a tricky subject. Your altimeter calculates your current altitude with pitot-static air pressure sensors located on the aircraft's fuselage. Normally, the way to perform an approach at any airport is to consult the ATC (or carrier) to get the proper barometric pressure setting. This way, you know that the altimeter will give you a reliable reading since the altitude you see on the HUD in BARO mode will always be correct. However, in the tutorial I didn't bother with the barometric setting. 29.92 inches of Mercury (Hg) (or 1013,2075 HPa) is what we call the "Standard Pressure", which is a reference pressure used above the "Transition Altitude", which is yet another altitude reference as explained by Jak525. Instead, I used the Radar Altimeter mode in the groove since in that particular situation it gave a more accurate reading. You could've totally landed with the Barometric mode, but for that you absolutely need to get the right Barometric Pressure Setting from the Carrier Controller. Otherwise, fly the ball and forget about the Baro Altitude reading. The Radar Altimeter mode has the advantage of being more accurate when flying straight, but the reading gets completely wrong when performing bank manoeuvers since the radar altimeter sends radar beams perpendicular to your fuselage, which is problematic when the wings are not level. Performing approaches over uneven terrain gives erratic readings as well.

Nothing on the MiG-19 for today's patch?

Any news on that particular issue? I've been looking for ASP-5 bombing charts... but no luck so far.

What about the Day/Night radar mode selector switch itself? Its logic is currently reversed.

Sound design is overall awesome all across WWII modules. The P-51 and Spitfire are my favourites in that regard. The framerate is roughly the same for all WWII aircraft and they are more or less all bug-free. The P-51 just got a cockpit overhaul and I think it looks great, just as good as the Spitfire (which is IMHO the prettiest WWII cockpit in DCS at the moment). As someone who has flown all DCS WWII modules for hours and hours... my two main choices would be the P-51 and the Spitfire.

At the moment the tutorial is almost the same... word for word! Current version dates from 23/03/2019. If you have a version dated before 09/12/2018 it's very likely that the procedure is just plain wrong.

Nope.

I don't think it had anything to do with the manual fuel control mode fuel valve damage. A compressor stall is a local disruption of the airflow in the compressor of a gas turbine. A stall that results in the complete disruption of the airflow through the compressor (such disruptions can be caused by rapid changes in airflow or throttle) is referred to as a compressor surge. The severity of the phenomenon ranges from a momentary power drop barely registered by the engine instruments to a complete loss of compression in case of a surge, requiring adjustments in the fuel flow to recover normal operation. Early fuel control units were mostly mechanical valves that were limited by both the slow response time of the engine and the possibility of the pilot opening or closing the fuel control valves too quickly with the throttle. The engine just chokes on air. Compressor stall was a common problem on early jet engines with "simple" aerodynamics and manual or mechanical fuel control units (like the one installed on the RD9), but that problem has been virtually eliminated by better design and the use of hydromechanical and electronic control systems such as Full Authority Digital Engine Control (FADEC). Modern compressors are carefully designed and controlled to avoid or limit stall within an engine's operating range.

How about we let them finish the MiG-19P first?

Hi guys, In the Razbam Flight Manual, there is a paragraph that says: I have never been able to induce an engine surge, flameout or compressor stall (neither a partial or a complete one) by doing rapid or erratic throttle movements. The MiG-19's engines were notoriously maintenance-heavy and engines of this generation were prone to surges during rapid throttle movements or continuous high-AoA manoeuvers. The DCS Sabre and MiG-15 have such surge and compressor stall dynamic failures implemented...

It's not fixed yet. This should go in the Bugs section.

It's out-of-date for radar functionalities and IFF... and it's missing the new radar modes, Mavericks, AMRAAMS, AIM-9X, JHCMS, HARMs, Datalink... I plan for an update once the Targeting Pod is implemented and existing features are mature enough. Keep in mind that it'll be a LOT of work.

When deployed, the airbrake creates a shaking effect on the cockpit and a sound effect of the air rushing against it. When in flight, it's working as it should. However, if we are on ground, we deploy the airbrakes and we are not moving at all, we still hear the sound effect and feel the cockpit shaking. I believe a condition based on a relationship with airspeed should be added to trigger these effects.

Would you have a quick video for those of us still stuck at work? :)

You must be new here... (edit: as a matter of fact, you are!)

Fixed. That's what happens when you live in an alternate dimension.