GrEaSeLiTeNiN

Middle mouse click to override works with BARO but not with RADALT once the problem (triggered by AI Pilot ON->OFF->ON) occurs. Other tests: BARO was set at 300ft. I right left clicked REL ALT of 50ft and helo went up all the way to 2800ft (added 2500ft instead of 50ft) << See video >> BARO was set at 400ft. I right left clicked REL ALT of 50ft and helo went up all the way to 2900ft (added 2500ft instead of 50ft) RADALT works fine with REL ALT

1. AI Pilot ON -> OFF -> ON will still cause the Altitude setting in RADALT mode to be denied by Barundas if that requested setting falls below ground level BARO value. (App thinks it is in BARO mode.) << See video >> Once that happens, it cannot be corrected other than restarting the mission or selecting another Kiowa. When this problem happens, it sometimes turns the REL ALT button red with a certain value (not sure why). Once the REL ALT button turns red, it can't be undone except by exiting and reentering DCS. 2. If I am testing 2 Kiowas in the same mission, jumping from one Kiowa to the other leaves the previous Kiowa bobbing up and down. Not sure if this is app related. Other than that this release is great!

After some puzzling tests, I found the problem why RADALT works and then something happens and Barundas refuses to oblige. The problem happens when you click AI ON, then OFF, then ON. The problem is reproduceable but I can't get it corrected once it happens.

Tested the latest build in the same Syria environment where ground level is 525ft. - In BARO mode, all is good. Button turns red for anything at or below 500ft with AI speech feedback. - But in RADALT mode, AI won't agree to anything at or below 500ft. The button does not turn red but there is AI speech feedback. I think this happens because the app thinks it is still in BARO mode.

MMS Sensor Select TV/TIS hotas binding under copilot to switch between the two. The symbology and crosshairs can be adjusted black or white using the MFD and MMS switches under SYM INTEN on the left panel.

I did my mapping for solo flying which meant basically mapping the commands to not overlap (unlike in the Apache) which allows you to work the copilot buttons from the pilot seat. Thankfully, many of pilot bindings work when you are in the copilot seat as well and vice versa. But for human-human players, I think all pilot and copilot bindings must be mapped at their respective seats.

Not a flight dynamics expert but in general, it is different, more nifty. It has no autopilot features but the AI pilot (Barundas) when commanded works like a very good autopilot feature, some say too stable when hovering. No 'pain' with the FM, SCAS and hover, unlike with the Apache in the beginning. Better than the Gazelle which has buggy autopilot issues.

Deleted old Config file. Replaced with updated (raw) lua and dlg files. Tested in Syria map. - RADALT seems to be working fine. - Ground level is about 525ft BARO in my test. When BARO is selected, selecting 500ft turns the button white (not red) so I can't see the text. I guess it's working just that the button colour isn't right. There is no speech from Barundas when he does not accept the value (when button is white). Maybe he could say "Can't do that" for some audio feedback. But I note that if using DCS bindings, Barundas also doesn't say anything and he actually proceeds with CFIT values.

In my case AVG quarantined a file called "ARF.dll" from the F-15E. I still had the F15E module but could not enter the pit to fly it. So I made scan exceptions in AVG settings for C:\Program Files\Eagle Dynamics\DCS World OpenBeta and C:\Users\User\Saved Games\DCS.openbeta. Did a repair to replace ARF.dll since this file could not be restored from quarantine. Working now (except the radar which is another issue).

+1 There is also no trace of any light beam coming from the searchlight, like you would see with a torchlight. It's just the bright spot on the object.

I don't quite see the animations as choppy when compared with the Apache or Gazelle. The jagged blade edges can be produced depending on which angle you view the aircraft from, although less pronounced in the Apache. I think what is more apparent may be the swash plate area. When paused, they are all in a blur. But when spinning, the Apache one looks more detailed.

Update: 1. In South Atlantic test: Altitude button works as you described whether in Hover, Cruise or Orbit. If I watch the HUD's AGL and Baro, AI will follow the set altitude value according to which flight mode was selected whether RADALT or BARO. And the AI will not stop a CFIT. 2. BUT in Syria test: When reducing altitude nearer to ground, AI often says "You want me to do what?!" or "Hey I can't do that". I'm not sure why when it does not appear to be a CFIT. What am I missing? Here is a video recording I did. Whenever the AI says he can't comply to say 20ft RADALT (= 600ft BARO in this case) via the overlay, he will do it if I use the DCS bindings.

Ok so when I change the Altitude button value, it is currently always with respect to barometric altitude. So if say I am 200ft above ground (AGL) and I want to go to 100ft, I have to know what it is in barometric altitude before I can change the value (granted the AI will not do it if I select a value that means flying into the ground). My suggestion was: Say I select RADALT flight mode (low level terrain flight profile), then the Altitude button value/increment now uses radar altitude (AGL) values. And if I select BARO flight mode (straight level flying), then the Altitude button value switches to use barometric values. Alternatively, and more simply, maybe a center mouse click could toggle between Baro and Radar values in the Altitude button. For example, when on a hill, say the Altitude value is currently set at Radar altitude of "R300ft" -> I click the scroll button and it coverts to -> "B1500ft" barometric. Another thing - The app shows up if you press Ctrl+Shift+F9 when flying any module. Anyway to restrict it to just the Kiowa?

- Looks to me like the HDG2FACE was fixed? I mean it looks right now when I check from the 'center seat'. I like it. - I note the Altitude adjustment is always in Baro. Without the HUD it's hard to know how many feet to set when flying low. Is there a way the Alt adjustment could correspond to Baro or Radar depending on the type of flight mode selected, ie. BARO vs RADALT? - Can the speed and degrees of turn be in increments of 5 instead of 10 (perhaps adjustable in config)? - Can the Alt increment be in increments of 5 until 100, then in 10 until 500, then in 100s onwards (perhaps adjustable in config)? - The app shows up if you press Ctrl+Shift+F9 when flying any module. Anyway to restrict it to just the Kiowa? Sorry for making so many requests! Appreciate the effort in making this.

The L2MUM drone footage will always show a target it alone decides to pick. At the moment, L2MUM drone footage does not follow the AFAC ME assigned targets or the AFAC auto target & lase script. It basically has a mind of its own. The coords of the target (selected randomly by L2MUM) as indicated in the footage are correct. But the coords of the drone as indicated in the footage will always be that of the drone you select in the INIT page, regardless of the target in the footage. I tested this with a custom mission: I had a Reaper AFAC with two assigned arty vehicle targets and a Predator AFAC doing the auto target & lase script with its targets marked by red smoke. When I started the mission, the L2MUM footage showed a completely unrelated target. It was a target not assigned to the Reaper, whether before or after the 9-line procedure. The target was also not lased by the Predator as the red smoke was at another target. Regardless of which drone I selected in the INIT page, it was the same target footage (no change). But after I destroyed the target in the footage, the 'L2MUM drone' decided on its own to pick yet another unintended target. So for the time being, to use this fun feature, it seems you basically target and destroy whatever the 'L2MUM drone' decides. Your drones' targets as intended in your mission design will not be followed. This may be the module's current design intent due to limitations in DCS? The above problem was somewhat mentioned in this tutorial vid. Hoping this will be corrected in future updates so the L2MUM drone footage follows your selected drone's mission design targeting.

L2MUM drone footage issue reported at bugs section

1. Can the app be made to be off (hidden) by default? Also, after I hide the app, if I press the Pause sim key and then Pause again (to unpause), the app will reappear. 2. HDG2FACE - If I position myself at the center between the two seats and look at where the aircraft nose is pointed after I command a HDG2FACE, it seems the final nose heading falls short by about 20 deg of where I was looking at. Is there a way to just add 20deg (or whatever the shortfall really is) to the command?

Hopefully. I mean it’s not bad but could use some improvement. If I were to nitpick, the rear panel switches for example look a bit cartoonish. But the aircraft’s capabilities and features make up for it, like L2MUM drone feeds !

In the bindings: "Force Trim - Interrupt" is the one that ‘invokes’ and sets the virtual stick where you want it, ie. trim "Trimmer Reset" is the one that undoes the trim

Most detailed tutorial I have seen so far and it's all-in-one. Just learned about L2MUM, pretty cool.

Yep, I have those green patterns too. Part of the pit artwork. Yep, I have them too, part of the pit's artwork.

Yes clicking the switch works. I meant the bindings for the switch do not work. Assignments not related to the hotas are still useful or necessary esp for pit builders or those with extra control panels or even just the throttle base switches.

While usually not a priority but since they should be easy to fix, I do hope they rectify the incorrect and missing switch bindings too. Also, there’s a neat AI command overlay being worked on by Bailey. I hope they incorporate it or something like that, into the module as an added option.

+1 Also, the Copilot Radio Select Switch doesn't do anything and is probably not suppose to be there? Or, maybe it was meant to be the left side radio panel's Copilot Channel Select 4-way Switch (CH UP, CH DN, KYBD, FREQ)

It is not being sold as an Early Access. That's why ppl are 'talking'. But yes, it will be updated with time.