December 27, 201411 yr Hello, I realized a problem with the default flight planner of P3D version 2.4: If I input a specific cruising altitude of for example 6000 ft and save the flight, then this cruise altitude value is getting lost. If I retrieve the flight, then I don’t find the saved cruising altitude, but a fantasy value. This fantasy value never is four digits or above, but two or three digits only. Is this a bug of Prepar3D 2.4, or is this a problem with my installation? Can I take any action? Kind regards Arndt Arndt Laube P3Dv4.5 and P3Dv5 Brunner CLS-E Yoke & Rudder, 2x Logitech Throttle, several GoFlight modules Intel i7 9700K, 16 GB RAM, Geforce 1080Ti, monitors 3840 x 2160 and 1360 x 768
December 27, 201411 yr I don't know if this is bug or feature, however, you can try external VfrFlight planner (http://vfrflight.org). It is very lightweight and easy to use, and can calculate your cruising altitude from elevation data, so you don't have to even think about it. Generate flight plan, then load it in P3D and start your flight. You can also SimConnect to it and follow your position on the map. Lukasz Lukasz Kulasek i7-8700k, RTX 2080 TI, 32 GB RAM, ASUS TUF Z370-PRO Gaming, Oculus Rift CV1
December 27, 201411 yr Hello, I realized a problem with the default flight planner of P3D version 2.4: If I input a specific cruising altitude of for example 6000 ft and save the flight, then this cruise altitude value is getting lost. If I retrieve the flight, then I don’t find the saved cruising altitude, but a fantasy value. This fantasy value never is four digits or above, but two or three digits only. Is this a bug of Prepar3D 2.4, or is this a problem with my installation? Can I take any action? Kind regards Arndt All work ok here. Are you using OLD flight plans (previous P3D version) or creating new ones now? Look in your flight plan folder : C:\Users\yournamehere\Documents\Prepar3D v2 Files open your flight saved plan in a text editor: My last saved flight plan just looks ok with 18000 feet .... and it loads with 18000 feet . <?xml version="1.0" encoding="UTF-8"?> <SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>testAltsaved</Title> <FPType>IFR</FPType> <RouteType>HighAlt</RouteType> <CruisingAlt>18000</CruisingAlt> Best Regards, Vaughan Martell PP-ASEL KDTW
December 27, 201411 yr Author Hello Vaughan, I am not using old plans, but only new one's. They are in the same format as yours. But: nearly all flight plan files do contain as cruising altitude not values like 5000 ft, 5500 ft or 6000 ft (this is my usual cruising altitude), but values like 55 ft, 524 ft and so on. I changed the cruising altitude values in all my flight plan files outside P3D back to my usual cruising altitude and then saved the file. Afterwards I reopened these files within P3D and cruising altitude again has changed to these strange values like 55, 524 and so on. I don't have any idea regarding the source of the problem. Regards Arndt Arndt Laube P3Dv4.5 and P3Dv5 Brunner CLS-E Yoke & Rudder, 2x Logitech Throttle, several GoFlight modules Intel i7 9700K, 16 GB RAM, Geforce 1080Ti, monitors 3840 x 2160 and 1360 x 768
December 27, 201411 yr Post a screenshot(s) of your NavLog and saved flight plan (like I did above) for a short 6000 crz flight. I did KDTW KTOL LOW ALT/IFR planThis is what I see This is the plan: <?xml version="1.0" encoding="UTF-8"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <FlightPlan.FlightPlan> <Title>dtwtol-test</Title> <FPType>IFR</FPType> <RouteType>LowAlt</RouteType> <CruisingAlt>4000</CruisingAlt> <DepartureID>KDTW</DepartureID> Best Regards, Vaughan Martell PP-ASEL KDTW
December 27, 201411 yr Author Here is the screenshot ... So far the cruising altitude is stable and didn't change, even after closing and restarting P3D for sebveral times. Arndt Laube P3Dv4.5 and P3Dv5 Brunner CLS-E Yoke & Rudder, 2x Logitech Throttle, several GoFlight modules Intel i7 9700K, 16 GB RAM, Geforce 1080Ti, monitors 3840 x 2160 and 1360 x 768
December 27, 201411 yr Author Arndt Laube P3Dv4.5 and P3Dv5 Brunner CLS-E Yoke & Rudder, 2x Logitech Throttle, several GoFlight modules Intel i7 9700K, 16 GB RAM, Geforce 1080Ti, monitors 3840 x 2160 and 1360 x 768
December 27, 201411 yr Do another plan but let the P3D flight planner create the route ...and see what happens. I want it to look like mine so I can see what is happening. For example .. your CRL should show a VOR freq ... and it does not. Your photos are too small .. hard to read. Best Regards, Vaughan Martell PP-ASEL KDTW
December 27, 201411 yr Ok, I can read your last screenshot now thanks for making it bigger. The altitudes are correct .. 4000 crz and KTOL is 684 feet. Correct? **** Do another plan (low alt IFR) but let the P3D flight planner create the route ...and see what happens. I want it to look like mine so I can see what is happening. Best Regards, Vaughan Martell PP-ASEL KDTW
December 28, 201411 yr Author Please see what I got from the P3D flight planner. Different from yours. Arndt Laube P3Dv4.5 and P3Dv5 Brunner CLS-E Yoke & Rudder, 2x Logitech Throttle, several GoFlight modules Intel i7 9700K, 16 GB RAM, Geforce 1080Ti, monitors 3840 x 2160 and 1360 x 768
December 28, 201411 yr Did you let P3D generate your route? List the steps you do to have P3D create your flight plan? Then I will test your steps here. Also, you need to make one photo of each the Plan and then the Navlog so they are bigger in your post ... I cannot read them. So you will post 2 screenshots here instead of one. Best Regards, Vaughan Martell PP-ASEL KDTW
Create an account or sign in to comment