Darkdiz

Same issue for me, I get around it by copying the Sinai map folder from my game install. I THINK the 2 files you need to copy over are dcs_manifest.bin and dcs_mt_manifest.bin (they were the only ones modified with the patch in this folder)

Yeah, figured it out... Designating with the HUD: In A-G MM with no tgt designated (boat switch aft), ensure the TPOD is in slave mode (Auto Acq press with TPOD in command, ATRK/PTRK unboxed). Take command of the HUD (Castle Press Short and Castle Fwd Short). If the "take command of the HUD" process is done a second time, the TPOD will automatically slew to the position of the velocity vector, and will remain slaved to the VV. PB17 on the TPOD will show SP RET. If the TDC button is pressed, as expected a tgt point will be created at the point of the pipper, however the TPOD will now remain locked onto that point, and the A-G radar will display a tgt point at that position. HUD cues will be for the release of the weapon to impact this point but will vary depending on if the system is in CDIP or AUTO mode. Auto Acq aft short with the HUD in command switches between the 2 release modes.

Was flying with a friend of mine and he managed to get the TPOD to slave to his A-G reticle. He was in A-G MM, took command of the HUD, took command of the HUD a second time and the TPOD slaved itself to the A0G pipper (center of the reticle). He was able to do this in CDIP or Auto mode. I was unable to duplicate this. Is this an undocumented "thing"?

Turns out that the keyboard was not recognizing the WIN key. Put another KB on, seemed to work now

Up until a few days ago, active pause worked fine (LSHIFT+LWIN+PAUSE). Now, even in the controls menu, it does not see this key combo, and I cannot select active pause. Ideas anyone?

Make sure the "Force AM" on radio 2 is starred (assuming you are using radio 2 to contact the tanker). Its on the radio 2 sub-menu, PB9. I was having that problem as well.

What I have found is that even if the pilot's XFR (PB1) button has nothing beside it, if the WSO designates (with whatever sensor) the transfer by the pilot STILL transfers the coords to the selected JDAM. To check, the pilot reads off the last 3 digits of the lat and the last 3 digits of the long, they SHOULD match what the TPOD/RADAR/Seq Pt says. The NAV designation (steerpoint with a decimal) gets you going in the right direction, and in the vicinity, unless it is a static tgt (building etc), then you can pick off exact coords and transfer them (pilot if he wants to do the drop and get the proper release cued. Agreed, its bugged, and hopefully fixed as the desynch issue has been problematic for some of the newer folks to the F-15E, and has detracted from several missions we have run.

Really like these. One thing you can add that I just learned, is that the NCTR can be done WITHOUT going through the EID IFF matrix by coolie right short. Coolie right long will also do the NCTR, but the system will run through the complete EID IFF matrix (interrogate whichever modes you have setup under EID). As well, another thing I discovered is that the AAI/EID works even if your radar is in stby. You get a return if a correct code is returned at the proper range and bearing of the contact on the radar display. It will either be a diamond (modes 1-3) or a circle (mode 4 friendly). Auto acq press will erase these mipples from the display. Obviously, you will get nothing if the tgt transponder is not replying (most hostiles dipn't reply, but friendlies do)

From what I have seen, there is still a huge desynch problem with the smart weapons. If the WSO designates a tgt AND transfers the tgt coords to a smart weapon, the pilot will not get the drop cues (in multiplayer). The WSO will get the correct cues in the HUD repeater, but nothing for the pilot. The workaround is either have the WSO do the weapon release, or for the WSO to designate the tgt (say with the TPOD for example), and have the pilot transfer the coords using PB 1 on the smart weapons page to the selected smart weapon. Even if the transfer TPOD legend is not shown on the pilot's page next to PB1, pressing PB1 still transfers the designated tgt coords correctly.

Got it. I also asked Notso directly via YouTube, he got back to me right away. If I want M3C, is that what I type in?

Recently saw a youtube video by Notso, a tutorial on the F-15E IFF system. In it, he had set several AI tankers to various IFF codes other than mode 4. When I checked in the ME, there did not seem to be a way to do this. Is there a way? If so, how? I would like to be able to assign specific IFF mode 1, 2, 3 codes to specific aircraft such as tankers and AWACS in my miz files. Cheers

This was an issue prior to the last patch when it I think it was supposed to be fixed. Finally got around to testing, and alas, when the WSO programs the JDAMs, the pilot gets no drop cues and vice versa. The WSO can designate (TPOD or whatever) but the pilot has to be the one that actually transfers the info to the weapon. If the WSO does it, only the WSO gets drop cues, the pilot does not (if the pilot does the transfer, then the WSO gets no drop cues). Occasionally, the desynch gets so bad that one crew or the other cannot even select a given JDAM, the Nxt Stn button doesn't Nxt Stn, which leaves the aircraft crippled, unable to launch JDAMs

Not sure buy MAYBE that has something to do with the CBU fuze, which is MSL. So if your tgt is at 2700' MSL, if your fuze is set for height at say 700', the weapon will never arm, as it is 2000' below ground level. Just a thought, maybe try adjusting your fuze to either use time, or 3000' ("K" setting on the CBU height parameter under A/G load)

It actually works, based on how I have my MPD/MPCD monitors placed in windows

So idiot-boy here went in and changed the resolution on his monitors, now DCS starts up with the settings icon unreachable (off-screen). How do I reset this? Pretty sure its a lua file somewhere

Not sure what you mean here. My WSO and pilot seat MFDs work as advertized. I'll attach my monitor lua. 1_Screen+4xMFCDs_above.lua

Interesting that the GBU24 worked with 1111 set in the 15 via the ME, as well as the 54. I purposely set the 54 to something other than 1111 in the ME, and changed it in flight to 1111, launched it to an "area" then terminally guided it to a point near the original coords

Just tested a GBU24 with 1111 set via the ME. Worked fine. Tested GBU54 set with 111 on the sm wpn page, worked fine (default was 1688, which is what came up on the sm wpn sensor page initially). I think there is a disconnect here, if it works in ME, it SHOULD be available via the ground crew, as IRL, they would be the ones physically changing the bomb's physical code.

Ok, so the bombs cant be set by the ground crew to anything under 1511. Why then, as it clearly states in the manual (for the F15E anyway) that valid laser codes are 1111 to 1788. I can also set 1111 (for example) in the mission editor, it shows correctly on the kneeboard, and for the GBU54, I can set 1111 on the smart weapons page. It seems there is a disconnect here, it SHOULD be available on the bomb itself, especially if I can set in in the ME, and through the smart weapons SENSOR page. My buddy tested 1111 on the A-10, he reported it worked fine.

When going to the F8 (Groundcrew) / F8 GBU Laser Codes menu to have the groundcrew change your laser codes to something other than default, the second digit only goes to 5, it SHOULD go to 1 to allow anything below 1511, all of which are available in the mission editor. In the manual, it clearly states valid laser codes are 1111 to 1788, but anything below 1511 cannot be set. Is this by design, or something that needs to be looked at?

How does one get this to work for different modules, or multi-place aircraft (F-15E front has 3 MFDs, back has 4)

After some experimentation, it turns out that the points entered as "normal" waypoints in the mission editor will populate route A. However, if you add points under the Nav Target Fix Point menu in the ME, and in the comments box type for example 1A, THIS point will overwrite Route A. So if you enter a point ("add" function in the NTFP menu above) by left clicking the map (a small box will appear at the point you selected) and then type XY, where X is is a number and Y is either A, B, or C, this point will become route A, B or C as applicable. You can make as many as you want (up to 99?) so it is quite easy to populate all 3 routes. If you want any of these points created with the NTFP to be a tgt point, call it X.A, B or C (which ever route you want this point as a tgt point on). On the TSD page, press PB9(?) to cycle between the routes you created. In the ME, the points you add under the WP tab will show up on the ME as a series of points joined by a line, but in the jet this will not be a route

You sir, are nothing short of a rock star!

Has anyone tried to create a route in ME that is NOT route A? If so, how is it done? I'm trying to have 3 different flight plan routes available in the F-15E, route A, B or C. From the book, I know that if you add #T in the name of a given waypoint in ME it turns to a tgt point and the previous WP turns into an Ingress point. But how does one make the waypoint part of route B or C?

I think there are several fixes that need to be done here, the am/fm thing, the V vs U label, and the guard also monitoring 121.5 FM vice AM