Darkdiz

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

It also appears that radio 2 is monitoring VHF guard (121.5) on FM, should be AM (R2 sub menu top row says GV121.5 FM). I guess while we are here, radio 2 line 5 seems mis-labelled in that it always shows U when there is a VHF freq entered (should say V).

Did you change the fm to am to get it to work?

Had this happen post update. Spawn (MP or SP), radio 2 is on whatever default freq is set in the mission (for example 121.5 AM). If I change to manual freq (GREC CM), and enter any freq (say 264, it comes up as 264.000FM (should be AM as the radio does not operate in the FM band at that frequency). In order to get this to work, it has to be manually changed in the R2 sub-menu, PB9 MAN-AM. This has only been noticed post update last week, and is also an issue on any preset channel (radio goes to FM, when it should stay in AM). When trying to talk either through the radio menu or any VOX (SRS or embedded) to say for example the AWACS (on 264.000AM) obviously there is no connection. Works fine after changing the system to AM through the R2 sub-menu PB9. Radio 1 works fine in this regard.

Wow, mine was fine. Do you use the "kneeboard fix" thing?

So, it seems in the kneeboard lua fix (change the lua file to declare_kneeboard_Device2 to make the kneeboard the size and position you want) there is an obscure line in the Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Flaming Cliffs\Cockpit/A10A/device_init.lua file, where it declares kneeboard_device_left vice the above. Just above this entry is creators = {{"A10A::avAutoPilotInterface_A10A"}}. Once I got this figured out, the AP now works as advertized, AND the kneeboard renders properly where I want it (bottom right corner). The final file should look like this if you are using the kneeboard size fix: attributes = { "support_for_cws", } creators = { {"A10A::avAutoPilotInterface_A10A"} } --------------------------------------------- dofile(LockOn_Options.common_script_path.."KNEEBOARD/declare_kneeboard_device2.lua") ---------------------------------------------

I'm having the same issues. EAC is armed, buttons bound, but no autopilot regardless if I use the keyboard or bindings. No HUD annunciation, nada. I tried it in level flight, VV centered, still nothing. Suggestions?

Hey has anyone figured out the F-15E kneeboard, and how to get it to display where you want it? Apparently RAZBAM kneeboards are different, and they don't display or can be manipulated like the standard (say A-10C) kneeboard positions

I'll have to check that out, I don't THINK I was transmitting, but I'll have a look *********** Looked, the "T" signifies the currently selected radio. SRS didn't seem to trigger the "T", only the radio menu triggered it, as far as I could tell

Initial impressions are REALLY nice! Couple of (inevitable) things... WSO UFC does not seem to work, in cockpit display does not change, nor does the IPad display when in the WSO seat. Exception is the vol rotaries, if pressed they change the preset number, this should be on the white button, slightly above the vol switch, same in the pilot seat. The white button is a press AND rotary, rotary changes the preset, press enters the freq into the system. The volume switches are just that, volume alone, and the bottom left brt rotary simply adjusts the brightness of the in-cockpit display (doesn't look like anything is mapped to it though) Radio 2 decimal is on the Ipad is one too many to the right (ie 266.000 shows as 2660.00). As well a leading "T" shows up, not sure what that is, it MAY be in-game, but I have not seen it before. Menu button does not indicate on the IPad display. The cockpit display changes though, so the actual push buttons SEEM to do what they are supposed to, it just does not display on the IPad As I find stuff, I'll let you know, but this is a clear game-changer!

Trying it out right now

For the A-10C only, I cannot bind any control from my Warthog throttle or joystick to any HOTAS mic sw button with VOIP HOTAS Mic SW Up, Down, Forward, Back, Press). It is available on the CII (and binds to the mic sw as expected), but not the C. I can bind it to my T16000, but not to the throttle, where I need it. It USED to work prior to the latest update, for both the C and CII. Anyone else have this issue?

The lineup for this starts right behind me