Peaches

Thanks, Bunny. I was afraid of that response. I don't want to go through and set up new export names for all the other modules, nor am I particularly happy to have to switch monitor setup lua files and restart DCS each time I swap to the Apache. Guess I'm waiting and hoping!

Does this approach affect your monitor setup for other module, like the F18, or can you switch modules without having to adjust your lua files?

Thank you, Floyd and j-tk. I am in the pilot's seat with George CPG handling the engagement, Direct LOBL. I've shot hundreds of missiles in this configuration, so it is not any issue with parameters. I suspect it deals with the fact that George CPG does not lead moving targets rather lases center of object, causing the missile to impact near but behind the target and not on it. This leads to my questions of what is the guidance logic of the Hellfire and is CPG SOP to lead moving targets until a few seconds to impact? If so, George CPG will be ineffective on (armored) moving targets until his tracking technique matches what a real CPG would need to do to land a shot.

Hitting moving ground vehicles coming towards me at an angle with standard LOBL shots has been challenging. I've tried multiple ranges and altitudes. Wondering if I am alone or if this performance reveals a limitation of the missile guidance logic (pure pursuit or collision guidance?). Doesn't seem like the Army would invest in a system that struggles with moving targets, but I am hoping that I am not doing something correctly here. Appreciate any thoughts! Sent from my SM-G960U using Tapatalk

I am seeing this direct-to export artifact, too. Hopefully ED has noticed it.

Formerly, the IR Pointer from the TGP appeared as a bright line when viewed with NVGs in the cockpit. Now it shows as a black line. Sent from my SM-G960U using Tapatalk

Thank you, Overalien and LeCuvier. I used CENTER_MFCD, and it works fine. Bignewy, the blurry AMPCD is caused by those using a viewport/export approach to the AMPCD, such as Capt Zeen's coding. Originally, the Hornet came hardwired to export the left and right DDIs, but users have had to modify the AMPCD init lua to get it to export. With the last version of open beta, the AMPCD init lua changed, causing the former export approach to cause fuzziness. The good news, though, is that the AMPCD is now preconfigured for export!

[REPORTED]Washed out exported displays Overalien, what is the name of the ED-defined AMPCD viewport that we can use vanilla in our monitor config file? I tried F18_AMPCD without any luck. Left and right DDI exports are working fine vanilla.

Take a look at Jabbers' flight characteristics video; he concluded that the Tomcat actually has proverse yaw.

Also here: https://forums.eagle.ru/showthread.php?t=270001

Bug report: I am new to the Tomcat but am experiencing the following issue consistently on SP and MP on the current open beta, no mods. At some point in a flight (I have not determined the conditions which trigger it), Jester goes haywire and starts clicking the RWS radar mode button repeatedly, ad nauseum, which effectively prevents the radar from functioning. Even the pilot commanded modes don't override this apparent do-loop that Jester is stuck in. I've tried turning the radar on and off, switching modes, anything to break the loop but cannot solve it. In the pilot seat, it sounds like a click-fest with the clicking noises two to three times a second. I've attached a track file from mission 2 of Cage the Bear, where the bug is manifested at the very end. Change the attachment file extension from .pdf to .trk to view. RWS looping .pdf

RESOLVED: I was changing a dummy copy of the monitor setup lua in the Saved Games folder vice the active version in the DCS root directory. No clue why there is a dummy copy in the SG folder—maybe I put it there as an archive at some point? Back to learning the ‘Cat!

Thanks for the thoughts. I am still wondering whether the F14 viewports you are using, HSD and VDI, are pre-defined, or did you need to stick code into their individual init.luas, like when one exports RWRs, CDUs, etc? Sent from my iPad using Tapatalk

Here's what my monitor lua looks like; note at the bottom that the coordinates for the F14 HSD are the same as for the A10C left MFCD, which is working fine with my monitor set-up (2560x1440 on the left--main view; 1980x1080 on the right--used for my exported viewports). _ = function(p) return p; end; name = _('JRM-Two-Monitor'); Description = 'Two monitor configuration'; Viewports = { Center = { x = 0; y = 0; width = 2560; height = 1440; viewDx = 0; viewDy = 0; aspect = 1.777777777778; } } LEFT_MFCD = { x = 2560; y = 380; width = 700; height = 700; } RIGHT_MFCD = { x = 3260; y = 380; width = 700; height = 700; } RWR_SCREEN = { x = 2695; y = 5; width = 370; height = 370; } CDU = { x = 3277; y = 5; width = 486; height = 370; } -- F-18C F18_LEFT = { x = 2560; y = 440; width = 640; height = 640; } F18_RIGHT = { x = 3200; y = 440; width = 640; height = 640; } F18_AMPCD = { x = 3840; y = 440; width = 640; height = 640; } F18_RWR = { x = 2565; y = 5; width = 400; height = 400; } F18_IFEI = { x = 3000; y = 5; width = 765; height = 340; } -- F-14B F14_HSD = { x = 2560; y = 380; width = 700; height = 700; }

Thanks for the ideas, and I'll double check them. One question: are the F14 viewports for HSD, DDD, VDI, etc. predefined (like the F18 DDIs and A10C MFCDs), or do you have to create and name them in the individual init.lua files like you do when exporting RWRs, IFEIs, CDUs, etc?