Maulkin

Where is the autoexec.cfg file located? I have looked everywhere in the DCS root folder and all subfolders but I have only see autoexec.lua...

From the book "Hornets over Kuwait": "Today, with the benefit of hindsight, and the clear knowledge that the F/A-18 is far superior to the F-14 in almost every respect," And: "Here you go: an honest comparison of how the aircraft performs relative to some of the other stuff that’s out there. The F-15 carries the same air-to-air weapons as the F/A-18, but has a better radar and associated systems that allow it to be more discriminatory about who and how it’s targeting at long range. Within visual range, similarly configured, the Hornet is more maneuverable and a better dogfighter. From a visual neutral start, similarly configured, I have never lost a “knife” fight with an Eagle. Also, the F-15 is not configured for air-to-ground operations. I can shoot down MIGs before and after I support my marine brethren on the ground. The F-15E is designed for the air-to-ground strike role, and it does outperform the Hornet in this role. However, the F-15E is very expensive and there are relatively few of them. At beyond visual range the F/A-18 is comparably equipped to the F-16, which is now (post Gulf War) capable of launching a radar missile. Within visual range I consider a well-flown Falcon (or Viper, as it is also called) to be a more formidable foe than the F-15. The Hornet’s slow-speed capabilities are still superior. Again, from a visual neutral start, similarly configured, I have never lost a knife fight with an F-16. Like the F-15, and just about everything else, the F-16 is faster than the F/A-18 and can run it down in a pinch. I’ve gotten engaged visually with a Mirage 2000 just once. I was carrying two external tanks, he was carrying none, and I beat him. The AV-8B Harrier doesn’t stand a chance against the F/A-18, or any of the other fourth generation fighters. The Air Defense Variant (ADV) of the Tornado is no match for the Hornet. The F-14 and F-4, likewise, are older and much less capable than the F/A-18. It is my opinion also that the Hornet can handle any Russian fighter currently fielded in any arena. I don’t mean to imply that Hornets don’t get beaten in dogfights by other aircraft. They do. The performance figures of most fourth generation fighters are very close. My personal contention is than an F/A-18, with an experienced pilot, in the visual arena against any similarly configured aircraft, is very difficult if not impossible to beat, depending on the other aircraft type and pilot. If you break out performance charts and start crunching numbers, you’ll find that several fourth-generation fighters have a certain envelope or regime within which they are superior to another given fighter. But, in a slow-speed fight (where most fights end up), the Hornet is tops."

I have been looking around but I have been unable to find any instructions on how to start a dedicated server. Is it embedded as part of the DCS.exe or is it a separate executable? What is the correct command line?

I am still getting this as well. On both Beta as well as stable versions.

OK I think I understand how it works now. First, the dispenser system must be set to OK (no BYPASS) and the EW set up in manual mode. Once that is done the big red button uses a 'hidden' manual mode 6 (you can only see manual modes 1 to 5) which has the following parameters, by default: chaff = 2 flare =2 interval = 0.75 cycle =20 This means that pressing the red button will effectively dump all 40 flares and chaff in 15 seconds. This can be changed by editing the file: ~\DCS World OpenBeta\Mods\aircraft\FA-18C\Cockpit\Scripts\TEWS\device\CMDS_ALE47.lua and look for the line: -- MAN 6 - Wall Dispense button, Panic

I know how to use the dispenser switch that is located on the throttle but how do I use the big red button on the left wall near the throttle? I checked RedKite's video here: and I checked Chuck's guide here: https://www.mudspike.com/wp-content/uploads/2018/07/DCS-FA-18C-Hornet-Guide.pdf But neither appear to go into this button...

I think by default there is no key bound. Look for "VTB Viewpoirt ON/OFF". I assigned 'ALT-V"

Did this update decrease the number of tracer bullets in the magazines? Because I love that!

One thing I noticed (with all training missions....not just the Mirage) is that sometime you need to wait until the instructor has finished saying all of the dialogue and then press space.bar right after he says to press the space bar. Doing it sooner can cause the press to be ignored.

In case anyone else is wondering the link to Matt Wagner's video is here: I created a small training mission here with a JTAC controller set close by a column of 4 heavy tanks. https://forums.eagle.ru/attachment.php?attachmentid=197356&d=1541642327

I ran into a problem when my JTAC would declare LASER ON but then would not declare LASING. But it worked for the first three Mavericks In any case if you would like to try the training mission I have it here: F-18C AGM-65E using JTAC.miz

I think what he means is that the mission you attached does not have a Reaper drone...or anything other than the F-18 sitting on the runway with the Mavericks loaded. I opened the mission in the mission editor and confirmed that the mission is basically empty. There are not even any waypoints for the F-18

UPDATE: Turns out my credit card company was on the ball and this triggered their fraud alert. I authorized the transaction and then tried the payment again. It worked without issue. If anyone else runs into this, and their bank does not instantly send texts to them in suspected cases of fraud, you might need to call them to let the payment go through.

I just attempted to pre-purchase the F-14 Tomcat from the DCS website but I keep getting this error: Processing failed The transaction could not be processed. Please use another payment means or try it again.

This would be useful information that should be included in the manual. I searched in the manual and I didn't see any reference to it.

Its a thread of someone very excited about the FA-18C.... cant blame him really ;)

I would say the F-5 is easier to learn only because it has a simpler set of systems. But I feel the Mirage has more potential and versatility. The tutorial for the Mirage is really well done. I fly the Mirage far more often than the F-5

How did you export the AMPCD? I am looking at the AMPCD_init.lua and I am not sure what I should do here. EDIT: Figured it out! I added these lines to AMPCD_init.lua: -- Specific part of MDI initialization dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("AMPCD") I then created a reference in my Multimontor_setup.lua file that I created in the ..\DCS World OpenBeta\Config\MonitorSetup directory: ------------ -- for FA-18C ------------ LEFT_DDI = { x = 2560; y = 0 + 360; width = 640; height = 640; } AMPCD = { x = 2560 + 640; y = 1440 - 640; width = 640; height = 640; } RIGHT_DDI = { x = 2560 + 640 + 640; y = 0 + 360; width = 640; height = 640; }

HEY!! Thanks sreventon! Just by moving those lines of code around I am now getting the left and right DDI's exported to the second monitor, and more importantly, the DDI's in-cockpit are able to display as well. However there appears to be a bit of weirdness going on with the exported video:

So I am having a bit of trouble getting this to work. This is where I am starting from, where the A-10C works and the MFCD's are exported correctly to the second monitor (but the F-18C is having trouble with the DDI output in-cockpit): multimonitor_setup.lua: _ = function(p) return p; end; name = _('General Multimonitor'); Description = 'A general multimontor config for all modules' Viewports = { Center = { x = 0; y = 0; width = 2560; height = screen.height; viewDx = 0; viewDy = 0; aspect = 2560 / screen.height; } } KNEEBOARD = { x = 0; y = 0; width = 526; height = 789; } ------------ -- for A-10C ------------ LEFT_MFCD = { x = 2560; y = 0 + 360; width = 1920 / 2; height = 1920 / 2; } RIGHT_MFCD = { x = 1920 / 2 + 2560; y = 0 + 360; width = 1920 / 2; height = 1920 / 2; } ------------ -- for Ka-50 ------------ SHKVAL_SCREEN = { x = 2560; y = 0 + 360; width = 980; height = 817; -- must be this height to hide splash screen } ABRIS_SCREEN = { x = 2560 + 980; y = 0 + 360; width = 940; height = 1080; } -------------- -- for M-2000C -------------- MIRAGE_RADAR = { x = 2560; y = -100 + 360; width = 1920 / 2; height = 1080; } MIRAGE_RWR = { x = 2560 + 1920 - 740; y = 100 + 360; width = 600; height = 600; } COM = { x = 1920 / 2 + 2560; y = 0 + 360; width = 120; height = 70; } ECM_CHF = { x = 1920 / 2 + 2560; y = 610 + 360; width = 75; height = 40; } ECM_FLR = { x = 1920 / 2 + 2560; y = 650 + 360; width = 75; height = 40; } PCA_UR = { x = 2560; y = 980 + 360; width = 500; height = 50; } PCA_BR = { x = 2560; y = 1030 + 360; width = 500; height = 50; } PPA = { x = 1920 / 2 + 2560; y = 810 + 360; width = 70; height = 90; } PCN_UR = { x = 2560 + 1920 - 700; y = 1080 - 120 + 360; width = 500; height = 60; } PCN_BR = { x = 2560 + 1920 - 700; y = 1080 - 60 + 360; width = 250; height = 60; } FUEL = { x = 2560 + 1920 - 80; y = 0 + 360; width = 80; height = 45; } -------------- -- for Mig-21 -------------- MIG21_RADAR = { x = screen.width / 2; y = 0 + 360; width = 1080; height = 1080; } -------------- -- for F-5E -------------- AN_APQ159_RADAR = { x = 1920 / 2 + 2560; y = 0 + 360; width = 1080; height = 1080; } AN_ALR87_RWR = { x = 2560 + 1920 - 740; y = 100 + 360; width = 600; height = 600; } UIMainView = Viewports.Center and this is the modified code with what I think you were describing: _ = function(p) return p; end; name = _('General Multimonitor'); Description = 'A general multimontor config for all modules' Viewports = { Center = { x = 0; y = 0; width = 2560; height = screen.height; viewDx = 0; viewDy = 0; aspect = 2560 / screen.height; } } KNEEBOARD = { x = 0; y = 0; width = 526; height = 789; } ------------ -- for A-10C ------------ function reconfigure_for_unit(unit_type) if unit_type == "A-10C" then LEFT_MFCD = { x = 2560; y = 0 + 360; width = 1920 / 2; height = 1920 / 2; } RIGHT_MFCD = { x = 1920 / 2 + 2560; y = 0 + 360; width = 1920 / 2; height = 1920 / 2; } else LEFT_MFCD = nil -- remove for others RIGHT_MFCD = nil -- remove for others end end ------------ -- for Ka-50 ------------ SHKVAL_SCREEN = { x = 2560; y = 0 + 360; width = 980; height = 817; -- must be this height to hide splash screen } ABRIS_SCREEN = { x = 2560 + 980; y = 0 + 360; width = 940; height = 1080; } -------------- -- for M-2000C -------------- MIRAGE_RADAR = { x = 2560; y = -100 + 360; width = 1920 / 2; height = 1080; } MIRAGE_RWR = { x = 2560 + 1920 - 740; y = 100 + 360; width = 600; height = 600; } COM = { x = 1920 / 2 + 2560; y = 0 + 360; width = 120; height = 70; } ECM_CHF = { x = 1920 / 2 + 2560; y = 610 + 360; width = 75; height = 40; } ECM_FLR = { x = 1920 / 2 + 2560; y = 650 + 360; width = 75; height = 40; } PCA_UR = { x = 2560; y = 980 + 360; width = 500; height = 50; } PCA_BR = { x = 2560; y = 1030 + 360; width = 500; height = 50; } PPA = { x = 1920 / 2 + 2560; y = 810 + 360; width = 70; height = 90; } PCN_UR = { x = 2560 + 1920 - 700; y = 1080 - 120 + 360; width = 500; height = 60; } PCN_BR = { x = 2560 + 1920 - 700; y = 1080 - 60 + 360; width = 250; height = 60; } FUEL = { x = 2560 + 1920 - 80; y = 0 + 360; width = 80; height = 45; } -------------- -- for Mig-21 -------------- MIG21_RADAR = { x = screen.width / 2; y = 0 + 360; width = 1080; height = 1080; } -------------- -- for F-5E -------------- AN_APQ159_RADAR = { x = 1920 / 2 + 2560; y = 0 + 360; width = 1080; height = 1080; } AN_ALR87_RWR = { x = 2560 + 1920 - 740; y = 100 + 360; width = 600; height = 600; } UIMainView = Viewports.Center But with this the F-18C is no longer having a problem but the A-10C is also not exporting. Am I putting this code in the correct location? I am a bit of a .lua n00b and only managed to get this far with it by trial and error. ;) I am afraid I will need detailed instructions on how to do this... Also, what is the unit_type for the Harrier as I think it also uses LEFT_MFCD and RIGHT_MFCD. Thanks!

Thanks SkateZilla I will try that out!

Make sure the axis is not also bound to some other controller.

I'm ok with it not implemented but setting DCS into a multimonitor mode (even if I have not set up the F-18 module to take advantage of it) causes the in-cockpit DDI displays to not function. This is annoying because it means I cannot use the multimonitor setup on my AV-8B, M-2000, A-10C, KA-50, and Mig-21 without having to switch back and forth. I was hoping it was simply something I was doing incorrectly. Sent from my P00A using Tapatalk

I tried using my multimonitor configuration but it causes the left and right DDI's to no longer display anything at all. I have not yet attempted to re-route the DDI video output so technically nothing should have changed from a single monitor setup. The center AMPCD still works however. Has anyone gotten this to work?

Thanks Dronin! #3 I found that switch for the strobe light but that is not the lights I am referring to. If you watch closely in that video you will see additional position lights on the top and bottom surfaces of the wings. #4 yes I am aware of that. Alternatively you can reset the battery power. I just found it odd that the order of the words changed since the audio is generated by a tape....which would have made that impossible.