Kharrn

Yeah its really wierd. I checked all the config files and deleted old ones etc. Then today i again checked those for old files, deleted the "default" folder, deleted the Temp folder (appdata/local) and then did a slow repair - just to make sure. Restarted DCS 3 times, loaded into AH64D, F4 and Huey without problems (always used a different map per module). So just normal loading times. So tomorrow after my pc has been shut down i will see if it still works or if the problem is back Fingers crossed️ I just hope they find a working fix for everyone, even if it takes some time Thy for all the great help you give and encourage @Flappie Cheers

FML! you are a genius, my saviour, my hero! Merci beaucoup! @Flappie The issue for me started in summer/automn as far as i remember. After some update. Either when DLSS was introduced or altered, dont know. Or maybe when Kola was released (i had it installed but when the next patch hit, i had to deinstall it to have enough free space to update xD). My hardware (HOTAS etc) did not change since 2023. So either it happened after a patch, or since i run not-installed modules (F14, Kola, some campaign) and those show up "red" (as usual). Well, its pretty subjective and i cant pinpoint it down, but that should be around the timeframe. I coped with it by only flying 1-2 module(s) at a time and loading into them via some instant action mission (then jsut going away for 5-15min helped). And after that it would load into the module quickly. i googled the issue and read some reddit but only today stumbeled over your post and IT WORKED! well at least partly. Deleted all the old .lua, some double .lua(s) and the Default folder. Ran a repair and it worked - a bit. -------------------------------------------- Just ran an F4 mission from the ME and it took a good while again to load (stuck in an F2 view, because i used the module as a "client" so no loading screen). Somehow deleting the Temp folder helped - again. wierd stuff

@Raptor9 @BIGNEWY You got any news on this? sucks to sit on a Pad or do a low Hover in the Huey during monsoon on the Marianas when the wipers are not working.... Thy! ----------------- EDIT: nvm, just saw your answer from the 8th feb. Thy! Linking thread here

your welcome. and no, not really. Unless you want to know where your AI wingman is without using the F10 map or looking out the window.

In DCS only AH64D can communicate with AH64D via datalink so far (dont know if more is planned or IRL possible). If your AI wingman and your helo are set up correctly, you can REQUEST position reports from the AI, but it will not send anything independently (for now). Also FARM reports did not work for me so far - afaik with AI they dont. Waiting for an update from ED into this for a loooong time....

If ppl know and follow procedures like i already stated in above comments, you wont miss triggers. Campaigns usually require knowledge about A/C and TTPs and are not a "basic learning environment". Dont take it personally, its just how i see this. For the wingman you need to put in the correct Freqs at startup as stated in the mission brief and kneeboard. Afaik Florence changed all missions so that there are random freqs set up in the cold Apache. So you really have to change them before continuing. Maybe check if you got the last update to the campaign Greetings and gl

my question - as i thought would already be detailed by asking about requirements - was aiming at which particular settings have to be applied to the weather to make the Dust Storm(s) (?) appear. If there are none, and it will be vis at sealevel, im thank you for that hint and i will try to take a look. But meanwhile it would be nice if you could substantiate your claim with something like a screenshot maybe!? thy K

@BIGNEWY sry to bother, but with the patch just released, could you tell us how to "enable" the new "Dust Storm" (except from enabling it in ME)!? Say what are the requirements that it will show., like pressure, humidity, clouds, temp !? I am currently testing on Nevada. Tried different weather settings, but never saw something that resembles a "dust storm" with vis 984-1600sth... Thy in advance! K

well, usually ppl who change "code" inside sth like a .lua file, know to take a copy for safety beforehand.... as you could be aware of, the problem with the not-continuing-campaign is elaborated in multiple different threads and always comes down to this: - yes, sadly (and strangely) it happens more often in this campaign then in others (personal assumption) - core problems can NOT be fixed by a campaign creator - there is a workaround I understand that loosing your progress might be extremly frustrating, but that is on you and noone else. hope you can regain it somehow and get back to having fun. peace

yeah im sry i might have stated it wrongly. you cant just use a TP as "target data" for LIMAs. TPs are more of a "reference" for you to know where to look or in which direction to shoot (e.g. when using LOAL and a buddy lase). @AstonMartinDBS linked the go-to thread an @Raptor9 already provided a thorough answer in that thread happy hunting

shameless copy/paste from FoS discord, just as an "add on" answer to what Florence already said. So always follow procedure and tasking, especially when working with controllers (eg ATC, FAC, JTAC, CCT). cheers

hey, first of, i guess you mean as "tasked" - well kind of because Foghorn comes up with the idea so you dont really get tasked by the JTAC but kinda by PC (pilot in command). "as fragged" would refer to the ATO fragment for the squadron which details missions, targets, etc etc. "as fragged" usually refers to a fragmentary order. In this case playing hide and seek plus whack-a-mole is not a part of the ato i'd assume now for the part of flying north. iirc and if @Florence201has not changed it in the last weeks, you fly back to WP3 close to a village (wp4 was the target small town iirc). there you turn around and start looking for targets but dont engage. wait till you get a text message/hint telling you to press spacebar when you have visually aquired an enemy team. then Dim will tell you to "call your shots". afterwards iirc you are cleared to creep towards wp4 and s&d the enemy teams. Hope this works out for you

why would you need a JTAC lasing a target (and thereby getting exposed irl) if you will attack it afterwards with "fire and forget" weapons that will not need the laser? Just use the coordinates the JTAC gives you, put a TP in the TSD, select that TP to get distance and bearing etc, and either a) let em fly OR b) scan with the FCR and use your Limas how they are meant to be used -> fire and forget group killers cheers as for the OT: type 3 will always give you "cleared to engage" (JTAC has neither eyes on the a/c nor on the target). if JTAC can lase, you will need to call (i think it was after his "continue") -> "IN", "LASE" (or "10 seconds" and then "lase" but thats not correctly simulated) and he will respond -> "LASING". Then you call "SPOT" (or contact the lase) and JTAC will (hopefully) give you -> "Cleared hot" If JTAC gave you an attack bearing, and you are not within that, he might call "abort". Vanilla DCS JTACs are kinda unreliable at times - especially in multiplayer btw

1. order via redu menu -> F10 -> other ? or did you try to radio menu -> F1 the wingman? cause that will not work in this campaign afaik. But yeah, the AI does crazy stuff sometimes none can "failsafe" other then ED themsleves.... 3. just re-flew it without problems. after destroying the northern and northeastern targets, i got a radio message. then destroying the rest of the southern another group pops up (also radio calls). After destryoing those Rescue 2-1 is safe to land. worked. Any mods installed maybe? i know sometimes its hard to identify remaining targets if they dont shoot back. what i do is get to 9nm from the waypoint (target area) and "creep in" slowly, letting George scan every corner. usually works out as long as its not an urban area xD cheers, hope this might help a little!

just re-flew M06. No real problems with triggers. some radio chatter overlapped a little (Foghorn setting the Freq and Dim starting a rather long back and forth about FMJ/ApoNow ...) but not really a biggy. Gun fire observed the whole time from inbound WP2 to engaging targets from 3 nm. then the enemy fire definately slacked off a little. maybe they heard 2 Apaches comming Wingman was behaving normally. Had to fly around a lot cause the last inf dude was hiding between some buildings (guess an AI pathfinding problem)... One of the best missions for me. Love to work the PNVS/TADS. Hot start, fly in with time acc, gun em all down, go home safe the day. cheers

that sounds like another logbook (/campaign progression) related bug. nothing a mission designer can do about atm. I personally stay away from replay after skipping and skipping at all. i replay until im okay with mission score to move on. else is just a pain would need to adress this to ED cheers (you "could" alter you logbook.lua to a 100 per mission if you want to finish the campaign gloriously, for the sake of your own satisfaction ;))

I think this might be an issue with the logbook.lua and/or the campaign mechanics. e.g. when i load into a mission via campaign (start the mission for the first time, not a retry or sth), when i fly the mission and look at the F10 map, the "callsign" of my aircraft will be my personal name, put in the logbook, in my case "KJ". If then another mission is loaded via trigger (say F10 radio menu) the "callsign" on the F10 will be a different one and the icon settings are changed. In my example my aircraft then had the "callsign" REFLECTED (cause i was flying the F-4 MIG Killers campaign when noticing this) and i only had the option between dot and none (as icon settings) as @Gretsch_Man already stated. If i load the same mission via ME, i have the full range of icon settings (like set up in the menu via options). Example to try it out: F-4 MIG Killers campaign by @Reflected Start any mission (that will have multiple parts, like Mission 3) from the campaign menu. Fly and look at your callsign on the F10 map and check the "icon settings" by switching icons (none/ dot/ symbol). Fly until another mission loads via trigger or until you can "change" the mission via F10 menu. Check the "callsign" and "icon settings" now. Greetings K

when you get the "clear" to proceed from arming, you have to close the canopy and then hold short (behind the lead or further wingmen depending on your pos in the flight). If Jester (or whoever is your on that day "GIB" ^^) gives you the "canopy closed stipes aligned" stuff and you hold short, then Lead or your RIO will call Tower (or do the "check") on Button 3. If Lead was already on the runway and didnt go on it might have been a trigger issue. Hope that help a bit quick idea for a workaround which might help: Use DCSs own "reset mission" key instead of the F10 menu (its in the control settings, ithink in the category "general"). I personally only had the issue with getting dumped to debriefing in the whole campaign once. And that was when i used "refly" after a 75% (or sth) attempt. After that i erased the flown mission out of the logbook.lua and reflew it from start. Cheers!

damn those logbug problems. The AH64-D campaign (not it itself cause its core related) has a lot of those too, especially if you have a draw or below 100% outcome and you want to refly. borkes up the whole campaign progress. In that forum thread, user Trankiller posted a workaround which might work here too. Find the logbook.lua in (sth like) C:\Users\username\Saved Games\DCS.openbeta\MissionEditor Make a copy for your own safety !!! If anything goes sideways, restore the copy. in my case i once altered sth wrongly and my whole logbook "profile" was gone... Open the .lua with a text editor (recommend notepad++). Search (left ctrl F) for "mig killers". I already tried to alter mine (as example) to your needs - in this case completion of "01 FAM Flight". dont just copy past it all, that WONT work. Look for the correct parts that you need and replace them! Hope it works! Another way would be to scrap the [3] part and refly the FAM flight. it teaches you A LOT of things for later BFM and ACM - if you havent already flown it like multiple times cheers K

no problem, was fun reading through the manual again and re-checking if it works out the way i remembered it Yeah would be really nice to have FARM, Target and someday firezones working. e.g. tell your wingman to hold pos, then drop 2 firezones, share those, tell him to engage FZ 2 while you engage FZ 1, then ask for a FARM report to see wingmans state. someday....2 weeks ^^ Would get rid of F2ing or F10ing to see where the f the wingman went...or crashed again. cheers

hope this might help

Since i read lots of threads where ppl struggle(d) to get the Apache Datalink to use, i recently posted a rather lenghty method in another (campaign related) thread. I know this is not all-encompassing and that was not my intention, but i hope it will clarify some of the mistakes that can happen during setting up (e.g. using wrong preset; not tuning to SC; etc). This will mainly focus on SP but most of it can be used to setup MP as well. It works for me with a cold and dark a/c. Feel free to add any knowledge about the datalink (ingame) you have and are willing to share. Hope it helps! Good hunting. Geschrieben vor 2 Stunden (bearbeitet) lets say "it depends". First things first: the only thing that is working for me so far, is to send and request the PP (present position) from AI, so that i can see the symbol of the sending AH-64D on the TSD. If i request FARM reports, i get none ("XMIT NAC"), while sending works (though even if the AI recieves it cant "do" anything with it ^^). Targets, FZs or NFZs, etc is still udner development afaik. Ok, now lets start. The SP Mission has to be set up to support AH-64D datalink on every AH-64D (AI and player/clients). BUT most of this stuff can also be done ingame, though you need to know some info which can more easily be optained though the mission editor. There is one (more like two) prohibiting option(s) that have to be checked to make it workable at all from my experience (see "c" and "d"). ME (mission edior) settings: a) check or set frequencies, e.g. 225 AM. For AI this can only be set in the "unit" tab (when you click on a unit). check in the player AH-64D in the (unit tab ->) radio tab, that under ARC-164 (UHF radio) channel 2 you have the same freq (e.g. 225 MHz AM). [we use channel 2 because we will use Preset 2 for the datalink] b) check "aircraft additional properties", some blue symbol lke 3 points in a row (lower unit tab where you can also choose waypoints, loadout, etc) -> check or set Datalink Originator ID and ownship callsign, e.g. i set the AI to be "Palehorse 6-1", gave it Datalink Orig ID of 6 and "datalink" callsign P-61 (addition: in the TSD for "P-61" you will only see "-61" bc it will only display 3 letters. Keep that in mind). Max number ID is 39. the callsign is just how that Apache will show up in Datalink and on the TSD. c) check that in the "waypoint" tab, in the first waypoint there is: EPLRS on (sometimes "EPLRS(on) -a"). Normally its automatic but sometimes it got (or gets) erased. Like discriped in my previous post, i found out that if EPLRS is not set to "on", the AI will not use datalink (my assumption!). d) set in the "datalinks" tab (pink tab with 3 little symbols like two squares and a rectangle) for EVERY AH64-D you want to communicate with by datalink: datalinks -> SMDL (no other option atm) -> Settings: check that PRESET 2 is set to UHF SC (= single channel) and DL NET is ticked. [addition: you can also change the name of the PRESETs here, but this is only how they show up on your (Apaches) COMs-page and EUFD. so not really needed atm and especially not needed for AI at all] SMDL -> Networks: navigate to chosen Preset (in this case "2") and add the groups/units to that preset you want to reach via this preset (up to 8 primary members / 16 team members). There you can recheck datalink ID and c/s. This is the (my) way, how I made it work for me. Not saying this is the method. Normally a difference in freq (UHF) to the Preset (e.g. if you choose VHF on PRE 1 instead of UHF PRE 2) shouldnt make a difference. BUT as long as we cant change freqs on AI aircraft (other then with set freq in waypoint options or the one "voice" freq in the main unit tab), the player has to be on the correct freq (so correct freq on the used preset), to communicate with AI via datalink. Ingame (flight) settings: I.) If we did set all up as described above we only have to "tune" to the correct Preset. Get in your Apache, set left MPD to COM. check the EUFD, use the "DL" labeled rocker (IDM Rocker Switch) down one to switch to UHF radio DL (the square with a hole in it) and also use the "RTS" rocker switch down once to switch "voice" also to the UHF radio (need it to change UHF preset). Now press on the "P" button on the right side of the EUFD to see all presets, and use the "WCA" labeled rocker switch (left side) down once to switch to Preset 2. Then press the "Enter" button on the right side EUFD. Now on the EUFD it should display "(square with hole / < / dot) UHF* 225.000 PRE 2 L2 ..." Go to the TSD (right MPD), press "RPT" (reports) top left. then left side "PP" (present position). check down left on the TSD page, if "MSG" is set to "RQST" or "SEND". put it to "RQST" if its not. Check if in the top right some datalink callsigns show up (in my case "-61" for Palehorse 6-1 and "R-1" for Rotary 1-1 (both AH-64D)). Choose if you want all of them "ticked" to send you their PP or just one etc. Press "SEND UHF L2" right side (only shows up if 1 "recepient" is ticked). Now some symbols (helicopter) with the datalink c/s should pop up on the position of the requested datalink members. Make sure you zoomed the TSD out enough to see them, and make sure they are flying or at least are fully started up. Check if you have line-of-sight and range to those datalink members (the UHF antenna is located on the underside of the tail boom !!!). If you get "XMIT NAC" there might be something wrong, not set up correctly or an other factor. II.) like i said you can set this all up within the cockpit. i will only briefly cover some hints to it here, but @Wags has some very good vids on datalink which i will link to at the end of this rather long post. a) COMs page, press "Preset 2 L2" on the left (if UHF is shown or not shown) -> "UHF" (top) -> "TUNE UHF" (down right) -> "SC" (UHF radio will be tuned to SC of preset 2. you can check SC of preset 2 in the middel, in my case "SC: 225.000". b) COMs page in the middel you see "Ownship" and in my case "H-2" (Hammerhead 2-1) which is my Datalink callsign. Press "ORIG ID" on the lower row and you get your ownship datalink ID on the top right "DATALINK ORIG ID" in my case "2". c) COMs page press "Preset 2" -> "NET" (lower row middel). Here you can see all your datalink "members" on that PRESET. you can also delete members, add members, switch if a member is team or primary, check their datalink IDs and c/s and you can also change them. this will only change those in YOUR aircraft. e.g. if you change the ID to an other number then set up in the ME, it will not work. The datalink IDs (on this page referred to as "SUB" = subscriber ID) are one per aircraft! Also the datalink c/s will only change how you see them on YOUR aircrafts datalink and thereby TSD. e.g. if i change the datalink c/s of "-61" (which is Palehorse 6-1) to "222" (always needs to be 3 letters), that aircraft will show up as "222" on my TSD, but nothing will change OUTSIDE of MY helicopter. He will still be Palehorse 6-1 on comms. You should also have a member directory "MBR DIR" on the left lower side of the NET page. Here you should see all datalink aircrafts even if they are NOT put in YOUR preset. They show up with a/c callsign, datalink c/s and datalink ID. BUT, if the AI has not been set up in the ME to have YOUR aircraft in their preset, it WONT WORK. Hope this all helps in getting you started! good luck FARM Reports (NOT with AI !) Target sharing via Datalink in multiplayer Greetings K ----------------------------- sorry, this took some time and got to be a wall of text. but i thought i rather try to explain it completely and thoroughly then half hearted. if you have any more questions, ask or PM me. Any typos or spelling mistakes are intentional english is not my first language, hope its read-able xD cya

lets say "it depends". First things first: the only thing that is working for me so far, is to send and request the PP (present position) from AI, so that i can see the symbol of the sending AH-64D on the TSD. If i request FARM reports, i get none ("XMIT NAC"), while sending works (though even if the AI recieves it cant "do" anything with it ^^). Targets, FZs or NFZs, etc is still udner development afaik. Ok, now lets start. The SP Mission has to be set up to support AH-64D datalink on every AH-64D (AI and player/clients). BUT most of this stuff can also be done ingame, though you need to know some info which can more easily be optained though the mission editor. There is one (more like two) prohibiting option(s) that have to be checked to make it workable at all from my experience (see "c" and "d"). ME (mission edior) settings: a) check or set frequencies, e.g. 225 AM. For AI this can only be set in the "unit" tab (when you click on a unit). check in the player AH-64D in the (unit tab ->) radio tab, that under ARC-164 (UHF radio) channel 2 you have the same freq (e.g. 225 MHz AM). [we use channel 2 because we will use Preset 2 for the datalink] b) check "aircraft additional properties", some blue symbol lke 3 points in a row (lower unit tab where you can also choose waypoints, loadout, etc) -> check or set Datalink Originator ID and ownship callsign, e.g. i set the AI to be "Palehorse 6-1", gave it Datalink Orig ID of 6 and "datalink" callsign P-61 (addition: in the TSD for "P-61" you will only see "-61" bc it will only display 3 letters. Keep that in mind). Max number ID is 39. the callsign is just how that Apache will show up in Datalink and on the TSD. c) check that in the "waypoint" tab, in the first waypoint there is: EPLRS on (sometimes "EPLRS(on) -a"). Normally its automatic but sometimes it got (or gets) erased. Like discriped in my previous post, i found out that if EPLRS is not set to "on", the AI will not use datalink (my assumption!). d) set in the "datalinks" tab (pink tab with 3 little symbols like two squares and a rectangle) for EVERY AH64-D you want to communicate with by datalink: datalinks -> SMDL (no other option atm) -> Settings: check that PRESET 2 is set to UHF SC (= single channel) and DL NET is ticked. [addition: you can also change the name of the PRESETs here, but this is only how they show up on your (Apaches) COMs-page and EUFD. so not really needed atm and especially not needed for AI at all] SMDL -> Networks: navigate to chosen Preset (in this case "2") and add the groups/units to that preset you want to reach via this preset (up to 8 primary members / 16 team members). There you can recheck datalink ID and c/s. This is the (my) way, how I made it work for me. Not saying this is the method. Normally a difference in freq (UHF) to the Preset (e.g. if you choose VHF on PRE 1 instead of UHF PRE 2) shouldnt make a difference. BUT as long as we cant change freqs on AI aircraft (other then with set freq in waypoint options or the one "voice" freq in the main unit tab), the player has to be on the correct freq (so correct freq on the used preset), to communicate with AI via datalink. Ingame (flight) settings: I.) If we did set all up as described above we only have to "tune" to the correct Preset. Get in your Apache, set left MPD to COM. check the EUFD, use the "DL" labeled rocker (IDM Rocker Switch) down one to switch to UHF radio DL (the square with a hole in it) and also use the "RTS" rocker switch down once to switch "voice" also to the UHF radio (need it to change UHF preset). Now press on the "P" button on the right side of the EUFD to see all presets, and use the "WCA" labeled rocker switch (left side) down once to switch to Preset 2. Then press the "Enter" button on the right side EUFD. Now on the EUFD it should display "(square with hole / < / dot) UHF* 225.000 PRE 2 L2 ..." Go to the TSD (right MPD), press "RPT" (reports) top left. then left side "PP" (present position). check down left on the TSD page, if "MSG" is set to "RQST" or "SEND". put it to "RQST" if its not. Check if in the top right some datalink callsigns show up (in my case "-61" for Palehorse 6-1 and "R-1" for Rotary 1-1 (both AH-64D)). Choose if you want all of them "ticked" to send you their PP or just one etc. Press "SEND UHF L2" right side (only shows up if 1 "recepient" is ticked). Now some symbols (helicopter) with the datalink c/s should pop up on the position of the requested datalink members. Make sure you zoomed the TSD out enough to see them, and make sure they are flying or at least are fully started up. Check if you have line-of-sight and range to those datalink members (the UHF antenna is located on the underside of the tail boom !!!). If you get "XMIT NAC" there might be something wrong, not set up correctly or an other factor. II.) like i said you can set this all up within the cockpit. i will only briefly cover some hints to it here, but @Wags has some very good vids on datalink which i will link to at the end of this rather long post. a) COMs page, press "Preset 2 L2" on the left (if UHF is shown or not shown) -> "UHF" (top) -> "TUNE UHF" (down right) -> "SC" (UHF radio will be tuned to SC of preset 2. you can check SC of preset 2 in the middel, in my case "SC: 225.000". b) COMs page in the middel you see "Ownship" and in my case "H-2" (Hammerhead 2-1) which is my Datalink callsign. Press "ORIG ID" on the lower row and you get your ownship datalink ID on the top right "DATALINK ORIG ID" in my case "2". c) COMs page press "Preset 2" -> "NET" (lower row middel). Here you can see all your datalink "members" on that PRESET. you can also delete members, add members, switch if a member is team or primary, check their datalink IDs and c/s and you can also change them. this will only change those in YOUR aircraft. e.g. if you change the ID to an other number then set up in the ME, it will not work. The datalink IDs (on this page referred to as "SUB" = subscriber ID) are one per aircraft! Also the datalink c/s will only change how you see them on YOUR aircrafts datalink and thereby TSD. e.g. if i change the datalink c/s of "-61" (which is Palehorse 6-1) to "222" (always needs to be 3 letters), that aircraft will show up as "222" on my TSD, but nothing will change OUTSIDE of MY helicopter. He will still be Palehorse 6-1 on comms. You should also have a member directory "MBR DIR" on the left lower side of the NET page. Here you should see all datalink aircrafts even if they are NOT put in YOUR preset. They show up with a/c callsign, datalink c/s and datalink ID. BUT, if the AI has not been set up in the ME to have YOUR aircraft in their preset, it WONT WORK. Hope this all helps in getting you started! good luck FARM Reports (NOT with AI !) Target sharing via Datalink in multiplayer Greetings K ----------------------------- sorry, this took some time and got to be a wall of text. but i thought i rather try to explain it completely and thoroughly then half hearted. if you have any more questions, ask or PM me. cya

fair now go and attend the best campaign in life! congratz

cant you just erase the AI plane(s) after the kissoff ? like have them fly out to X after the kissoff for another 10 sec and then erase the plane itself? (( sry i cant look into ME myself currently if there is an "erase" command or script at all, that makes the plane disappear and not explode... ))