Dazzlercee

OK Thanks. Approach data for EGCC is greyed out (and ILS freqs are missing)...is this relevant to the bug fixed in 1.04?

Is it possible to display the approach charts for an airport when not following a programmed route? E.G. Flying from New York to Boston in free flight, select your STAR for KBOS once landing runway has been notified and then the relevant chart displayed for KBOS in EFB. To get these charts at the moment I believe you have to have a full route loaded.

I also get the stutters with a dual monitor set up. Various instruments display the stutter, especially the airspeed indicator.

Having a few problems getting the RT2 plans to load into the PMDG FMC, even with NATS disabled. As an experiment I built a plan from EGCC to KMCO with FSBuild2 and exported it to both PMDG and FSX (XML). I then loaded the FSX version into EFB and confirmed the waypoints were identical to the FSBuild2 plan. I then saved the route as RT2 in EFB. In short, the original FSuild2 plan loaded into the PMDG FMC with no problems. The same plan converted to FSX and then to RT2 with EFB did not load into the PMDG FMC. I expected the runway errors, but most of the way points also showed an error. Apologies for the long post, I just thought this may help in ironing out the PMDG issues. The generated plans are as follows: FSBuild (RTE) (this one works): Generated by Fsbuild 2.3 28 EGCC 1 DIRECT 1 N 53.3540 W 2.2751 257 23L 1 1 N 53.3482 W 2.2770 257 1 257 - -1000000 -1000000 WAL 2 DIRECT 1 N 53.3918 W 3.1343 0 0 0 0 BEL 2 DIRECT 1 N 54.6612 W 6.2298 0 0 0 0 MORAG 2 DIRECT 1 N 52.7529 W 5.5001 0 0 0 0 MIMKU 2 DIRECT 1 N 56.0001 W 10.0001 0 0 0 0 5700N/02000W 2 DIRECT 1 N 57.0001 W 20.0001 0 0 0 0 5700N/03000W 2 DIRECT 1 N 57.0001 W 30.0001 0 0 0 0 5500N/04000W 2 DIRECT 1 N 55.0001 W 40.0001 0 0 0 0 5300N/05000W 2 DIRECT 1 N 53.0001 W 50.0001 0 0 0 0 YAY 2 N184B 1 N 51.3940 W 56.0840 0 0 0 0 TOPPS 2 DIRECT 1 N 45.3401 W 67.7387 0 0 0 0 EMJAY 2 J174 1 N 40.0929 W 73.2618 0 0 0 0 ZIZZI 5 J174 1 N 38.9407 W 74.5290 0 0 0 0 WARNN 5 J174 1 N 38.7501 W 74.7329 0 0 0 0 SWL 5 J174 1 N 38.0565 W 75.4640 0 0 0 0 SWL12 5 J174 1 N 37.8848 W 75.5940 0 0 0 0 KALDA 5 J174 1 N 37.8420 W 75.6265 0 0 0 0 SAWED 5 J174 1 N 37.5334 W 75.8582 0 0 0 0 ORF 2 J121 1 N 36.8918 W 76.2004 0 0 0 0 WEAVR 5 J121 1 N 35.8537 W 77.1343 0 0 0 0 ISO 5 J121 1 N 35.3709 W 77.5582 0 0 0 0 BARTL 5 J121 1 N 34.3032 W 78.6515 0 0 0 0 JMACK 5 J121 1 N 33.9884 W 78.9665 0 0 0 0 CHS 2 J79 1 N 32.8943 W 80.0379 0 0 0 0 MILIE 5 J79 1 N 31.3287 W 81.1737 0 0 0 0 BEENO 5 J79 1 N 30.6393 W 81.1526 0 0 0 0 OMN 2 DIRECT 1 N 29.3032 W 81.1126 0 0 0 0 KMCO 1 - 1 N 28.4293 W 81.3090 96 18R 0 1 N 28.4482 W 81.3270 96 1 96 - -1000000 -1000000 EFB converted to RT2 (does not work): // rt2 v1.0 EGCC to KMCO generated 24/03/2010 by AivlaSoft EFB http://www.aivlasoft.com 28 EGCC 999 KMCO 999 - EGCC - WAL BEL MORAG MIMKU 5700N/02000W 5700N/03000W 5500N/04000W 5300N/05000W YAY TOPPS EMJAY ZIZZI WARNN SWL SWL12 KALDA SAWED ORF WEAVR ISO BARTL JMACK CHS MILIE BEENO OMN - KMCO

Any release timeframe for 1.04? Will the Routefinder plan be analyzed correctly in the new release? Thanks, Daz

Thanks for your reply. I admit I ticked the NATS option in the route planner so that is my oversight. The reason I did this was that without the NATS option the route EGCC to KMCO was for some reason taking me south to the Canaries and beyond before lurching back north towards the destination. The FSX flight planner also does the same and I don't understand why, unless NATS are a requirement for this route to pan out as expected, i.e. across Irleand, across the North Atlantic and down the east coast of the USA. Regarding EGCC. I commented out the entry for EGCC in Runways.txt as I use the UK 2000 Manchester Extreme scenery which has the correct runway designations of 5L, 5R, 23L, 23R. This allowed me to select SIDS and STARS for EGCC in EFB. The ILS frquencies show in FSX but not in EFB. Could they be missing from the navdata? How do I check? Thanks, Daz

I am sure this was OK yesterday, but today none of my routes saved as .rt2 will load into the PMDG 747 FMC. It rejects most waypoints and runways are reported as 999, example below: // rt2 v1.0 EGBB to KMCO generated 23/03/2010 by AivlaSoft EFB www.aivlasoft.com 17 EGBB 999 KMCO 999 - EGBB - TNT UL28 RODOL UP6 NELBO UN551 NIBOG ETARI NATC YAY N184B TOPPS J581 ENE J55 HTO VS1 ORF J121 CHS J174 MILIE J79 BEENO J103 OMN - KMCO This route will not fully load. The same route generated by FSBuild2 is fine. I am also missing ILS data for EGCC (Manchester). Could this be due to bad navdata (1003)? Thanks.