nemesis19

Vic,the more realistic solution might be, to just plug in a set of headphones on your networked PC, and keep the FS PC for the Aircraft sounds ... More real world if you like.Adrian W.

Alf,under vista and Windows7 you need to put the .dll into the \WINDOWS\syswow64 folder, not the system32 folder.Regards,................Adrian19

Hi,your problem lies in the way FSC has formatted the VORs in the flightplan,[flightplan]AppVersion=9.0.30612title=KALB to KIAD description=KALB, KIAD type=IFRroutetype=1cruising_altitude=32000departure_id=KALB, N42* 44.82', W073* 48.28', +000282.00departure_position=01destination_id=KIAD, N38* 56.67', W077* 27.35', +000312.00departure_name=Albany Intldestination_name=Washington Dulles Intlalternate_name=waypoint.0=, KALB, , KALB, A, N42* 44.82', W073* 48.28', +000282.00,waypoint.1=KK, SAX, , SAX 115.70, V, N41* 04.05', W074* 32.30', +000000.00,waypoint.2=KK, BWZ, , BWZ 114.20, V, N40* 47.91', W074* 49.31', +000000.00,waypoint.3=KK, LRP, , LRP 117.30, V, N40* 07.20', W076* 17.48', +000000.00,waypoint.4=KK, JOANE, , JOANE, I, N40* 02.64', W076* 27.36', +000000.00,waypoint.5=KK, DELRO, , DELRO, I, N39* 57.93', W076* 37.52', +000000.00,waypoint.6=KK, BINNS, , BINNS, I, N39* 47.10', W077* 00.66', +000000.00,waypoint.7=KK, HYPER, , HYPER, I, N39* 41.04', W077* 13.51', +000000.00,waypoint.8=KK, MULRR, , MULRR, I, N39* 37.89', W077* 20.14', +000000.00,waypoint.9=KK, AML, , AML 113.50, V, N38* 56.08', W077* 28.00', +000000.00,waypoint.10=, KIAD, , KIAD, A, N38* 56.67', W077* 27.35', +000312.00,An FS flightplan doesn't contain this information, FS gets it from elsewhere, edit the plan to remove the frequencies that I've highlighted in red, like this :-[flightplan]AppVersion=9.0.30612title=KALB to KIAD description=KALB, KIAD type=IFRroutetype=1cruising_altitude=32000departure_id=KALB, N42* 44.82', W073* 48.28', +000282.00departure_position=01destination_id=KIAD, N38* 56.67', W077* 27.35', +000312.00departure_name=Albany Intldestination_name=Washington Dulles Intlalternate_name=waypoint.0=, KALB, , KALB, A, N42* 44.82', W073* 48.28', +000282.00,waypoint.1=KK, SAX, , SAX, V, N41* 04.05', W074* 32.30', +000000.00,waypoint.2=KK, BWZ, , BWZ, V, N40* 47.91', W074* 49.31', +000000.00,waypoint.3=KK, LRP, , LRP, V, N40* 07.20', W076* 17.48', +000000.00,waypoint.4=KK, JOANE, , JOANE, I, N40* 02.64', W076* 27.36', +000000.00,waypoint.5=KK, DELRO, , DELRO, I, N39* 57.93', W076* 37.52', +000000.00,waypoint.6=KK, BINNS, , BINNS, I, N39* 47.10', W077* 00.66', +000000.00,waypoint.7=KK, HYPER, , HYPER, I, N39* 41.04', W077* 13.51', +000000.00,waypoint.8=KK, MULRR, , MULRR, I, N39* 37.89', W077* 20.14', +000000.00,waypoint.9=KK, AML, , AML, V, N38* 56.08', W077* 28.00', +000000.00,waypoint.10=, KIAD, , KIAD, A, N38* 56.67', W077* 27.35', +000312.00,Resave the plan and the waypoints should now be shown correctly,regards,...............Adrian19.

Hi Vic,this may seem like a silly question, but does your FS PC have a dual network adapter ?I had similar connection problems on my setup sometime ago, it turned out that with the dual adapter that there was a conflict. The solution was to configure them as a single highspeed adapter.Regards,................Adrian19

That is the complete flight plan (cut and paste) loaded in Radar Contact:[flightplan]title=LIRF to KJFKdescription=LIRF, KJFKtype=IFRroutetype=0cruising_altitude=31000departure_id=LIRF, N41* 48.02', E012* 14.33', +00015destination_id=KJFK, N40* 38.38', W073* 46.74', +00013departure_name=ROMA/FIUMICINOdestination_name=JOHN F KENNEDY INTLwaypoint.0=LIRF, A, N41* 48.02', E012* 14.33', +00015, waypoint.1=GILIO, I, N42* 22.00', E010* 55.57', +000000, SIDwaypoint.2=ELB, V, N42* 43.84', E010* 23.74', +000000, UM729waypoint.3=DOBIM, I, N42* 57.23', E009* 45.00', +000000, UM616waypoint.4=GIRAG, I, N42* 59.70', E009* 37.80', +000000, UM616waypoint.5=AKUTI, I, N43* 13.63', E008* 56.42', +000000, UM616waypoint.6=PIGOS, I, N43* 37.33', E007* 22.27', +000000, UM616waypoint.7=BODRU, I, N44* 12.52', E006* 22.67', +000000, UM616waypoint.8=KOTIT, I, N44* 36.15', E005* 41.45', +000000, UM616waypoint.9=ETREK, I, N45* 11.27', E004* 38.32', +000000, UM616waypoint.10=LERGA, I, N45* 15.43', E003* 45.02', +000000, UM616waypoint.11=FOUCO, I, N45* 45.28', E000* 28.83', +000000, UT183waypoint.12=BOLGU, I, N45* 55.93', W000* 3.63', +000000, UT183waypoint.13=VENAR, I, N46* 8.62', W000* 43.23', +000000, UT183waypoint.14=MANAK, I, N46* 12.80', W000* 56.52', +000000, UT183waypoint.15=TIRAV, I, N46* 35.93', W001* 23.45', +000000, UT183waypoint.16=MOKOR, I, N47* 0.42', W002* 0.83', +000000, UT183waypoint.17=DEGEX, I, N47* 44.63', W003* 9.40', +000000, UT183waypoint.18=TERKU, I, N48* 1.80', W003* 37.00', +000000, UN490waypoint.19=BERAD, I, N48* 18.12', W004* 3.70', +000000, UN490waypoint.20=DEKOR, I, N49* 0.43', W005* 55.98', +000000, UN512waypoint.21=LARLA, I, N49* 22.68', W007* 7.25', +000000, UN512waypoint.22=RATKA, I, N49* 30.00', W008* 0.00', +000000, UN521waypoint.23=DINIM, I, N51* 0.00', W015* 0.00', +000000, waypoint.24=52N020W, I, N52* 0.00', W020* 0.00', +000000, NATGwaypoint.25=53N030W, I, N53* 0.00', W030* 0.00', +000000, NATGwaypoint.26=53N040W, I, N53* 0.00', W040* 0.00', +000000, NATGwaypoint.27=51N050W, I, N51* 0.00', W050* 0.00', +000000, NATGwaypoint.28=DENDU, I, N50* 30.20', W052* 4.12', +000000, NATGwaypoint.29=CYMON, I, N49* 43.00', W054* 59.94', +000000, NATGwaypoint.30=EBONY, I, N44* 54.14', W067* 9.39', +000000, N144Bwaypoint.31=SEAER, I, N43* 55.47', W069* 29.51', +000000, J573waypoint.32=SCARS, I, N43* 32.92', W070* 20.46', +000000, J573waypoint.33=ENE, V, N43* 25.54', W070* 36.81', +000000, J573waypoint.34=KJFK, A, N40* 38.38', W073* 46.74', +00013, STARThanks,Maurizio Balvetti

Their actions are indefensible and I really find it frustrating that theres always a few people on the forum who will try and jump to their defense.

Iron out the bugs in the Weather Engine, sure there are 3rd party Developers that have done their best to improve it, but it's still way from perfect.A common Navdata database that can be used by FS (ATC, GPS) and 3rd Party developers - easily updated in one download, to include Navaids, Airways, SIDs, STARs etc. At the moment if you own several 3rd Party Aircraft you may need to download 5 or 6 different databases, and within FS it's almost impossible to update, as it's in BGL's all over the place.Linked to the above, allocation of SIDs and STARs by ATC, dependent on Runway and flightplan (including AI)Improve the AI engine to reduce bottlenecks at Runways - At the moment AI(1) lands, AI(2) is still some 5 - 6NM out, on approach and AI(3) waits, etc, etc. The improvement would be AI(1) lands, AI(3) taxis into position and holds, AI(1) leaves the Runway, AI(3) is cleared for Takeoff and does so, AI(2) lands.Possibility to make Taxiways directional dependent on Runway(s) - Larger aeroports tend to have "one way systems" that change depending on the Runways in use, would probably reduce bottlenecks/headons caused by AI taxiing in and AI taxiing out, often on the same Taxiway.Possibility to exclude a Taxiway as an exit from Runway, again Runway dependent - Often seen AI trying to exit the Runway where there are Aircraft waiting for Takeoff, instead of moving down the Runway to the next clear exit (mostly GA types).Correct Drive In/Drive Out parking - At the moment we are using the "Plumbing" technique from I think, Jim Vile, of overlaying a second AFCAD, onto the first to achieve this. Not always successful and can play havoc with the drawing of Taxiways (the directional Taxiway could possibly be used here, one way in and one way out).I'm sure I'll think of other stuff, but there's enough here to keep MS occupied for a while,regards,............Adrian W.

Jd beat me to it :(

As JD suggests, the SSTSIM Concorde doesn't use the standard FS Autopilot, so "Otto", won't be able to control the Plane, he can however take the Comms.Regards,...........Adrian W.

Sanal,if your error message is telling you that "comdlg32.ocx is not registered or is missing", then registering "mscomctl.ocx" won't help you, you should be registering "comdlg32.ocx".Download comdlg32.ocx from here , unzip and place the file into the \Windows\SysWOW64\ dir. Then run "regsvr32 C:\Windows\SysWOW64\comdlg32.ocx" Remember to right click the command prompt and run as admistrator.Your comdlg32.ocx should now be registered, giving you the same type of confirmation as you had for "mscomctl.ocx".Re-installing RC4 won't help you, as it's a VB runtime library that your missing on your system.Regards,............Adrian W.

Thanks John - "FlyBe." It`s British AirlineGeorge

Hi Adrian,I know this post is a couple of weeks old, but I thought you might be interested in how I put FISDO out of business, with 'Ole Pointy'.The flight plan from EGLL to KJFK is filed initially at FL280, this takes care of the subsonic cruise out to UPGAS. Once I'm passed UPGAS I then ask for FL590 (the maximum allowed by RC) and start my trans-sonic climb in Max Climb mode. When I kill the Re-Heats I know that my climb rate is going to start fluctuating, so at this point I ask for 'Deviations for Turbulence', RC now ignores my Altitude and Alpha Charlie can climb or descend to her hearts content in Cruise Climb mode.I have found that RC calls me down, to somewhere around FL350, within a few miles of my calculated deceleration/descent point, so I proceed with the deceleration, and once I'm actually descending, inform ATC that I'm past the turbulence, RC is now once again keeping an eye on my altitude.From now on I'm just like any other airliner, respecting Altitudes, speed restrictions, crossing restrictions, etc. ATC vectors me in over New York to land on 13L.Once I've taxied in and parked, JD informs me that there may be redundancies at FISDO and RC hasn't griped once about my altitude.I hope JD puts something in RC5 for Concorde, it needn't be anything fancy, the same mechanism as the Turbulence deviation, but with additional phraseology for cruise climbing.Regards,...........Adrian W.

Hey, hasn't anyone put this into 2010 yet

Sounds about right. Don't forget when FSUIPC starts RC, it only executes the software, you still need to tell RC what flightplan your using, alternate airports, altitude restrictions, etc. Once you've selected all your options, you must click the "START" button to tell RC that it can start ATCing, then ALT/TAB back to FS.Regards,.............Adrian W.P.S. If you have access to a second PC, then using RC via WideFS is an option, this way you don't need to come out of FS to access RC, plus you can pipe the sound straight into headphones, much more realistic !!

Hi Alex,I too found that it was sometimes difficult to hear RC with all the aircraft sounds as well. If you have access to a second PC (doesn't need to be a powerful one), you can do like I have and put RC onto the second PC via WideFS, then put the sound directly into headphones, much more realistic and no interference from FS sounds.Regards,........Adrian W.

There is FSUIPC Run Options from Jos

Rob,IIRC vroute doesn't give the Gate lat/long, only the airport's lat/long, so this might be the problem. The only way I know to overcome this would be to edit the .pln to include your Gate position before loading it into RC.Regards,........Adrian W.

Hi,this is a long shot, but have you re-run the makerwys.exe since installing the new sceneries ?I did say it was a long shot !Regards.......Adrian W.

First of all, there is an ICAO naming convention for waypoints, here's a copy from the FAQ's at vroute.info :-If you need to enter exact waypoint coordinates in a flight plan, which is pretty common when coding North Atlantic Tracks (NATs) and other oceanic routes, here's how to do it: On northern hemisphere: (00N-90N)Our example is on 60N:7 letter coordinates : 5 letter ICAO fix60N180W-60N100W : 60N80-60N0060N099W-60N001W : 6099N-6001N60N000E-60N099E : 6000E-6099E60N100E-60N179E : 60E00-60E79 That goes for all latitudes on the northern hemisphere. So we are on the60N, starting at 180W (60N80) and moving to the east ending in 179E (60E79). On southern hemisphere: (00S-90S)60S180W-60S100W : 60W80-60W0060S099W-60S001W : 6099W-6001W60S000E-60S099E : 6000S-6099S60S100E-60S179E : 60S00-60S79 Such encoded waypoints (i.e. 60S79) can be also typed into standard navigation computers, i.e. 737 FMC. Thanks to Johann M. Kjartansson for preparing the instruction. Now to the FS .pln file, each field in the file has a purpose and must be correctly formatted to work, also each field is seperated by a comma,waypoint.x=REGION, FIXNAME, , FIXNAME, FIXTYPE, LON, LAT, ALT, AIRWAYREGION = ICAO region code e.g. LF: France, EG: United Kingdom, ED: Germany, (max 2 chars), blank if an Airport or no regionFIXNAME= ICAO code for Airport, waypoint, VOR etc. (max 5 chars)FIXTYPE= A: Airport, V: VOR, N: NDB, I: Intersection. (max 1 char)LON/LAT= Longitude and Latitude expressed in Degrees and Decimal minutes/seconds, the format must be N/S/E/W(x)xx* xx.xx' .ALT= Altitude in feet. Seems to be the Airport AMSL, +000000.00 for all other waypoints.AIRWAY= ICAO Airway code e.g. UL607, UM859, UG1 etc. can also be used for SID/STAR name e.g. NED1A, SAM3C etc. Blank if no name.Following this format, your 3 waypoints above should read :-waypoint.7=, 50N00, , 50N00, I, N50* 0.00', W100* 0.00', +000000.00,waypoint.8=, 50N10, , 50N10, I, N50* 0.00', W110* 0.00', +000000.00,waypoint.9=, 49N20, , 49N20, I, N49* 0.00', W120* 0.00', +000000.00,vasFMC will also accept the standard ICAO format 50N00, 50N10, 49N20, which is much quicker than typing out the full Lat/Lon co-ords.Hope this helps..........Adrian W.

Hi everyone, I am in the process of planning/building a simpit based loosely on the BAe ARJs and have a question. Is there a program (free or payware) that will display FS panels on networked computers via WideFS or similar, as most of the "remote" panels/gauges that I have found are for 1 and 2 engined aircraft (not 4). And when I do find engine instruments for 4 engines they don't really fit the aircraft. Thanks in advance, Adrian W.

Hi Guys, forget the above post, I've found the problem. It's in the A/C speed in Aircraft.txt. I tried a default A/C that flew in no problem, and when I changed it back (using AITM) the 146s flew in also without a hitch. The only thing that had changed was the A/C speed. Just a final thought is that some of these AI flightplans were downloaded from Avsim, MRAI etc., can't you guys test these things out before uploading? Anyway at least I'm no longer flying in the 24th century :-spacecraftBeam me up Scotty

Hi, I have added some AI commercial flights into French regional airports i.e. Flybe, Ryan, Easy etc. into LFBL, LFBE, LFBD, LFBO ...etc. the smaller airports have had parking added where required. Aircraft range from DH8s to BAe 146s. Now for the problem... If I wait at one of the smaller airports the aircraft just appears in its parking spot at the aproximate arrival time, it doesn't fly to the airport, whereas if I follow the A/C from it's departure Airport it takes-off, flies its whole leg, lands, taxis and parks. This problem doesn't present itself with the larger airports such as LFBD, LFBO, only the smaller ones, LFBE, LFBX etc. I've checked the AFCADs for the airports and can find no anomalies, is it the Runway length? If so why do the aircraft fly the legs and land when I follow them? Can anyone explain this ???P.S. I've checked the AI flightplans and there is more than ample time to fly the leg, park etc. before the next leg. I even set up one aircraft on it's own with at least 8hrs between legs to do EGSS - LFBE -EGSS , with exactly the same result, if I wait at the airport the A/C just appears like magic at it's parking spot !!! Thanks in advance