Hi again.I know there's another thread on this, but I wanted to create a new clean one specifically for PIC as the other one was too generic.So, what can Virtual Co-Pilot can do for your PIC flights?Not much actually... The panel already has most of the features that VCP has, so I had to disable them in VCP. And there are other features that do not work with PIC because of how the gauges are programmed.Let's first see what doesn't work with PIC.1. Upon selecting VCP from the adventure menu, and load it, you will see that the panel has been put in a rather strange stage! The Starters will be both in the GND position, FMC data lost etc. I don't know why this happens. The only cure is to manually bring the panel to the state it was before or load a panel state from a flight.2. The autopilot shortcut keys for altitude and heading changes.VCP communicates with the autopilot via the adventure variables made available by FS. PIC has its own autopilot programmed and therefor does not use (neither read or write to) the default FS autopilot.3. GPWS. PIC already includes a very well done GPWS, so there was no need to have another one running. I've disabled this feature when PIC is selected as the aircraft type flown to increase execution speed and reduce demand for FS interrupts. However, two calls that I missed in PIC will be made. Those are the 2500Ft AGL and 1000Ft AGL. (PIC calls only 500 downwards)Here is a description of what to expect from VCP with PIC.Consider it a small tutorial so you can benefit the most from your 'friend'.1. Generic checklists. I know they are not PIC specific. I wanted to keep them as generic as possible yet going through the most important stuff.2. Speed calls. VCP will call when airspeed is active (40KIAS), at 80, 90 and 100Kts and then V1, Rotate and V2. 80, 90 and 100 are pretty standard... They don't 'usually' change! :-) But V1, Vr and V2 do. So, once you have set up your FMC and have those speeds, feed them into VCP one by one.3. During your initial descend (or at about end of cruise) you calculate the Vref speed (via the FMC) and feed it to VCP. Once you've entered the Vref speed the flap retraction schedule is roughly calculated as follows:Flap 1 : Vref + 80Flap 5 : Vref + 65Flap15 : Vref + 55Flap20 : Vref + 35Flap25 : Vref + 25Flap30 : Vref + 154. Flap calls are made at +- 1Kt from the reference speed. If flaps are not started moving after 10secs from the call, the call is repeated. When flaps up call has been made and flaps are still not up, and speed goes beyond 250Kts, a warning will be heard.5. During landing, VCP will call decellaration from 100Kts down to 60Kts (per 10Kts) and then will call for manual braking.Any comments or further ideas to implement are welcome.George DorkofikisAthens, Greece

George,A few comments. Positive and negative :).1. The documentationNice layout, and otherwise clear etc. etc., but it has errors in the keypress combos for different functions. For example the CTRL-Q in ending the speed entries is stated CTRL-A in the docs. Also the entires for V1, Vr, V2 are stated to work with CTRL-P, -S and -M, but elsewhere is said CTRL-1, -2, -3. And by the way, the order in the program itself is CTRL-1 for V1, CTRL-2 for Vr and CTRL-3 for V2, unlike in the docs. Acceleration height with CTRL-5 did nothing for me, so I guess it's something else ?Anyway, the errors in the documentation put me off a bit, because I couldn't make the keys work that were stated in the manual, and had to guess some of the keys and restart the adventure a couple of times, because I couldn't get the stated combos to work. You might want to correct the errors there, to make it more "user-friendly" ;).2. The programNicely done, however, a few comments to the "PIC-functionality" you discussed in your post.- I flew PIC and selected it appropriately from the list in the configs. Despite this, the GPWS shouted things like "glide slope" or "sink rate", which were of course duplicates to the PIC calls. (which AFAIK weren't supposed to be there)- I don't understand the FLAP retract/extend speed logic in VCP. Is it supposed to operate in the way that the Flaps are EXTENDED AND RETRACTED in exactly the same speeds, that are setup with either CTRL-F or CTRL-4 (which is it, these two are again mentioned in the docs) ? Or are the Speeds automatically calculated as per your post ONCE the "Vref" ("Vr" ??, same entry?) is given to VCP ?Is the "Vref" you are talking about also the same as "Vr" in the setup ? This is all I could find on approach speeds in the docs:"During approach your aircraft will warn you with a sound if your speed drops below your Vr -5kts (IAS) setting. You will also be warned if your approach speed is higher than your Vr +40Kts (IAS) setting. So, you may also want to reset the Vr speed to approach reference speed during your descent." ??- What is the correct key-combo for acceleration height ? CTRL-5 did nothing for me ?- What is the function of the checklists ? Two voices just go through some checklist. I thought that there was the possibility to "check" every item with spacebar or equivalent before going further. Apparently the lists are just "ear goodies", or am I missing something ? (probably am...)- The gear logic defies my logic. First "my voice" commands "Gear Up", then I put the gear up and the F/O says "positive rate, gear going up", and once it's up, the f/o says "gear up and locked" (in PIC it says this even when there are two green lights on and doors open).The above logic goes against what I've learnt. Isn't it usually this way:- PNF: "positive rate" (once radalt abv 0 and VSI abv +1000fpm)- PF: "gear up!"- PNF: "gear (going) up"- PNF: "gear up and locked"In my opinion the VCP "should" do it like this:- Once the RADALT increases AND VSI is +1000fpm the F/O should say: "positive rate"- Then once "g" (or equivalent button in whatever to initiate gear up) was pressed, the F/O should say: "gear (going) up"- And finally, once it's up and locked, the F/O should say: "gear up and locked".I think there is no need to include "my voice" to command the F/O, who then does nothing... it feels weird to command an F/O who, in effect, is me... anyway, you get my point :).Finally, I'd like to thank you for making this great piece of software available to us free, and even taking us PIC-heads into account. This post is not meant to put you off, only to tell what I've discovered, that I think should maybe get corrected or done some other way.Cheers,Tero

> 1. The documentationYou are absolutely right about the documentation! This manual was written 2 years ago for ver 4.5 for FS2000. I did a quick correction to the keys on the table at the beginning of the manual but forgot to actually read through it carefully. 100% my mistake.The correct keys for V1, Vr and V2 are indeed Ctrl-1, 2 and 3.Ctrl 4 is for the flap speeds and Ctrl 5 should be acceleration height. I don't know why it did not work for you. I'll check it out.> 2. The program>- I flew PIC and selected it appropriately from the list in the>configs. Despite this, the GPWS shouted things like "glide slope" or >"sink rate", which were of course duplicates to the PIC calls. (which>AFAIK weren't supposed to be there)By selecting that you are using PIC, all GPWS should be hashed except the 2500Ft and 1000Ft calls... I'll check it...>- I don't understand the FLAP retract/extend speed logic in VCP. Is>it supposed to operate in the way that the Flaps are EXTENDED AND>RETRACTED in exactly the same speeds, that are setup with either >CTRL-F or CTRL-4 (which is it, these two are again mentioned in the >docs) ? Or are the Speeds automatically calculated as per your post >ONCE the "Vref" ("Vr" ??, same entry?) is given to VCP ?First, yes, Vref is the same as Vr (as referenced). While on the ground it's Vr, once airborne its Vref.You can set VCP to call flap retraction and extensions at different speeds. During pre-flight (on the ground), you feed VCP with the flap RETRACTION speeds. Once in the air, and with flaps up, you feed VCP with the flap EXTENSION speeds. Flap speeds can be set with Ctrl-4.Caution though. When you set Vref it will overwrite any speeds you had entered before. If you wish to manually enter the extension speeds, first enter the Vref speed and then the flap extension speeds.>- What is the correct key-combo for acceleration height ? CTRL-5 did nothing for me ?I'll check it...>- What is the function of the checklists ? Two voices just go through>some checklist. I thought that there was the possibility to "check" >every item with spacebar or equivalent before going further. >Apparently the lists are just "ear goodies", or am I missing >something ? (probably am...)Yeap.. that's just that. Ear candy... Just a reminder if you have done some basic stuff... Going through the items with spacebar you say... Hmmmm Interesting... :-roll I'll see about this...However, FS doesn't provide too much information to adventures...Some things can't be known if done or not.>In my opinion the VCP "should" do it like this:>- Once the RADALT increases AND VSI is +1000fpm the F/O should say: >"positive rate">- Then once "g" (or equivalent button in whatever to initiate gear up) was pressed, the F/O should say: "gear (going) up">- And finally, once it's up and locked, the F/O should say: "gear up and locked".The only difference I can see if the 'gear up' call after the positive rate... You can always edit the wav to your liking and simply cut off that part... :-)>Finally, I'd like to thank you for making this great piece of >software available to us free, and even taking us PIC-heads into >account. This post is not meant to put you off, only to tell what >I've discovered, that I think should maybe get corrected or done some>other way.And I want to know all your comments. I'll try my best to correct any errors or wrong logic (time permitting).I'll better go re-write the manual now...Jeniffer... can I see you in my office please? ;-)George DorkofikisAthens, Greece

George:fyi...I have not been able to change the acceleration height either.Great job overall! Now I can stop using S-Combo (another program running and slowing my poor PIII-600 frame rates).Damon

You are correct guys.As I put that in at the last minute I didn't check it (too sure of myself... yikes!) and had forgot to define the CTRL-5 key that triggers the input.I'll fix it asap along with most of the comments of Tero (GPWS etc) and release a fix very soon...Thanks for your support!George DorkofikisAthens, Greece

George,Thanks for the great work and flexibility!I'd like to elaborate a bit more on the gear logic thing though, as I see that you probably didn't understand my point.I mean, that could the PF's "command" GEAR UP be removed, AND the POSITIVE RATE message be put to actually trigger ONCE there IS positive rate (+vsi and +1000fpm). The once the Gear lever is moved UP, the f/o could say "gear going up", and once it's up "gear up and locked" (or "gear up, lights out")To make this a bit more clear. This is how it works now:PF (me): "Gear Up"PNF: "Positive rate, gear up"PNF: "Gear up and locked"See? There's no point for the VCP to call anymore "positive rate"s, if the captain has already commanded the gear to go up. The positive rate -callout has no other meaning than to inform the PF that the aircraft has actually left Terra Firma, and then the Captain can decide whether or not he/she thinks it's suitable to actually raise the gear or not :).This is how I would like it to be :) PNF: "Positive rate" (once +vsi and +1000fpm, or one of them)PF: no voice, but once the gear lever is moved -->PNF: "gear going up"and once it's upPNF: "gear up and locked"OR alternatively you COULD insert a PF voice to the point where the PILOT moves the Gear lever, to say "Gear Up!". I think that it's not needed because I AM the pilot flying, I don't need anyone to portray ME in the VCP :). Then it would look like this:PNF: "Positive rate" (once +vsi and +1000fpm, or one of them)PF: once the gear lever is moved -> "Gear Up!"PNF: "gear going up"and once it's upPNF: "gear up and locked"Sorry for being a nit pick... just trying to make the most out of this :) !rgdsTero

Hi Tero,Yes, got your logic. VCP was originally made for FS5, and then got its new wavs for FS98. The reason I've made many things the way they are is because when I first programmed VCP I wanted it to act like a reminder.At those days I kept forgetting things, and still do if too busy flying, and wanted something to remind me.Especially for the gear, there were times that I forgot to raise the gear and remembered it while already at 200KIAS...Back then, VCP really helped me remember basic things while flying airliners, like an instructor over my shoulder.That's why the 'Gear up' call from the PF.Let's not forget that the real pilots fly at least in pairs, one checking and completing the other, while we fly alone and have to do everything! In an Airbus, this is fine... Only one is required, the other one is to make the passengers comfortable and for safety reasons, but in the 767 the workload can get pretty high...Why am I saying all this? I don't have a clue! :-)Anyway, to keep it short, I'll see if I can put yet another option and make 2 seperate types of call. This only if I can use the existing wavs. Andy Brummer who recorded the second voice is unreachable the last few years so I'm unable to record any new wavs. Last time I heard from him he was moving to New Zealand as F/O of Air New Zealand on the 767s (He was F/O on 757 for AMM when he helped me with the recordings)Fly safe,George DorkofikisAthens, Greece