Red Dog

same problem very annoying when creating mission in ME. The waypoints are there because on the far right of the windows I see multiple waypoints in the menu, but on the map you cannot see them when you fly the mission, the ins has the waypoints. It's just that they are not drawn on the map

I think I have seen something about it in one of Wag's video about the F-16 and steerpoints Has to do with coordinates conversion for steerpoints 21 to 25. The DCS SEQ now converts the coordinates and the AUTO/MAN sequencing has to be entered and changed with the scratchpad on the option

Well sure enough there is a line missing from the DED LIST MISC LASER page for auto lase timer in DCS. Pretty sure the real F-16 can do auto lase when using the right pod obviously. The lasing system is part of the F-16 internal systems otherwise why would there a Laser arm switch on the MISC panel. Sure it can't fire any laser without the targeting pod, but lasing is settable in the F-16 system and the auto lase feature is missing from DCS. Hopefully implemented in the future

Thanks Rob, I started thinking I was alone having this issue. I started playing around with the programming and either adding DLY or separating the press and release to attempt to make the buttons recognized in 3D The DCS in the F-16 pit for instance doesn't work with DLY but started working once I better separated the press and release action. Many thanks for your input

I am still fighting this issue unfortunately. It may be related to the fact that my keypresses are not programmed with any delay and they are too fast to be recognized in 3D (although they are fine in the UI config screen) Before I change all my programming, Is there a way to set the time DCS works best with key combo? Setting milliseconds or something like that? I don't have much hope it has, but I figured I'd rather feel sorry to ask than discover it after having completely reprogrammed my whole pit Thanks

Thanks I thought for a minute it might have been the Su-25 Mimino which looks very similar

Can anyone tell me what airplane is that? Thanks

When I create a mission (Marianas) in Stable version, There is no way i can see my flightplan. Steerpoints and lines remain invisible although there are placed on the map as I see the steerpoint number incremented and when I enter 3D I see the flight plan in my MFD. So I know they were created - they are just not displayed on the ME map If I do the exact same procedure with the latest beta version, I perfectly see my flight plan in the mission editor. They are created fine, and I can see them on the ME map This was tested with Marianas, F-16 stable and latest beta. Any idea if that's me doing something wrong, a known issue or something else? 5I clearly made sure the hidden on map option was NOT checked obviously Thanks

Thanks for the checks you made. I confess the quick test I did this morning was simply flying the ILS 06L and 24R and then sitting on RWY 06L ready for departure and trying to get the morse code for all ILS. 06R didn't sound. just like the other 3 didn't either. I will fly all 4 approaches tonight and play a bit more with wind direction and speed. it's a bit of a hit and run to get this working and IMHO will be much simpler once the initial issue is fixed

Thanks, sorry for the repeat then and I hope this issue gets fixed as it really makes IFR mission creation complicated. Hopefully I can get more acquainted with the huge forum in the future and can track the history of these issues

Very interesting, thanks for that detailed technical answer - much appreciated

Working on a custom mission at Andersen AFB I set surface winds to 058 @6 kts (DCS STable - Marianas - F-16 & Vanilla install, no mods) Getting into 3D, none of the 4 ILS: 109.3 RWY 06L; 109.35 RWY 24R; 110.1 RWY 06R and 110.15 RWY 24L) were working. Needles were dashed, Flags were displayed and the morse ID didn't sound. TACAN 54 was Ided correctly and worked fine. Comparing with the Marianas HOT START F-16 INSTANT action mission provided, all 4 ILS were working at the same time. So there was definitely something wrong with my custom mission. As advised and confirmed by another user kind enough to make the test, Setting surface winds to zero solved the issue and all 4 ILS were now working with my custom mission. So IF ILS are supposed to be activated only for active runway depending on winds, then there is a problem Since the 058 winds I set initially should have at least made the ILS on both RWY 06 active where it wasn't the case. IF ILS are supposed to be ON no matter what wind conditions, then there's a problem as well since setting winds to some value turn the ILS OFF. I haven't tested other winds conditions yet I haven't tested other runways ILS in the Marianas yet Thank you

Sure enough I put the winds to zero and all 4 ILS are back on in my custom mission. Rgr on markers, that's what I thought as well. Just wanted a sort of confirmation Thanks PS: I'm surprised the ILS are activated/deactivated according to winds or active runway. Do they really do that IRL too? I rather thought they were all On no matter. Especially when sharing the same frequency like real Andersen base (not in DCS for the limitation to have the same freq on both approach ends of the same runway)

Surface winds are 058° @6 kts For reference all 4 ILS are working on the instant action F-16 mission on Andersen (Hot start) (no markers though)

quick question about the Andersen ILS I have no idea if the issue I am encountering right now is me, the F-16 or the marianas, so bear with me When I take the instant action ready made mission with the F-16 at Andersen, I do have all 4 ILS working at Andersen AFB, no issue at all (except the nice weather ) If I create my own basic mission with the mission editor just to fly the ILS at night and in different weather then I do not have any of the ILS active. Once in pit, the procedure I apply is the same but neither the ILS ID are heard, and obviously all needles remains flagged and bars dashed. TCN works fine and is ided correctly. Is there anything special I missed we have to do to activate these ILS in the mission editor ? Side question, I wasn't able to get Inner and outer markers on these ILS, something else I missed or is that intended? I don't really expect outer markers on the 2 ILS from the sea, but are they supposed to be present at least on the 2 inland ILS? Any hints welcome Thanks

by the looks of it, it still does not work. Seems the "-" sign is not recognized in the LUA files preventing negative coordinates for screens placed on the left of main. Too bad because there is really no reasons to prevent us to place secondary monitors to the left of main. Actually, it's a safest process to have them on the left rather than the right side because when a shift of resolution happens on the main monitor, the secondary placed on the left are not shifted while the right ones are shifted as well. If any one know how to do it, I'd love to hear about it. Thanks

I just found out the problem as my 2.5 install (with MFDs on the left of main) is working pretty fine but 2.7 is offset with the same lua file. Hopefully the LUA now supports negative value coordinates with exported screens on the left then?

Thanks gents, i'll investigate Helios to start with. Many thanks for the pointer

Are the Main F-16 instruments extractable to displays? I can extract MFDs and I extracted the F-18s 3 Mfds and UEFI so that's ok but I was wondering if the centre panel instruments of the F-16 are extractable as well? Mainly ADI, VVi, AOA, Machmeter, Altimetre and (e)HSI. I think I have found the HSI subfolder and I may try to activate it like it was required for the F-18 UEFI, but the instrument don't seem to have the same _init LUA files where I declare the variable for export. Any of you guys try this already? Many thanks It's a shame to have a dark pit flying DCS F-16 I'd prefer to have it well populated like when I fly the DCS F-18

bump - I still have the issue reported above. another example: Master Caution in my pit is wired as "SHF c" When I program it in the UI (as "LSHF c"), it's recognized when I press my pit master caution button I go into 3D, press my pit master caution button, nothing happens, MC doesn't reset. if I press "LSHF c" on the keyboard, it works and master caution is reset. I don't get it why it works fine in the UI but stop working once I get in 3D, whereas it does work with the keyboard? I initially though it was a matter of L shift and R shift but the keyboard test seems to rule that out. Any idea on the matter would be most helpful as I have a dozen of such problems Many thanks

I must say I enjoyed the two days of trial with the Harrier It's been a blast :) Haven't bought it yet but I am very tempted. Well done DCS for the multiple trials, it's a great incentive to select the modules you like before buying them. And of course, Well done Razbam. From my very limited experience, it looks like a great module indeed

Thank you. Unfortunately in my case having a 100% (err, 95) implemented cockpit, it is not an option for me to reprogram the whole pit whenever I am changing aircraft. This is actually make me stick with one module only (hence less sale for DCS) because of the hassle to reprogram the pit buttons. It's quite easy to do for a Hotas with less than 40 entries, it's a bit more tedious with a 250+ entries of a cockpit of which many might be used and many others not due to the obvious specificities of one aircraft against the other. Still reprogramming is not an option. It's much faster to reprogram the DCS module keybindings, which is what I am doing but wondering simply if there is a faster, better way to address this that I may have missed. Apparently not :) Thank you It's not the end of the world, if you do it once and for all. It's tedious and time consuming but in the end, it is quite possible. the advantage is that it's part of the learning process of each module, so that adds up nicely to some extend. That reassures me to my ability to understand this but there is obvious room for improvement IMHO on that aspect. If one of you has a way to ease the process, I'll keep my ears open. Thanks

Some are I agree, but honestly that answer is probably motivated because of lacking to understand what I am trying to achieve :) A MFD push button is the same, the harrier, the F-18, the F-16 and many others have them. Having a TM MFD for instance if you have common assignation for the MFDS throughout all modules (or most of them using them anyway) then you don't have to reprogram your MFds each time you switch aircraft. There are many other examples ICPs, Gear, airbrakes, flaps, lights, trims, etc etc; All this are most of the time common to the modules. Managing those are the reason for my question. As I said in my first post - I am aware of the specificties of the modules. But an aircraft is always an aircraft with common stuff all around

Well, just to be clear, I'm not complaining or requiring a change. Just inquiring if there's an easy (read less time consuming) way to do the above ? :) Thanks

Is there a "easy" way to reuse at least part of the key file configuration from one module to another? Let's imagine I have a cockpit that I do not want to reprogram each time when I switch from the AV8 to the F-18 to the F16. It's actually much easier to have each module calling the same keys for the same actions although I understand some will be specific but Gear, flaps, lights, ICP, MFDs etc etc will always be needed in these aircraft, I don't really see the reason why these bindings are different by default from one module to another? So these common bindings is what I am trying to get on the same programming for different (but semblable avionics) modules. That would allow my cockpit and my HOTAS file to work always the same way eventhough I may change aircraft Currently the only way I have found is to go command by command and assign the same keystrokes, but this is really time consuming and I doubt I am the only one doing this. Any method or point to a topic is welcome. Made a quick search about this but came up either too general or not relevant to my question at all. Od course finding the right keyword may be the issue too :) Thanks for inputs you guys may have