hi guys, i never write in this form because i dont know what to say. but i realy enjoy reading.anyway i encounterd 2 problem: one with merging the 767pic with IFDG or POSKY and the second is that i dont know if its a problem but when i press the LOC button (at a really good distance) and its being captured (LOC in GREEN) its not realy locked its a bit off the rwy then i press the APP and its capturing the GS very good but still do not intercept the LOCALIZER well then when im over the TRASHOLD its beging to localize and its too late... 2. when merging everything is fine (exept the LOC problem) but i can start rotating the plane at 100KTS (the trim is set exactly as the original 767pic and the ZFW too) what can i do?? i know ive merged correctly because Van sent me his aircraft.cfg but still....any help will be aprriciatedcheers,Dan

Make sure you are using a PIC767 WP air file and nothing else.I don't know about the IFDG, but with POSKY you need the Merge application by Lee Heatherington (on avsim library or this forum). There may be entries in "van's" config file interfering with the aircraft performance.Search the library for picposky merge or this forum.Rob.

Nothing was changed in the aircraft cfg that could affect the flight dynamics and I had stated that the WP 767 .air file was to be used for the merge. I set the merge up the same way Lee did for his PIC/Posky merge, leaving slat scalars set to zero as to not affect PIC flight dynamics and added the typical contact point and lighting info, so other then not creating a batch file as Lee did the merge is pretty much the same. I can't say that I get early rotation problems at all when I have the plane trimmed properly.Regards,Van LatendresseYeoDesigns/AFG GroupPanel/FDE Designer

Hi Van,I'd ike to try the IFDG 767...where can I find your config file?Thanks,Rob.

Rob http://www.czeg.org/ifdpic.zip you will have to change some of the info in these lines to suit you airplane.---------------[fltsim.0]title=767 iFDG CanadianVA/picsim=767 Pilot in Command Wilco Publishingmodel=panel=sound=texture=kb_checklists=767PIC_CHECKkb_reference=767PIC_REFatc_id=BTVCatc_airline=Canadian VAatc_flight_number=1123ui_type=Boeing 767-300ui_manufacturer=Boeingui_variation=Canadiandescription=767 Pilot in CommandnCopyright © Wilco Publishing, 2002------------------------

Cool. Thanks.

..and just to be sure...NOTHING in the config file at this link will interfere with PIC air file?? I had heard some rumours to the contrary.Rob.

1 - Try a different runway with NO winds. Some runways are really poorly lined up ILS in MSFS....KLAX 24r, comes to mind.2 - Check the trim setting (should be around 4.5-5.0 at 'standard' weights) and rotate at Vr on the EHSI. You do have the FMC ZFW entered correctly and such?Rob.

The aircraft cfg is from the PIC package and only the slats section from the ifdg 763 was added with scalars set to zero so as to not affect PIC flight dynamics, but the slats will animate and contact point and lighting info was added as well.Like I said nothing was added that would affect PIC flight dynamics as the aircraft cfg is PIC and not ifdg and I had informed Dan on more then one occasion that he needed to check his trim as by default the panel loads with the trim set too high if you are at a low to standard weight. I also use the trim numbers you have set out above Rob.Regards,Van LatendresseYeoDesigns/AFG GroupPanel/FDE Designer

Very good, thanks for the reply.My concern was that the link to the IFDG config file on the PIC Flying Club website may NOT be the same as your -original- config file, Van.If it is original and not changed at all, great...but I know Bill likes to tweak and fiddle about with things...including his underware ;-)Thanks,Rob.

LOLThe original aircraft cfg for the ifdg/PIC merge that Bill had on his site was put together from the directions I had set out at IFDG's forums, but after checking the aircraft cfg out I had noticed some double entries that could cause problems, so i emailed him my aircraft cfg and as far as i know it's the current one on his site.It was also nice to find out that Bill is only about a 20 min drive from me...Always nice to meet a fellow PIC head that lives so close and he likes beer to boot! :)Regards,Van.

I knew it...he tinkered with your config...and people think I am paranoid..heheI don't trust him anymore ;-)Where can I get the necessary -unadulterated- file from?Rob.

I just downloaded and checked out the aircraft cfg from Bill's site and all looks the way I left it, no tinkering.So the one at his site is current and unadulterated...lolVan.

Hi Van,I replaced the config file from the zip downloaded (changed rudder effectiveness to 24), edited the aircraft specific information, d/loaded an IFDG original model from avsim (Delta) and booted up.The model is very sharp...except...the leading edge slats do not extend with the flaps... I am surprised Captain Bill did not notice this ;-)...and I can only get the front door to open. Oh, I did manage to get the flag to extend through the roof, but I see in the config file mentions multiple doors, etc. I tried shift- E, F, Q, T..all the animation commands I know of.I also notice the flap settings in the config file relate to different system types...I am not convinced that it is in NO way affecting the PIC original flight dynamics.Great looking plane despite what I say above!Thanks,Rob.

The leading edge slats extend with the flaps just fine for me and the system type number won't affect PIC flight dynamics (remember the original PIC aircraft cfg didn't even have a slat section) as it is the scalars that will and they are set to zero. I really notice no difference between flying the Posky or ifdg763, but to each their own :)As far as the exits go, only the main exit opens and if you press shift+E+2 the one cargo door will open (on the passenger model) I believe either the tail hook or wing fold commands are used for the large cargo door on the freighter versions. I see you found the flag already (whats that all about anyway?...lol) I assigned just "D" to the select exit command this way I eliminate a key stroke and run in to far less headaches opening the exits, so it's "D" for the main exit and "D+2" for the cargo door.Regards,Van LatendresseYeoDesigns/AFG GroupPanel/FDE Designer