Jump to content

Recommended Posts

Posted
12 hours ago, TimSell75 said:

Just tried mission 4 a couple of times. Some problems I faced:

- The SA2 site was never attacked. In the mission briefing it was said it would be attacked by Tomahawks, but this never happens. It is always active.

- The F-14s don´t really protect the strike. They turn back to the carrier immediately after they attacked the first wave of scrambled jets and let the strike planes cope with all the other bandits that sramble afterwards leaving UZI flight in a knife fight with F-5s and F-4s.

This is actually how it's supposed to go in the mission.  Things don't always go to plan.  😉

Posted
vor 2 Stunden schrieb Sedlo:

This is actually how it's supposed to go in the mission.  Things don't always go to plan.  😉

Ok, it’s not a bug, it’s a feature 😉

  • Like 1

🖥️ CPU: i9-14900K, RAM: 64GB DDR4 3200, GPU: RTX5090 32GB, HD: M2 PCIe 2TB   🥽 Pimax Crystal Super  🕹️ Thrustmaster Warthog HOTAS, Thrustmaster TPR Rudders

Posted
7 hours ago, TimSell75 said:

Ok, it’s not a bug, it’s a feature 😉

Haha!  Feature-bug 😉

7 hours ago, TimSell75 said:

Ok, it’s not a bug, it’s a feature 😉

I spent countless hours and lots of grey hair trying to get the deck crew to work with these missions well featuring is somewhat realistic, looking aircraft carrier deck.

Pretty sure mission three was working fine in an earlier build, something must’ve changed in a subsequent one.

Pretty much at the point where I’m just going to delete all the static on the carriers because I don’t know what’s better, working deck, crew or realistic looking carrier decks.  

 

Posted
vor 1 Stunde schrieb Sedlo:

Haha!  Feature-bug 😉

I spent countless hours and lots of grey hair trying to get the deck crew to work with these missions well featuring is somewhat realistic, looking aircraft carrier deck.

Pretty sure mission three was working fine in an earlier build, something must’ve changed in a subsequent one.

Pretty much at the point where I’m just going to delete all the static on the carriers because I don’t know what’s better, working deck, crew or realistic looking carrier decks.  

 

Yeah the problem is now, that you can´t rely on player intelligence to choose the cat, it is being defined by the AI. And the AI is just not seeing statics and ignores them. I think ED will have to work on it, otherwise you have to clear the deck on pretty much all statics that might interfere with cats and the ways to them.

🖥️ CPU: i9-14900K, RAM: 64GB DDR4 3200, GPU: RTX5090 32GB, HD: M2 PCIe 2TB   🥽 Pimax Crystal Super  🕹️ Thrustmaster Warthog HOTAS, Thrustmaster TPR Rudders

Posted

The rest should be good, I think I just missed that mission.  
 

All aircraft spawns have a single, predetermined cat.   You can put a static in those particular spots to prevent a cat use.  For example, blocking the slot in front of forward starboard elevator can prevent cat 1 yo be used.   
 

I missed it in that previous mission. 😉

Posted
vor 10 Stunden schrieb Sedlo:

The rest should be good, I think I just missed that mission.  
 

All aircraft spawns have a single, predetermined cat.   You can put a static in those particular spots to prevent a cat use.  For example, blocking the slot in front of forward starboard elevator can prevent cat 1 yo be used.   
 

I missed it in that previous mission. 😉

Cool, is there some documentation about this or is it try and error?

🖥️ CPU: i9-14900K, RAM: 64GB DDR4 3200, GPU: RTX5090 32GB, HD: M2 PCIe 2TB   🥽 Pimax Crystal Super  🕹️ Thrustmaster Warthog HOTAS, Thrustmaster TPR Rudders

Posted
Am 14.12.2024 um 09:40 schrieb Sedlo:

This is what I was using: 

IMG_0282.jpeg

Cool. thanks a lot!

🖥️ CPU: i9-14900K, RAM: 64GB DDR4 3200, GPU: RTX5090 32GB, HD: M2 PCIe 2TB   🥽 Pimax Crystal Super  🕹️ Thrustmaster Warthog HOTAS, Thrustmaster TPR Rudders

Posted

Small Bug recognized in Mission 8: TACAN commad was not set at the carrier, so no carrier TACAN in this mission. Making it a bit difficult to find in a sand storm 😉

  • Like 1

🖥️ CPU: i9-14900K, RAM: 64GB DDR4 3200, GPU: RTX5090 32GB, HD: M2 PCIe 2TB   🥽 Pimax Crystal Super  🕹️ Thrustmaster Warthog HOTAS, Thrustmaster TPR Rudders

Posted
vor 4 Stunden schrieb Sedlo:

@TimSell75made the fix, v 2024-12-20 now available.  Thanks!

 

https://www.digitalcombatsimulator.com/en/files/3326679/

Great! I actually managed to find the carrier without Tacan, so already moved on in the campaign 😉

Is there some kind of donation link? The campaign is easily on par with the best paid ones.

🖥️ CPU: i9-14900K, RAM: 64GB DDR4 3200, GPU: RTX5090 32GB, HD: M2 PCIe 2TB   🥽 Pimax Crystal Super  🕹️ Thrustmaster Warthog HOTAS, Thrustmaster TPR Rudders

Posted

Is it possible that there is no carrier in Mission 12 Cold start? When I start, I am in the air and immediately crash. I also can not see a carrier in the mission editor.in contrast to the hot start version.

🖥️ CPU: i9-14900K, RAM: 64GB DDR4 3200, GPU: RTX5090 32GB, HD: M2 PCIe 2TB   🥽 Pimax Crystal Super  🕹️ Thrustmaster Warthog HOTAS, Thrustmaster TPR Rudders

Posted

Great campaign- just finished it. I also ran into the missing carrier issue on M12, but I renamed the the 'start from push' version of the mission so that it would fire in the campaign and I could progress. That'll work as a stopgap until the cold start version is fixed. 

It looks like this was meant to be released as a paid campaign- it's definitely that good. Really enjoyed playing these missions. That was also the first time I ever trapped a Hornet single engine in DCS. Glad I made it on the first try! 

 

Looking forward to trying more of your missions / campaigns! BZ!

  • Like 1
Posted (edited)

Hey Sedlo,

I was replaying your campaign again and re-downloaded the new version. It’s the best campaign in DCS so far! I'm glad you didn’t forget about DCS players—your brief to have the HSI page up because you’ll likely be getting coordinates is a big help, as are the pre-programmed frequencies with comms that say which channel to push. It might seem like a small point, but having to cycle through pages for frequencies over and over is such a massive pain—I wish others did what you do.

Anyway, Mission 5: I chose to refuel and got a reply saying I should dial up Arco on 51Y, but there was nothing from Arco on 51Y. I tried 51X and got the tanker. I flew to it, but something may have broken. I was told to change to channel 4 left, and then all communications stopped. When I got to ARCO, I tried to call him on channel 10 (as outlined on your frequency sheet), but got no reply. I ended up plugging in max range speed and made it with just a few fumes to spare. Not sure if it was something I did wrong.

Also, I wanted to confirm I was doing the timing correctly. There's a hold and a push waypoint. I timed it so I was overhead the push waypoint at 00:55. Is that correct, or is your campaign set up so you’re overhead the hold and then fly to the push at 00:55?

Many Thanks

Edited by nikoel
  • Like 1
Posted

I just finshed the campaign. It is easily on par with the paid ones and you can see that it was intended to be one. Also the quick reaction time to bugs is outstanding!

Spoiler

In noticed a difference in Mission 13 between the Cold start and Push Version. In cold start the F-14 arrive way later and the F-4 never show up. Also the SA-10 get´s destroyed before it can shoot down most of the F-15s. I also had several crashes of DCS with the Push Version (5 out of 5 trys) mostly after heading back to the boat. The Cold Start Version worked fine though, no crashes.

 

  • Like 1

🖥️ CPU: i9-14900K, RAM: 64GB DDR4 3200, GPU: RTX5090 32GB, HD: M2 PCIe 2TB   🥽 Pimax Crystal Super  🕹️ Thrustmaster Warthog HOTAS, Thrustmaster TPR Rudders

Posted (edited)

Hi @Sedlo, thanks again for this awesome campaign.

Just finished mission 8 and I'm getting a score of 60 despite having completed all the objectives and returned safely to the carrier. It seems the landing is not getting recognized, I'm not getting the usual message once in the carrier deck. I took a brief look at the mission in the editor and it seems the trigger zones are misplaced. Maybe something was broken when switched from Stennis to George Washington?

Screen_241224_155406.png

Edited by miguelaco
Posted
22 hours ago, miguelaco said:

Hi @Sedlo, thanks again for this awesome campaign.

Just finished mission 8 and I'm getting a score of 60 despite having completed all the objectives and returned safely to the carrier. It seems the landing is not getting recognized, I'm not getting the usual message once in the carrier deck. I took a brief look at the mission in the editor and it seems the trigger zones are misplaced. Maybe something was broken when switched from Stennis to George Washington?

Screen_241224_155406.png

Hey @miguelaco.  I doubled checked and tested the mission, all is working well on this end.  Those zones are down there because the mission was made before we could link zones to moving objects.  It used the trigger unit in moving zone, and the carrier is still linked to it, although in a different way.  I've tested the mission twice now and I'm getting good landing comms.   

I'm not sure why you didn't get any comms on your attempt.

Posted
On 12/23/2024 at 2:59 AM, nikoel said:

Hey Sedlo,

I was replaying your campaign again and re-downloaded the new version. It’s the best campaign in DCS so far! I'm glad you didn’t forget about DCS players—your brief to have the HSI page up because you’ll likely be getting coordinates is a big help, as are the pre-programmed frequencies with comms that say which channel to push. It might seem like a small point, but having to cycle through pages for frequencies over and over is such a massive pain—I wish others did what you do.

Anyway, Mission 5: I chose to refuel and got a reply saying I should dial up Arco on 51Y, but there was nothing from Arco on 51Y. I tried 51X and got the tanker. I flew to it, but something may have broken. I was told to change to channel 4 left, and then all communications stopped. When I got to ARCO, I tried to call him on channel 10 (as outlined on your frequency sheet), but got no reply. I ended up plugging in max range speed and made it with just a few fumes to spare. Not sure if it was something I did wrong.

Also, I wanted to confirm I was doing the timing correctly. There's a hold and a push waypoint. I timed it so I was overhead the push waypoint at 00:55. Is that correct, or is your campaign set up so you’re overhead the hold and then fly to the push at 00:55?

Many Thanks

Hey @nikoel glad you enjoyed it! As far as the timing goes, be at the push waypoint at the indicated time.  In this mission's case, they are close enough together that it should work out ok either way.

 In terms of contacting the tanker, you would have been pushed to WHITE 42 by AWACS, which is preset 12 on the COMM2.   Sometimes things in the mission will be different that what is on the mission kneeboard.   I've re-flown the mission and it seems to be working OK on this end.

The TACAN was working OK for me, but the trick in DCS is you don't use the A/A mode on your UFC.   It's a long-standing issue with DCS, but seems to be working "as intended" even though it's not correct.

null

 

image.png

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...