Sandman Simulations Posted January 15 Author Posted January 15 34 minutes ago, draconus said: It was 2h for me with my 2 AARs. I take my time on those And that's not a problem at all. Just balancing as even 90 minutes CAP duty is too much for part of players. In real life there might be AAR also before return to the carrier and much more waiting.
draconus Posted January 21 Posted January 21 (edited) #5 - all good but the message "Contact Overlord on button 3" was there up until around WP2. I didn't make it to the carrier though, so embarrassing... Edited January 21 by draconus Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Sandman Simulations Posted January 21 Author Posted January 21 5 hours ago, draconus said: #5 - all good but the message "Contact Overlord on button 3" was there up until around WP2. I didn't make it to the carrier though, so embarrassing... Message should disappear when pressing spacebar. I'll check.
Sandman Simulations Posted January 21 Author Posted January 21 9 hours ago, draconus said: #5 - all good but the message "Contact Overlord on button 3" was there up until around WP2. I didn't make it to the carrier though, so embarrassing... Checked and the instruction message is set to be there for 1000 seconds or until player calls Overlord by pressing spacebar whichever comes first. Worked fine in my test. I don't know why it happens to you as you already reported that you had same kind of problem in mission 6 with contact approach message.
draconus Posted January 21 Posted January 21 Took the #5 second time. No problem with message this time. Still the crew stopped me in the middle of the deck after landing. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Sandman Simulations Posted January 21 Author Posted January 21 11 minutes ago, draconus said: Took the #5 second time. No problem with message this time. Still the crew stopped me in the middle of the deck after landing. Maybe bacause of statics. I think they want you to shut down there and they will get your bird to the elevator.
draconus Posted January 29 Posted January 29 #10: I made a mistake and have sent wingman to refuel too (but I know it's bugged atm, so is the tanker orbit unstable). The strike package have done its job and egressed so all fine but I got no RTB message. So I landed, got the music, all fine I guess. When approaching WP2 Jester says something short (can't remember) but there's no VO for it. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Sandman Simulations Posted January 29 Author Posted January 29 1 hour ago, draconus said: #10: I made a mistake and have sent wingman to refuel too (but I know it's bugged atm, so is the tanker orbit unstable). The strike package have done its job and egressed so all fine but I got no RTB message. So I landed, got the music, all fine I guess. When approaching WP2 Jester says something short (can't remember) but there's no VO for it. Yes ED has the AAR problem under work. Did you get the conversation about enemy AWACS after strike package had done their job?
draconus Posted January 30 Posted January 30 7 hours ago, Sandman Simulations said: Did you get the conversation about enemy AWACS after strike package had done their job? Yes, and I have choosen to stay with the pack (remember the wingman was still on the hose) as a more realistic approach. The other option disappeared then. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Sandman Simulations Posted January 30 Author Posted January 30 (edited) 2 hours ago, draconus said: Yes, and I have choosen to stay with the pack (remember the wingman was still on the hose) as a more realistic approach. The other option disappeared then. Great. Then you missed only the contact app call. I'll check why as it shouldn't depend on wingman being around. Edited January 30 by Sandman Simulations
draconus Posted January 31 Posted January 31 #12: I was about to join up with the tanker when whole pack started ingress, so I felt kinda left behind, but ok, let me do my job - maybe I flew too close to WP2 atm? I heard some action was there on my way (some messages without VO, either because of radio distance or because I was still on buttons 14 and 13, for tanker, not 1) and was still pretty far away when I got new tasking. Took some time to find the aircraft but had to run after it quite a distance so I shot whenever I could without going close - did I miss some visual ID dialogs? Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Sandman Simulations Posted January 31 Author Posted January 31 2 hours ago, draconus said: #12: I was about to join up with the tanker when whole pack started ingress, so I felt kinda left behind, but ok, let me do my job - maybe I flew too close to WP2 atm? I heard some action was there on my way (some messages without VO, either because of radio distance or because I was still on buttons 14 and 13, for tanker, not 1) and was still pretty far away when I got new tasking. Took some time to find the aircraft but had to run after it quite a distance so I shot whenever I could without going close - did I miss some visual ID dialogs? Strike package will push when bombers are ready. Now that you mentioned it the exact push time is not given in the briefing. That could be an improvement I should do. You are supposed to visually identify the aircraft so you missed some VOs if not close enough.
EvoMayhem Posted February 4 Posted February 4 (edited) Not sure if this is a bug or not, but I just recently started this campaign, and once I’m in the air in mission 1, I’m of course instructed to contact the boat on button 5 for clearance. Doesn’t matter which radio I use, if I tune it manually or not, I get zero reply from the carrier when declaring inbound. Is there a set time I have to wait for any reply? Additonally, this doesn’t happen on other missions, such as instant action, etc. Edited February 4 by EvoMayhem
Sandman Simulations Posted February 4 Author Posted February 4 3 hours ago, EvoMayhem said: Not sure if this is a bug or not, but I just recently started this campaign, and once I’m in the air in mission 1, I’m of course instructed to contact the boat on button 5 for clearance. Doesn’t matter which radio I use, if I tune it manually or not, I get zero reply from the carrier when declaring inbound. Is there a set time I have to wait for any reply? Additonally, this doesn’t happen on other missions, such as instant action, etc. Hi, Thank you for your message. As it's DCS stock carrier atc there is no way I could set any timer. Is the frequency right behind the button 5? I have no idea why it would have changed but everything is possible. I'll check the mission.
EvoMayhem Posted February 5 Posted February 5 14 hours ago, Sandman Simulations said: Hi, Thank you for your message. As it's DCS stock carrier atc there is no way I could set any timer. Is the frequency right behind the button 5? I have no idea why it would have changed but everything is possible. I'll check the mission. Didn’t think you could, but I really wasn’t too sure. I’m not sure what you mean by the frequency being behind the button? I did get Jester to tune 255 manually, and it didn’t make any difference though. i did notice that the carrier deck crew didn’t act like the update, as in needing to salute for startup, follow crew instructions for hooking up to the catapult, etc. Not sure if that makes any difference. I’ve done a full repair of DCS as well. Only thing left to do in my mind, is remove the campaign and reinstall it.
Sandman Simulations Posted February 5 Author Posted February 5 (edited) 6 hours ago, EvoMayhem said: Didn’t think you could, but I really wasn’t too sure. I’m not sure what you mean by the frequency being behind the button? I did get Jester to tune 255 manually, and it didn’t make any difference though. i did notice that the carrier deck crew didn’t act like the update, as in needing to salute for startup, follow crew instructions for hooking up to the catapult, etc. Not sure if that makes any difference. I’ve done a full repair of DCS as well. Only thing left to do in my mind, is remove the campaign and reinstall it. Hi, You can check the frequency with the switch right side of you front radio. Anyway I checked and frequencies for both radios seems to be right. Also for the carrier. I tested the mission with easy communication on and off but wasn't able to replicate the problem. ATC replied normally. Have you already played mission 2 or other missions of this campaign. If yes was the problem there too? I think you already have but if not check you have the right key binding for mic button for both radios. You need to use both as you are giving orders for wingman with channel 1 and other communication with ATC, tanker and AWACS on other channels. The taxi director is forced off for the mission one. As you should taxi right back to the cat after landing I found that the director is not yet capable for that. It changes with every update so maybe some day it will work also with this mission. Edited February 5 by Sandman Simulations
draconus Posted February 5 Posted February 5 @EvoMayhem Make sure you turn the front radio on, set to channel 5, check the volume is up, call mother (CVN-71) inbound by using AN/ARC-159 MIC button when you're advised to by the mission message. If that doesn't work check DCS audio devices, volumes and remove mods if you have any. Run DCS clean and repair. Make sure you have easy comms off in the DCS options. @Sandman Simulations In M1 I got first message at 10nm that I should contact departure on button 2 and that I should climb 3k at 7nm and turn left to reach the pattern Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Sandman Simulations Posted February 5 Author Posted February 5 (edited) 1 hour ago, draconus said: In M1 I got first message at 10nm that I should contact departure on button 2 and that I should climb 3k at 7nm and turn left to reach the pattern Hi, Thank you for your radio instructions. In mission 1 the "Contact departure..." message is triggered when player altitude is more than 100m (about 330ft, no idea why it has to be set in meters in the ME). There is no other conditions to be met so I can't find any other solution for late activation but flying below that altitude. Edited February 5 by Sandman Simulations
EvoMayhem Posted February 5 Posted February 5 (edited) 5 hours ago, Sandman Simulations said: Hi, You can check the frequency with the switch right side of you front radio. Anyway I checked and frequencies for both radios seems to be right. Also for the carrier. I tested the mission with easy communication on and off but wasn't able to replicate the problem. ATC replied normally. Have you already played mission 2 or other missions of this campaign. If yes was the problem there too? I think you already have but if not check you have the right key binding for mic button for both radios. You need to use both as you are giving orders for wingman with channel 1 and other communication with ATC, tanker and AWACS on other channels. The taxi director is forced off for the mission one. As you should taxi right back to the cat after landing I found that the director is not yet capable for that. It changes with every update so maybe some day it will work also with this mission. So, I removed and then reinstalled the campaign. Tried again, using the menu, and nothing. Then I decided to try saying it through Vouce Attack, as opposed to selecting through the comms menu. It worked. Why only spoken works, I don’t know, but great. Then after my third cat launch, DCS crashed. FML. @draconusI doublechecked all radio settings for both radios, had tried button 5 for both, and I also had zero issues with comms to anything else. Just requesting landing. Anyway, as above, it seemed to work speaking it as opposed to selecting it through a menu. God knows why. But thank you. Edited February 5 by EvoMayhem 1
draconus Posted February 5 Posted February 5 7 hours ago, Sandman Simulations said: In mission 1 the "Contact departure..." message is triggered when player altitude is more than 100m (about 330ft, no idea why it has to be set in meters in the ME). Thx, that must be it. The usual requirement was to fly below 500ft so I did but it did't always mean flying exactly 500ft. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Sandman Simulations Posted February 6 Author Posted February 6 (edited) 20 hours ago, draconus said: Thx, that must be it. The usual requirement was to fly below 500ft so I did but it did't always mean flying exactly 500ft. I think the exact wording in the NATOPS is "maintain 500 feet altitude until 7 nautical miles (NM) from the carrier". Anyway there is a chance to miss the trigger. There was some good reason why it's not triggered by speed but just can't remember what it was. Edited February 6 by Sandman Simulations 1
draconus Posted February 18 Posted February 18 On 1/31/2025 at 12:09 PM, Sandman Simulations said: You are supposed to visually identify the aircraft so you missed some VOs if not close enough. Boy, I'm glad I flew the mission again. It turned out I missed whole alternative plot! 2 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Sandman Simulations Posted February 18 Author Posted February 18 3 hours ago, draconus said: Boy, I'm glad I flew the mission again. It turned out I missed whole alternative plot! Great to hear you tried it again
draconus Posted February 26 Posted February 26 On 2/18/2025 at 1:19 PM, Sandman Simulations said: Great to hear you tried it again Forgot to mention - the voice over for Yak aircraft says [Jack] instead of [Yuck] but I know it's minor and you probably wouldn't want to rerecord the file again Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Sandman Simulations Posted February 26 Author Posted February 26 59 minutes ago, draconus said: Forgot to mention - the voice over for Yak aircraft says [Jack] instead of [Yuck] but I know it's minor and you probably wouldn't want to rerecord the file again Thanks. Didn't notisce that. Maybe if there will be some other vo-updates.
Recommended Posts