Jump to content
Sign in to follow this  
simbio

FSB build and RC4

Recommended Posts

Hi I need some further explanation on this problem wich i haven't solved http://forums.avsim.net/dcboard.php?az=sho..._id=18965&page=I normally create the FP in FSB and import in RC4 and the FMC levelDBut when I pass the waypoint in RC4.2 it dosen't go to the next WPT and of course rc4 ask to to go back and pass the WPT.Now I know that I can instruct the RC4 to bypass the WPT and also I know that I can set in the preference a big Heading Deviation but i just wondering if other user get the same problem with FSB I mean if the flight plan is offset from the fs9 database here two example look below:Another question to the support is when the RC4 load the .pln it read's the lat-lon coordinate or the WPT name because maybe this explain the problem.Thank youFabrizioFSB[flightplan]title=LFML to LSGGdescription=LFML, LSGGtype=IFRroutetype=3cruising_altitude=11000departure_id=LFML, N43* 26.07', E005* 12.49',+000069.00departure_position=32Rdestination_id=LSGG, N46* 14.12', E006* 06.42',+001411.00departure_name=MARSIELLE_PROVENCEdestination_name=GENEVA_COINTRINwaypoint.0=LFML, A, N43* 26.07', E005* 12.49', +000000.00,waypoint.1=AVN, V, N43* 59.43', E004* 44.47', +23000.00,waypoint.2=MTL, V, N44* 33.17', E004* 46.47', +33000.00,waypoint.3=ROMAM, I, N45* 06.09', E005* 09.48', +26000.00,waypoint.4=LTP, V, N45* 29.20', E005* 26.20', +18000.00,waypoint.5=BELUS, I, N45* 40.31', E005* 35.38', +17000.00,waypoint.6=PAS, V, N46* 09.49', E005* 59.59', +05000.00,waypoint.7=LSGG, A, N46* 14.12', E006* 06.42', +01411.00,FS9[flightplan]title=LFML to LSGGdescription=LFML, LSGGtype=IFRroutetype=1cruising_altitude=11000departure_id=LFML, N43* 26.20', E5* 12.90', +000068.90departure_position=32Ldestination_id=LSGG, N46* 14.26', E6* 6.32', +001410.76departure_name=Marseille/Provencedestination_name=Genevawaypoint.0=LFML, A, N43* 26.20', E5* 12.90', +000068.90,waypoint.1=AVN, V, N43* 59.72', E4* 44.78', +000000.00,waypoint.2=MTL, V, N44* 33.30', E4* 46.79', +000000.00,waypoint.3=ROMAM, I, N45* 6.17', E5* 9.80', +000000.00,waypoint.4=LTP, I, N45* 29.34', E5* 26.34', +000000.00,waypoint.5=BELUS, I, N45* 40.52', E5* 35.63', +000000.00,waypoint.6=PAS, V, N46* 9.82', E6* 0.07', +000000.00,waypoint.7=LSGG, A, N46* 14.26', E6* 6.32', +001410.76,


 

 

Share this post


Link to post
Share on other sites

i thought there was an fmc bug, where it forgets the first checkpoint, or something like that. i don't know the specifics, but it sounds awfully familiarjd

Share this post


Link to post
Share on other sites

>i thought there was an fmc bug, where it forgets the first>checkpoint, or something like that. i don't know the>specifics, but it sounds awfully familiar>>jdI have got an answer from ErnieAlston but I wondering if everyone have this problem? http://www.fsbuild.com/forum/viewtopic.php?t=721I don't know what did you mean by (but it sounds awfully familiar) it's normal this for you and by the way rc4 read the lat-lon coordinate or the WPT name..Thank you


 

 

Share this post


Link to post
Share on other sites

Here another session where RC4 dosen't cross the MTL WPT to the next.To fly this way is quite boring If i have to bypass all wpt.I even set deviation of 50 Deg in general pref.radarrk8.jpg


 

 

Share this post


Link to post
Share on other sites

do not set the heading deviation to 50 degrees. that is irrelevant and making matters worse, probably.this is a short flight, i'll try to fly it tomorrow. or maybe i can get a beta tester to fly it, while i'm sleeping :-)jd

Share this post


Link to post
Share on other sites

The track recorded shows I believe you fell outside the horizontal limits which are tight at departure. I also note from the screen shot that your last command in your text box was to climb to FL 15 which is 1500 feet. However I did not check the transition level (first flight level after transition altitude) and a transition altitude of 1,000 is unusually low. There is also an ack prompt awaiting in the menu.It looks like you did not get credit for MTL. It was not a heading error. Your LNAV did not take you close enough to MTL.I may be repeating, but how did you load the plan into the aircraft.From the manual tutorial 4 page 179:---------------------------------------------------------------

Share this post


Link to post
Share on other sites

Are you using speed acceleration during the flight (especially when crossing waypoints) by any chance?I think what would be most useful is a screenshot exactly like the above, but a few miles earlier, as you pass MTL. If you can provide one of such, it'll be much easier to see what is going on. It allows us to be at the scene of the crime as it is happening.As Ron said, we will also need to know which plan you're importing when and where.Subs

Share this post


Link to post
Share on other sites
Guest NIC0

I do also have this problem, with the PMDG 737NG. I use FSBuild 2.2 to create FP's to both FS9/RC and PMDG FMC. Even if I'm at the right heading towards the WP, RC ask me to change heading, maybe with only 1-2 degrees.I haven't got any missed checkpoints yet, but RC still hustle about that I have to change my heading. It is very annoying that the controller tell me the same sentence every 5th second for XX miles, and when I reach the WP, he accept that, and starts yelling about my "wrong" heading to the next WP... And so does it continue until the approach...Isn't it anyway to fix it?

Share this post


Link to post
Share on other sites

If you are using FSB to generate all waypoints to the FMC and RC, then there should not be a difference. If you are getting a heading correction that does not want you to go back for a missed waypoint, try increasing your heading tolerance in the options table.If your waypoints are very close to your departure point and you are using LNAV for a significant departure turn, the LNAV will adjust turns for bank limitations cutting corners and anticipating turns on the inside limits of the course. What I do and seems to be done in the real world is until any initial severe turns are completed is use MCP heading control or yoke steering. I also do not use VNAV until the turn is complete but SPD and FLCH.The "rounding out" of the flight path by the FMC falls outside of RC's requirements.I frequently use the NOTAMS option for these tight departures which will stop the nagging of the controller.These close in departure waypoints tyuically have a label like DT110 and there intent is to establish an outside limitation "turn by".

Share this post


Link to post
Share on other sites

Ok I had another test Same route created with FSB and imported in 767LDS via FSB plugin .RTF and for RC4 .PLN :If you want to try copy those text and paste in notepad and save it.[flightplan]title=LFML to LSGGdescription=LFML, LSGGtype=IFRroutetype=3cruising_altitude=28000departure_id=LFML, N43* 26.07', E005* 12.49',+000069.00departure_position=32Rdestination_id=LSGG, N46* 14.12', E006* 06.42',+001411.00departure_name=MARSIELLE_PROVENCEdestination_name=GENEVA_COINTRINwaypoint.0=LFML, A, N43* 26.07', E005* 12.49', +000000.00, waypoint.1=AVN, V, N43* 59.43', E004* 44.47', +23000.00, waypoint.2=MTL, V, N44* 33.17', E004* 46.47', +33000.00, waypoint.3=ROMAM, I, N45* 06.09', E005* 09.48', +26000.00, waypoint.4=LTP, V, N45* 29.20', E005* 26.20', +18000.00, waypoint.5=BELUS, I, N45* 40.31', E005* 35.38', +16000.00, waypoint.6=LSGG, A, N46* 14.12', E006* 06.42', +01411.00, LFMLLGSS.RTF;Flight Plan Generated by Fsbuild 2.2 LFML-LSGGH,LFML,LSGG, ,W,AVN,,0,43.995400,4.746500,112.300000,0.000000,0,0,0,0W,MTL,,0,44.554800,4.779800,113.650000,0.000000,0,0,0,0W,ROMAM,,0,45.102600,5.163400,0.000000,0.000000,0,0,0,0W,LTP,,0,45.489000,5.439000,115.550000,0.000000,0,0,0,0W,BELUS,,0,45.675400,5.594000,0.000000,0.000000,0,0,0,0End of FlightPlanI get some delay sometime before receive confirmation with ATC ,and also I like to change freqency my self and stay in taining for Vatsim.The first VOR AVN as you can see, passed right over but before got the ding sound took some second and shows 0 NM->1 NM->2 NM When I reach VOR MTL I passed right over and got 0 NM but this time I diden't get credit and the NM get infinite.Sorry Ronzie But I don't really understand your suggestion I get more confiusion and I think i am not shure the problem it resides on the way all this software translate lat end Long some by decimal and other by minute.But way is only me to get this trouble this is a mistery, and as you can understand i don't ejoy that much if it dosen't work.here some screenshot:http://img243.imageshack.us/img243/9813/firstnz7.jpghttp://img372.imageshack.us/img372/969/midma7.jpghttp://img350.imageshack.us/img350/5517/lastea6.jpgHope to see a solution.Thank's


 

 

Share this post


Link to post
Share on other sites
Guest NIC0

Ron, my heading tolerance is increased to max, but the problem is still there. It seems that if the WP is at 204.5 degrees (heading indicator constantly switch between 204 and 205) , RC wants you to fly at 205 degrees. But it's strange that the increased heading tolerance didn't solve the problem...

Share this post


Link to post
Share on other sites
Guest NIC0

>heading tolerance has nothing to do with what you're doing.>>jdSo then whats the deal with heading tolerance...?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • 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.
×
×
  • Create New...