ChillNG

Hey, thanks for the comments! There's not much to it to be honest, just the basic SAM avoidance techniques. Biggest threats are the SA-6s, there are three in range of the target but you will only have one online at any one time. It's been ages since I flown this one but from memory things were a little safer west of the target (towards the mountains at the Lebanese border), this is a safer place to loiter and press your attacks from.

Hi sorry for the delay, I was away for a few days. Just done some checks and all worked ok in the short test version I did, Newt broke off into an orbit as we arrived at the crash site and left the orbit to attack when requested. One thing to watch out for is that the radio must be set correctly for Shadow at the crash site as this is a condition in some of the triggers.

Thanks v much, some of the other campaign devs have seen a bug with the follow task not stopping, I've not seen it happen in any of my campaigns yet but it could possibly be this, I'll have a check.

It puts you in position to enter the 'Gold Corridor' for your entry into Syria.

Most mission you will need to hit the zone around waypoint 1 to get started. Once handed off by departure at 25 (I think) miles you'll get a message saying go to waypoint 1. Once you arrive there you and the wingman or flight lead will the communicate and things will get moving. Don't skip WP1 as it will break most missions.

Ok thanks I get what you're saying. The FLIR coords are always a little off in the Hornet, this is an old bug with the Hornet. They're close enough to allow you to still get the pod looking close but it is a bit of a pain. Not sure about the 98 seconds, could be part of the same bug, or perhaps a new one. Same issue you're seeing on mission 5 and 7 I think. Any JDAM mission where you have pre-briefed coords I would just use PP mode, the weapons should still hit as long as you set it up and drop it right.

I'm not sure what you mean here, a bug with the campaign or with DCS/Syria itself? Not sure what you're referring to with 98 seconds. Just for clarity I've just retested M6 and my previous comment below still applies. If you set your JDAMs up in PP mode the coordinates are correct. There was a long standing Hornet bug where the TGP doesn't quite lineup when adding way points manually, not sure if this is still the case or not.

OK thanks for reporting, I'll do some checking, I remember this as a DCS bug a while back I'll see what I can dig up.

Campaign updates 17/11/22: Operation Cerberus North Mission 1 - Adjusted Poodle AI behaviour - should now not sink to the ground at low level after no fly zone interception. Mission 2 - Adjusted ATC zone to fix possibility of not being handed off if player is off course. Mission 7 - Adjusted AI behavior to avoid rare potential for mid-air collisions. Mission 11 - Fixed error in scoring incorrectly deducting points for hitting TOT.

There should be enough time allowed for a drop from that height, did you put any loft on the bomb, just wondering if the time of flight could have been increased at all?

Ok no worries, thanks for letting me know.

Yes no issues.

OK sounds like odd behavior, the two campaign version are currently identical I think. Just done a test my end on M1 in OB, Hornet was fine, a little asymmetric like I said but a small amount of trim fixed that. Did some yanking and banking and all felt as normal, no abnormal stalls. Only other thing I can suggest is to try a DCS repair, maybe something is a little corrupted your end, also just to check, any mods installed that might impact things?

I think you have a small asymmetric load out in this mission so you will need some trim to compensate but it won't be an excessive amount. Not much more I can offer than that I'm afraid, the Hornet is the Hornet - the mission doesn't change it and the Hornet's code and flight model remains the same, so most likely a combination of weight/asymmetric load/maybe some wind throwing things off a little.

For the F10 menu just make sure the radio is set correctly and you have pressed enter on the UFC. I'm not sure what could be causing your HUD issues, it's nothing specific to the campaign but hopefully we can collectively help you figure it out. What do you mean by strange avionics?

Fix has been submitted to ED, should be on next OB patch.

If the helos departed you should be fine to RTB, the trigger that activates the RTB ATC option is turned on at this point, only thing I can think of if you didn't get the options is an incorrect radio setting or possibly some damage to the radio (this can at times be an issue). Did you not get any conversations at all on the way back? These will be activated providing the UHF radio is still set to 260, even if Davy's AI messes up and he refuses to go home he will still communicate with you.

Just tested on a BMP-3 with VT fuse set at height of 500...dropped a pair of Mk-20 and got a solid kill. Still think the cluster modelling needs some work but it does work well enough on the tests I've done..think density of bomblets is the answer

Hi, it should be fine, I don't think it will break anything.

OK no worries, let me know if it happens again and I'll dig in a little more.

Hi mate, Just ran a quick test of that part of the mission, all worked ok for me, selected F10 option and things proceeded as they should. Only variables in that trigger are selecting the F10 menu option and the radio being set correctly, so logic would suggest it was the radio setting causing the issue - worth double checking you didn't inadvertently switch something by mistake. Hope that helps!

No it won't work I'm afraid, a lot of triggers tie in to the radio settings, which are specific to the A10.

I can check, I didn't set any rtb behaviour but worth a look.

Yeah mine's been rock solid so far in 2.8, in VR as well. F18, Harrier, F16 and A10 plus PG and Syria...no crashes at all. But I'm aware of plenty who are seeing them, I know the other campaign devs have similar issues with some users getting crashes. Most likely some instability brought about from 2.8, we'll just have to keep flagging it up so ED can ID the issue and fix.

Sorry to hear this. I've been unable to reproduce myself so will have to ask ED for some support if they can ID the reasons behind the crash. Before I do can I please just check a few things with you. First confirm if you are using any mods at all, and if you are what are they, second are you in VR? If in VR it may also be worth setting preload to max and trying again, other users have reported this having solved their crashes in VR.