QuaxTheSnoopie

Searching for "Hudson Miracle APCH" from the mentioned wiki site leads to https://ww2.jeppesen.com/wp-content/uploads/2019/04/us-airways-flight-1549-sully-skiles-hudson-river-miracle-approach.pdf (just VFR 😂)

Assuming P3D V6 is based on Unreal Engine, I would expect the need to buy all airports, aircraft, tools again (I suppose "we have no plans to make major architectural changes" doesn't mean, addons don't have to be rebuild by the developer - and mostly payed again as history has shown) fiddling with performance settings without historical knowledge from FSX or P3D V3,4,5 wasting time to get hardware (controllers) and software working again It will be interesting what advantages and what realism will be delivered for flying an aircraft, thinking about Turboprob behaviour Heli flying VOR as ATIS Other bugs since FSX times resolved Or will V6 contain mainly optical enhancements or (worst of all) will it be more like one of these UE based games ("missions") ? We will see...

Maybe a first try: https://support.microsoft.com/en-us/topic/microsoft-net-framework-repair-tool-is-available-942a01e3-5b8b-7abb-c166-c34a2f4b612a

Found https://forums.hifisimtech.com/threads/wrong-runways-active.11223/ I will compare Shift+Z "wind direction and speed" on my next flight, but after some further investigations, I suppose, I have to offer my runway request to P2A in a more precisely spoken way or look for a day with winds of >6 kts (even then P3D's internal runway selection may be stochastic 😖).

Hmm, I don't think "prevent download" hit in my case as winds at the destination airport were reported 1-4 kts over hours on this (historical) day. The "ATC wind lock" should only become active when winds are below 6 kts, it locks the winds to 6 kts. But I found an entry at Hifi leading to a bug in ASP4 7410. Checked current_wx_snapshot.txt : LOWK::LOWK 121320Z VRB01KT 9999 FEW060 07/02 Q1022 NOSIG::LOWK 121115Z 1212/1312 VRB02KT 9999 FEW050 TX07/1213Z TNM02/1307Z TEMPO 1217/1309 0800 PRFG BKN010 TEMPO 1220/1308 BKN004 PROB30 1302/1306 0300 FZFG So it seems, despite the "wind lock activation bug", ASP4 doesn't set the "ATC wind lock" in these files at all. ...thinking about, the problem may arise from ASP4 not knowing a wind direction at all (VRB), therefore assuming the runway randomly. I had some troubles with the speech recognition (omitted words), so the force pilot runway selection may not have known my direction intentions, I've trained the grammar again - may it lead to better success on my next flight.

Hi, I run Active Sky for P3Dv4 7410 in P3D 4.5 HF3 to fly with historical weather and have the option "ATC wind lock" on. It should set the wind speed at the target airport to a minimum of 6 kts to get a "stable" approach direction. In P2A, I set the weather folder to C:\...\AppData\Roaming\Hifi\AS_P3Dv4\Weather but it seems not to work: although ASP3Dv4 "Briefing" tab states LOWK RW28 as destination runway, P2A will guide me to RW10. Now I found that the files in the ASP3D weather folder have LOWK entries for VRB01KT, even in activeflightplan.txt, I find under the waypoint list LOWK with 238@1 (I assume this as wind direction and speed ?). Example activeflightplanwx.txt : DepartureMETAR=LOWL 121320Z AUTO 30004KT CAVOK 07/03 Q1019 NOSIG DestinationMETAR=LOWK 121320Z VRB01KT 9999 FEW060 07/02 Q1022 NOSIG AlternateMETAR= AverageWinds=280@14 AverageHeadwind=-1.2 AverageTemperature=-1.9 CruiseAltitude=11500 CruiseSpeed=200 LOWL 253@5(8) 267@22(1) 262@29(-3) 282@35(-12) 314@28(-23) 318@33(-35) 316@47(-52) 320@50(-60) 322@50(-62) 299@29(-58) 295@29(-61) 278@41(-63) LIMRA 253@5(8) 267@22(1) 262@29(-3) 282@35(-12) 314@28(-23) 318@33(-35) 316@47(-52) 320@50(-60) 322@50(-62) 299@29(-58) 295@29(-61) 278@41(-63) TOC 253@5(8) 267@22(1) 262@29(-3) 282@35(-12) 314@28(-23) 318@33(-35) 316@47(-52) 320@50(-60) 322@50(-62) 299@29(-58) 295@29(-61) 278@41(-63) GRZ 263@6(6) 284@15(1) 289@19(-2) 292@16(-11) 328@23(-24) 342@35(-36) 337@54(-52) 338@50(-60) 334@39(-60) 305@28(-58) 296@28(-62) 283@38(-64) TOD 238@1(6) 278@7(1) 280@15(-2) 284@17(-11) 332@25(-24) 343@39(-35) 335@53(-51) 339@50(-59) 337@48(-61) 298@28(-59) 299@25(-61) 284@39(-64) WK824 238@1(6) 278@7(1) 280@15(-2) 284@17(-11) 332@25(-24) 343@39(-35) 335@53(-51) 339@50(-59) 337@48(-61) 298@28(-59) 299@25(-61) 284@39(-64) KFT 238@1(6) 278@7(1) 280@15(-2) 284@17(-11) 332@25(-24) 343@39(-35) 335@53(-51) 339@50(-59) 337@48(-61) 298@28(-59) 299@25(-61) 284@39(-64) WK833 238@1(6) 278@7(1) 280@15(-2) 284@17(-11) 332@25(-24) 343@39(-35) 335@53(-51) 339@50(-59) 337@48(-61) 298@28(-59) 299@25(-61) 284@39(-64) LOWK 238@1(6) 278@7(1) 280@15(-2) 284@17(-11) 332@25(-24) 343@39(-35) 335@53(-51) 339@50(-59) 337@48(-61) 298@28(-59) 299@25(-61) 284@39(-64) My question: On what information relies P2A ? Is it DestinationMETAR (VRB01KT) or the last waypoint LOWK 238@1 (I guess it's wind direction and strength ?) ? In my opinion, ASP3Dv4 (Version 7410) is incorrect in injecting the "wind lock" feature into P3D and showing RW28 into its flight plan briefing but just writing "VRB01KT" into the external files in its weather folder. So I thought about upgrading to the newer "ASP3D for P3D V5 and P3D V4",but - as its not a five bucks shopping - I want to be sure, this bug (or feature) doesn't hit me again in this newer program version. Could some user of ASP3D for P3D V5/V4 state that P2A would get the wind lock corrected information from the newer ASP3D ?

Have you checked your spam folder ? In my cereproc account, I see all files from my first login in 2019. Since 2021, voices are delivered as one combined installer "CereVoiceEngine.exe", I think, it loads all voices at installation time, so by executing this "CereVoiceEngine.exe" (it's the same file for all my orders in the past), even after re-installing Windows, I got all voices I have bought in the past. I cannot find any hint on "7 days", neither in their FAQ nor in their "Terms & Conditions"

Did you enable access for P2A ? https://support.microsoft.com/en-us/windows/turn-on-app-permissions-for-your-microphone-in-windows-10-94991183-f69d-b4cf-4679-c98ca45f577a

Not sure if I had the same problem today (P3D), but similar behaviour. Update to Beta 9, Departure from LOIJ (Info act as tower), everything's fine. Switched to LOWI ATC, got airport somewhere, approached to LOWI, switched between LOWI ATIS and LOWI ATC, finally got one message from LOWI ATC, no controller response. Reinstalled 8Q (inflight), reconnected, no communication to ATC possible (while chatter continued). Checked P2A log, found stack trae: Pilot2ATC_2021.exe Information 0 SAPI does not implement phonetic alphabet selection. at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo) at System.Environment.get_StackTrace()

So how does P2A get its frequencies, asks it Prepar3D (so maybe a bug in ORBX LOWI may influence P2A) ? Hmm...if P2A uses only its internal Navigraph database, there should be no influence of ORBX (as ORBX LOWI has some quirks). It's reproducable: with Beta 6 the problem doesn't occur, just from Beta 7 onwards. Oh, it's not only the display - P2A talks "ATIS" after 120.10 changes from LOWI TWR to LOWI ATIS. Btw the initial LOWI ATIS is kept, so I have two ATIS frequencies for LOWI. When I have a little more time, I will modify the route to see if it's specific to an area on this route.

BTW, I talk about ORBX LOWI, not the default one.

Too early. It changes on the fly 🙃 First test in LOWI ground, LOWI TWR 120.10 ok: https://www.dropbox.com/s/v69roo217qsaqtd/Screenshot - 10_8_2022 %2C 8_42_47 AM.png?raw=0 Afterwards, a short flight from LOIJ to LOWI, on ground and takeoff frequency shown ok shortly after take-off and turn north : LOWI 120.10 has changed from TWR to ATIS: https://www.dropbox.com/s/pwptutc8u1qw2oi/Screenshot - 10_8_2022 %2C 12_19_22 PM.png?raw=0 Strange: P2A's talkback for 120.10 is EDQC ATIS - about 200 miles away ! I cannot remember happen this up to Beta 6.

Public Beta 8B shows LOWI 120.10 as TWR again. Thanks !

OK, maybe just one picture per post. Today approach to LOWI, P2ATC 7B shows 120.10 as ATIS: Beta 7B Picture: LOWI 120.10 is ATIS After fallback to Beta 6, 120.10 works again as ATC: BETA 6 Picture LOWI 120.10 is ATC again

Hi Dave, after updating to Beta 7B, I've lost ATC frequency in LOWI. The official ATC frequency that worked up to last week: 120.10 is now shown as "ATIS". As workaround, I use Radar Control 119.27, it works as ATC. Has there anything changed regarding Navigraph ?