Sarge55

Nice, now all you need is a third Cougar MFD to export the AMPCD to. I use the third one with the Harrier as the UFC.

@Tiberius, Thanks for checking that. The grand kids are over for a few days so no time to start DCS. ____________________________________________________________________________ @Sephroth Yes there is, actually I think it is the most commonly used method. Check the first post in this thread, Cowboy10uk provides a link. Also check the "Input and Output" thread although you will have to do a bit of a search. https://forums.eagle.ru/forumdisplay.php?f=96

@Tiberius, Thanks I'll check it out. Does it affect the EW page though?

This for sure. :thumbup: The 8 Nm limit is frustrating.

Which one is doing the AG radar? That is the most important Engineer.

Hi Mike, Glad you sorted it out. I use YAME with my BMS setup as well. Tried Helios in the early days but I think it shines with a touch screen and I didn't have one. There is a mod which puts a black border on the text in the AMPCD display. I think I saw it in the user files on the DCS site. I actually turn off the map and only pop it up if I need it.

Was the F-18 pilot wearing NVG's?

Doesn't TKR mean Tanker? The carrier has a different acronym.

Holy cow... You're right. It does look like they left the plastic protective coating on the glass. Arg, "what has been seen cannot be unseen". I can't help noticing it now. Damn!

Hi Mike, When you renamed the file you were missing a ; in your monitor file (FA18C.lua). I added it, so try the attached one and see if it works. FA18C.lua

@Peaches, That's all I get as well. I gave it up for now.

Hi Mike, I'm not a programmer, just picked up a few things along the way after many years playing with DCS. Here is the monitor setup file I use for my Hornet and Harrier export. DCS will ignore the Harrier settings so you can leave them in or delete if you wish. You will have to modify the x,y locations to match your setup. I have a 4240x1080 setup, monitor one is 2560x1080 and monitor 2 (exported to) is 1680x1050. I have 4 Cougar MFD's afixed to my lower monitor so the exports are located to display inside them hence the odd size and placement. I've attached the .init file for the AMPCD. I've also attached the IFEI .init I find it handy having it more visible. Eyes are starting to go being on the wrong side of 60... I should say just in case you're not aware, use Notepad++ to make changes to your files. You'll have to ask a programmer what the difference is between Windows Notepad and Notepad++ but apparently it can screw up the modifications. BTW I use OvJME to uninstall and re-install my mods when there is an update. Makes it a lot easier. If you have any questions I'll check back again or PM me. Harrier Hornet.lua AMPCD_init.lua IFEI_init.lua

Works great. I just made an OvJME file for it, nice to have if you are on OB and constantly updating.

Looks like you have "commented out" your AMPCD CENTER_MFCD in your monitor setup. It shows two -- infront of AMPCD CENTER_MFCD=

The way the video came across to me is not how a Bullseye is established or implemented. So a flight lead decides to set a bullseye "Waypoint" as part of his flight plan, then what? He has to pass that location onto every other flight, AWACS, Air Defense system, etc so they know where it is and be able to produce calls from it. Then every other flight lead does the same thing? I doubt it. It is a single location established by the Command HQ for a period of time that is passed on to "All" assets to be used as the Bullseye. It's a perfect example of the saying "everyone playing from the same sheet of music", no confusion. Why is it part of the flight plan? It should just be a Bullseye location (call it a markpoint if necessary) entered into the system that shows on the HSI / Radar.

Here is a link in the forums to a "How to" thread. Worked for me. https://forums.eagle.ru/showthread.php?p=3537988#post3537988

Do you have any mods to reduce the blurry text in the DDI's? If so, that might also be effecting the JHMCS lines.

You could try reducing your Saturation Y in the axis control setting, it flattens the line out. Try 70 and work from there. It will affect all the slews but it's subtle.

Excellent work Blbo. Thanks I'll add that to my OvJME mods.

Search "Yardstick" and you'll get a bunch of hits in the forum with full expalinations. Briefly, you and your wingman set your TACAN 63 apart and you will get DME but not direction. So for example you set 29X and he sets 92X.

Looks interesting. Do you really have to add the "Deck crew" mod? Hate adding unnecessary bloat.

Hey Cap, Why would you take the airport locations off the map? Ships and targets for sure but airports would normally be on any map. Didn't know you could do that in the F10 map, learn something every day.

Arg... I downloaded and printed an older one. Sigh. :cry: Thanks for pointing me to the right location Chuck. I'll do a quick comparison and mark it up. :book:

Thanks for the reply WAGS. However, I'm still unclear on this point. A bullseye is a theater asset for all aircraft to reference, assigned by a commander (mission maker in ME in our case) and changed as required. It should have a separate entry apart from waypoints and markpoints. It shouldn't get muddled in with them, could be inadvertently changed with waypoint updates during flights etc. Early days yet, we'll see how it develops.

Quick question, I keep seeing the Bullseye being referenced as a waypoint inferring it is part of your flight plan. Isn't the Bullseye set as it's own separate location apart from your flight plan waypoints or am I misunderstanding the term waypoint?