Tim_Sims

Taking photos in and around the many airports in Greece which also serve as military bases is a big no-no. You might even end up in jail for spying: http://news.bbc.co.uk/onthisday/hi/dates/stories/november/12/newsid_2518000/2518385.stm. There are prominent 'no photography' signs in terminals and on perimeter fences, and it's common for cabin crew to warn landing passengers accordingly. As for taking photos or videos en route - I'd have thought the drawbacks of irritating all of your customers with petty restrictions would outweigh the benefits of avoiding occasional mildly embarrasing stuff on YouTube or whatever. I've not heard of any European airlines taking a similar stance.

Seems to me this is just a step on from the longstanding "Boris Island" airport proposal (see here: http://en.wikipedia.org/wiki/Thames_Estuary_Airport). That's named after the Mayor of London, Boris Johnson, who's one of the main advocates (and a strong opponent of a third runway at LHR). But I guess even Johnson - who's known for his eccentric approach to politics - would draw the line at this.

Just to say that there's an identical problem with the PSS Dash 8, which you can fix either via FSUIPC as above or configuring the a/c always to load cold and dark. Scenery doesn't seem to make any difference. So maybe it's a PSS thing.

FLC mode is hardwired to descend at ~2000fpm above 10,000 and ~1000 below that regardless of thrust setting; I believe that IRL it's rarely used on descent. But by using VS and managing the thrust manually you should be able to descend at 2500-2800 fpm above 10,000 without overspeeding in most conditions.

Change the game time (even by only 1 second). Should force an ATC & traffic reload, and might do the trick?

There was a long-running and acrimonious debate on the POSKY forums about this, back when they still existed. IIRC the designers insisted it was accurate, and a couple of real-world CRJ pilots backed them up. I take their word for it, but you do wonder why Bombardier built an aircraft with so much excess power: every actual CRJ flight I've made has been perfectly normal.

Yep, saw your post on the FeelThere forum. They're normally really helpful on there (so long as you use your real name...) so the response was a bit odd. I've flown the ERJ for thousands of hours since it came out, and I'd like to think I knew it pretty well. But you're definitely not the only one with problems. I can think of several more FMC-induced glitches - eg double-clicking on the NEXT key any of the right LSKs on the Perf Plan page can also cause an immediate crash to desktop. And there are less fatal ones too - inserting a hold or procedure turn in slightly the wrong order erases your flightplan; attempting a direct routing with no intermediate waypoints (eg KJFK.KBOS) messes up the fuel calculations; inserting some STARs gives you waypoints thousands of miles away (try any approach to 23L at EDDL, for one), and so on. It's a lovely plane, as I said. But it's not flawless - so I may well weigh in on that thread IDC.

No worries. I just doubt that the workaround would have much credibility with your real-world pilot. There must be an easier and quicker (but non-simulated) way... FeelThere's E-Jets (ie EMB170/175/190/195) are in my experience less prone to crashes BTW, and with a more intuitive (but more complex) FMS. But the cockpit isn't as well done and they're not as much fun to fly IMO. I'd love to try out RC4, but on this ancient PC I have to be selective about the addons I use... The ERJ is fine, even with addon scenery, but adding too much other stuff means I get frame rates in low single figures.

It's a fairly basic rendition of what is a fairly basic FMC on the real ERJ (no VNAV on either the simulated or real FMC, for instance). But 'basic' doesn't always mean 'easy to use'... I've been flying the (simulated) ERJ for years and have never needed to route direct to a previous waypoint, but then again boring old default ATC doesn't make you do stuff like that. After a bit of experimenting, though, it seems that you're right: you can't use DIR to insert the origin of your current leg as the direct-to waypoint (ie, make the aircraft perform a 180-degree turn) as the FMC automatically clears the second of two identical waypoints placed together in a flightplan . What you can do is separate them by inserting another waypoint (let's call it ABCDE) between the origin and next waypoints (type it in the scratchpad and then press the LSK next to the next waypoint), then insert the origin after ABCDE. So you end up with a flight plan page which in your case would look like this: RSW ABCDE RSW KTPA ...and that works just fine; after ABCDE the aircraft routes back to RSW. The trick is in selecting "ABCDE". One thing the ERJ FMC does let you do is create manual waypoints. You need to pick a name not in the database already (like "ABCDE"); if you try to enter than in the flight plan it brings up the manual waypoint page instead. You now enter position information which places ABCDE shortly ahead of you on the same track. Suppose you're already 30nm from RSW on a 270 degree course. Type RSW/270/35 in the scrachpad; enter it using the LSK below "P/B/D"; and then select RETURN using LSK1R. This creates waypoint ABCDE 5nm straight ahead of you as the next waypoint; on reaching ABCDE the aircraft should turn through 180 degrees back to RSW. It's a convoluted and I dare say wholly unrealistic workaround, but it does work. Also NB that saving and reloading flights in the ERJ causes all manner of strange things to happen. Not recommended. Hope this helps. It's a lovely little plane, and its quirks are just part of its charm (for me).

There are (I think) 3 ways of doing this in the ERJ, only the first of which involves the DIR key... 1. To route direct to a waypoint already in the flightplan, press DIR, then the LSK next to that waypoint (using the NEXT key if it's on a later page of the plan). Don't try to enter the name of the waypoint again. That may well be what causes the CTD - there are a few other quirks of the ERJ FMC that seem to do that. 2. Alternatively and more simply / crudely, delete all intermediate waypoints between current position and the one you want to route directly to (by pressing DEL then the left LSK next to each one). May well leave you off course, of course. 3. To route direct to a waypoint not in the flightplan, don't press DIR. Type the waypoint name in the scratchpad, then left LSK2, effectively inserting it as the next waypoint. You may then need to delete intermediate waypoints from the original flightplan (as in 2 above). So in short, DIR only works with existing waypoints, and only then by selecting them from the flightplan itself.

Air UK Air Wales BA CitiExpress / BA Connect (ill-fated BA venture into commuter market, later sold to flybe) bmibaby Continental Go (ill-fated BA venture into low-cost market, later sold to easyJet) Highland Airways KLM Exel Maersk Manx (before being absorbed by BA CitiExpress - see above)

Commercial flights on this route use a BN Islander. The video OTOH is clearly taken from a single-engine type, I guess on a private flight. Another way of looking at this is that that flight is significantly shorter than the taxiing distance from Terminal 5 at LHR to the departure end of RWY27L/R. As the captain said as we taxied out a couple of years ago, "Ladies and gentlemen, unfortunately the first few miles of our journey to Johannesburg tonight is by road".

Something similar actually happened to me. I had a PPL before I had a driver's licence. First driving lesson I had, I somehow switched back into pilot mode and tried to take a right-hand bend by depressing the right pedal. Instructor not amused; thankfully no damage done other than to my self-esteem.

I see what you mean - the 'old' Exeter costs £6, whereas for £10 you can get that plus a couple of dozen mostly smaller fields in SW England. Sounds like a simple choice... except if it's Exeter you're really interested in, I'd wait until UK2000 release the promised new version in their Xtreme series later this year. Previous sceneries in this series have been very high-quality with not much effect on framerates. Will cost a bit more but worth it - and they usually release a free 'lite' version anyway.

Lovely panel, visually on a par with the payware FeelThere version IMO (if less complex & realistic). Andy's almost right. APU start sequence is... 1. Battery on (BATT 1 turn to AUTO) 2. Fuel pump 2 on (TANK 2 turn to ON) 3. APU start (APU MASTER click on ON) Engine start is then... 1. Fuel pump 1 on (TANK 1 turn to ON) 2. Engine 1 start (START/STOP 1 click and hold on START) 3. Wait for engine 1 to stabilise 4. Engine 2 start (START/STOP 2 click and hold on START) - fuel pump 2 is already supplying the APU of course.

If that's the plan you've created and selected in Flight Planner then ATC should give you vectors on departure from JFK to intersect the direct track from there to CCC no more than a few miles out from JFK. When you get within (I think) 2nm or so of the direct track, ATC will say "turn left/right heading xxx, proceed on course". If you stay on course ATC shouldn't then bother you at all with turn instructions until giving you approach vectors into KBOS. The aircraft you're using should make no difference at all.

I'd say this is a similar & maybe linked problem to the one in your other thread (http://forum.avsim.net/topic/378332-scenery-problem/). You've somehow lost some of your default textures. Solutions as in that thread - reinstall from the CDs or download a better-quality replacement set. Good luck, Tim

I thought (could be wrong) that AI aircraft only follow direct routes from origin to destination. They don't make enroute turns, although they should follow ATC vectors on departure and arrival. That said, I used to have an AI EMB190 which refused to climb. A few weeks of constant "please expedite your climb to FLxxx" was enough to make me change it.

If you know the filenames of the two textures you seem to have overwritten (presumably the same as those you downloaded) - then there's a really useful Excel file here in the library which lists the contents of the original CDs and .cab files. Search that for the two filenames, extract the original textures from the relevant .cab file back into your main texture folder, and all should be well. It's saved me more than once, with both textures and sounds.

Absolutely. In this case probably the GOW VOR, which is almost at the departure end of runway 23 and also on the southbound airway. When compiling an airways route FS9 starts with the waypoint on the relevant airway closest to the departure airport - in this and many other cases, far too close. Even if you did cross GOW, if you did it before being handed off to Departure then ATC won't recognise that. Another alternative would be could compile a flightplan in something like vroute, including a proper SID for the runway in use. Export to FS9 and the default ATC will pick up all the points on the SID.

When I got married 9 years ago I gave up real-world flying because it seemed that a solo hobby that took up lots of my spare time and all my spare money wasn't fair on the lucky Mrs Tim. Simming, OTOH, takes up all my spare time and virtually none of my spare money, and that pleases her no end.

IIRC, that file was part of quite a few of Project Opensky's models, which despite their demise you can still get from www.projectopensky.com. It definitely comes with this Delta 767-400 which is still lurking in my hangar. So if you download that you ought to get a copy of opensky_beacon.fx, which along with the other .fx files in that download you'd then just move into your Effects folder - and it should work just as well with your 737-800 too. That is, if you don't mind downloading 12MB worth of 767 to get a 4KB .fx file.

Downloaded & installed yesterday. I've got several other UK2000 sceneries and the quality has always been impressive. But EGFF is my local airport, I've used it hundreds of times, and I haven't really been able to realise the accuracy & attention to RW detail in Gary's work before. Everything is exactly where it should be and beautifully rendered, right down to the the disability spaces in the short stay car park - which (given the airport's commercial troubles) is just as realistically shown as mostly empty. Also no obvious FPS hit, even on my elderly machine. If only the actual owners of it cared as much about managing the airport as Gary did in developing this! Very highly recommended.

Hmm, I'd be surprised if a top-end scenery developer like UK2000 made a duff AFCAD file: it's such a basic error that I can fix it... Maybe it's something else altogether, or maybe you've got a duplicate AFCAD still installed? I've never moved from AISmooth v1.11. Not perfect but a lot better than the default. Others may be more familiar with the alternatives.

I'd guess neither of these problems are anything directly to do with World of AI, although having that much AI (WoAI plus default) won't help. 1. sounds like an AFCAD problem, ie with the .af2 file which maps out (in this case) Gatwick. It happens when the 'hold short node' (ie the point where the AI stops) is set in the wrong place, for instance too far back from the threshold. Easily fixed with a freeware editor like AFCAD or, for more modern sceneries, ADE9x. Both in the library here I think. Alternatively, so are several replacement .af2 files for Gatwick - maybe worth trying whichever one fits the scenery you're using. 2. sounds like a regular glitch in how FS manages AI: it vectors them onto final without any regard for speed or spacing. The solution is another freeware program, AISmooth, again in the library.