flightsimulatorplatfrom/OpenSquawk
1
0
Fork 0
mirror of https://github.com/OpenSquawk/OpenSquawk synced 2026-08-01 22:26:04 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix(pm): require manual tuning at session start; name the correct frequency

Browse Source 
Reverses the auto-tune: tuning to the first controller is part of the exercise.
Each scenario now starts from a fixed baseline frequency (121.900), and the
first call is rejected until the pilot dials the correct one — we do NOT silently
put them on the expected frequency.

The wrong-frequency reply now names the position and frequency to switch to,
e.g. "DLH6RK, you are on the wrong frequency. Contact Approach on 119.900."

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
leubeem
2026-06-17 15:28:10 +02:00
parent fdc8bbd02d
commit 54aa999875
1 changed files with 13 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

27
app/pages/pm.vue
View File

@@ -2804,9 +2804,13 @@ const handlePilotTransmission = async (message: string, source: 'text' | 'ptt' =
const expectedFreq = expectedFrequencyForState()
if (expectedFreq && frequencies.value.active !== expectedFreq) {
const callsign = (vars as any).value?.callsign ?? ''
const freqName = (currentState.value as any)?.frequency_name as string | undefined
// Tell the pilot exactly which frequency to switch to (and the position),
// since tuning is manual and the call won't go through until they do.
const target = freqName ? `${freqName} on ${expectedFreq}` : expectedFreq
const reply = callsign
? `${callsign}, check frequency. You are on ${frequencies.value.active}, expected ${expectedFreq}.`
: `Station calling, check frequency. Expected ${expectedFreq}.`
? `${callsign}, you are on the wrong frequency. Contact ${target}.`
: `Station calling, wrong frequency. Contact ${target}.`
pmLog.warn('WRONG FREQUENCY', { active: frequencies.value.active, expected: expectedFreq })
lastControllerSay.value = reply
scheduleControllerSpeech(reply)
@@ -3059,18 +3063,13 @@ const startMonitoring = async (flightPlan: any, scenario: Scenario) => {
currentScreen.value = 'monitor'
persistSelectedPlan(flightPlan)
// Tune the radio to the starting position's actual frequency so the pilot's
// first call is on the right frequency instead of being rejected with a
// "check frequency" (the active freq otherwise carries over from a prior run
// or a hardcoded default, which breaks every non-EDDF start and any arrival
// that begins on Center/Approach rather than Delivery).
const startFreq = expectedFrequencyForState()
if (startFreq) {
if (frequencies.value.active && frequencies.value.active !== startFreq) {
frequencies.value.standby = frequencies.value.active
}
frequencies.value.active = startFreq
}
// Start every scenario from a known baseline frequency. Tuning to the first
// controller is part of the exercise: the pilot must dial the correct
// frequency themselves, and the first call is rejected (telling them which
// frequency to switch to) until they are on it. We deliberately do NOT
// auto-tune to the expected frequency here.
frequencies.value.active = '121.900'
frequencies.value.standby = '118.100'
// 4. Walk the initial ATC/system states locally (deterministic, no LLM).
// Safe because we loaded the tree from the same Python backend, so the