sq024

Dave, I came across a small issue during decent: route LHBP DUZL2R DUZLA VEBAL KUDUL KUDU1Z LDZD - IFR-flightplan cruising FL360 - Short before ToD I get the instruction "Begin descent at pilot discretion", no assigned altitude - 10 nm further I start decent, on flightmap and in flightplan after ToD. - 5 min later I get the instruction "Climb and maintain FL360" - Instruction to climb stops after requesting decent to FL100. Rob

thanks for the support. Rob

I'm using MSFS2020. MakeRunways I always used for V2. Let's leaf the data management for later, I have a workaround. Rob

Dave, While trying to figure out how to add airways to the flightplan I noticed the following: I want to create the following flightplan: EHEH/21 VELN4K VELNI Y869 SUMOP L179 MEVEL Y850 BASUM Z78 WSN T903 RIBSO RIBS2D EDDH/15 Using simbrief import by copy/paste the plan in the text-box the plan is correct created in P2A with all in between waypoints. Using the direct import from simbrief (3rd option in import-menu) the flightplan is created but last leg of an airway is always a DIRECT in stead of the name of the airway. No big deal. When creating the flightplan without import the main issue arise, these are my steps: Start new plan, Add Wpt EHEH and EDDH Click App-Dep procedures in flightplan window and add sid VELN4K and star RIBS2D Select VELNI in flightplan (or select in the map) and add airway Y869 to SUMOP, no result Add Wpt SUMOR manual, select waypoint and add airway L179 to MEVEL, last waypoint MEVEL is not loaded in the plan Add Wpt MEVEL manual, select waypoint and add airway Y850 to BASUM, last waypoint is not loaded. So when manual creating a flightplan with airways the last waypoint is not loaded in the flightplan. Regards, Rob

Dave, Some feedback on my progress. Did a data migration of my P2ABaseData.mdf file and update to version 0.0.30.n Pros: - save, load and import of taxiways works fine. - taxiways are used in the taxi-instructions Neg: - import of gates is broken, nothing is imported at least is not shown on the map or saved. Loading of gates that were saved in the previous version works fine. - not all taxiways/runways are shown on the map in data management after loading. They do exist in the database because they are used in taxi-instructions, so I assume it's a display problem (maybe just on my system) - imported data is often too complex for P2A to workout a taxi-route especially on major airports so there is a need for maintaining taxi-data and gates. - maintaining data is nearly impossible in data management. Most options in the context-menu (right mouse-click) don't work (delete, add gate, add taxi-way etc). - dragging objects to the correct position have a very slow response in the display. Might be related to the previous mentioned display problem. I have an issue when manual creating airways in flightplans but will make a seperate post for that. Regards, Rob

Dave, I did as you suggested but with limited effect. I tried to work out the logic behind the behaviour but no success. I made a backup of my existing version 0.0.29, uninstall it and installed the full version in a new directory. Here are my observations, I hope they help you to figure out what is going on: - After start of the program no taxi-data is shown for any airport in data management. I wonder if airport data is only available in data manager after you create/load a flight-plan, most of my testing is done without a flightplan. - Importing taxiways with MakeRwys works most of the time but sometimes only the runways are shown. - Importing and saving taxiways creates a DataICAO.txl (i.e. DataRJAA) file in the root-directory of 1kb with only header-information except when you mark the "Override User Modified Airports" option. Then it creates a file of up to 6MB for large airports. After restarting P2A in data management it shows the taxiways of the just imported airport but not for airports I imported the day before. - Loading a saved airport works most of the time but sometimes it only loads runways or taxiways without runways. I suspect that this is more a display problem because saving the airport again creates a txl-file with the same content as loaded. - There is a Data\P2ABackups folder in the root-directory where only glx-files are stored. In V2 it also contains txl-files. There are 2 options left that I can try: 1. Use Data Updater to migrate my V2 P2ABaseData.mdf into V3, I did that a few months ago to get my V2 modified and saved airports in V3. 2. I can use Data Manager to import all airports from MakeRwys-files but but prefer not to do that because I have 150 add-on airports that I fly from/to and don't need the rest of the 46K-airports of MSFS in my system. Regards, Rob

Dave, Since one of the recent updates of V3 the program loads without taxiway and runway information . The "show" function in data management shows only the map. The result is that the taxi-instruction is limited to "taxi to runway xx" or "taxi to gate xyz" (btw gate information is loaded). I can load taxiway information of saved airports but to activate them I have to restart the program and everything is lost again. I noticed that when I load saved taxiway information of an airport the pop-up is looking for a filename ICAO_Taxiways (filename used in V2) where the airports are saved as ICAO.txl. Maybe this is an indication of where the problem is. I can't find any errors in the log-files but can of course send one to you. Regards, Rob

Hi Dave, Found a small bug in the use of the "Load Airway"-function take as an example: EGPD/16 DCT GLESK P600 FENIK L612 CALDA DCT MCT JACK1M EGLC/09 Using the function on GLESK the pop-up window shows airway P600 and its waypoints, the second time you use the function on FENIK it shows L612 with the waypoints of P600. Regards, Rob

Dave, That was what I did. While flying the STAR I requested the next altitude restriction in the arrival (this was before you explained the difference between "fly the xxxx Arrival" and "descend via the xxxx Arrival"). The pop-up referred to a waypoint in the SID. Now with my current knowledge I know that I shouldn't ask for the lower altitude when instructed to "Fly the approach". You can leave it for now, If it happens again I will make a report. Thanks for the support Rob

Thanks David, This helped me a lot. My next flight was flawless with P2A assigning my SID, STAR and Approach. Altitude assignments were aligning to STAR-entrypoint and altitude restrictions in the STAR. Rob

Thanks Dave, I understand. I don't let P2A determin my SID,STAR and Approach (switchd that off in Config) so I enter the complete plan before departure. Not realistic but helps to keep the different add-ons aligned. I assume the pop-up was not correct. Rob

Hi Dave, I have a question about the TOD calculation and found what I think is a bug. Version 2.0.1.5, cycle 1609, route -EDDL/23L N0452F370 MODR1T MODRU Z283 SUMAS UZ283 RITAX UT27 GTQ UN852 BALSI BALS8C LFML/31R. FL370, Plan GS 350, Descent rate 1500 FPM, TOD Dist 31.1 NM In the plan the TOD is calculated between GIRKU and BALSI on airway UN852, this is much further away then the 31.1 NM mentioned in the top of the screen. What's the difference? I saw the response from Helge on my previous report but like to understand. During descent I request a lower altitude and get a pop-up telling me "Minimum altitude restiction: Cruise altitude set to Minimum SID altitude at MODRU". As the message says MODRU is part of the SID and I'm flying the STAR. Regards, Rob

Thanks Helge, very helpful info. Still I think something is wrong with the TOD calculation represented in the P2A screen but will make a seperate report for that. Rob

Hi, I'm not always getting a new FL on TOD but as I get the instruction to fly the assigned STAR I request a decent to the next altitude. Something else I have experienced in that case is that later in the descent TOD shows up as the next waypoint where it is not in the flightplan. As soon as I have an example I'll post a report for Dave. Rob

Hi Dave, I have some observations you might want to look into. They could be related to my previous report about double entries in the airways-list. Version is 2.0.1.5 and cycle is 1609. Route: ENZV rw36 RUMO1H RUMOG DCT MITSI DCT AMADA UZ705 PAM UP62 TEBRO TEBR1G EDDL rw23R 1. After entering ENZV, EDDL and the SID the next waypoint is a direct to MITSI - I can add MITSI via the map ('add to flightplan') - I can add MITSI via the Wp+-button - I cann't add MITSI via the waypoint option 'Insert After' on RUMOG. 2. On waypoint AMADA I select the airway UZ705 to PAM. The leg is added but without the in between waypoint MOKUM. It works if I first add UZ705 to MOKUM and then on MOKUM UZ705 to PAM. 3. At EDDL the active runway is 23L in P2A but that is a Departure runway so I select as STAR 23R TEBR1G. - I get an error-message that the flightplan should have a Cruise Altitude and Planned Ground Speed. I'm pretty sure I would get that message in previous versions only after hitting the Validate-button. - After adding FL and GS I try again rw23R TEBR1G, the STAR is added but still with rw23L - I unload the STAR and select only the ILS approach on 23R with transition TEB23. Now I get rw23R assigned in the plan. Does this mean that if the last waypoint in the flightplan is also a transition in the approach you don't select a STAR or should I be able to select the STAR on rw23R and get rw23R as the active landing runway. Just not sure what the procedure is. Overall no serious bugs because there is an easy way around it. Regards, Rob P.S. Just noticed that after step 2 in point 3 I can select an ILS-approach on rw23R transition BOT so no issue. Remains my question about direct an approach or first a STAR,