ATLAS Radio Cockpit Waypoint Preview =================================== Use Open Beta 4.29 Free or Premium multiplayer as the host and the matching Radio Cockpit Waypoint Preview as the pilot. Run Install / Repair DCS integration on the host with DCS closed, then restart the mission. Pilots install the preview with DCS closed and pair Radio to the host through the ordinary connection flow. The preview is opt-in. The host selects the exact DCS mission unit name and player name and gives that pilot a unique key in private. The key grants cockpit delivery for that slot. Keep the host configuration outside the DCS mission and share each key with its pilot only. Host setup ---------- 1. Create a JSON file in the host's private settings folder. Use the DCS unit name from the mission editor and the exact multiplayer player name. The file has this shape. Replace the placeholder with a real key. [ {"unit_name":"Viper Assigned","pilot":"Pilot Name","key":"<64 lowercase hex digits>"} ] 2. Generate each key with the Windows cryptographic random generator. In PowerShell, assign the result to a variable so the key stays out of output. $keyBytes = New-Object byte[] 32 $generator = [Security.Cryptography.RandomNumberGenerator]::Create() try { $generator.GetBytes($keyBytes) } finally { $generator.Dispose() } $pilotRouteKey = -join ($keyBytes | ForEach-Object { $_.ToString('x2') }) 3. Close the host launcher and start it from a PowerShell session with the environment variable set to the absolute path of the host JSON file. $env:ATLAS_DIRECT_ROUTE_TEST_PILOTS = 'C:\path\to\private-atlas-pilots.json' Launch your installed ATLAS.exe from that same session. Use its usual Server Setup controls to start the instance. A fresh launcher is required when the pilot configuration changes. Pilot setup ----------- 1. Close Radio completely. In PowerShell, set the pilot key in the current process environment and launch Radio from that same session. Enter the key through a masked prompt so the value stays out of your command history. $entry = Read-Host 'Cockpit waypoint preview key' -AsSecureString $env:ATLAS_DIRECT_ROUTE_TEST_KEY = [Net.NetworkCredential]::new('', $entry).Password & "$env:LOCALAPPDATA\ATLAS Radio\ATLAS-Radio.exe" 2. Take the enrolled pilot slot. Keep the aircraft powered and parked with the controls free. Use SRS and request an approved IFR route. Read back the full clearance normally. 3. Inspect your aircraft navigation display before moving. The preview loads the ordered horizontal fixes when ATLAS first transmits the clearance. Altitude, restrictions and clearance limits come from ATC. A route with existing mission waypoints is protected. ATLAS can clear it as filed when it matches a validated plan. An unverified empty slot, changed pilot, second crew member, or route above the aircraft's capacity blocks the write. Cockpit preparation and maximum fixes ------------------------------------- F/A-18C Center display on HSI 20 F-16C DED on CNI or STPT with no active edit 8 JF-17 UFCP on FP-A 8 A-10C/A-10C II CDU OTHER, steering FLT PLAN, L/L 3 AH-64D Pilot seat, empty TSD route 3 CH-47F Right-seat pilot, FPLN DATA in LAT/LONG 2 F-14A/F-14B Pilot seat, no human RIO, Jester menu closed 3 F-14B(U) Pilot seat, no human RIO, Jester menu closed 2 The Hornet and five Tomcat variants have live parked cockpit checks. Other modules have automated cockpit checks. Treat this as a DCS preview. Review any failed or interrupted load before trying again.