RestUnknown

Damn, display text was already unchecked. I thought you guys meant the text itself, like 'req higher', 'contact ground',... Changing the priority didn't do anything either. I guess it's just my laptop. I run FS9 directly on Windows (XP, 4gb of ram but only 3 is useable due to XP itself). Nothing else is running. It's an onboard audio chip (I guess, just plug my headphones in to the side of the laptop).

And for stupid question number 1234, how can I achieve this? I don't see an option in the options section of RC4. Number 1235, I assume you mean the priority of RC4?

No problem Ray, any answer is assistance! But this 'problem' only occurs with me? Or as klamal says, is it just the way RC is? I mean, does everyone have a slight delay when pressing a button before RC reacts? Or does it work immediately (in the assumption it is not instructing any other aircraft at the time)?

I feared this was the case... Even with AI traffic off it shows no improvement. For good old sake I tried the default ATC that comes with FS9 this morning and although I liked the immediate responsiveness, I forgot how awful it was. I was still at 28.000 feet when it was already vectoring me in to line up with the runway and chose a VFR approach on a runway way too short for a Boeing 747...

The CPU is running at about 50%. It's a Macbook Pro from late 2007: 2.2ghz Core2Duo and a Geforce 8600M GT. Far from the best, but FS9 runs fine enough. 3-4 seconds is in the extreme cases, I have very very rare moments where it responds instantly, but this is only for one 'order' I give. About average it's 2-3 seconds. Random AI chatter is unchecked, but to no avail. Unfortunately no spare pc available.

Hi all Been using RC for a while now, but it annoys me that it responds so slow. You press a button, but only reacts after 3-4 seconds. I hope it's a fault on my side so I can solve it or has this to do with the program or FSUIPC? Will a registered version of FSUIPC solve this? Thanks!

Hi all I make a flightplan using FsCommander (without sid's as I don't know which runway I'll be taking off), load it in RC4 (v.4.3) and take off using a sid. After a while RC starts saying I'm off my filed route and have to fly heading... (which usually is a 180° turn), this is quite annoying as I eventually will be getting back on my filed route because I'm just using a sid. I have to use Dir Ckp quite often because of this. Is there a way I can disable this message? I tried putting 360 in "heading deviation" but this doesn't help (in fact it makes it even worse and even at a 1 degree deviation it starts notifying me I'm off course). Smaller numbers in this option, won't help either. Thanks!

I tried everything. Des now or pressing the altitude knob, but nothing works. I guess something has a wrong setting in the fmc, I'll read the manual again and will keep you posted. Thanks for the help!

Ok thanks will try it later! Is there perhaps a better alternative to RC for Fs9? (not up to date with the evolutions anymore since I didn't play for a while)

Hi all I use the 747, but as this probably applies for the other PMDG products too, I've placed in this section. I fly using VNAV and LNAV, but also with RC4 and I tend to follow the instructions of RC4. This leads to a descent way before the T/D and leaves the CRZ mode enabled till I pass this T/D point, even though I'm already descending. Is there anyway I can tell the FMC to go to DES mode? Thanks

Wow nice site, thanks!

Thanks Mike! The gross weight is calculated by the FMC itself by clicking on request. I'll do the rest you said later on! P.S. the video is not mine, I stumbled upon it and it looks the same as how my 777 reacts

Thanks for the quick and clear answers! I have another small question which I will ask here, would be stupid to start another thread just for it. I fly using RC4 and without sid/star, so it aligns me parallel to the runway and then it lets me make a 180° turn to intercept the localizer. Not the most realistic way without the star procedure, but it's fine for me. But I'm wondering about the speed settings. I'm aware that you have to be at 250kt below 10.000ft. But what about the final parts of my approach? When I'm parallel with the runway? => still 250kts? Making the first turn? => still 250kts or starting to slow down to lets say 220kts? The second turn to intercept the localizer? => you get the point Intercept? => .... Glideslope alive? => ... (I believe I have to slow down to the landing speed here, no?) Thanks! P.S. it doesn't has to be absolutely spot on, because it probably depends on many factors, but just the grand rules would suffice.

Hi all I was wondering at which FL or at which point in the descent/approach pilots generally turn on the seatbelt sign? There are of course many rules and situations but let us just assume there is no turbulence, extensive holding or anything else, just a normal approach. I always put it on when at 10.000ft (the same where I put it off when climbing). Thanks!

Edit: It's basically like this, it can't be right the rear wheels stay this long on the ground after the nose is in the air, no?