Scott, I have searched the forum for this, but unable to find an answer- Will the .wav (Fleetwood) files for RC3 be public domain as with RC99? If so, any idea of the size of the basic set without chatter? Now I believe it is somewhere around 76Meg zipped.Sure wish it were coming out sooner....but for all good things, we must wait.Steve ParkPresident Livewire AirlinesFlight Director Livewire AirlinesHub Manager KATL/[email protected]

wavs will be free, absolutely. i can't/won't charge for other people's recordingswith version 3, there won't be a fixed number of controllers/pilots you have to have. if you only want one controller, you only have to download one controller.right now, i have 12 controllers and 6 pilot/copilots. i'm zipping them all up, and they add up to 187mb zipped. but not all 12 controllers are required, nor are all pilots.

14 controllers, 6 pilots (counting JD and Jamie).

I hope the new version will NOT ask you for a transponder change if you declare an emergency.JImCYWG

Jim,It would be realistic.

Sounds great Scott.If that is what really happens then by all means. I just thought that ATC might not bother you with something like that with the workload of landing in the Azores with no fuel.JimCYWG

Diane,Center's are "assigned" sets of codes. We sort of own them. ZME for instance is the '15xx' and '56xx' set. ZID has their own, ZKC their own etc...If a Center's computer detects that an incoming aircraft is on a code that's already being used by another aircraft in it's Center, a new code is assigned randomly. Happens all the time, everyday.Though a controller issuing a new code doesn't happen each time an aircraft is switched to an ajoining Center, if you get a new code it'll be when you first check onto that new Center's first freq.Consider yourself very lucky to never have this happen to you . Very odd. I hope you haven't jinxed yourself .Doug

Jim,What actually happens is that the pilots will enter the emergency code into the transponder if they can and call in with the emergency. The reason for the E xpndr code is to get you immediate attention. I've seen it for real in an ATC facility - it seriously gets attnetion.The controller then will ask the status. If the pilots can answer, ATC will have them change to another xpndr code. Still an emergency, but stops all the alarms going off.Also, if the pilots lose comms, then they can quickly enter the E code, then switch to an "I have no radios" code. There are numerous codes for various problems.I am not going to give the codes, although they are generally known. We are still debating whether or not to use them.

Those codes are available on the net well listed and documented. I don't remember the site now but I have seen them. My point being I don't think it would be any harm to use them, if the reason you are debating has to do with security concerns.

Hi, I'm new to Radar Contact and this forum, but I'd like to add a few comments to the discussion about the user interface in RC3. (The picture of the window seems to be unavailable now, but I hope I get the general idea.) Please, bear with me if some of it has been said before.One of the things I dislike about the default ATC in FS2002 is that you first have to locate the appropriate reply on the screen and then find the corresponding key on the keyboard, so I'm mildly disappointed to learn that this principle will be taken to RC3. I appreciate that something has to change in relation the RC2.2 interface, given the many choices available in RC3, but I think it should be possible to use the mouse to make your picks as well.When flying jets with complex panels, in my case the DF737-400, the mouse is often the most intuitive control device, at least if you're not a complete fanatic with either a full-blown hardware cockpit or a fantastic memory for keyboard layouts. Furthermore, it's becoming increasingly difficult to find intuitive positions for all those keys that you need for various add-on products. Others have explained why yokes, sticks and other controllers are poor alternatives for many.Another concern of mine is the apparent dependence on Pete Dowson's AdvDspl. Unless he makes something special for RC3, this means that the current collision between RC and e.g. FSAssist will continue to exist. Presently, I also experience some problems when trying to use AdvDspl with Dreamfleet's new Archer, but that may be some freaky anomaly in my setup.I would much rather see RC3 have its own dedicated interface, perhaps in the shape of a one-gauge panel, like e.g. FSMeteo's WeatherDisplay gauge. This would allow you to make a more slick interface and it would probably enable "gauge wizards" to come up with alternatives designed for particular aircraft. And it wouldn't exclude the keyboard alternative for those who prefer that control method.

Henrik,The use of Pete's AdvDisp is the simplest way for an RC interface. The problem with making a gauge with the RC information is that the gauge would have to be included in every single panel anyone could possible use. Not possible. It's one reason I stopped using ProFlight. I got tired of making panels to fit the FMC, although it is how I got started in this "biz". It's a total pain in the ass, and users who don't know how to edit panels would be out of luck.With AdvDisp, one just moves/scales the window and docks and they're done.As for keys, V2.2 and V3 allow you define any key or combination for all commands. In 2.2, it's in the init_voices.txt file. In V3 it's part of the main interface.V3 will be made more simple with a numeric selection: '1'-'5', with paging '8'-'9', and return to page 1: '0'. So B3 will be much more simple to use. I am using Ctrl-Shift-# so it doesn't interfere with anything. Again, the keys are definable.

just a point of clarification, i was using this menu-ing technique, with advdisp.dll, prior to fs2002 was released. so i didn't carry it forward :-)we've had this button/mouse versus character/keyboard discussion for a long time. all things being equal, the balance is swayed by the fact that you can program joystick buttons to send the key strokes that you define.considering the fact that you can size the window, match the background color to the panel, change the font size and color, you can make this menu window any size you want, and put it anywhere on the panel you want. or you can undock it, and put it on a different monitor, if you would like

>Another concern of mine is the apparent dependence on Pete >Dowson's AdvDspl. Unless he makes something special for RC3, >this means that the current collision between RC and e.g. >FSAssist will continue to exist.I've been using fsassist while beta testing rc3, and there doesn't seem to be any conflict. The rc menu is displayed in the advdspl window, and the fsassist menu is displayed in the fs message window.Sidney Schwartz [KPDX]

Scoot, >The problem with making a gauge with the RC >information is that the gauge would have to be included in >every single panel anyone could possible use. Not possible. It could be a free-floating window like the fs gps. Not the most elegant solution, but workable.I just downloaded the demo version of "Easy Gauge", a program that purports to allow even idiots like me to create gauges for fs2k/2k2. Maybe an rc display/control gauge is not that far-fetched.Sidney Schwartz [KPDX]

Suds,If the product is as simple as they make it sound, then that obviously opens the door to all kinds of things. And I would certainly be the first at the gate with my Platinum card in hand to update everything I have, including all my panels and ACLoader. I'm chomping at the bit to get rid of the 2K2 autopilot, but I don't think it'll be that complex.We'll see.It could be a free-floating window like the fs gps. Not the most elegant solution, but workable.Still, that doesn't change the fact that every panel file would have to include another window with the gauge, in all shapes and sizes for different panel sizes, taking up more space, covering things over to display it. I'm not about to add yet another window to all my panels for one product, even if it is RC. This again is all too ProFlightish. I do everything in my power to get rid of windows and make the panels all visible at once. But if someone wants to come up with something, certainly they can.Besides, AdvDisp does that now. I suppose one could make an RC Control Panel style gauge with clickable commands.