StephanG2312

Same issue here. It seems to be dependent on the flightplan itself. LFMN -> EDDV = "INVALID F-PLN UPLINK"; LFMN -> EDDS = no problems. Never had that with the A320NX or another aircraft before. Maybe updating the AIRAC will solve the issue.

Renaming the folder to "z_..." didn't help, after recompiling the library with 2.6.6 the stock airport is displayed again. If it helps you or others, I'm happy to assist and provide the files you need; in this case please let me know what exactly you need and where to find. Otherwise it's fine for me to use 2.6.5.rc1 to recompile the library if needed and work with 2.6.6.

Made some checks: - Reinstalling of EDDK and rebuilding of scenery library had no effect - Used 2.6.5.rc1 and rebuilded the library and now it works again: So it seems the issue is in building up the scenery library in 2.6.6?

- Before means a couple of days ago, maybe before installation of 2.6.6; as I haven't used EDDK for approx. 1 week, I can't say it for sure; but I'm 100% sure with the beta it has worked - Nothing - No - Circle 2013 rev1 Let's see if reinstalling of EDDK has an effect in case something without my knowledge has changed within the installation.

Hi Alex, thanks for your reply. Don't know if it's a DRM locked airport, but I don't think so. Where can I find the BGL.fsarchive files? Before it was visible as described at LNM. All other Aerosoft airports, I still can see them with gates and accurate building shapes. So I don't think that this is the issue. Will un- and reinstall EDDK tomorrow and run again the scenery library at LNM to see if it makes a difference. Brgds Stephan

Dear all, since a couple of days (maybe since installation of 2.6.6) I have an issue with EDDK from Aerosoft: Before I was able to see the gates with it's number as well as the shape of the airport buildings. Now, I only have parking positions and also the buildings look different, maybe just the standard scenery is displayed? I've changed nothing to the EDDK installation and there wasn't any update available the last weeks. Any idea what can be the issue? Brgds Stephan

Dear Dave, I'm currently on day 2 of my test phase and I'm pretty impressed. P2A works well with my MSFS2020. But there is one thing I'm really confused meanwhile: Implementing X ATC Chatter into P2A. So I have two questions: 1. Can the files from X ATC Chatter which I purchased yesterday via x-plane. org be played with P2A 2.6 and MSFS2020? 2. Here in that forum I read somewhere that a folder "Regions" have to be created under "ATC-Chatter" with the regions inside (see attached picture), in the YT video of Stick and Rudder Studios the "Controllers" folder is placed into "ATC_Chatter" without "Regions" folder. What is correct? With my setup I currently don't hear any regional chatter, only the sound from the "radio-static" file I guess. Brgds Stephan

Dear Bryan, thanks a lot. As the settings haven't changed during updating previous versions, I didn't realize that they have changed this time for what reason ever. I even wasn't aware that different modes are available. 🤭 So easy to make me happy again! Thanks & Brgds Stephan

Dear Dev's, I want to express my disappointment that with 1.4 the individual steering during pushback via Z axis is gone and the direction can just be initiated once by using the X axis. With the previous option you had the chance to correct the direction to bring the plane exactly on the taxiway (or correct the direction if you realized you mixed it up 😉). The need to hold the joystick all the time didn't bother me. What are others thinking? Personnally, I really wish the old way of steering back. Or maybe it's possible to let the user choose in one of the next versions? Thanks & Brgds Stephan