Foul Ole Ron

Is there a way to get the kneeboard on the pilot's leg to display stuff like how it works in the Mustang?

Bumping this as the issue is still outstanding. It's pretty cosmetic but likely should be a quick and easy fix.

Happened to me as well - luckily doesn't really impact the mission. Also I noticed that in the next mission to escort the general when coming back to Sochi Adler none of the runway lights were on despite the really low visibility.

Wasn't fixed in the last release. Was playing the Museum Relic campaign last night on the stable release and the issue is still there. It's a pretty minor issue and I'm sure they'll get around to it shortly - they're probably more focused on fixing up F-5E issues at the moment.

They don't but if a project goes very significantly off the rails in terms of planned dates then it's probably a good idea to ramp up the communication a bit. A monthly update from the devs outlining progress would give some comfort to their customers and would take very little time to put together. It'd be good for AvioDev and good for the rest of us. It's just common sense.

+1

Which is how it should be. If you check out the F-14 Topgun pilot video at around 19:20 he says "The F-5s.. you couldn't see 'em outside of about 5 miles". [ame] [/ame]

Standard model F-5E was only capable of carrying two and that's all we have. Some other countries had this modified along with other things like A-A refueling but we've got the standard model.

Not functionality planned to be implemented. The standard F-5E model didn't have it. Would be a nice option to have though.

After spending more time with it and making sure rudder input is neutral before engaging NWS I don't have any sensitivity issues anymore. Seems to respond realistically. I guess the issue I had at first was using the rudder before NWS which causes some jerky moves and can lead to trouble.

Not sure if this is a HOTAS issue but when using the X-55 at least the UHF radio mic button doesn't work the same as with other planes such as the A-10C. When I use the keyboard command the switch goes in and out and I get the menu option. When I map the keyboard command to the hotas however it doesn't work - it's like it only half presses the button. To get it to work I had to make an advanced command in the Saitek software which simulated both the button being pressed and released. After that it works ok but I haven't had to do this for other planes so seems like a minor bug to me.

There's no "Single" folder in C:\Program Files\Eagle Dynamics\DCS World\Mods\aircraft\F-5E\Missions. Without this it's not possible to play new missions that we create for ourselves in the editor. Can workaround for now by manually creating our own "Single" folder and saving missions there. Can see F-5E then in the missions list.

The method is easy and similar to the Sabre but the sensitivity to rudder input seems very high. If that's the way it is then I'm sure I'll learn to live with it but it just seems unusually sensitive compared to other planes is all.

I didn't map differential wheel brakes - just use the pinky switch on the hotas for both brakes. Even when I'm applying no brakes at all the NWS is extremely sensitive to the most minor of rudder inputs. I know it's a completely different plane but the A-10C's NWS seems a lot more realistic when it comes to reacting to rudder input.

Does seem very sensitive once you engage the NWS and that's with a rudder curve of 25. No idea how accurate this is but seems like it wouldn't be so sensitive in real life. Might be a limitation of using something like saitek rudder pedals though.

Well we don't really know how long they had it in dev for but fair dues to Belsimtek - they have shown that they know how to crank out quality modules at a steady pace.

Approximately August 2034..

Yes but they've openly said that they're getting close to release so I'd be cautiously optimistic that we're going to see it pretty soon. I don't see it slipping past the July-August window that they gave themselves. If that happens it happens but right now it doesn't look that way.

I really don't think we need the AI to fly using the same PFM that we fly with. That always seemed like overkill to me. So long as they fly a reasonable facsimile of it that's good enough for me. I'd prefer to see AI CPU calculations being diverted towards trying to get the AI to fly tactically decent.

It just checks that you hit all the ones you were supposed to - the order doesn't matter. At least that's the way it was before anyway.

Was playing on the latest release. Didn't have the taxi bug on either mission 2 or mission 3. Appears to me that the issue has been resolved but my testing has been fairly limited. Re the Sam launches I was fired at and hit on mission 2. Wasn't fired at on mission 3 as stayed up high but Pontiac was fired at when doing CAS. The MWS on my plane triggered a warning but wasn't due to the missile being aimed at me. The only issue I had was maybe one that's been discussed before. With the custom F10 dialogue if you accidentally select the wrong radio channel to transmit then the dialogue plays out but you only hear your character talking. So on mission 3 I couldn't hear Uzi give their location. I had it jotted down from a previous attempt of the mission so was able to input into the CDU. Not sure if there's any way to prevent custom F10 dialogue from playing out if the wrong transmit channel has been selected as technically Uzi wouldn't have heard my request for their location.

All seemed to be working fine. Got hit by a SA-18 that forced me to bail out so don't know if the whole mission works but everything seemed to be working OK up to that point.

I tried mission two a few times on Thursday and the AI (3 planes) couldn't taxi but tried again after installing the latest release version on Friday and everything worked fine. Haven't tried anything else though.

Yes - for this training mission you can land wherever you want. The marker is for Tiblisi but it makes no difference. This mission is mostly about giving you practice with LGBs, IAMs and Mavericks.

So now that we're in 1.5.4 stable is there an ETA on this? Looking forward to it.