Bugs and Problems

[coldViPer]

19 minutes ago, Kharrn said:

Only thing i couldnt rly get to work is the datalink, but haven spend much time on that tbh.

 

 

Datalink works when you set UHF radio to preset (345.6) and put that DL square on that UHF radio.

[Florence201]

32 minutes ago, coldViPer said:

Datalink works when you set UHF radio to preset (345.6) and put that DL square on that UHF radio.

I feel I set DL to UHF 345.6 in the ME

[Simonster83]

1 hour ago, Kharrn said:

wow i think you never tried any of those old campaigns? i mean some are really horrible in terms of triggers/bugs, but this one!? rly!?

I had 1 not firing trigger so far (just finished MIission 5) in Mission 2 which was fixed with the latest patch (and befor you could even download the fixed mission right here in the forum!).

What i do when flying:

a) set everything up and lift at time given (do able);

b) follow route as good as possible - you dont really have to stick to wp given hights from the briefing, but at least fly along the route; ((If you cant follow that, you might wanna relearn the aircraft before proceeding to "life fire" campaigns (not training campaigns)))

c) set freqs via com page manual and do NOT use presets (which is stated multiple times in briefing and campaign docs);

d) watch when it says "DATA", sometimes Foghorn likes to tinker with the pilots radio But it will say that in the top right (sth like "Foghorn will change freq to.........." and so on.

Only thing i couldnt rly get to work is the datalink, but haven spend much time on that tbh.

Maybe just re-fly and try to have fun. we dont have many campaigns in general and this one has been fine so far.

I will try Mission 6 now and report if i encounter said issue.

cheers

 

Haven't flown much of any older campaigns expect one really good one for UH-1H (low level heaven spring campaign). Maybe I'll try to fly at a lower altitude than stated at the briefing cards, I'll see if that helps with the mission triggers. I've set the the frequencies the best I can, but still sometimes they change during mission by themselves. And usually when Foghorn is supposed to change the frequency nothing happens.

 

Can you explain what do you mean by presets? I have manually typed the frequencies for the different channels, but sometimes they don't seem to work.

Edited August 12, 2024 by Simonster83

[Blackhawk163]

Mission 8 still broken for me. 1st set of targets by the village gets wiped out by U1 then we proceed to orbit until I get tired of formation flying. nothing else triggers. The only time I've ever triggered anything past the first set is when I rambo'd my way into the village.

[coldViPer]

8 hours ago, Simonster83 said:

Can you explain what do you mean by presets? I have manually typed the frequencies for the different channels, but sometimes they don't seem to work.

 

null

18 minutes ago, Blackhawk163 said:

Mission 8 still broken for me. 1st set of targets by the village gets wiped out by U1 then we proceed to orbit until I get tired of formation flying. nothing else triggers. The only time I've ever triggered anything past the first set is when I rambo'd my way into the village.

Maybe we have to kill those targets, not U1. When I killed the first set of targets, trigger worked ok. When U1 killed 2nd set of targets, trigger was not activated, only endless formation flying. Anyway, had to to skip this mission.

[Blackhawk163]

17 minutes ago, coldViPer said:

Maybe we have to kill those targets, not U1. When I killed the first set of targets, trigger worked ok. When U1 killed 2nd set of targets, trigger was not activated, only endless formation flying. Anyway, had to to skip this mission.

Yeah, I agree. The first time I played the mission I did it as if I were playing lead because I didn't listen or read the brief and assumed I was still lead. The second I heard that there were targets near a village I headed that way and blasted them with rockets. I got up to the smoke marking section, but was Winchester before I could complete. I headed back the FARP where nothing happened there. Frustrating. Guess I'll have to skip yet another mission then.

[Florence201]

I'll take a look at M8 tonight once home from work. Sounds like there's a trigger not firing for some reason. Everything did work when i released the updates for this patch.

Edited August 13, 2024 by Florence201

[Florence201]

I just want to check where it is in M8 people think it's broken

1. Launch as Wingman

2. Get on station - Streethawk RTB's (No action from Ugly here)

3. Overwatch calls contact - JTAC vectors GR4s for Show of Force (No action from UY5)

4. Uy5 vectored to new Op Area and freq change

5. UG5-1 then leads an attack

6. Follow on attacks directed by FAC

 

At what point is this not working please? A Tacview file or DCS trk file will help me see what's broken.

[coldViPer]

For me number 6. Got directed by FAC, UG1 attacks first and kills all enemy -> no any message, only silence and endless formation flying.

[Kharrn]

vor 11 Stunden schrieb Simonster83:

Haven't flown much of any older campaigns expect one really good one for UH-1H (low level heaven spring campaign). Maybe I'll try to fly at a lower altitude than stated at the briefing cards, I'll see if that helps with the mission triggers. I've set the the frequencies the best I can, but still sometimes they change during mission by themselves. And usually when Foghorn is supposed to change the frequency nothing happens.

 

Can you explain what do you mean by presets? I have manually typed the frequencies for the different channels, but sometimes they don't seem to work.

 

lower altitude shouldnt make a difference concerning the triggers (cause they are not altitude bound afaik).

on my end the freqs didnt change by themselves so far and when foghorn did the input it worked - as long as i did not click stuff during his input.

As per presets:

vor 3 Stunden schrieb coldViPer:

 

There are presets for every radio which can be used to switch freqs pretty fast. But they seem to mess with triggers using freqs. If you did put the freqs in manually you did everything correct

[Florence201]

4 hours ago, coldViPer said:

For me number 6. Got directed by FAC, UG1 attacks first and kills all enemy -> no any message, only silence and endless formation flying.

Ok that helps thanks. Gives me a starting point to look into the mission. I suspect, it's the AI not fully engaging the group they are supposed to and the follow on trigger therefore not firing.

Apache presets are broken in that the param in range trigger that works for every other aircraft, does not read the Apache presets if you change frequencies that way. I have reported this a number of times to ED, but........

 

Sometimes the player will be told to change freqs, others Foghorn will do it for you (Good Crew Resource Management) and a message will appear in the top right corner telling you Foghorn is changing freqs. And yes lol, don't touch anything whilst he's doing so, as you'll actually see your MPDs and KU being used (weirdly they are the same command codes for front and back seats?!?!)

Edited August 13, 2024 by Florence201

[Simonster83]

11 hours ago, Kharrn said:

lower altitude shouldnt make a difference concerning the triggers (cause they are not altitude bound afaik).

on my end the freqs didnt change by themselves so far and when foghorn did the input it worked - as long as i did not click stuff during his input.

As per presets:

There are presets for every radio which can be used to switch freqs pretty fast. But they seem to mess with triggers using freqs. If you did put the freqs in manually you did everything correct

Thanks for your help, I also had "easy communications" checked at game settings and I swear I unchecked that earlier. That might also be the reason for funny behavior on radios. Better to make sure on every restart that it is off as instructed.

[Kharrn]

vor 10 Minuten schrieb Simonster83:

Thanks for your help, I also had "easy communications" checked at game settings and I swear I unchecked that earlier. That might also be the reason for funny behavior on radios. Better to make sure on every restart that it is off as instructed.

no problem, we are all here to learn and have phun which reminds me...i need to fly the F4 more often xD

That could indeed have messed with your comms. hope it fixes those probs!

happy hunting!

[coldViPer]

8 hours ago, Simonster83 said:

Thanks for your help, I also had "easy communications" checked at game settings and I swear I unchecked that earlier. That might also be the reason for funny behavior on radios. Better to make sure on every restart that it is off as instructed.

If you are using a new Launcher, it forces easy communication ON, at least for me. Known bug. 

[Florence201]

2 hours ago, coldViPer said:

If you are using a new Launcher, it forces easy communication ON, at least for me. Known bug. 

I did not know that!

 

Thanks for posting that tidbit of info

[Simonster83]

By turning easy communication off, everything seemed to work correctly.

[Florence201]

45 minutes ago, Simonster83 said:

By turning easy communication off, everything seemed to work correctly.

Great stuff bud thanks. Us campaign designers have lodged a "complaint" to ED about it

[Kharrn]

Am 12.8.2024 um 21:28 schrieb coldViPer:

Datalink works when you set UHF radio to preset (345.6) and put that DL square on that UHF radio.

got it, didnt know it only works for presets or if you tune to UHF in this case (COM page, preset 1, UHF (top) and TUNE -> SC (single channel) lower right). That does work but dunno if the preset will then mess again with UHF triggers (so far its good, finsihed M7).

Though in M6 is an error with the setup of the wingman (UGLY 52) cause in advanced waypoint options the EPLRS is on position 4 and somehow not checked (an error that has been there for ages within DCS concerning adv waypoint actions.....). its a sad story...

Florence is aware and will re-check it

---------

@Simonster83 good to hear! hope the rest works out! happy flying

[Athlon]

Still having problems with mission two. Completed mission and landed. Message pops up shut down or exit mission. No progression registered so have to skip to go to mission 3.  Played M2 twice now, got to say I didn't mind as I really enjoyed it.

[Florence201]

9 hours ago, Athlon said:

Still having problems with mission two. Completed mission and landed. Message pops up shut down or exit mission. No progression registered so have to skip to go to mission 3.  Played M2 twice now, got to say I didn't mind as I really enjoyed it.

Please report this direct to ED, as logbook type issues are core DCS problems and not Four Horsemen specific. There is a work around posted earlier in this thread i believe.

[normanleto]

On 8/15/2024 at 2:28 PM, Kharrn said:

got it, didnt know it only works for presets or if you tune to UHF in this case (COM page, preset 1, UHF (top) and TUNE -> SC (single channel) lower right). That does work but dunno if the preset will then mess again with UHF triggers (so far its good, finsihed M7).

Though in M6 is an error with the setup of the wingman (UGLY 52) cause in advanced waypoint options the EPLRS is on position 4 and somehow not checked (an error that has been there for ages within DCS concerning adv waypoint actions.....). its a sad story...

Florence is aware and will re-check it

---------

@Simonster83 good to hear! hope the rest works out! happy flying

Guys, how is datalink usable in SP mission? I just set radios and TSD threat circles, but datalink? I was sure it is a MP feature only in apache?

[Kharrn]

Am 18.9.2024 um 10:05 schrieb normanleto:

Guys, how is datalink usable in SP mission? I just set radios and TSD threat circles, but datalink? I was sure it is a MP feature only in apache?

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

Edited September 20, 2024 by Kharrn

[normanleto]

On 9/20/2024 at 11:39 AM, Kharrn said:

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

 

Thanks for such a great reply. I will dig in. I wonder if campaigns like "MAD" are going to support it. Would be good to know your wingman position without radar in the MAD campaign.

[Kharrn]

vor 6 Stunden schrieb normanleto:

Thanks for such a great reply. I will dig in. I wonder if campaigns like "MAD" are going to support it. Would be good to know your wingman position without radar in the MAD campaign.

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

[mdtenor22001]

Florence, thank you for an ambitious campaign. There are aspect of it that are great. But I'm having the same problem with Mission 2, completing all objectives, getting prompts, landing, getting a score, and then it isn't recorded. I know you say it is a "core DCS problem", but none of my other single player campaigns have this problem. Even the ones with lots of other bugs.  I know that ED manages to introduce bugs often. But somehow some of the campaign developers seem to deal and give us less buggy campaigns.  I'm only on the third mission now, but I'm just concerned that maybe I should hold off until some future campaign patches? Also, what's your discord so we can follow the progress of your bug fixes? All the discord links I've seen in these threads are expired.