JKawai

Hi Dave Thanks for this. I've email you a log for the last flight I did where ATC asked me to cross an intersection at FL320 which resulted in the descent after that being 5000fpm, and ATC demanding I reduce to 250kts (I was at 300, with spoilers). My descent rate set in P2A is 2200, but I'll drop it to 1800. Is this behaviour normal though? Thanks

Done a handful of IFR flights now with the trial and unfortunately am being put off very quickly, and was hoping someone could maybe reassure me or explain to me why on each flight I'm having issues. On one flight I asked for vectors to the ILS at LIRF to cut out the drawn out arrival, which initially seemed fine. I seemed to be on an intercept heading, and then ATC put me on a 90º angle to intercept about 2 miles away from it, and told me to contact tower. Obviously on turning to this heading (didn't want to ignore them) I shot straight through the localizer, so then I'm trying to get back on it, whilst tuning tower and checking in. Also had some odd crossing restrictions which don't match my VNAV path - where I'll be asked to cross a waypoint at an arbitrarily high altitude, then follow the arrival, which has much lower altitude restrictions immediately after, to the point where I have to reign in the speed and really anticipate this huge increase in negative VS. More annoyingly is the RT. For example, on approach, I am asked constantly to read back the entire arrival over and over again. For example, "cross INTXN at FL230 then descend on the XXXXX arrival with the YYYYY transition to 6000', for the ILS 18R with the ZZZZZ transition at AAAA airport" (thereabouts). Then later on, when I'm cleared for the ILS, repeating the entire thing but this time with the word 'cleared' in it. On top of that, saying the entire airport name... I've never known pilots to read back the name of the airport in any arrival readbacks, let alone a landing clearance. "Cleared to land runway 18R at Madrid Barajas Adolfo Suarez airport, callsign". It's just "cleared to land runway 18R, callsign". Same with "request push and start". "Request pushback and engine start" - I mean it's obvious you're starting the engines. That's a minor one. The taxi clearances are the worst. They are always incredibly convoluted, and whilst I'm willing to accept this given the complexity of some airports and the software may not understand how to join certain taxiways together, at EGLL it will spell out 'LINK 21' as Lima India November Kilo Two One. Moreover, just now at LEMD I didn't bother reading back the clearance verbally, I just pressed 'Say It' to get it over and done with. Yet apparently that was insufficient, as I got the entire clearance again. I pressed 'Say It' again... same again. I just ignored her that time. Looks like the copilot was omitting the callsign for some reason, but why does this warrant the entire clearance again? IBERIA Three Four Six Four Taxi to Runway One Eight Right Via taxiways Echo Bravo Six, Echo Bravo Seven, November One Zero, November Niner, Bravo November Three, Bravo Eight, Bravo Seven, Zulu Seven, Zulu Eight, Zulu Whiskey Three, Zulu Whiskey Four, Zulu Whiskey Five, Zulu One Four, November Oscar November Echo, Hold Short Runway Three Six Left ~ Taxi to Runway One Eight Right Via taxiways Echo Bravo Six, Echo Bravo Seven, November One Zero, November Niner, Bravo November Three, Bravo Eight, Bravo Seven, Zulu Seven, Zulu Eight, Zulu Whiskey Three, Zulu Whiskey Four, Zulu Whiskey Five, Zulu One Four, November Oscar November Echo, Hold Short Runway Three Six Left IBERIA Three Four Six Four Taxi to Runway One Eight Right via Taxiways Echo Bravo Six Echo Bravo Seven November One Zero November Niner Bravo November Three Bravo Eight Bravo Seven Zulu Seven Zulu Eight Zulu Whiskey Three Zulu Whiskey Four Zulu Whiskey Five Zulu One Four November Oscar November Echo Hold Short Runway Three Six Left IBERIA Three Four Six Four; IBERIA Three Four Six Four Taxi to Runway One Eight Right Via taxiways Echo Bravo Six, Echo Bravo Seven, November One Zero, November Niner, Bravo November Three, Bravo Eight, Bravo Seven, Zulu Seven, Zulu Eight, Zulu Whiskey Three, Zulu Whiskey Four, Zulu Whiskey Five, Zulu One Four, November Oscar November Echo, Hold Short Runway Three Six Left ~ Taxi to Runway One Eight Right Via taxiways Echo Bravo Six, Echo Bravo Seven, November One Zero, November Niner, Bravo November Three, Bravo Eight, Bravo Seven, Zulu Seven, Zulu Eight, Zulu Whiskey Three, Zulu Whiskey Four, Zulu Whiskey Five, Zulu One Four, November Oscar November Echo, Hold Short Runway Three Six Left IBERIA Three Four Six Four Taxi to Runway One Eight Right via Taxiways Echo Bravo Six Echo Bravo Seven November One Zero November Niner Bravo November Three Bravo Eight Bravo Seven Zulu Seven Zulu Eight Zulu Whiskey Three Zulu Whiskey Four Zulu Whiskey Five Zulu One Four November Oscar November Echo Hold Short Runway Three Six Left IBERIA Three Four Six Four; IBERIA Three Four Six Four Taxi to Runway One Eight Right Via taxiways Echo Bravo Six, Echo Bravo Seven, November One Zero, November Niner, Bravo November Three, Bravo Eight, Bravo Seven, Zulu Seven, Zulu Eight, Zulu Whiskey Three, Zulu Whiskey Four, Zulu Whiskey Five, Zulu One Four, November Oscar November Echo, Hold Short Runway Three Six Left ~ Taxi to Runway One Eight Right Via taxiways Echo Bravo Six, Echo Bravo Seven, November One Zero, November Niner, Bravo November Three, Bravo Eight, Bravo Seven, Zulu Seven, Zulu Eight, Zulu Whiskey Three, Zulu Whiskey Four, Zulu Whiskey Five, Zulu One Four, November Oscar November Echo, Hold Short Runway Three Six Left IBERIA Three Four Six Four Taxi to Runway One Eight Right via Taxiways Echo Bravo Six Echo Bravo Seven November One Zero November Niner Bravo November Three Bravo Eight Bravo Seven Zulu Seven Zulu Eight Zulu Whiskey Three Zulu Whiskey Four Zulu Whiskey Five Zulu One Four November Oscar November Echo Hold Short Runways Three Six Left; IBERIA Three Four Six Four; IBERIA Three Four Six Four Taxi to Runway One Eight Right Via taxiways Echo Bravo Six, Echo Bravo Seven, November One Zero, November Niner, Bravo November Three, Bravo Eight, Bravo Seven, Zulu Seven, Zulu Eight, Zulu Whiskey Three, Zulu Whiskey Four, Zulu Whiskey Five, Zulu One Four, November Oscar November Echo, Hold Short Runway Three Six Left ~ Taxi to Runway One Eight Right Via taxiways Echo Bravo Six, Echo Bravo Seven, November One Zero, November Niner, Bravo November Three, Bravo Eight, Bravo Seven, Zulu Seven, Zulu Eight, Zulu Whiskey Three, Zulu Whiskey Four, Zulu Whiskey Five, Zulu One Four, November Oscar November Echo, Hold Short Runway Three Six Left IBERIA Three Four Six Four At the moment this feels like a lot of effort, constantly battling to be understood - even by the copilot. Tell me I'm doing something wrong? Thanks

Hmm, doesn't seem to work. See screenshot below. I've connected to the sim, I've switched weather sources to and fro, I've selected weather on the map... it's not pulling LEMD WX whereas XWeather does it immediately from the METAR.rwx, arguably more accurate as well as that's the weather I'm flying in. Never mind, I'll use XWeather. Thanks https://imgur.com/VUCgGlY

Hi, Having this issue with XP, SIM weather. Connected to the sim, weather doesn't update so can't see genuine active runway for planning purposes. Updates later on though. Is there not a 'refresh weather' option? Screenshot: https://imgur.com/Czd0oEi Many thanks

Hi, Trying to get my head round importing airports from XP11 into P2A, as all the gates and taxiways are incorrect until imported. I am first of all interested to know, is there a way of marking the airports as modified so I know which ones I have imported so far and which I have not, as it looks like for every flight I am going to have to import scenery for the taxiways and gates to be correct as according to the manual it seems with XP you can't do a mass import. Also, can you advise what the 'mark airports as unmodified' tickbox does? As no mention of it in the manual. Thanks

Hi again - please disregard all this now. I did a fresh install of windows because of some other issues and the database is fine now. Thanks!

Just to clarify, the GTN is definitely having a huge impact on frames. With avionics off everything is smooth as butter. As soon as the GTN comes on it is juddery. If I disable the GTN plugin it goes smooth again... I tried vulkan and it was unbearably juddery so I just went back to 11.41r2.

Both... very strange. See this video to see what I've got/what happens: https://www.youtube.com/watch?v=q6HWr4LZEkA

Hi Jean-Luc Thanks so much for the prompt reply. I think there was in fact an Oculus update. However, as is typical with sim troubleshooting, I'm now noticing issues *without* GTN running (even though before it was noticeably attributed to GTN through testing), and on removing a different plugin, I notice an improvement. So I'll be testing without the other plugin first before I get back to you fully. However, just to answer, I did try to update NVidia, it made things worse so I rolled back. Any XP update I will unfortunately not be doing because I have so much in perfect balance that it would just destroy the tweaking I've spent the last year doing. Windows 10 Home 1909 18363.1016 is my OS. But yes, like I say I'll get back to you if my issue is solved by disabling the *other* plugin. While I'm here though, interested to hear the reasoning (if possible to divulge briefly) why you think Process Lasso is not necessary - couple of years ago when I got all this kit (XP, Oculus) it seemed common knowledge that Process Lasso helped and I have noticed a difference using it by making changes to the XP exes and OVRServer exes, and adjusting the general power profile of the PC to not constantly switch itself off left right and centre as it wishes to 'save power' (despite being a gaming PC)... Cheers

Not sure as when I run the GTN installer it fetches and downloads its own trainer so unfortunately there's no option for me to just stick with one version. All airports outside the US are missing.

Thanks Bert - I have the jeppesen worldwide one selected.

Reinstalled the trainer as having performance issues and thought I'd try that. The trainer (which I use outside of the sim to look up airports) used to have all airports worldwide in it, now on reinstalling it only has US airports. Is there something I'm missing here. Rather odd. Thanks

In the last week or so I have noticed a dramatic hit to my performance in XP11 VR whilst GTN Simulator.exe is running (a process I've never seen running in Process Lasso until recently). Whenever the rxpGTN plugin is enabled in XP, performance takes a huge hit and if I launch the Oculus overlay whilst in-game, the frame rate in the overlay is about 1fps. This never happened before and it only happens whilst GTN Simulator.exe/rxpGTN is running. I am using a Nvidia GTX1070ti on an Intel i7 7700k 4.5ghz quadcore CPU. Windows 10. XP 11.41. The GTN is the latest version apparently as checking for updates says latest version installed. I have never had any issues before with performance until recently. I have read the bit in the manual about integrated/discrete GPU - there is no option on right clicking the .exe to select a GPU and I also doubt this is the issue as it shouldn't have just changed on its own in the last couple of weeks. Can anybody advise where I can begin trying to rectify what was absolutely fine until recently - would love to get back to simming instead of spending trillions of hours trying to fix issues that keep popping up at random. Many thanks EDIT: just to stress, this is a VR issue. I Dont see a performance hit on the 2d desktop version of what I'm seeing in the Oculus. The GTN seems to be directly affecting the Oculus performance even when the GTN window is hidden but the plugin is running in the background. It's odd because it used to be fine.

Thanks, although I can't find anything that specifically solves my issue. It says "An altitude constraint is invalid if it is added to a waypoint past the FAF" (it isn't - it IS the FAF) Transition to approach is enabled in AFMS, so that's not an issue. 4.3.3.6 says that when disabled "En route VNAV terminates at the waypoint prior to the FAF on approaches with vertical guidance". Can anybody else here shed light on what they do in this situation?

Hi, Trying to get VNAV to tell me my TOD etc but it's all greyed out and I get a MSG saying 'Upcoming flight plan leg not supported'. I have an ALT restraint at my FAF which is 1800'. Even if I DTO the VNAV on this waypoint, nothing changes - still no VNAV data. The enroute waypoints have their ALT populated with my current altitude, cruise altitude (FL199 or so the Garmin believes, actually FL200). Then there is a waypoint in descent that it has calculated I will be at around FL150. So the descent profile IS there in the plan, it's just not giving me any TOD/VS info. Any guesses? Thanks EDIT: I wonder if it's anything to do with there being a disconnect between PEPIS and the FAF: On the map view, PEPIS does not join the FAF, for some reason. EDIT 2: Just tried manually inputting CI20 and FI20 before the 'Approach' section. It let me enter FI20 first, then CI20 before it, with alt restraint 1800' at FI20. I then deleted the original CI20 but it would not allow deletion of FI20 post approach section. On adding alt restraint 1800' to the new FI20, the VNAV works. But now I have two FI20s, one '0nm' after the other, after the start of the 'approach' section. But presumably this isn't the official workaround? EDIT 3: Incidentally is there a way of having the VNAV required VS on the map view? Just spent most of my descent just now staring at the VNAV screen making sure the VS was correct, not much time to look at the map.