VAF [136] Striker

Yep, I and I figured out what the problem is. I did a lot of testing this morning and if you set any advanced actions at the origin point for late activated units, they ignore them completely. So that pretty much blows any spawn in without waypoints. This is definitely on ED to fix this problem or if this is the way it's supposed to work now, make it not possible to put in any advanced actions at the origin point. This basically hoses me on tons of missions I've done in the past that this used to work fine on and the mission I've been working on is basically trash now.

Sorry Flappie, but what you're saying isn't exactly correct. I've been designing missions for many years and they've always engaged in the past regardless of waypoints when configured with the proper advanced waypoint actions for their initial spawn in. I also can't do that in the mission I'm building because they have to spawn at different random locations so setting a waypoint is impossible. I'm probably going to just bag it and use MOOSE. We use that for our big missions we build and it works all the time with AI aircraft, they simply engage like they're supposed to as long as they have the munitions and you set them to weapons free. This is a real frustrating problem and I really hope that ED can fix some of this stuff because it used to work fine and it sucks to work with the basic editor now because of stupid problems like this. The AI are just a joke to work with right now without using stuff like MOOSE and CTLD.

I'm continuously having problems getting late activated aircraft to engage. I put together this simple example to demonstrate the problem. The Late activated Su-27 just turns and heads home instead of engaging the F-15C. This used to work great but now it's either broken or I'm doing something wrong. Any thoughts on this issue? The Su-27 has these properties in the "Advanced Waypoints" (I've tried a bunch of different options and no difference) 1. Search And Engage - 50nm 2. ROE - Weapons Free 3. A2A Weapon Use - By Threat Type & Range 4. RTB - Bingo Fuel I've tried both "Fighter Sweep" and "CAP" and the exact same result. I've also tried it with a Russian AWACS and still the same problem. I've even gone as far as setting both to the same frequency and still get the same results. It seems like none of the advanced waypoint actions are being applied to the late activated aircraft, including the initial state of either Fighter Sweep or CAP. The Su-27 completely ignores the F-15C, and the Eagle, that is set to "Reaction To Threat-No Reaction" heads over and shoots down the AWACS. So this behavior is really frustrating now. This should be really easy to solve and it's not. It must be a bug unless someone can point out something specific I'm not doing. VAF Late Activation A2A Test.miz

Hey Taz, I get what you're saying but what I did was to change the left and right to use the CMPS up and down rotary and then left the forward and aft alone. Now in manual when I push the switch down short, which used to be the JMR switch (jammer is now down long), it does the manual programs that I want. So it's a little more cumbersome in my humble opinion but there is a work around to make it more like I prefer it anyhow. You can also reassign the left/right to for/aft if you want to. The default left/right spits out 6 chaff and flare and the for/aft does one each but you can always switch them if you want more chaff and flare as a quick press. Anyhow, that's my solution and I'm back in biz.

OK, I misread that term "cycled" to be that it was starting the program cycle and I get how the system works now. Pg416: Activate a Program Each program (PROG) is assigned a letter (A - Z) and they can be cycled by either pressing the CMS switch Forward or Aft Long (>0.5 seconds), or by pressing the NXT button on the CMSP. The selected program is also displayed on the CMSC below the HUD. When in MAN or SEMI modes, depress the CMS switch Z-axis to start the program. Depress the switch again to cease the program. You can also easily activate the following quick-access programs: CMS Right Short 6 chaff CMS Aft Short 1 chaff CMS Left Short 6 flares CMS Forward Short 1 flare If in AUTO mode, you do not have direct control of the program selection or activation.

Something is messed up with it though. According to the manual when you do the CMS Forward Long, it should dispense using the current program selected. I changed the left and right to select the program using the rotary but the dispense isn't working for me as described in the manual. I tried switching the assignments from forward/aft to left/right and it doesn't work that way either.

I have to agree this is a pretty annoying problem. It would be nice if someone replied that it's going to be fixed at some point.

OK, thanks. Will give it a try.

Will there be a new textures layer file for the A-10C II? The old ones will not work with the Pavepeny removed from the external model. We use the 23rd and the 75th custom files and nose art.

Cool, glad you liked it. We've made a lot of improvements in the new version 3.2 and added another mission. Should be a lot of fun on Saturday.

Thank you very much for that suggestion Grimes! I set a "once" trigger like you tried right at the beginning of the mission after about 30 seconds and it sets the Patriots to green state and everything off. Now the switched condition triggers work perfect.

Notes about the mission (will update as necessary): Please note: There are some MP stuttering and desynch issues on servers with a high number of clients especially when launching A2A missiles currently! This is not a problem with the mission itself but rather with recent changes in the network code. Unfortunately late activated allied aircraft at Sukhumi will not be available in this release version. There is a problem with the scripting engine where the coalition airfield ownership switching is not working properly. See this thread. This is posted in the mission briefing but please DO NOT attack the enemy ships West of Sochi Adler. They are used in a mission and are a Krivak destroyer and 3 cargo ships. When the mission becomes available they are fair game.

Important: THIS IS BEING RUN ON OPEN BETA! Sorry, my bad for not posting it earlier. Also, the server is named "Virtual Armed Forces (Main OB)", so look for that one! Hello all DCS enthusiasts. The Virtual Armed Forces along with our partners the Black Veal Squadron, have been working on our campaign "Operation Khatachapuri" for just over a year now and we think it's more than ready for a good public run. The missions are all pre-designed but they are picked from a table in a random order. So even though they are not dynamically generated missions, the campaign missions are dynamically picked, so depending on the order of the missions the campaign can have a completely different feel and outcome based on that. But this is a very long campaign that requires serious A2A and ground attack coordination and typically takes anywhere from 10-12 hours to finish successfully. We are inviting the community to participate in our campaign on the weekend of September 5th and 6th starting on Saturday morning at 9 EST. We run our main server on a dedicated fiber optic line with 100/100Mbs and it's been very stable for large numbers of clients but the total is limited to 32 for stability. We will also be running LOTATC so if you are interested in doing AWACS, please message me or discuss it with any VAF member on the ED Discord channel. There's no sign up in advance so please feel welcome to join in the campaign whenever you feel like doing so. The campaign is set up to accept any air frame since it's not trigger dependant although we only use a few airframes in our group. It's currently set up with F/A-18C, F-16C, F-14B, A-10C, UH-1H and MI-8. If you would like to come in with your dedicated group and would like to have other airframes available, please message me directly with your request. I can't add just one airframe just because someone would like to see one of everything in there but I'm willing to add for instance F-16's, M2000's or JF-17's for your squadron based on a group request. This is a campaign against Eastern equipment so we won't be adding any Eastern bloc aircraft other than choppers to reduce SA confusion. The mission files is about 17MB and takes a few minutes to finish loading. You may get a black screen for that time depending on your connection. Please be patient and wait for the mission client slot screen to load. Both the VAF and BVS use custom, personalized skins for regular operations. For this weekend's event, we will be using generic (non-personalized) skins, and making these skins available to the public. The BVS skins included are the "Bazadaise" (grey) patterns for the F-14, F-16, and F/A-18. VAF skins include the CAG/Show and line birds for the 111th FS (F-16C) and VFA-136 (F/A-18C). VFA-131 and VF-142 members will use the stock DCS skins for this weekend. Google Drive Skin Downloads The requirements are as follows: 1. It's not required but we recommend that at least one person per squadron be on our Discord server. If you do not have our Discord information please message me. This will be the primary coordination channel for the entire campaign. 2. Please read the in mission briefing carefully! It contains a lot of very helpful information and will answer a lot of your questions. Be sure to write down common TACAN's and frequencies for tankers, carrier and AWACS. Also, it's very helpful if you download the 476th Caucasus flight pub documents. Big thanks to the 476th for all their hard work on all of their amazing flight publications! Russia Flight Pub, Georgia Flight Pub 3. All participants are required to use SRS and the VAF/BVS integrated comns plan. The comns plan is very simple and is included in this post. I will also be able to message it to anyone that needs it. But essentially all comms on the ground for ATC use 264, all carrier ATC on 266, all fighter coordination on 255, all strike packages on 127, all global tactical comms (please keep clear unless necessary) are on 251. AWACS on 251 and refueling packages are listed in the mission briefing. If you are in a dedicated group I recommend that you use a combination such as 251 for tactical comms and 255.10 for your group as a preset at minimum. If you're in an F-16, the fighter coordination is 134 or if you're in a group I recommend that you use a combination such as 251 and something like 134.10 or similar. 4. If you want to do one of the dynamically picked missions, please state your intentions on the main tactical channel on SRS. 5. The server is limited to 40 clients to reduce chaos and too many packages running at the same time. I will be working directly with squadron commanders to make sure we don't have too many active groups in the server at any given time to avoid over tasking and general chaos. 6. The mission also requires flying choppers to ferry troops in to capture bases or support ground operations so keep that in mind. The campaign cannot be completed successfully without capturing Sukhumi and Gudauta and the FARPS needed to secure those areas. There is also a FARP near Beslan that can be captured to further the campaign and all airbases in North are capturable as well. Thanks to everyone including the Black Veal Squadron, Eagle Dynamics, the MOOSE team, MIST, CTLD, SRS and all the VAF team members for the unbelievable number of hours spent working on and testing our multiplayer missions! VAF BVS Integrated Comm Plan.pdf

This is another frustrating problem we've been dealing with on top of some of the other AI logic issues I've posted about before. I built a simple mission to demonstrate the problem. The trigger zone is used to set the state of the Patriot system. Outside of the zone the system AI should be off with no emissions and when the aircraft enters the zone the AI should turn on and change from weapon hold to weapon free. I'm also setting the Red/Green state of the system. To be clear this used to work perfectly fine earlier this year. I can't remember what patch really messed a lot of this up. But it should be obvious that you can't restrict the AI SAM's to only engage within a specific range now. I've tried reversing the red/green state just to see if that's the issue and it has no effect. We've been able to get it to work on the PG map but not on the Caucasus map recently. VAF Patrol Patriot Zone Test Caucasus.miz

I'm sorry but this is definitely a Harpoon issue in my humble opinion and not just a visual problem. When it takes 5 or 6 of them to do the same thing as 3 mavs then it's an issue with the Harpoon not having enough boom.

I know this post is getting old but just wanted to add my thoughts to it. The Harpoon is pretty much useless in the sim. We've hit the Krivak 6 or 7 times and still not enough to do damage that disables the ship, but I can hit it 3 times with a AGM-65F and it's a goner. So something is wrong with the Harpoons IMO.

Was going to report this separately but looks like it's being investigated anyhow as a potential memory problem. Just wanted to add my voice to the list. Beautiful looking map. Obviously a ton of work went into it. Experiencing a lot of trouble with it in MP though. Bad stuttering especially on the ground. And it wasn't only me. Several people in our group reported the same problem so I can't provide a track file or mission file but I could do a video. The problem eases up a little when airborne but it makes flying missions on it difficult at best currently. We had about 9 people on last night and some of us dropped off the mission because of it. I know it's brand new and will probably receive some optimization over time. Seems to be worse in heavily treed areas.

Thanks Sanj, I only wanted to know how to change the path and I did the same thing and it worked for me as well. I just didn't know what file to edit. I changed it from this: D:\\ To this: E:\DCS World\_downloads\\

I'm having the same problem. I posted it here. I want to know how to change it back to where it should be. https://forums.eagle.ru/showthread.php?p=4421623#post4421623

I get the warning from today's installer saying that files on my download drive may be deleted in I continue so I exited. I think the problem started when I had a fairly small SSD drive and it automatically found a drive with more space and changed the path to that drive. I have a large enough game drive now and I need to change the path back so that my files won't get deleted. I still have the file E:\DCS World\_downloads\.torrents folder in my main DCS Open Beta directory so I need to point the downloader there instead of on my backup drive. Any help would be appreciated.

Thanks for looking into it. We've tested it both ways, with scripts and without with the exact same results. For the last 5 years we've been doing this you could not spawn enemy aircraft on field they did not belong to and now you can. We're also experiencing weird behavior with the MOOSE scripting because of this. I know it's not a DCS problem but I'm just letting you know. In our Operation Khachapuri the red spawn in all over the place now instead of on the airfield like they should. I'm just pointing this out because it started happening at the same time.

That's not what we're saying. We're saying that we're putting another coalition on the other teams airfield, late activated client blue on red airfield, in the editor or client red on red airfield and all are late activation but will still spawn even after the airfield coalition has supposedly changed. Please look at the mission file. I've been building missions in DCS for almost ten years now. I know that they can't change sides after being placed in the editor.

OK Bignewy, I did another mission to show you the difference. I placed a group of late activation A-10C's on Sochi Airfield. I should NOT be able to get into this client aircraft because the condition for making them available is set by a trigger now. When blue owns the airfield they are activated. This is how we've been doing our missions in the past and it always worked that you could NOT get into a client aircraft until it was activated by your coalition owning the airfield. It looks like something happened with the back end code so that the airfield is showing as either red/blue/neutral on the map but it's state is somehow always being all three instead of just one of them. So when the mission started the A-10C's were already activated. I'm adding a new mission file and track file. VAF Patrol Late Activation Test Caucasus-20200702-114911.trk VAF Patrol Late Activation Test Caucasus v2.miz

Never used to work that way BN and it's causing all sorts of problems in our MP scenerios. We didn't use any of the "coalition has aerodrome" back a few years ago and the red would not spawn on a blue airfield or vice versa.

We have about a dozen missions where it used to work correctly and now it doesn't so I'm really surprised that no one else has reported it. I'm attaching a track file that I just did this morning and it clearly shows that about 7 minutes into the mission that blue takes ownership of the airfield but red still is spawning in. We also have the same problem when we put blue clients on a red airfield so when we take the airfield we have available aircraft but we can jump into them before we take it. So it's failing to work correctly for both clients and AI. Just to be clear, this has always worked in the past up till I think two patches ago on OB. I have not tested it in stable because I don't have that installed, but everyone in our group is reporting the same problem. Also, this is a global problem and not a map problem. We have the same type of scenarios on the PG map and the Caucasus and it's happening on either one. And the airfield runways in PG are repairing in 1 hour instead of 10 like in Caucasus. This happened about the same time. VAF Patrol Late Activation Test Caucasus-20200701-100146.trk