CH4Pz Posted July 25, 2023 Posted July 25, 2023 On 7/23/2023 at 11:59 PM, g2k said: Are you sure it was only a week ago? I don't believe I have any mods installed. Certainly not Voice attack. Oddly it worked not long ago (unsure how far back). Hopefully someone else will chime on their experience in M10. Note: I just seen this morning on BD FB page there is upcoming changelog on this mission in regard to Sluggo attacking the SAMS Yep, it was recently, still during last patch, have you tried today with the update? any luck?
g2k Posted July 25, 2023 Posted July 25, 2023 (edited) 2 hours ago, CH4Pz said: Yep, it was recently, still during last patch, have you tried today with the update? any luck? After the patch I eagerly tried the mission. The dialogue is still missing from the Cutlass flight, but Sluggo still flies through the motions anyway to head towards the the SA-6's. Designer notes indicate if Sluggo states he is shooting first, Flip needs to wait, then fire. The dialogue from Sluggo indicating he's fired on the north SAM is still missing, but he actually fired on it this time! So I fired on the south SAM (no post missile launch dialogue from Flip that he actually fired either) and my South SAM somehow detonated on it's own before my missile arrived. So I didn't score points there, but Sluggo did on his North SA-6. So we press on to the HATBOX's. Typically there is some dialogue about the Migs at Luke (enemy airbase) on the way to HATBOX, but no dialogue. Sluggo does normal dialogue when he banks into HATBOX. He smashes his SAM and I smash the SA-3. Good times! We press to Luke to attack the launching of Migs. In the past when not nailing all SAMS the MIGS stayed in the hangar, so I was a bit pessimistic that this mission would keep rolling, but low and behold the Migs were launching! I nailed 3 and Sluggo nailed 1 for the fullhouse! Good times! Scored 80 points. Likely because the south SA-6 exploded before my missile even arrived. I don't know if these ongoing "broke mission" issues are my computer or the mission itself. You mentioned add-ons that might be causing my problems. Not sure what you meant. I had the open kneeboard add-on (that i could never figure out) so I removed that prior to flying. I have Skatezilla (which I also don't know how to use), so perhaps I should remove that too? I'm not using it anyway. Really hoping someone else flys the mission and posts their feedback. Thanks for your efforts trying to help me. It's a great mission when everything is working. Edited July 25, 2023 by g2k (I just jotted this hardware info down so younger smarter people can help me troubleshoot possible flaws) i7 9700K 3.7Ghz | ROG Strix RTX2080S GeForce RTX 3080 | Corsair Vengeance RGB Pro 64GB | WD 1TB-SSD | Corsair RGB 280mm Liquid CPU cooler | Asus TUF Z390-Plus w/DDR4 2666 TM Warthog HOTAS | MFG Crosswinds | HP Reverb G2
CH4Pz Posted July 26, 2023 Posted July 26, 2023 19 hours ago, g2k said: After the patch I eagerly tried the mission. The dialogue is still missing from the Cutlass flight, but Sluggo still flies through the motions anyway to head towards the the SA-6's. Designer notes indicate if Sluggo states he is shooting first, Flip needs to wait, then fire. The dialogue from Sluggo indicating he's fired on the north SAM is still missing, but he actually fired on it this time! So I fired on the south SAM (no post missile launch dialogue from Flip that he actually fired either) and my South SAM somehow detonated on it's own before my missile arrived. So I didn't score points there, but Sluggo did on his North SA-6. So we press on to the HATBOX's. Typically there is some dialogue about the Migs at Luke (enemy airbase) on the way to HATBOX, but no dialogue. Sluggo does normal dialogue when he banks into HATBOX. He smashes his SAM and I smash the SA-3. Good times! We press to Luke to attack the launching of Migs. In the past when not nailing all SAMS the MIGS stayed in the hangar, so I was a bit pessimistic that this mission would keep rolling, but low and behold the Migs were launching! I nailed 3 and Sluggo nailed 1 for the fullhouse! Good times! Scored 80 points. Likely because the south SA-6 exploded before my missile even arrived. I don't know if these ongoing "broke mission" issues are my computer or the mission itself. You mentioned add-ons that might be causing my problems. Not sure what you meant. I had the open kneeboard add-on (that i could never figure out) so I removed that prior to flying. I have Skatezilla (which I also don't know how to use), so perhaps I should remove that too? I'm not using it anyway. Really hoping someone else flys the mission and posts their feedback. Thanks for your efforts trying to help me. It's a great mission when everything is working. Glad u got it (mostly) sorted !! ..Im not sure what Skatezilla is, but i would definitely try it without it, especially if you dont even use it, the golden rule with all campaigns is no mods, or 3rd party apps. The kneeboard is fine, as thats Vanilla DCS.
Yurgon Posted July 26, 2023 Posted July 26, 2023 2 hours ago, CH4Pz said: Im not sure what Skatezilla is, but i would definitely try it without it I'm also unsure what this refers to in this particular case. Anyway, SkateZilla is a forum member who provides a bunch of really useful tools for the community, and I doubt any of these tools would have an effect on the campaign. But I agree, when tools aren't even used, I'd also opt to simply remove them.
baltic_dragon Posted August 7, 2023 Author Posted August 7, 2023 Hey guys. Sorry I've been quiet, I am away from my gaming rig for almost two months, so there is only so much I'll be able to do to fix bugs / check things until September. Last time I flew M11 (a patch ago) it worked fine for me. The problem I am seeing more often, that there are bugs that some people experience but don't exist for other users, based on the strength of the machine they have (more bugs are apparent on older PCs), whether they fly the MT version or not, if they have 3rd party mods installed etc. Which makes the troubleshooting extremely difficult. In any case, I'll have to look into all the Raven One and Raven One Dominant Fury missions because of some cool upcoming DCS features which will heavily affect both campaigns, so I'll be busy with that in the next month or two, trying to fix any bugs along the way. 3 For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
g2k Posted August 13, 2023 Posted August 13, 2023 Understood BD. Thanks for touching base. Looking forward to these features and how they will enhance the campaigns! (I just jotted this hardware info down so younger smarter people can help me troubleshoot possible flaws) i7 9700K 3.7Ghz | ROG Strix RTX2080S GeForce RTX 3080 | Corsair Vengeance RGB Pro 64GB | WD 1TB-SSD | Corsair RGB 280mm Liquid CPU cooler | Asus TUF Z390-Plus w/DDR4 2666 TM Warthog HOTAS | MFG Crosswinds | HP Reverb G2
finnish3r Posted September 3, 2023 Posted September 3, 2023 I'm also having issues with M10. We engage the SA6s successfully with Sluggo and then turn towards LUKE. Sluggo calls the HAT BOX and engages with two HARMs. Then he just casually flies over LUKE through AAA fire and heads west, no comms. At some point he decides to head for the Tartus SA3, but apparently it's not active and he then just turns towards the boat. I'm running MT 2.8.8.43704 and my only mod is VAICOM. Tacview attached. Tacview-20230903-185855-DCS-RODF M10.zip.acmi 1
g2k Posted September 8, 2023 Posted September 8, 2023 On 9/3/2023 at 11:57 AM, finnish3r said: I'm also having issues with M10. We engage the SA6s successfully with Sluggo and then turn towards LUKE. Sluggo calls the HAT BOX and engages with two HARMs. Then he just casually flies over LUKE through AAA fire and heads west, no comms. At some point he decides to head for the Tartus SA3, but apparently it's not active and he then just turns towards the boat. I'm running MT 2.8.8.43704 and my only mod is VAICOM. Tacview attached. Tacview-20230903-185855-DCS-RODF M10.zip.acmi 15.01 MB · 0 downloads Thanks for the update. I was concerned it was just me. Also, when I fire my HARM at the south SA-6, it explodes a micro-second before my HARM reaches it and I don't score the kill. Every time this happens. I score kills half the time on Hatbox. (I just jotted this hardware info down so younger smarter people can help me troubleshoot possible flaws) i7 9700K 3.7Ghz | ROG Strix RTX2080S GeForce RTX 3080 | Corsair Vengeance RGB Pro 64GB | WD 1TB-SSD | Corsair RGB 280mm Liquid CPU cooler | Asus TUF Z390-Plus w/DDR4 2666 TM Warthog HOTAS | MFG Crosswinds | HP Reverb G2
lowki Posted September 15, 2023 Posted September 15, 2023 On 9/3/2023 at 7:57 PM, finnish3r said: I'm also having issues with M10. We engage the SA6s successfully with Sluggo and then turn towards LUKE. Sluggo calls the HAT BOX and engages with two HARMs. Then he just casually flies over LUKE through AAA fire and heads west, no comms. At some point he decides to head for the Tartus SA3, but apparently it's not active and he then just turns towards the boat. I'm running MT 2.8.8.43704 and my only mod is VAICOM. Tacview attached. Tacview-20230903-185855-DCS-RODF M10.zip.acmi 15.01 MB · 0 downloads I'm experiencing the exact same issue. Were you able to get it through somehow?
5EVC Tiger Posted September 19, 2023 Posted September 19, 2023 Just "completed" mission 10. Same problem describe above and here : After 2nd attack Sluggo just leaves and RTP and nothing else happens. I have a recorded DCS & TacView track if needed. OS: Windows 10 64-bit | CPU: Intel i7-7700K @4.2GHz | GPU: EVGA GeForce GTX 1080 Ti Founders 11GB | RAM: G-Skill 16GB (2x8GB) DDR4/3600MHz | SSD: 480gb Corsair HyperX | MoBo: EVGA Z270 Stinger | Oculus Rift | HOTAS Warthog
Fresh Posted September 25, 2023 Posted September 25, 2023 (edited) Hello Baltic Dragon, I just finished mission 1, loved it! Looking forward to the next missions. Just wanted to report the comms are wrong, telling me the FB is 211 then 210. The actual FB is more like 199 or 200. I checked the LSO monitor and saw the BRC was 209. Cajun almost killed me when Texaco spawned and he turned suddenly to intercept.. I saw the warning in the briefing, but thought that happened just as we are about to connect. Just to share the experience. Thanks! Edited September 25, 2023 by Fresh
baltic_dragon Posted September 26, 2023 Author Posted September 26, 2023 On 9/3/2023 at 7:57 PM, finnish3r said: I'm also having issues with M10. We engage the SA6s successfully with Sluggo and then turn towards LUKE. Sluggo calls the HAT BOX and engages with two HARMs. Then he just casually flies over LUKE through AAA fire and heads west, no comms. At some point he decides to head for the Tartus SA3, but apparently it's not active and he then just turns towards the boat. I'm running MT 2.8.8.43704 and my only mod is VAICOM. Tacview attached. Tacview-20230903-185855-DCS-RODF M10.zip.acmi 15.01 MB · 1 download Thanks. I'll have a proper look at this mission when I start overhauling whole campaign for taxi directors and adding some cool extra features (check video below). I did try it twice and it worked OK for me and VAICOM is known to (for some unknown reason) mess the DLC campaigns and create bugs with AI behaviour others cannot recreate. Still, I'll try to get to bottom of this, but most likely not before full campaign redo which I hope to have finished by November. 11 hours ago, Fresh said: Hello Baltic Dragon, I just finished mission 1, loved it! Looking forward to the next missions. Just wanted to report the comms are wrong, telling me the FB is 211 then 210. The actual FB is more like 199 or 200. I checked the LSO monitor and saw the BRC was 209. Cajun almost killed me when Texaco spawned and he turned suddenly to intercept.. I saw the warning in the briefing, but thought that happened just as we are about to connect. Just to share the experience. Thanks! The BRC will be something that is dynamically changing during the recovery. I will have a look at it but I might not be able to fix it (I had to use several tricks to make this mission interesting that limit my options). In any case that is not a huge thing. The Texaco and Cajun turning.. yeah, that's the AI being AI. Not much I can do about it. 1 For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
Fresh Posted September 27, 2023 Posted September 27, 2023 (edited) Now finished mission 2, have some remarks (caution: spoiler alert!): Spoiler I used the ADF homing to find the boat, but I guess you placed the transmitter in an oil rig? Is that a workaround/trick you needed to do, or unintentional? (Found the boat eventually nice story thereafter..) According to the readme we shouldn't use the in-game comms.. but after I pressed spacebar to contact marshall, nothing happened.. so I did use in-game comms to recover. Is that per design, or did I mess something up? (I did say I found the boat too early, and also said I needed to refuel, but it was only to get Claire to talk more Edited September 27, 2023 by Fresh
baltic_dragon Posted September 27, 2023 Author Posted September 27, 2023 You shouldn't use in-game comms for AWACS and wingmen, the Marshal works normally apart from M01 which is completely custom - built, the rest uses normal supercarrier comms. Maybe I need to update the readme to be more specific on that as for the ADF.. I didn't use ADF in any of the missions, I honestly forgot it was even implemented in the Hornet. So not sure what happened there! For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
finnish3r Posted September 28, 2023 Posted September 28, 2023 On 9/26/2023 at 12:38 PM, baltic_dragon said: Thanks. I'll have a proper look at this mission when I start overhauling whole campaign for taxi directors and adding some cool extra features (check video below). I did try it twice and it worked OK for me and VAICOM is known to (for some unknown reason) mess the DLC campaigns and create bugs with AI behaviour others cannot recreate. Still, I'll try to get to bottom of this, but most likely not before full campaign redo which I hope to have finished by November. Thanks for the reply baltic_dragon! Just to clarify, am I supposed to engage the HOT BOX after Sluggo fires the HARMs? Also, since Vaicom is not really needed for these campaigns, is it sufficient to just not run it to see if that fixes things or does Vaicom has its roots deeper in DCS configs that might cause the bugs?
baltic_dragon Posted September 29, 2023 Author Posted September 29, 2023 Yes, AFAIR you have to wait for Sluggo to shoot first. As for the external software I don’t really know, should be enought to not load / run it, but this is something that is really difficult to put one’s finger on. For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
MAXsenna Posted September 29, 2023 Posted September 29, 2023 Thanks for the reply baltic_dragon! Just to clarify, am I supposed to engage the HOT BOX after Sluggo fires the HARMs? Also, since Vaicom is not really needed for these campaigns, is it sufficient to just not run it to see if that fixes things or does Vaicom has its roots deeper in DCS configs that might cause the bugs?If VoiceAttack is started before you started DCS, and closed again after closing DCS, it should clean out all settings. But sometimes things gets out of sync. So to be completely sure. Close DCS and VoiceAttack. Do a full repair of DCS, and then play the campaign without starting VoiceAttack. That said, I've never had issues with VAICOM in any campaign, while other mods have done peculiar things.Cheers! Sent from my MAR-LX1A using Tapatalk 1
FPS_Sage Posted November 29, 2023 Posted November 29, 2023 Just played Mission 09 today. Looks like there is a bug during mission start where one of the F14's (Spartan 1-1, DCAG I think it was?) taxis right into the tail of the E2 (Knight?) when it is on the catapult, destroying them both. I just downloaded the stable 2.9.1.48335 update on Steam today. Thing is, when I was trying this mission yesterday, and still on some version of 2.8 I suppose, I don't think that collision happened. Nevertheless, I don't think this majorly impacted the rest of the mission. The voiceovers from DCAG still occurred, and I don't think Tomcats actually did anything in this mission, anyway. Also, I feel like some triggers didn't work as intended towards the end of mission. There were absolutely no comms from Raven 33 after reaching WP7/Waikiki on the return. I just pressed on and landed anyway, but I think something was missing there. Maybe that's partially because it took me a super long time to find the TELs, and according to some other threads, you have to find them quickly to progress the mission fully. So that might have broken some of the later triggers, I suppose.
baltic_dragon Posted November 30, 2023 Author Posted November 30, 2023 You likely won't make the campaign to work on Stable build. The DCS is so fluent that the best option is to use Open Beta for the campaigns... And if you get stuck with a bug (which is very likely because Stable release is not chosen based on campaign stability) then you're stuck with it for very long time... 1 For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
FPS_Sage Posted November 30, 2023 Posted November 30, 2023 Interesting, I will try the open beta version from now on, thanks for the tip 1
MrPresident Posted December 6, 2023 Posted December 6, 2023 On 11/29/2023 at 10:07 PM, FPS_Sage said: Just played Mission 09 today. Looks like there is a bug during mission start where one of the F14's (Spartan 1-1, DCAG I think it was?) taxis right into the tail of the E2 (Knight?) when it is on the catapult, destroying them both. I just downloaded the stable 2.9.1.48335 update on Steam today. Thing is, when I was trying this mission yesterday, and still on some version of 2.8 I suppose, I don't think that collision happened. Nevertheless, I don't think this majorly impacted the rest of the mission. The voiceovers from DCAG still occurred, and I don't think Tomcats actually did anything in this mission, anyway. Also, I feel like some triggers didn't work as intended towards the end of mission. There were absolutely no comms from Raven 33 after reaching WP7/Waikiki on the return. I just pressed on and landed anyway, but I think something was missing there. Maybe that's partially because it took me a super long time to find the TELs, and according to some other threads, you have to find them quickly to progress the mission fully. So that might have broken some of the later triggers, I suppose. I have the same issue. When I last played this campaign about 3 months ago this did not happen. I am playing on the open beta branch.
baltic_dragon Posted December 8, 2023 Author Posted December 8, 2023 Hey, I'll try to fix M09 for next OB patch. Already got problems with M10 solved and huge M14 should be working like charm after next patch. 1 For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
CH4Pz Posted December 10, 2023 Posted December 10, 2023 On 12/9/2023 at 7:34 AM, baltic_dragon said: Hey, I'll try to fix M09 for next OB patch. Already got problems with M10 solved and huge M14 should be working like charm after next patch. Make Campaigns they said.... It'll be FUN they said...
baltic_dragon Posted December 10, 2023 Author Posted December 10, 2023 Yeah.. just fixed M09, there indeed was a problem. For more information, please visit my website. If you want to reach me with a bug report, feedback or a question, it is best to do this via my Discord channel. Details about the WinWing draw can be found here. Also, please consider following my channel on Facebook.
FPS_Sage Posted December 10, 2023 Posted December 10, 2023 This may be a very dumb question, but how do I access the 'skip ahead' feature in the F10 menu for missions 14 & 15? I try the normal comms menu and don't see any F10 options for this. Asking because I ran into the issue with M14 where Olive wouldn't take off (sounds like that's already being looked into), so I skipped that entire mission on the campaign menu but am wondering if the mission itself works if skipping ahead to somewhere after launch. On M15, I got shot down by a SAM on the ingress, and would prefer to skip ahead at least after the AAR to try the ingress/strike again, just to save the long transit time.
Recommended Posts