chase

I have found that the best odds on making voip work the best is to first wait till each and everyone is first loaded and waiting in the spectator lobby before entering a plane and hitting fly. You need to wait first till all are fully loaded in and in lobby first, then all at the same time enter your aircrafts then all works. But if a few enter their ac while others are still loading into the briefing screen those guys won't be able to communicate with you. Dave.

IDK the score. I start the missions from the ME now and don't worry about the score any more. So wasn't paying attention.

@baltic_dragon Just adding a cpl bugs i found today dealing with same Miz #9. This was on the latest stable release Version # 2.9.3.51704 - The last targets, the 3 Scuds never went active, they use to fire. I still took them out and got the correct end of mission announcement though. - The other strange thing was Texico was refueling anther tanker upon Wakiki. Which you can imagine takes forever. So I just by passed it and went to the boat. I never saw this before, so I figured it's a bug. I know your going to be revamping all these missions, so I'm not expecting anything to be done quick, just figured you'd want to add this to your to do list. Thanks for these great missions and keeping them valid. You got more patients than me lol. SS Attached of the two tankers. Dave

Only stable release typically will auto update. Beta you got to do yourself. And all new things are always released on betas. Such is the DCS Way. Chase

Thank you for the test. I will try again with no mods.

So if your unable to fly the mission how did you test the spawning of the snipers?, being the helo is the same miz. Or are you simply stating your findings from earlier tests? If that is the case, what can i do to show you the problem i encounter. A video and a log file? What file(s) would help you if any? And where do i find the files. Dave

Since I was surprised by another OB this morning I went ahead and re flew the mission only to find out it's even worse now than before. Now once the Helo's emerge, my WM shoots one down, but then the other either crashes or got shot down. So now the mission won't progress passed the Helo part. I do have a video recording of this if you need it. I will need to upload it which takes time, so I'm not going to do so, unless asked. I'm hoping you can easily see what the problem is. Thanks Dave.

@baltic_dragon This seams to be a thing again. I'm running the latest OB. Same thing as usual. After the troops start moving, they stop and the snipers do not show and then radio silence. You had done a fail safe of sorts to push the story along in an earlier build, maybe that trigger is now broken? Could you possibly add an F10 menu item for us to force the mission along when this happens? It's some times random, but happens more times than not. I have this flight recorded if you want it. and I also have the DCS Log. if you think either of them will help. But you can see my screen shot above which i posted a while ago which is dealing with the same scenario. Thank you for the constant upkeep of your missions. Dave

Never mind. It was a MOD which didn't like the Dcs beta update. The mod was updated and now it's working. Just wanted to close this out in case you were testing. Thanks.

The Boat. Orig RO Miz 3 & 9 were tested. Both times i was sitting on deck and could not recieve a TCN Signal from the Carrier. I checked the ME and it's listed in there. So i don't know what could cause it. Thanks. Dave

None of the missions, well at least Miz 3 and Miz 6 which i tried have an active TCN. This is on the original Raven One Campaign. Next i tried two Miz on Raven One Dominant Fury And both of them are working properly. I'm guessing the latest Beta messed up something on your initial campaign. I did do a search for this to See if it's been reported already but came up empty. Dave.

LOL,

I understand DCS has messed with the carrier AI which creates bottleneck situations and nothing moves. In this case, Cajun starts to move forward, but due to one of the F14's waiting in line, Cajun stops there. Then Stuggo comes down to the Cat area and stops just off of Cajun's left side, then Irish comes down. resulting in nothing moving. I did however find a way to stop the F14 from damaging me, so maybe the mission dev can adopt this... I went into the ME and delayed Flip's start time by 5 minutes later. This doesn't actually make me wait the full five minutes, but it does spawn me at the rear of the ship, which no longer interferes with the F14 wings. So maybe that is something which can be fixed for future updates. Moving on to the next mission now as this one is borked lol. Dave.

Ok thank you for testing it out. I will try again soon. Dave.

@baltic_dragon I just tried the same mission today with the same Bug present. I've played this mission a bunch, so I know when things should happen. But yeah same time as the OP states, right after Venom says they are on the Move, nothing progresses..Usually at this time, is when the Infantry start firing from the Oil Drum and we have to use guns on them. Those infantry never appear. I tried again through ME, and same thing. Tracks are to big, but I attached a pic of the last few events before all came to a stop. I don't know if it's a trigger, or a DCS Bug, but wanted to let you know. Thanks. Dave.

Ok. It's Not me. It's a DCS Bug. The changes you made to these missions don't actually provide acls yet. Hopefully one day ED will fix this. If not, then the only true fix is to create a brand new Super Carrier Replacing the original ones in these missions which use case 3 recovery. Dave.

I know this has been reported, but I thought one of the last updates had fixed the issue. Either way it's still broken. ( "placing a new carrier and setting it up in an already existing mission will make the ACLS work as expected (Wag's video for reference), while a CV already placed before the update , but configured the same way will not work as intended (no mode 1 on ACLS display and no proper autopilot." ) This is especially true on any of the updated raven one campaign Mission's which use the system. These campaign missions were updated as of the last open beta, DCS 2.7.14.24228 * Added ACLS / Link 4 in mission 04, 08, 10, 11, 13. I was able to open miz 11, add my own carrier in the ME, launch the game from the ME and it worked only on the SC I added. I also tested this using an old mission of my own using the SC. I updated the old one and placed a new SC down. Only the newly created SC worked. I am attaching the track i used to test this. The track is landing on the new SC I just added. However, you can try to land on the other carrier which is also set up with a different link-4 freq, but it won't work. Hopefully this info helps. Dave. YES_ACLS.trk

Nope the mission was made with the super carrier from day one. It's still broken. The campaign dev's updated their SC to include the Link 4 and ACLS but it still don't work. I just literately just opened the miz in the ME, added my own SC next to their SC added my own freqs and only my ship worked. I tried approaches on both and only mine worked. So this is an ongoing bug

I believe the post you quoted was prior to the dcs patch which should of fixed this issue. Are you still finding this to be true? That being "A CV already placed before the update , but configured the same way will not work as intended (no mode 1 on ACLS display and no proper autopilot." Cause i especially find this still to be true with the Raven One Campaign Dave

Okay, I watched my own video. One thing I noticed is I didn't turn on the actual ILS. As in the ILS Button on the FCU. I verified in the video that all other systems were on, but I did not check the ILS nor do I remember turning it on. So I guess that was actually still in the off mode. I didn't think to turn it on, when the ALS boxes both TCN & ILS boxes and the ILS Cross hairs are visible. So I assumed the system was operating correctly. So maybe the ILS has to also be turned on in order for the ALS to give the tadpole symbol? Wags does indeed turn on his ILS System, so that's likely the issue I'm having.

I have yet to be able to get the ACLS to lock on. I have never seen the tadpole. I do start these missions from the ME screen, maybe that is the cause? Is anyone else having trouble with autolanding? It even says ACLS Lockon by ATC, but nope. Am I doing something wrong? It should just work right? Everything was on, TCN, BCN, DL, ILS, everything. Here is a twitch recording. A track would be to big of a file. Jump to time: 1hr 31 minutes 30 seconds for my first attempt. This is the time where ATC says ACLS lockon, but no actual lockon. I go around and try again, but again no luck. Any help with this would be appreciated. 00:15:45 kneeboard carrier info 1:31:30 in No ACLS https://www.twitch.tv/videos/1308804396

Yep. That was it. Thank you

Has a global setting or option change over the last cpl beta builds which would prevent units from being visible on the F10 map upon starting the mission?. The only way i can see targets is to force a ground battle: then they show up and i can click on them and change my view using F7 keys etc... it's like a fog of war setting is on permanently or something. I have not changed any of my settings. Thanks for any clarification on this issue. Dave.

That should do the trick. Thank you for the help. Dave.

@NineLine I'm not sure if having other F18 groups/ units in the mission Makes any difference. i took one of my missions deleted all groups of F18's. So only my Hornet remained. I took my original SC, Lincoln i think, where i had the tcn and ILS set. I added both link 4 and ACLS. And still no ACLS lock on. So my working theory is if you use a carrier from any prior mission it won't work, which would also explain the campaigns. So maybe you have to make a new carrier using the latest beta in order for it to work. Anyway you should be able to see this from my track. Never mind, the track is larger than 5 megs. Won't allow upload. I tried. Thanks for the reply. I'll look out for the next update to try again. The night crew lighting effects Are awesome so thanks for that. : ). Dave