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