New version of Virtual Co-Pilot is about to be released.Now it works with PIC!The new version will be specifically for FS2002 and will not work with prior versions.Many of you may already know what I'm talking about, others maybe not. It's been around since the days of FS5. Do you want a co-pilot? But this is another type of co-pilot... You can't nag to him. Instead, he nags to you all the time!Virtual Co-Pilot is intended to make your flights more realistic by adding a complete airliner environment. This version of Virtual Co-Pilot features:* Complete set of custom sound files.* Parking brakes to set confirmation.* Cockpit Crew checklists compiled and recorded by actual airline crew : a. Before startup checklist b. Before taxi checklist c. Before take-off checklist d. After take-off checklist e. Initial descent checklist f. Before Landing checklist g. After landing checklist h. Shutdown checklist Automatic playback or manual triggering of the checklists is possible.* Speed calls during take-off and landing rolls : (80Kts, 90Kts, 100Kts, V1, Vr and V2) with user defined speeds for V1, Vr and V2.* "Gear Up" call, confirmation when gear up is selected ("Positive rate, gear up..") and "Gear, Up locked" when gear up and locked.* Flap retraction and extension calls according to user defined preset reference speeds, and according to aircraft type.* Autopilot keyboard shortcut keys to change altitude and heading holds. Easy and speedy control over the altitude and heading bugs, and also over the NAV1 OBS course when the autopilot is at NAV1 hold mode. This function is not available with PIC 767, PSS A320 and DF 734 because they use custom autopilots not sharing data with the outside world.* Warnings for too slow or too fast approach according to Vref.* Automatic approximate calculation of flap extension speeds according to Vref.* Ability to change the flap calls speeds for take-off and landing.* Fully functioning GPWS (within the limitations of Flight Simulator) for aircraft that don't have it (PIC is excluded since feature full GPWS).* Radio Altimeter calls at 2500ft, 1000ft, 500ft, 400ft, 300ft, 200ft, 100ft, 50ft, 40ft, 30ft, 20ft, 10Ft and 5Ft AGL. (For PIC, only the 2500Ft and 1000Ft are added, rest are done by PIC itself).* Minimums call at your defined decision height (50 - 500Ft).* Windshear warning in case such situation occurs.* Aircraft configuration error warnings according to aircraft type.* Fuel low warning. * Automatically or manually operated seat belts and no-smoking signs.( Not linked to the panel unfortunately.)* Cabin Crew announcements.* Cockpit to cabin crew calls.* Go Around detection and appropriate calls. * Fuel Dumping emulation. * Single keystroke exchange of NAV1 & NAV2 frequencies. Very handy when overflying your waypoints and don't use the FMC. Following aircraft types are supported in this version:PIC767, DF734, PSS320, PSS744, Default 734, 744 & 777.VCP works well with PIC/Posky Merge and with PSS744/MelJet/Posky merge.Did I forget anything? Maybe... Don't know...Oh, and if you have any more ideas, let me know before tommorow...Tests going fine, so unless something really serious comes up, I will upload it Saturday Evening/Night (UTC).George DorkofikisAthens, Greece

I like it, I like it A LOT! Can't wait for my chubby partner :]Best Wishes,Randy J. [email protected]" A little learning is a dangerous thing"AMD XP2100 |MUNCHKIN512 DDR RAM |ECS[/b ]K7S5A MB |[b]GF364 MEG |WIN XP PRO

GeorgeI would just love to have a co-pilot like that!!! :-jumpyEspecially since I'm testing FS2002 Flight Assistant, a voice recognition program that is being developed by Timm Linder www.thelindercompany.deIt would be awesome to be able to both speak to my FO and get approriate responses as well. :DTGIF

You can actually speak to your copilot using Game Commander 2.I currently have 767 PIC/FlightDeck Companion/Game Commander all configured together so that the copilot in FDC reads the PIC checklists; I respond by voice and the voice recognition in Game Commander translates my commands back to FS2002/PIC. It's really cool to say, for example; "Gear Down" then hear the sounds of the gear descending, followed by the co-pilot saying "Gear down, three green and locked."All this works very well but I'm interested in trying George's Co-Pilot since it's an adventure and should be better integrated and use less resources that the programs I'm currently running. Incidentally, you can also use Game Commander 2 to control any Windows software and it can be found at http://www.gamecommander.com/

WorkingStiffI think I was a little bit unclear about Flight Assistant. It uses MS Speech as the voice recognition engine. But the main thing with FA is the read backs and translation to key assignments. FDC is payware right? Is it worth the buy? Where can I get more information and finally. Does it integrate nicely with online flying?As far as microphone input I've split my headset mic to two soundcards on my comms-computer. One servicing Roger Wilco and the other one Flight Assistant. Thanks

>WorkingStiff >>I think I was a little bit unclear about Flight Assistant. >It uses MS Speech as the voice recognition engine. But the >main thing with FA is the read backs and translation to key >assignments. >I understood what you were saying. In my configuration, FlightDeck Companion does the readbacks and Game Commander 2 serves as the interface to translate my voice commands into keystroke actions. All this works very well; I only have to press my PTT button and I can execute all the PIC commands by voice.>FDC is payware right? Is it worth the buy? Where can I get >more information and finally. Does it integrate nicely with >online flying? You are correct; FDC is payware, the author has a support forum here on AVSIM at http://ftp.avsim.com/cgi-bin/dcforum/dcboa...&conf=DCConfID6 and you can also find more info on his website at http://www.oncourse-software.co.uk/fdc.htmTo me it's worth the buy but everyone assigns value differently. For the most part FDC is highly customizable; for example I can turn off the GPWS/altitude calls in FDC and use PIC's calls instead. The only problem I have with FDC is that the checklists are modular, so you can't move some items around to comply with the PIC checklists by Eric Sarkissian for example.However, this has been addressed in the forthcoming patch 1.2 which is expected to be released very soon.I sometimes use FDC while flying online on VATSIM to fill in those areas where there is no ATC coverage...that way at least I can hear the appropriate ATC chatter.

Please don't confuse VCP with FDC.Basically they are doing the same thing using a different method.FDC is a compiled program written in a high level language (doesn't matter which) and as such has advantages and disadvantages. The advantage (and the only one I can see actually!) is that you can set it up for each different a/c to play different wavs from different folders and save these options. Disadvantage is that it's an additional program running taking up valuable resourses from FS, depands on FSUIPC for communication with FS and response may be late. Don't know, haven't tried it, no flames please. Not my intension.VCP on the other hand is an adventure. It runs from within FS, does not take up resourses, communicates directly with FS (FSUIPC is not required), cannot save preferences and if I want different wavs for each a/c type I will have to make one separate adventure for each a/c OR program it in the same but the pilot would still have to use pre-defined options per a/c type, pretty much as done now, since there is no way to save/read data of any kind outside FS.I had started making VCP something like what FDC ended up, but aborted it because it's performance was terrible (that was 2 years ago)!If you want to have different wavs for each a/c type, we can work it out... I won't charge you much for the required changes... :-)George DorkofikisAthens, Greece

"It would be awesome to be able to both speak to my FO and get approriate responses as well."Maybe it's not clear enough. You don't command VCP... VCP commands YOU.It's VCP that will make the calls at the appropriate time you YOU must follow the actions. It's like a reminder... Or maybe I should rename it to Virtual Captain and not Virtual Co-Pilot! :-)Anyway, wait till you try it. It's a 'I love it' or 'I don't like it' situation according to each person's opinion.George DorkofikisAthens, Greece

ThanksI'll check it out. Sounds like something worth trying at least! :-)One more question though. Is it possible to change values using FDC in an easy way, for say radios and transponders and similar?Cheers

Hi againI get the difference between VCP and FDC! Looking forward trying your adventure out George!Cheers

LOLOk I get it. So when my FO reminds me to command "Positive rate. Gear up", I command "Gear up" to my FO and he then confirms "Gear is up and locked"? :DI still think it can integrate quite well with this Flight Assistant add-on!Cheers

Almost yes...There are 2 voices in the VCP wavs. Yours and the 2nd pilot.You are the PF and he is of course the PNF. Since not everybody has voice recognition programs its all done in wavs.Let me describe a take-off roll...You line up and advance the throttles to 50%, stabilize and off you go...At 35KIAS you will hear 'Take-Off Thrust'At 60KIAS you will hear 'Airspeed active' and the needle will start moving...3 more speed calls at '80Kts', '90' and '100'...then 'Vee One' at v1, 'Rotate' at Vr and 'Vee two' at V2.At positive rate you will hear the PF (which is actually you but you may not have a voice recognition) to call 'Gear Up'.As soon as you move the lever of the gear (VCP doesn't care how it is done, by you or an external program, just to see the movement), you will hear 'Positive rate, gear going up' from the PNF. Then as soon as the gear is up/locked PNF will confirm with a 'Gear up and locked'.At the accelaration height (1500AGL always for VCP) call for 'Climb thrust' will be made. Then at the proper speeds the flaps will be called by PF.PF 'Flaps 5'As soon as the flaps start moving PNF 'Speed checks, flaps 5'and so on...Now, FltAssistant can integrade at the point where the calls are made.I.e. the calls 'Gear Up', 'Flaps 5' in the above example should be made by you on your microphone at the proper time and FltAssistant should carry out the command (raise the gear or flaps) and VCP will detect that and respond accordingly.BUT... You will have to give the call at that time (when VCP makes the call) and not before because otherwise VCP will think you are ahead on the schedule and won't make the calls or confirmations.Let me know if you need more clarification.George DorkofikisAthens, Greece

Matt, I honesly don't know if you can change transponders and radios with the copilot in FDC, I only use it to read back the checklists. I'm sure if you go to the site I listed you'll see if it call also operate the radios.

George,I understand the distinction you're making between the two projects; and it's exactly what I was trying to convey to Matts. I agree with you about the resources taken up by FDC etc.I'm looking forward to using VCP with 767 PIC; hopefully it will be released this weekend.By the way, are you planning to support the PSS Dash-8 also?

Thank you guysI think I got everything out straight. It's friday afternoon over here and my brain is almost gone for the weekend and my guts are longing for a beer so please excuse me if I was confusing things up! :-beerchug