F-14B : OPERATION CAGE THE BEAR

[draconus]

11 hours ago, Damian-J said:

I'm finding every time that one of the SEAD Hornets ends up in the drink after launch

That was supposed to be fixed in the latest beta.

[Damian-J]

On 8/13/2021 at 7:06 PM, draconus said:

That was supposed to be fixed in the latest beta.

I know lol

but nevertheless, into the drink she goes.

[kaba]

6 hours ago, Damian-J said:

I know lol

but nevertheless, into the drink she goes.

Yeah I can reproduce - ED are still tinkering with the AI flight models so they can be a bit off.  A kind soul reported this here, and is hopefully corrected in a future update.

I don't think this should prevent you carrying on with the mission, but let me know if it turns into a bigger problem!

 

[Smokin Hole]

I am a bit late to discovering this campaign.  Loving every minute of it!  I've never had problems staying on the tanker before.  But I realized that after an hour of pretty busy flying I need to breathe and find some zen or I easily make a mess of both tanking and trapping.  The missions are that intense.

[winghunter]

On 11/20/2019 at 2:14 PM, kaba said:

Air threats are random. Sa6 is timer triggered. AAA and MANPADS switch on in stages if you spend too long loitering.

 

Air threats are a new inclusion. Reason for this change is the feedback from first version that this mission was too easy and a bit stale.

 

I'm not going to change loadout to phoenixes. If the air threat is consistently too heavy to the extent that this is not coming across as a fun mission then I am happy to tweak - but i need your tacviews or more specific feedback (preferably both).

Ok now that makes sense, I retried the mission at least 6 times and every time I felt it got harder.

Because my strategy was to take out the remaining air defences first, then drop the bombs. But somehow me and my wingmen kept blowing up.

Edited April 25, 2022 by winghunter

[draconus]

11 hours ago, winghunter said:

Because my strategy was to take out the remaining air defences first, then drop the bombs. But somehow me and my wingmen kept blowing up.

It's not your task to fight the AD. It's the quick bomb run and egress.

[winghunter]

20 minutes ago, draconus said:

It's not your task to fight the AD. It's the quick bomb run and egress.

I got hit by the shilka on my first run. I know its not my target but i wanted to clear them out to avoid this

[Joe1978]

Sorry, I recover this old thread (please excuse me for my poor English too). I have one problem with this campaign and I need some help.

After finishing mission nº9 "interceptor", specifically when I return to the carrier, DCS always suffers the same crash; the picture freezes (although not the sound) and I see on SteamVR the message "waiting for DCS"... I'm just flying back, preparing for landing, etc... There are also several friendly aircraft flying nearby.

It has happened to me several times more or less in the same place (close to the carrier). Could it be a mission issue?

Thanks

PS: I have repaired the DCS but I still have the same "bug".

[draconus]

7 hours ago, Joe1978 said:

Could it be a mission issue?

There might be some issues currently.

 

[Joe1978]

Thanks!!! 

I've been working away from home all week and haven't been able to see your message. 

En 5/7/2022 a las 8:01, draconus dijo:

There might be some issues currently.

 

 

[JupiterJoe]

I too am having the same freezing issue with this campaign.  Around 60 miles out from carrier, heading home.  Has happened on multiple missions, but sometimes they play straight through with no problems.  Here is a log from the latest crash.  Hope it helps:

 

dcs.log

 

Also posted in this thread:   

 

Edited July 21, 2022 by JupiterJoe

[draconus]

6 minutes ago, JupiterJoe said:

Here is a log from the latest crash.

"Pagefile: 4864 MB" Seriously?

Make it 32GB fixed.

Edited July 21, 2022 by draconus

[draconus]

3 minutes ago, JupiterJoe said:

Why have I got to mess about with my operating system' settings?  I am happy to do so, but will doing so mess up anything else?   Why doesn't DCS change the pagefile settings to run optimally, if that's what's needed?  Is this a problem exclusive to Open Beta?   Is everyone altering their pagefile as a matter of routine then? 

It started somewhere around here:

It was 16GB at the time but then changed to 32GB with DCS growing and new better hardware. It helped numerous people to get stable DCS play again so it's a common and one of the first advise for anyone experiencing crashes.

DCS cannot change it in your system and the change does not affect other application or your system in any wrong way. It is not exclusive to beta version.

Anyone using high DCS settings and demanding modules and missions should do that apparently. It's probably a workaround for some suboptimal memory management but what do I know.

[JupiterJoe]

Thank you Draconus.  Is what I'm doing here correct?  DCS is on its own SSD:

null

Edited July 21, 2022 by JupiterJoe

[draconus]

Just now, JupiterJoe said:

Thank you Draconus.  Is this correct?

Input also 32000MB for the initial size.

[draconus]

11 minutes ago, JupiterJoe said:

Thank you Draconus.  Is what I'm doing here correct?

Sorry, I just noticed... You can change the page file settings which is already on your C drive. No need to make it on the other drive and it does not have to be the one with DCS on it. Also make sure it is the fastest drive in your system like NVMe M2 SSD if you have one.

[Chief_Biv]

I having the same problem on Mission 7 "Interception". I cannot get closer than 60nm to the carriers after being cleared RTB. My virtual memory already set to 32768 MB for initial and Max size.

[Chief_Biv]

I just spotted another thread discussing games freezing with the F-14.

[PawlaczGMD]

I have a problem with this campaign. My wingman is not communicating on channel 1. He does not reply, call out targets, or listen to commands. I have done the first 2 missions like this, but I am barely making it- running out of missiles. My wingman does nothing, just follows me passively and does not shoot. I can contact everything else fine, AWACS, carrier, so it's not my comms issue. It's just the flight channel that doesn't work. Any ideas?

[draconus]

9 minutes ago, PawlaczGMD said:

It's just the flight channel that doesn't work. Any ideas?

It's usually CH1 on the RIO's radio (AN/ARC-182, V/UHF #2). Make sure you use proper comm/mic/PTT binding.

To make sure check in the mission editor.

Edited January 29, 2024 by draconus

[PawlaczGMD]

1 hour ago, draconus said:

It's usually CH1 on the RIO's radio (AN/ARC-182, V/UHF #2). Make sure you use proper comm/mic/PTT binding.

To make sure check in the mission editor.

 

Thanks, I was using my own radio for this. I usually have Ch. 1 on the front radio, and something else on RIO's (AWACS).

I will check if the frequencies are different tomorrow. I am aware of the different bindings for the two radios. 

[PawlaczGMD]

On 1/29/2024 at 2:45 AM, draconus said:

It's usually CH1 on the RIO's radio (AN/ARC-182, V/UHF #2). Make sure you use proper comm/mic/PTT binding.

To make sure check in the mission editor.

 

Yeah, that was it. Looks like only the RIO channel 1 is tuned to Flight.

[draconus]

1 hour ago, PawlaczGMD said:

Yeah, that was it. Looks like only the RIO channel 1 is tuned to Flight.

Yep, that's common for the wingman to use default 127MHz AM and only the RIO's radio can cover that freq. range.

[PawlaczGMD]

15 hours ago, draconus said:

Yep, that's common for the wingman to use default 127MHz AM and only the RIO's radio can cover that freq. range.

OK, I didn't know that. Most other campaigns I've played had duplicate channels across the radios, or had separate sheets for the 2 radios. I know that the RIO radio has a wider freq range. It would help if the kneeboard/briefing specified the radio, because channels 2-4 work just fine on the pilot radio. 

[speed-of-heat]

With Mission Recon Strike, I am getting no comms with anything (Carrier nor Tanker) after the Mission has completed. recon duties.trk it also gives a mission failure Notification after you land and have had a successful mission 

With Mission Interception, no comms at all, with either AWACS or Wingman  right from the start.  I can receive but not transmit to Focus or Wingman, so I can't request a picture and I cant get the wingman to fence in change formation or engage or fence in.

I have tried both on the Pilot ad RIO radios in both cases, any help or suggestions ?