Jump to content

Sign in to follow this  
Guest tonyc

C4TO Version 3.3.1 "Patch"

Recommended Posts

Guest

OK. Here's another patch. This one fixes the Center-to-Center handoff bug. Cheers, Tony

Share this post


Link to post
Share on other sites

Hi Tony,See here the results of a test flight with C4TO v3.3.1 from ESGG to EBBR with B757. Route: BAK AAL DHE EEL PAM RTM NIK.In this version the center-to-center handoff was OK, but other phenomenon occured.Hope the info below is clear.Cheers,Frank.------------------------------ESGG runway 03.GND, TWR, DEP, Center was OK.Center-to-Center handoff was now OK.On course to "EEL" I received vectors for traffic separation.After vectors for traffic separation, the B757 resumed the original leg "DHE-EEL" as requested by center. From then on, center kept calling my plane "N34512" without instructions.I replied each time by (Alt-R).Tried Alt-S, but no reply.Tried Alt+A and Alt+C to re-establish contact, without succes.After several times I received a vector opposite to my flight course.(Bearing towards navaid "AAL", which I had already overflown before).For test I looked at next waypoint (Alt+N): it showed "AAL" instead of "EEL" (which was next in my flightplan).I denied this vector and continued my original route.Center kept calling without new instruction. Each time I replied by Alt+R.After navaid "EEL", I succeeded to re-establish contact with center (Freq. 124.40) and received my descent.After navaid "RTM" I received handover to Approach (118.25).Approach instructed further descent (4000 ft) and provided a normal approach heading. Then approach instructed vectors which send me in circles around.After 2 circles, I denied the instructions and flew an approach towards runway 25R at EBBR.(Could not establish contact with TWR, because I denied the Approach instruction). When I left Fly!2, the C4TOv3 log file was empty.--------------------------------

Share this post


Link to post
Share on other sites

Hi Tony,Performed another testflight with C4TOv3.3.1.EBBR_EDDF with B757 via ETENO1M - NTM - KIR - TAU - MTRFind below the testresults.Please let me know if anything specific to test.Cheers,Frank-------------------------------------At EBBR: GND, TWR, DEP and Center OK.Handover center-to-center: OK.10 Nm inbound navaid KIR on a hdg 120: "vector for traffic hdg 080".Then new vector to resume has hdg 240. This is nearly the opposite direction of original hdg in order to be able to overfly waypoint "KIR".After having overflown "KIR", I didn't receive a new hdg to the next waypoint "TAU". So I resumed my flightplan with a new heading to the next waypoint "NTM".Once again on courrse to "NTM", ATC resumed with call for descent andhandover center-to-approach.Appr. guided me onto an initial approach course for rwy 25L at EDDF (Hdg 160 at 2000 ft, speed 190 kts).Then Appr called me several times without instruction: "N34512 ???".I replied each time with Alt+R. Tried Alt+S: no reply.Immediately after, approach instructed an opposite heading (Maybe in the direction of waypoint "MTR", which approach didn't let me overfly).After headings for 2 circles, I resumed own navigation for landing. -------------------------P.S: Phenomenon:"Vector for traffic" on an inbound course very close to the next waypoint, cause trouble to intercept that waypoint afterwards.(Need to fly opposite direction to overfly waypoint KIR)Proposal: IF less than 40NM close to waypoint and after vector for traffic, C4TO could propose the next waypoint to resume. (E.g. TAU instead of KIR).----------------------------P.S:Phenomenon:During approach, vectors towards a remaining waypoint in the flightplan which hasn't been overflown.Proposal:Once handover from center to approach has started and approach provides vectoring, an exact overfly of the remaining flightplan waypoints shouldn't be mandatory anymore.---------------------------------P.S:This time the log file C4TOV3 was present after leaving Fly!2.Copy in attachment.Begin C4TO LogVersion = 3.3Aircraft Information Name = PMDG 757-200 Registration = customac Heavy = 1FlightPlan Information *COMPLETE ROUTE* BRUSSELS NATL Comm Channels TWR = 118.600 GND = 121.875 DEP = 126.625 CLNC = 121.950 ATIS = 132.467 APP = 118.250 ABELAG = 130.550 TWR = 118.600 GND = 121.875 DEP = 126.650 CLNC = 121.950 ATIS = 132.475 APP = 118.250 NAVAID HULDENBERG Bearing = 151 Distance = 10.6 Frequency = 117.550 NAVAID SPRIMONT Bearing = 112 Distance = 40.0 Frequency = 113.100 NAVAID NATTENHEIM Bearing = 131 Distance = 46.0 Frequency = 115.300 NAVAID KIRN Bearing = 107 Distance = 33.9 Frequency = 117.500 NAVAID TAUNUS Bearing = 52 Distance = 38.7 Frequency = 116.700 NAVAID METRO Bearing = 87 Distance = 26.3 Frequency = 110.000 FRANKFURT MAIN Bearing = 218 Distance = 19.1 Comm Channels ATIS = 118.033 ATIS = 118.025 DELIVERY = 121.900 DEP = 120.150 GND = 121.800 GND = 121.900 INFO = 119.150 RADAR = 120.150 RADAR = 120.800 TWR = 119.900 TWR = 119.900 *END OF ROUTE* Total distance = 214.7 Departure Airport ID: EBBR Arrival Airport ID: EDDF Requested en route altitude is: 23000 Initial Course is: 151Flight Plan Frequencies Clearance Delivery = 121.950 Departure Ground Control = 121.875 Departure Tower = 118.600 Departure Control = 126.650 Center = 120.000 Approach Control = 120.800 Arrival Tower = 119.900 Arrival Ground Control = 121.900 Departure CTAF = 0.000 Departure MULTICOM = 130.550 Arrival CTAF = 0.000 Arrival MULTICOM = 0.000 UNICOM = 122.800DEPARTURE AIRPORT (BRUSSELS NATL) INFORMATION: Winds 250 degrees at 4 knotsRunway #1 is runway 20 Length is 9790 feet Magnetic heading is 196 Localizer frequency is 111.15 Crosswind is 54 degrees from the right Runway is usableRunway #2 is runway 02 Length is 9790 feet Magnetic heading is 16 Localizer frequency is 109.90 Crosswind is 126 degrees from the left Runway is not usableRunway #3 is runway 25L Length is 10534 feet Magnetic heading is 252 Localizer frequency is 110.30 Crosswind is 2 degrees from the left Runway is usableRunway #4 is runway 07R Length is 10534 feet Magnetic heading is 72 Crosswind is 178 degrees from the right Runway is not usableRunway #5 is runway 25R Length is 11935 feet Magnetic heading is 247 Localizer frequency is 108.90 Crosswind is 3 degrees from the right Runway is usableRunway #6 is runway 07L Length is 11935 feet Magnetic heading is 67 Crosswind is 177 degrees from the left Runway is not usableThe active runway is 25LARRIVAL AIRPORT (FRANKFURT MAIN) INFORMATION: Winds 249 degrees at 3 knotsRunway #1 is runway 36 Length is 13123 feet Magnetic heading is 360 Crosswind is 111 degrees from the left Runway is not usableRunway #2 is runway 18 Length is 13123 feet Magnetic heading is 180 Crosswind is 69 degrees from the right Runway is usableRunway #3 is runway 25R Length is 13123 feet Magnetic heading is 249 Localizer frequency is 109.50 Runway is directly into the wind Runway is usableRunway #4 is runway 07L Length is 13123 feet Magnetic heading is 69 Runway is directly out of the wind Runway is not usableRunway #5 is runway 25L Length is 13123 feet Magnetic heading is 249 Localizer frequency is 110.70 Runway is directly into the wind Runway is usableRunway #6 is runway 07R Length is 13123 feet Magnetic heading is 69 Runway is directly out of the wind Runway is not usableThe active runway is 25LAPPROACH VECTORSFRANKFURT MAIN = 50d 2m 35.12s N 9d 33m 35.25s EFINAL APPROACH FIX = 50d 4m 8.--------------------------------------

Share this post


Link to post
Share on other sites
Guest

Thanks Frank! Your testing efforts have been extremely valuable. I'm not terribly good at flying the 757 and so I don't get a chance to test some of the vectoring logic with aircraft that turn slowly and move very fast. It really messes up things up. I'll see what I can do on all points mentioned. However, in the current version, once you've been switched over to approach, all of your remaining waypoints are discarded. The phenomema you've encountered stems from your aircraft's inability to respond to the approach controller's instructions quickly enough. The upshot is that I've got to do some work on the vectoring logic that will provide more maneuvering lead time to heavy aircraft.Thanks again for your help.Cheers, Tony

Share this post


Link to post
Share on other sites

>OK. Here's another patch. This one fixes the Center-to-Center>handoff bug. >>Cheers, TonyTony, on a very fresh install of Fly!2 with latest patch 240, should I install the basic dll(C4TO) plus the latest patch 331 or the basic plus all the patches succesively?ThanksRakam

Share this post


Link to post
Share on other sites
Guest

The basic plus just the latest patch.Cheers, TonyP.S., You might want to hold off on this one. There is a pretty nasty bug in the approach controller module that I will be fixing in the next couple of days. Once fixed, C4TO should be much more stable.

Share this post


Link to post
Share on other sites

>The basic plus just the latest patch.>>Cheers, Tony>>P.S., You might want to hold off on this one. There is a>pretty nasty bug in the approach controller module that I will>be fixing in the next couple of days. Once fixed, C4TO should>be much more stable.Ok Tony, take your time and sleep some too! This program is already fantastic to use as such. In fact for the time being what I do is to connect the APP once close enough from the airport and land it myself.RegardsRakhamPIV 2.53 Ghz 1536 DDR GeForce3 TI200 WinXP ProYoke & Pedals CH Products

Share this post


Link to post
Share on other sites
Guest

Just completed a flight from Tallahassee to MCO. Approach put me into a continual left turn for the approach to runway 17. First I would receive directions to turn left to a certain heading, then receive two commands with no additional information other than the aircraft number. After replying to the instructions, I received another left turn heading - turning circles over Disney. I've included the log file for your use.WayneBegin C4TO LogVersion = 3.3Aircraft Information Name = B737-500 Registration = customac Heavy = 1FlightPlan Information *COMPLETE ROUTE* TALLAHASSEE RGNL Comm Channels APP = 133.850 CLNC = 126.650 CTAF = 118.700 GND = 121.900 GAINESVILLE = 122.200 ATIS = 119.450 TWR = 118.700 UNICOM = 122.950 NAVAID FOLEY Bearing = 124 Distance = 46.4 Frequency = 254.000 NAVAID GAINESVILLE Bearing = 112 Distance = 68.7 Frequency = 116.200 NAVAID LEESBURG Bearing = 146 Distance = 53.8 Frequency = 335.000 ORLANDO INTL Bearing = 132 Distance = 34.9 Comm Channels APP = 125.550 ATIS = 121.250 CLNC = 134.700 GND = 121.800 ST = 122.200 TWR = 118.450 UNICOM = 122.950 *END OF ROUTE* Total distance = 203.7 Departure Airport ID: KTLH Arrival Airport ID: KMCO Requested en route altitude is: 21000 Initial Course is: 124Flight Plan Frequencies Clearance Delivery = 126.650 Departure Ground Control = 121.900 Departure Tower = 118.700 Departure Control = 133.850 Center = 129.200 Approach Control = 125.550 Arrival Tower = 118.450 Arrival Ground Control = 121.800 Departure CTAF = 0.000 Departure MULTICOM = 122.950 Arrival CTAF = 0.000 Arrival MULTICOM = 122.950 UNICOM = 122.800DEPARTURE AIRPORT (TALLAHASSEE RGNL) INFORMATION: Winds 87 degrees at 4 knotsRunway #1 is runway 36 Length is 6076 feet Magnetic heading is 2 Localizer frequency is 110.30 Crosswind is 85 degrees from the right Runway is usableRunway #2 is runway 18 Length is 6076 feet Magnetic heading is 182 Crosswind is 95 degrees from the left Runway is not usableRunway #3 is runway 27 Length is 8000 feet Magnetic heading is 272 Localizer frequency is 111.90 Crosswind is 175 degrees from the right Runway is not usableRunway #4 is runway 09 Length is 8000 feet Magnetic heading is 92 Crosswind is 5 degrees from the left Runway is usableThe active runway is 09ARRIVAL AIRPORT (ORLANDO INTL) INFORMATION: Winds 115 degrees at 9 knotsRunway #1 is runway 35 Length is 10000 feet Magnetic heading is 4 Localizer frequency is 110.50 Crosswind is 111 degrees from the right Runway is not usableRunway #2 is runway 17 Length is 10000 feet Magnetic heading is 184 Localizer frequency is 111.75 Crosswind is 69 degrees from the left Runway is usableRunway #3 is runway 36L Length is 12004 feet Magnetic heading is 4 Crosswind is 111 degrees from the right Runway is not usableRunway #4 is runway 18R Length is 12004 feet Magnetic heading is 184 Localizer frequency is 111.90 Crosswind is 69 degrees from the left Runway is usableRunway #5 is runway 36R Length is 12005 feet Magnetic heading is 4 Localizer frequency is 110.70 Crosswind is 111 degrees from the right Runway is not usableRunway #6 is runway 18L Length is 12005 feet Magnetic heading is 184 Crosswind is 69 degrees from the left Runway is usableThe active runway is 17APPROACH VECTORSORLANDO INTL = 28d 26m 44.00s N 81d 19m 57.69s WFINAL APPROACH FIX = 29d 31m 8.38s N 81d 18m 48.31s WINTERCEPT FIX = 29d 41m 8.75s N 81d 18m 54.63s WRIGHT TURN FIX = 29d 41m 10.42s N 81d 14m 29.31s WLEFT TURN FIX = 29d 41m 7.09s N 81d 21m 19.94s WRIGHT BASE FIX = 29d 41m 12.08s N 81d 11m 4.00s WLEFT BASE FIX = 29d 41m 5.43s N 81d 25m 45.25s WRIGHT DOWNWIND FIX = 29d 41m 14.30s N 81d 7m 30.25s WLEFT DOWNWIND FIX = 29d 41m 3.21s N 81d 29m 19.00s WRIGHT MISSED APPROACH FIX = 29d 31m 13.93s N 81d 6m 23.94s WLEFT MISSED APPROACH FIX = 29d 31m 2.84s N 81d 29m 12.69s WEnd C4TO Log

Share this post


Link to post
Share on other sites
Guest richpress

Tony could you give me the rundown on downloading C4TO and the order of patches. I am interested to try this out.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Sign in to follow this  

×
×
  • Create New...