Justin Case

So I’ve been flying the L-39 a lot since release, so much that my community mates makes fun of me. I even have a basic flight training program where i spend a lot of time in the back seat. Since a while back I’ve stopped switching controls between the pilots because of desync problems. A few months ago a “student” and I were flying along on a low level navigation sortie, as he went heads down in the F10 map, the nose dropped and our vector pointed towards a tree line. I took over controls, lifted the nose carefully and gave him back the control of the aircraft. As I did that, our right aileron went flying forward like a missile...the aircraft was now damaged and I lost my airspeed indicator. Similar things has happened during the last year-ish, so much that I’m not able to demonstrate manoeuvres anymore for fear of breaking the aircraft. This has been between a server and clients with good bandwidth and stable connections, ping is usually around 10-30. Physical distance is within Sweden which is a well developed country when it comes to internet connections.

Forward to 40 seconds in. Edit: Strange, tried that yesterday but it came up blank. Must have copied a letter too many or something. Thanks!

A deep stall is often caused by shifting of centre of lift or pitch controlling surfaces being shadowed aerodynamically when increasing angle of attack. I believe the term “deep” stems from the severity and often unsolvable nature of a deep stall. An accelerated stall is just reaching critical AOA through pitch input at speeds higher than that for a 1G stall. I might be oversimplifying this but it’s been a while since I’ve opened that book.

Could we have an option for the mission creator to decide wether or not the HMD is available for the pilots, then we can adjust somewhat to different time periods. The solution could be similar to other options such as the exhaust diffusers for the Mi-8. Thank you for reading my request.

I think this effect is seen when you wave off close to the deck but still not touching it , if you try to lift your nose the input feels dampened until you clear the deck and then the aircraft pitches up abruptly. Similar to a cat shot.

I don’t think the OP intended to jettison his sidewinders, he wanted to fire them.

I've learned about this the hard way yesterday. Will the same apply to the F-4?

The topic title says [REPORTED]!! :thumbup::D

Thanks, I'll look through some other functions of MOOSE to see if something fits my need!

Hi! I looked into the RAT system and found it interesting. I'm trying to create a somewhat realistic airspace system for my community with controlzones, terminal areas and training ranges. I would like the random aircraft to follow specific routes, navigating around the shooting ranges and such. This would make the airspace seem more realistic to our ATC controllers, who will see the civilian traffic staying out of our way as long as we stick to our corridors.

I totally agree, this would make night rejoins enjoyable as well.

Yes I agree! In some missions I would not like the player to have the assistance of a GPS.

On pdf page 50 the Aero Vodochody manual says However, when starting up the emergency circuit pressure starts rising immediately and then stops for a while at about 50kg/cm2, eliminating an instrument delay, then eventually rise to 150kg/cm2. Both systems rise simultaneously. Shouldn't there be a delay until the main system reaches 90kg/cm2?

I agree! 2nd point would be awesome for any module.

The risk of tail strike could be a reason not to flare the aircraft close to a stall, as you do a Cessna. This would also require you to cross the threshold at a lower speed, closer to stall, which is quite dangerous in any jet and especially this one with its long spool up time. Now that I read your comment again I realise you've got most of it covered! Follow the manual and you'll be doing it right :) This airplane already has some sweet short(er) field performance compared to other jets, no need to stall it and risk getting behind the power curve .3 miles before touchdown. Just my thoughts, and I love this module.

That would make night flying and finding lost wingmen so much more enjoyable!

That goes for every module, there's might be a change coming in 2.1 though. I recall seeing that somewhere but maybe I'm making stuff up. The landing lights should also be visible for many miles ahead of the aircraft. Try finding and L-39 in darkness using the nav lights...they won't pop in until about 500 meters making midnight IFR rendezvous very difficult unless you use the flares, which shouldn't be required every time.

I'm not sure what you are referring to but it sound more like a DCS related thing, but I'm probably wrong.

I just flew for more than an hour in the L-39C, we landed with about 200 kg. We didn't run the tanks dry but it seemed to be working correctly.

Then I can't really think of amything that bothers me about the L-39, that's awesome!

And come on ED! Please fix this as it can't be a major update. This is my favourite module but it embarrasses me when I have to instruct new community members to install a mod to rectify this.

People always ask this about any module like it's just to copy paste another cockpit inte the module, my guess is no. But I sure would like one!

Giving the gyros a long time for spin up doesn't help, it still topples after an IFR departure with speed below 250 knots and less than 30 degrees of bank.

I'd love to see this feature soon.

Still present, even when flying smooth IFR it can't do the job properly.