Jump to content

Archived

This topic is now archived and is closed to further replies.

Hans Hartvelt

RC doesn't read cruise altitude from flightplan

Recommended Posts

I make flightplans with FS Commander 9.0. Below you see a flightplan from Amsterdam Schiphol to Stockholm Arlanda. The cruise altitude has been set to 33.000 feet. Nevertheless, RC doesn't read this cruise altitude, but uses the last cruise altitude that is manually set in the controller info window. Why doesn't RC read the cruise altitude from the last loaded flightplan? [Flightplan]AppVersion=9.1.40901title=EHAM to ESSA description=EHAM, ESSA type=IFRroutetype=1cruising_altitude=33000departure_id=EHAM, N52* 18.28', E004* 45.96', -000013.00departure_position=GATE C 12destination_id=ESSA, N59* 39.11', E017* 55.11', +000121.00departure_name=Schipholdestination_name=Arlandaalternate_name=waypoint.0=, EHAM, , EHAM, A, N52* 18.28', E004* 45.96', -000013.00,waypoint.1=KK, ANDIK, , ANDIK, I, N52* 44.36', E005* 16.22', +000000.00,waypoint.2=KK, KEKIX, , KEKIX, I, N52* 46.94', E005* 21.68', +000000.00,waypoint.3=KK, AGISU, , AGISU, I, N53* 52.90', E006* 29.96', +000000.00,waypoint.4=KK, KUGAL, , KUGAL, I, N55* 00.00', E007* 37.23', +000000.00,waypoint.5=KK, VES, , VES, I, N55* 36.18', E008* 17.99', +000000.00,waypoint.6=KK, INTET, , INTET, I, N56* 13.57', E009* 24.68', +000000.00,waypoint.7=KK, RADIS, , RADIS, I, N56* 32.50', E009* 59.70', +000000.00,waypoint.8=KK, GOTEX, , GOTEX, I, N57* 12.29', E011* 16.37', +000000.00,waypoint.9=KK, LOBBI, , LOBBI, I, N57* 19.08', E011* 29.88', +000000.00,waypoint.10=KK, BAK, , BAK, I, N57* 33.31', E011* 58.61', +000000.00,waypoint.11=KK, DEGAV, , DEGAV, I, N57* 43.68', E012* 20.41', +000000.00,waypoint.12=KK, LABAN, , LABAN, I, N58* 10.16', E013* 17.65', +000000.00,waypoint.13=KK, DETSO, , DETSO, I, N58* 35.99', E014* 15.86', +000000.00,waypoint.14=KK, PELIT, , PELIT, I, N59* 12.02', E015* 41.26', +000000.00,waypoint.15=KK, TORVA, , TORVA, I, N59* 24.74', E016* 12.71', +000000.00,waypoint.16=KK, ARS, , ARS, I, N59* 35.17', E016* 39.02', +000000.00,waypoint.17=KK, ELTOK, , ELTOK, I, N59* 49.46', E016* 59.39', +000000.00,waypoint.18=, ESSA, , ESSA, A, N59* 39.11', E017* 55.11', +000121.00,


Hans Hartvelt
The Netherlands
forumbanner1.jpg

 

Share this post


Link to post
Share on other sites

what value did you enter in the rc options screen? what direction of flight is this plan? i'd have to see the .log file, to see why rc chose a different cruise altitude. instructions pinned to the top of the forum. important to hit debug before loading the .pln jd

Share this post


Link to post
Share on other sites
I make flightplans with FS Commander 9.0. Below you see a flightplan from Amsterdam Schiphol to Stockholm Arlanda. The cruise altitude has been set to 33.000 feet. Nevertheless, RC doesn't read this cruise altitude, but uses the last cruise altitude that is manually set in the controller info window. Why doesn't RC read the cruise altitude from the last loaded flightplan? [Flightplan]AppVersion=9.1.40901title=EHAM to ESSA description=EHAM, ESSA type=IFRroutetype=1...
Interesting, I loaded this up and the cruise altitude showed up just fine. DJ

Share this post


Link to post
Share on other sites

Hello Ubursu, Thank you for thinking with me. I sent the log file to JD as he asked and I am waiting for his answer. Maybe he will find something in the log file.


Hans Hartvelt
The Netherlands
forumbanner1.jpg

 

Share this post


Link to post
Share on other sites
Hello Ubursu, Thank you for thinking with me. I sent the log file to JD as he asked and I am waiting for his answer. Maybe he will find something in the log file.
I noted two things that are different from the plans that I produce with FSBuild, the routetype is 1 rather than 3 and the appversion is different. On the other hand, your plan loaded fine for me (with the proper cruise altitude) in RC exactly as you posted it so I'm not sure just what's going on on your setup... I'm running the latest 4.3 version. Hope JD can tell from the log. DJ

Share this post


Link to post
Share on other sites

The latest version is 4.3 build 4385. I too loaded your posted flight plan correctly. In the RC Controller tab it shows 330 (with the two trailing zeros filled in by RC. I did note some extra fields ahead of the waypoints. Build 3845 correctly filters these out. You can see the build number on the RC splash screen and at the top of he RC screen. The only other possibility might be that a character might have been omitted in pasting the flight plan into the browser. A log will show how RC read the plan. To check the plan as it was created, you have to zip up the plan file and e-mail it. If you like PM me with your e-mail address and I'll return mine. Then you can send the zipped up plan file to me for examination. I assume this is happening with multiple plans? If this is not a unique issue then it is worth pursuing. Please note that you can set the cruise altitude directly on the Controller page by entering the cruising altitude dropping the last two numbers.

Share this post


Link to post
Share on other sites

Hi, just read this post and I find I have the same problem. If I set the cruise altitude directly in the Controller page, the next time I loada FS Planner flight plan say at a lower level RC will not read the new level and will still have the old level set. I only useFS Navigator derived plans which I then save in FS Flight Planner then load into RC.


R C Stevens

Share this post


Link to post
Share on other sites

I would not recommend modifying or saving a plan exported by FSNav to FS format loaded into FSNav. Load the plan into RC as exported directly by FSNav into FS format. Anyway, I always proof the loaded plan on the Controller page for the various data. I also note my FSBuild exported .pln files state routetype=3 , not 1 as posted. Unfortunately I do not see in the available FS9 SDK definitions for the .pln file.

Share this post


Link to post
Share on other sites

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
  • Donation Goals

    AVSIM's 2020 Fundraising Goal

    Donate to our annual general fundraising goal. This donation keeps our doors open and providing you service 24 x 7 x 365. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. We reset this goal every new year for the following year's goal.


    43%
    $10,910.00 of $25,000.00 Donate Now
×
×
  • Create New...