RTS354

I just did a clean reinstall of Windows 10 and when I downloaded the latest beta installer, as of the date that I am posting this issue, I get the following error message: "Couldn't Connect to Server" Note that my computer's hardware and software configuration hasn't changed. I have checked my settings on my router's firewall which allows ALL outbound traffic from my network and all inbound traffic that is initiated from my network. I have verified that Norton AV does have a program rule that allows the updater access to the Internet. The updater doesn't create any log files the I can find in the installation folder which is located on a separate M.2 SSD for my gaming software. Any suggestions?

Yea, just confirmed that if I start a mission with the F-18 from either a cold start or from parking ramp hot from any carrier, the track file fails and the F-18 crashes. If I start the mission on the catapult on any carrier then the track file works as intended. Is this a known bug because I can't find anyone else reporting this?

I think I found the issue. When I takeout from an airfield, or start from mid air, the track replay work correctly even when landing on the basic or super carrier; it's only when the F-18 cold starts from a carrier when the track file starts breaking. I haven't tested a track file create from a catapult launch, or a ramp hot start, and will update this post later in the week.

I been having an issue where when I land at on the supercarrier, the tower stops communicating with me, and the only message that I get when contacting the tower is "Arrival Parking". I tried taxiing to a designated parking spot according to the supercarrier manual, but the tower will not talk to me. The reason this irks me is because I want to practice super carrier procedures and it's a pain in the ass to keep starting up a new aircraft to do this. Am I missing something?

Yes, I had to use this mod, but why is it taking so long for the devs to add grid coordinateds, and fix the AGM 65E?

If I land at an airport, or on the super carrier to do just touch an goes, I longer get any menu options to talk to the tower after landing. All I get is the option to return to the "Parent Menu" when I contact the tower. BUT if I shut down the plan and then rearm and refuel, then I get the option to request start up and every thing works normally. When landing at an airport, I'm told to taxi to parking, but when I taxi to a parking slot, I still only get the option to return to the "Parent Menu". The airport is configured as a friendly in the mission editor. What am I doing wrong or missing?

By the way, I noticed in Wagner's video, he fired after telling the JTAC laser on, and did not follow the entire JTAC procedure. He only did one run through. Can anyone recommend a video that does show several runs using the correct JTAC procedures with a F-18C using AGM 65E and F? Thanks for the feeback.

It's still hit or miss with both the AGM 65E and 65F on my system. I'm having issues even when not using a JTAC. I watched over 20 hours of videos on using this missiles in the F-18, and I'm not getting why sometimes the AGMs lock on the target and sometimes they don't. I don't have this issue with GBU's or JDAMS; it's only with the AGM 65E and F with or without the JTAC.

How to get the disount for the A-10CII if you had the steam A-10C version If you transferred all of your Steam DCS modules to the standalone version, you will not see the upgrade price of &9.95 for the A-10C II. So what I did was I bought the upgrade for $9.95 on Steam. Reloaded the Steam version of DCS. Then I when into the properties of the Steam DCS and verified that the A-10C II was installed. Next I logged into my DCS World account, went into my profile and selected the option to Edit/Delete profile. Once you are here, you should see a Steam section. There is an option to "GET LICENSES" Click on this button and DCS will search your Steam account for the downloaded A-10C II module. You should see a greyed-out A-10C II module appear which you can then bind to your DCS standalone version. Once you do this, you can remove the Steam DCS installation. I hope this clears up the confusion.

I have several issues with the F-18, JTAC, and the AGM 65E. The first issue is that the AGM65E will not fire after slewing to the JTAC's laser, if I don't have the AGM65E in uncaged mode before telling the JTAC to "Laser on" in the comm menu. After destroying the first target, this work around no longer works. The next AGM65E does find the target, but it doesn't lock on, no matter how close I get to the target. The other issue that I have is that the A-10C manual states that once you fire the weapon, you contact the JTAC and say "Off' to let him know you fired the weapon, and you then wait for conformation that the target is destroy and further JTAC instructions. BUT if I to this, the JTAC immediately response that the target is not destroyed and I assume that the laser is removed from the target because the AGM65E misses the target every time I do this. I also cannot enter grid coordinates into the UFC, I have to go into the map and scroll around the pointer until I find the Lat/Long coordinates. This is nuts! Is my F-18 installation broken in that I cannot enter grid coordinates?

I think I found the problem. There was an issue where two different units were using the same frequency. At least I think this was the problem as when I fixed this, the mission now loads and saves fairly quickly.

I just started playing with the mission editor, and before I started scripting, the mission editor took less than a second to save a mission and now, after using the MIST scripts, its taking 30 seconds to a minute for my missions to save. Is this normal? Note that I haven't been testing the mission in the "Prepare Mission" mode, it this helps. I'm using a new 2 TB Corsair M.2 SSD just for this game, and I had Dell run system utilities for 24 hours on my system with no issues, to rule out a hardware issue, and the video drivers are the latest released from NVIDIA. Thanks, Rick

I'm in a hornet.

I'm having an issue where the track replay doesn't accurately replay the mission; for example, I had a two hour mission where I launched from a carrier and when I replayed the track, it show my plane going off the side of the carrier. Note that Tacview track does replay the same mission correctly using the data it collected from the game. Anyone else having this issue? If so, how are you fixing this?

Yea, I'm in the TOO mode. Like I said everything worked perfectly, and now its a 50% probability that the ability to which between radiation targets works.

This just started after the big update. When I have the HARM page displayed and it detects two or more (SAM) radar emitters, I cannot switch between them using the RAID button. Yes, I have the diamond in the upper right of the display, and yes, the RAID button is mapped and detected in the keybindings. This happens about 50% of the time. Anyone else having this issue?

Thanks you all for the information.

Pmiceli, thanks for the info. The script works perfectly now. Since I had to create the "bridge1" zone, I assumed I had to create the flag1 variable. I'm still confused to where the flag1 variable is created. I thought that the "flag = 1" partof the function was to pass the flag that I created, in this case, flag1 to the function call, and then the function call would flip it to true if a map object was destroyed in the "bridge1" zone. Thanks again.

I’m trying to get a MIST script running that can detect if map objects within a zone are destroyed. The script is a function call to: mist.flagFunc.mapobjs_dead_zones{ zones = {'bridge1'}, flag = 1} Note that the trigger zone I created is named "bridge1" and I'm using FLAG 1. I know how to program in LUA, but I’m having issues with how the scripting works in the DCS mission editor. I’m assuming that if a FLAG is zero, it is considered FALSE. I am also assuming that FLAG (1) must be turned on and assigned a value of 0 before calling the “mist.flagFunc.mapobjs_dead_zones” function. According to the MIST documentation this function sets FLAG (1) to TRUE if a map object the zone is destroyed. Here is the MIST documentation for this function: Examples: mist.flagFunc.mapobjs_dead_zones{ zones = {'bridge1'}, flag = 51 } --[[Once run, this function will set flag 51 is set true if/when a map object has died/dies within the zone named "bridge1".]] BUT I get the following error message when starting the mission: [string"Mist.flagFunctin.mapobjs_dead{zones = {'bridge1'}, flag = 1}"]: attempt to index global mist' (A nil value) Here are the triggers in the order they are to be executed: Trigger1: Mission Start Condition1: Time More(1) Actions1: Do SCRIPT FILE (mist_4_3_74.lua) Trigger2: ONCE (Create Bridge Zone Flags, NO EVENT) Condition2: (NONE) Actions2: FLAG ON(1) and then SET FLAG VALUE(1,0) Trigger3: ONCE (Check Bridges, ON EVENT) Condition3: FLAG IS FALSE (1) Actions3: DO SCRIPT( mist.flagFunc.mapobjs_dead_zones{ zones = {'bridge1'}, flag = 1}) Trigger4: ONCE(Are Bridges Destroyed, NO EVENT) Condition4: FLAG IS TRUE (1) Actions4: MESSAGE TO COALITION (BLue, All Bridges are Destroyed, 30, false,0) So what am I missing?

It wasn't made from a track, and I have 64 GBs of memory. I have since deleted the mission and recreated it and I have no issues at this time.

Dynamic Campaign Engine compatibility? Read about the latest news of the new Dynamic Campaign Engine, but there was no information if this would be a separate module or integrated into the current mission editor. So, if it is integrated into the current mission editor would the current mission files that I have downloaded be compatible with this new dynamic campaign engine? Or if the Dynamic Campaign Engine is a separate modules, will it allow the import of the current mission files?

Here's a link to the mission file below, click on the download icon of your browser to download it: https://drive.google.com/file/d/1weFwNH4SrF1fLMNcUzHR9NFtywhvLeNa/view?usp=sharing

I'm designing a mission were all the aircraft start from the same airport. The issue is the tanker follows all of the waypoints and successfully takes off, but it does not continue to the orbit waypoint. Immediately after takeoff, the tank just orbits the airports. Note that if I spawn the tanker in the air, it does reach the orbit waypoint and functions correctly as a tanker. Anyone every had this issue? I had this issue with the AWACS too. Once it takes off, it just circles the airport.

Rudel_Chw thanks for the list.

Flappie, your a genius! The button was mapped to the VR zoom function. I was really pulling my hair out on this. Thanks again.