Weasels Mission 1 No F10 Menu

[jbucholz]

As the title says, the F10 menu is missing from mission 1 of the Weasels campaign so can't contact ATC for start up per the instructions.null

[CageyLobster]

I am also running into this.  I assume it has to do with 2.9's new comm system. I also tried to push through, but none of the later F10 menus work at any point during the sortie either.  

[Jayhawk1971]

Have you turned the battery on? Fully, not just in the middle position. Leaving the battery switch in the middle position before asking for startup clearance will not trigger the F10 option.

 

Edited October 20, 2023 by Jayhawk1971

[ChillNG]

3 hours ago, jbucholz said:

As the title says, the F10 menu is missing from mission 1 of the Weasels campaign so can't contact ATC for start up per the instructions.null

 

2 hours ago, CageyLobster said:

I am also running into this.  I assume it has to do with 2.9's new comm system. I also tried to push through, but none of the later F10 menus work at any point during the sortie either.  

Check easy Comms is turned off in your game settings, that fixed it for another user.

[tsefreeflow]

Yes these Comms do not work. Tried every which way and even using voice attack/Viacom and you just cannot Connect with ATC. Ground Crew yes, but not ATC.

[ChillNG]

3 hours ago, tsefreeflow said:

Yes these Comms do not work. Tried every which way and even using voice attack/Viacom and you just cannot Connect with ATC. Ground Crew yes, but not ATC.

Are you selecting the F10 option on the comms menu, not the F5 option for ATC.

[ChillNG]

Please check this quick video out if having problems accessing the F10 comms menu, three most common problems are not using the F10 menu option, setting the battery wrong at startup, having easy comms turned on or using the wrong key bind.

 

 

[CageyLobster]

3 hours ago, ChillNG said:

Please check this quick video out if having problems accessing the F10 comms menu, three most common problems are not using the F10 menu option, setting the battery wrong at startup, having easy comms turned on or using the wrong key bind.

 

 

Thanks for the quick response @ChillNG  I've been pretty excited for this campaign.

I double checked my settings just to be sure.  No easy comm.  My F-16 UHF/VHF are individually bound and not suffering any conflicts that are evident.  

When I apply battery power I can contact ground for clearance to start and I get a response from ground that I am cleared to start.

I crank and get notified that my "engine is online"

I get notified to turn on avionics systems and when ready set the VHF to comm 2/ chnnl 7 to prepare for radio check.  I thought I may be rushing it and not being patient. (I tend to do that) So this morning I ran it again and waited until 10:01Z and that is passed takeoff time. So I stopped this attempt and restarted with the goal of making it short to get a track, so I started the sortie over at this point.

At this point on my second attempt after my initial conversation with ground no other F10 option ever populates on either UHF/VHF radios to communicate taxi with ground or a radio check with lead.  I have the back-up radio in preset mode and use the rocker in comm 2 to select channel 7.  No communications happen.  But when I turn the back-up radio to manual and use the ufc to manually input 141.50 I immediately get a radio check callout.

P.S.  I am so rusty in the -16.  don't tell anyone, but this may just be switch-ology or order of operations I'm messing up.  I'm including this track.  this is me down and dirty with no checklists, just trying to get a track and test.  So it is possible Im making the issue happen by missing a step.  Or it could just be the new radio logic.  I am neither smart nor smart.

Edit: clarification that actually didn't clarify anything. 

Comm progression.trk

Edited October 20, 2023 by CageyLobster
Words

[ChillNG]

1 hour ago, CageyLobster said:

Thanks for the quick response @ChillNG  I've been pretty excited for this campaign.

I double checked my settings just to be sure.  No easy comm.  My F-16 UHF/VHF are individually bound and not suffering any conflicts that are evident.  

When I apply battery power I can contact ground for clearance to start and I get a response from ground that I am cleared to start.

I crank and get notified that my "engine is online"

I get notified to turn on avionics systems and when ready set the VHF to comm 2/ chnnl 7 to prepare for radio check.  I thought I may be rushing it and not being patient. (I tend to do that) So this morning I ran it again and waited until 10:01Z and that is passed takeoff time. So I stopped this attempt and restarted with the goal of making it short to get a track, so I started the sortie over at this point.

At this point on my second attempt after my initial conversation with ground no other F10 option ever populates on either UHF/VHF radios to communicate taxi with ground or a radio check with lead.  I have the back-up radio in preset mode and use the rocker in comm 2 to select channel 7.  No communications happen.  But when I turn the back-up radio to manual and use the ufc to manually input 141.50 I immediately get a radio check callout.

P.S.  I am so rusty in the -16.  don't tell anyone, but this may just be switch-ology or order of operations I'm messing up.  I'm including this track.  this is me down and dirty with no checklists, just trying to get a track and test.  So it is possible Im making the issue happen by missing a step.  Or it could just be the new radio logic.  I am neither smart nor smart.

Edit: clarification that actually didn't clarify anything. 

Comm progression.trk 40.17 MB · 0 downloads

 

Thanks for the track, that helped me spot what you were doing wrong, you set the pre set incorrectly.  The option you selected I think was determining what the presets are set to, to set the radio to that preset, just dobber over to the value on the right, type the channel number and press UFC ENTER.  Once I did that and pressed spacebar, all worked as it should.

 

 

 

null

[CageyLobster]

@ChillNG That was absolutely my issue.  The great news is I am bound to get shot down a lot.  So, theoretically I should get a lot of practice with proper start-up and UFC procedures, lol.  YGBSM!

 

DCS: F-16C Viper Manual Dated: 11 July 2023

Pg. 195

When talking about the function of the rocker switch when the UFC is accessed by pressing the COM 1 or COM 2 override buttons. 

* Cycles the Preset Channel Number data field to the next/previous preset radio channel for editing the assigned frequency of that preset; the radio will not be tuned to that preset channel or frequency.

One would hope I learned a valuable lesson about reading more and talking less.  Hopefully, my learning experience helps someone else that forgets this gem.

Edited October 20, 2023 by CageyLobster
adding more information

[ChillNG]

20 minutes ago, CageyLobster said:

@ChillNG That was absolutely my issue.  The great news is I am bound to get shot down a lot.  So, theoretically I should get a lot of practice with proper start-up and UFC procedures, lol.  YGBSM!

 

DCS: F-16C Viper Manual Dated: 11 July 2023

Pg. 195

When talking about the function of the rocker switch when the UFC is accessed by pressing the COM 1 or COM 2 override buttons. 

* Cycles the Preset Channel Number data field to the next/previous preset radio channel for editing the assigned frequency of that preset; the radio will not be tuned to that preset channel or frequency.

One would hope I learned a valuable lesson about reading more and talking less.  Hopefully, my learning experience helps someone else that forgets this gem.

 

Well the Comms settings are always the biggest thing people struggle with so hopefully you've shone a light on it for anyone else having issues.

[Atari800XL]

vor 17 Stunden schrieb ChillNG:

Well the Comms settings are always the biggest thing people struggle with so hopefully you've shone a light on it for anyone else having issues.

Good morning,

I had exact the same problem: the comms did not work. Checked "easy comms" in game settings, checked the bindings of my stream deck, read this threat here multiply times, checked the temperature of my coffee ... nothing worked! Leeck-mode on, back to Viper-manual, back to some youtube tutorials ... then I realised that this was the first time I really had to deal with comms  (SRS and MP-Servers made me lazy!)

Finally my failure was, that I mixed UHF and VHF Todays learned lesson: reading slower may help! 

[ChillNG]

13 minutes ago, Atari800XL said:

Good morning,

I had exact the same problem: the comms did not work. Checked "easy comms" in game settings, checked the bindings of my stream deck, read this threat here multiply times, checked the temperature of my coffee ... nothing worked! Leeck-mode on, back to Viper-manual, back to some youtube tutorials ... then I realised that this was the first time I really had to deal with comms  (SRS and MP-Servers made me lazy!)

Finally my failure was, that I mixed UHF and VHF Todays learned lesson: reading slower may help! 

Ha ha thanks, glad you got it sorted!

[Arch-vile]

Still having the issue described in this thread. Checked easy-comms are off. Using radio-specific comm menu commands. I turn the battery on and the F-10 menu option is not available. The options go through F8. I've tried turning on the backup uhf radio and tuning it manually as well but the frequencies listed in the SPINS don't seem useable for requesting engine startup.

<EDITED> Found this thread: 

which explains the issue. You can't make the radio call on battery power, you have to flip the aircraft's main power to "on" but not start the engine. Looks like this is labeled "not a bug" but it's at least confusing since the instructions specifically reference turning on the battery only. Also, i was able to get this radio call to work using "intercom" and the steps don't involve actually powering on or tuning the backup UHF radio. But at least I can continue.

Edited October 22, 2023 by Arch-vile

[ChillNG]

2 hours ago, Arch-vile said:

Still having the issue described in this thread. Checked easy-comms are off. Using radio-specific comm menu commands. I turn the battery on and the F-10 menu option is not available. The options go through F8. I've tried turning on the backup uhf radio and tuning it manually as well but the frequencies listed in the SPINS don't seem useable for requesting engine startup.

<EDITED> Found this thread: 

which explains the issue. You can't make the radio call on battery power, you have to flip the aircraft's main power to "on" but not start the engine. Looks like this is labeled "not a bug" but it's at least confusing since the instructions specifically reference turning on the battery only. Also, i was able to get this radio call to work using "intercom" and the steps don't involve actually powering on or tuning the backup UHF radio. But at least I can continue.

 

Thanks, yeah I've noticed the battery instruction has caught a few out already. I've changed the wording for the next update.

[tsefreeflow]

Comms figured out, it is very strange way, but no worries. 

Another problem, and maybe it is me somehow, but the steerpoints (SP) entered into the system and showing on the HSD do not show correctly in the HUD. Can any assistance be provided on that? They are WAY off on the HUD even when cycling through them.

Thanks

Edited October 23, 2023 by tsefreeflow

[ChillNG]

5 hours ago, tsefreeflow said:

Comms figured out, it is very strange way, but no worries. 

Another problem, and maybe it is me somehow, but the steerpoints (SP) entered into the system and showing on the HSD do not show correctly in the HUD. Can any assistance be provided on that? They are WAY off on the HUD even when cycling through them.

Thanks

 

Maybe an INS alignment issue?

[tsefreeflow]

Did a stored alignment, does it need to be a full alignment every time?

[ChillNG]

1 hour ago, tsefreeflow said:

Did a stored alignment, does it need to be a full alignment every time?

No stored is fine, never do a full alignment myself.  Another issue could be that after the recent update the way SPIs work has changed, if your waypoints are way out, go back into the TGP/wep page and undesignate with TMS down.

Edited October 25, 2023 by ChillNG

[tsefreeflow]

24 minutes ago, ChillNG said:

No stored is fine, never do a full alignment myself.  Another issue could be that after the recent update the way SPIs work has changed, if your waypoints are way out, go back into the TGP/wep page and undesignate with TMS down.

 

Just did a full alignment and now all the SPs are correct. Seems the full alignment is what was needed I guess . Thanks

[Braunn]

My GAWD I've been swearing, crying and screaming for 30 minutes trying to wake up Tower for cleared start up this fracking thing and didn't catch you gotta go OTHER at F10 option...

 

 

YGBSM!!!! 

:)  

[ChillNG]

1 hour ago, Braunn said:

My GAWD I've been swearing, crying and screaming for 30 minutes trying to wake up Tower for cleared start up this fracking thing and didn't catch you gotta go OTHER at F10 option...

 

 

YGBSM!!!! 

Lol it's funny how many people think of the radio menu as the F10 menu and not realise straight away it means the F10 menu in the radio menu.  And so many people do it you can't really criticise anyone for it, just a human thing we do I guess!

[Braunn]

Yeah, the radio stuff is easier when you just pop in SRS and have humans to deal with in mission. Played the first mission. Campaign looks to be magnificent. Really enjoyed it but it's NOT for beginners that don't want to get down and dirty with the systems in the Viper. 

Thank you  for making it. 

[ChillNG]

35 minutes ago, Braunn said:

Yeah, the radio stuff is easier when you just pop in SRS and have humans to deal with in mission. Played the first mission. Campaign looks to be magnificent. Really enjoyed it but it's NOT for beginners that don't want to get down and dirty with the systems in the Viper. 

Thank you  for making it. 

No worries, hope you enjoy!