james_uk

Ron, Thanks for the detailed reply. It'll take me a little time to go through this but i'll go through it in detail and try your suggestions and report back. thanks again James

Oliver - thanks for pointing this out. I downloaded a recent version and tried again - and the runways are now correct. Thanks for your help.

Hi, I've flown a few flights now from EGCC to EGLL whilst I practice using RC4. On every occasion that i'm given vectors to Heathrow using runways 09L/09R, the final heading that the approach controller provides (125 degrees) is not an intercept course for the localiser. I'm using PMDG 737 NGX and the ILS doesn't seem to be in range at the distance from the runway the 125 heading intercepts the runway heading. From memory I was at least 25nm away from the runway and the display in the 737 didn't show the ILS yet - so there was no chance i'd establish on the localiser. Anyone know what i'm doing wrong? I'm using REX essential, PMDG 737 NGX, RC4, My Traffic X 5.4B and FTX Eng. Thanks James I forgot to mention: when i'm given vectors to runway 27R it's all fine - the intercept heading for the ILS is perfect.

Hi, I've recently installed RC4 again and i've been enjoying using it for a few simple domestic UK flights. I've noticed that RC4 is reading out the runways as 06 and 24 at Manchester but the correct names are 05 and 23. I'm using PMDG 737NGX, REX Essential, My Traffic X 5.4B, UK200 EGCC Extreme and FTX Eng. I investigated this and found that the FSX database had 06 and 24, so clearly not RC4's fault, so I re-enabled my UK2000 scenery (I had it disabled as I decided to use the default FTX Eng EGCC airport) and the runways were then correctly marked as 23 and 05 in the FSX flight planned. I used the "Rebuild scenery DB" option in RC4, but when I next used FSX RC4 was still reading out 06 and 24. Any ideas where i've gone wrong? RC4 version 4.3.3845 many thanks James

http://www.realenvironmentxtreme.com/forums/index.php?/topic/14771-natural-enbplus-download-included/

Thought i'd share this. For REX customers there's a "Free Stuff" area on the forum and Tim has added an ENB tweak download. I'm quite impressed with the results - couple of images attached. I thought i'd let people know it was there - I tried it out at Manchester in the NGX.

for a laugh I tried a transatlantic flight in the 800-WL and made it to JFK, just to see how far it could really go on a tank of fuel.

I've had a look at the the PDF and it does mention limitations in FSX that could cause problems with this approach. I did a test in the built-in 737 - i've attached some screenshots. Interestingly I could program the radio to 108.35 and actually get the autopilot to fly the approach. The autopilot correctly intercepted the localiser and eventually the glideslope when in APP mode. The only thing that was odd was that the DME reading was still not showing a figure (which is quite important on this approach given you fly visual at 5.5 DME!! So i'm certainly getting different results in the built-in 737 (I can fly the approach via the nav radio) but cannot in the ngx.

Hi thanks for the responses. I've tried the scenery fix suggested, however this didn't make any difference to the IGS approach. The FMC can find the ISI IGS if you enter it on the RTE page - in effect I can fly direct to it but I can't get it to be interpreted as an IGS - i.e. with the glideslope on APP mode. The best I can do is fly direct to it. I've attached a couple of screenshots showing my setup. The images show the approach with ISI as a waypoint on the RTE page. The nav radios were manually tuned to the appropriate frequency but I couldn't get the VOR/LOC or APP buttons to work. It's notable that the DME reading on the left display shows ----. thanks againJames

Hi, I've got a question about IGS approaches, and the correct way to input these (either into the radio or the FMC). I'm flying the 737-NGX into LSGS (Sion, Switzerland). I've chosen IGS RWY 25 as the approach as it looked challenging/interesting, however i'm having difficulty programming the IGS approach into the FMC. I fly the following route: LSZH -> LSGS SID WILG5 FRIW105 SANETD MOTMOT086/25 The last entry into the FMC is part of the approach chart - i.e. 25 DME from MOT VOR on radial 086. I then initiate a left turn to 247deg to intercept the IGS (108.35, 246deg, ISI). There's no way of inputting ISI IGS on the DEP/ARR page of the FMC (it simply isn't listed). I've tried: - inputting on the RTE page- manually entering into the NAV radios and applying a CRS on the A/P panel- entering on DEP/ARR (isn't listed) however none of these work. I cannot seem to get a distance reading to ISI - it's as if I never get into range or something else is wrong. The left display in the VC (attitude / FD display??) shows "ISI" however the distance reading never kicks in, no matter how close I get to LSGS. I've also tried VOR/LOC mode, APP mode etc but none of them kick in and start to fly the IGS. Any ideas of what i'm doing wrong? Thanks in advance James