Since the ILS doesnt work properly (intercepting the LOC is screwed up, descends and climbs too much etc when intercepting, not a smooth interception) if i replace the PSS [autopilot] section-which is from the PSS aircraft.cfg-with the POSKY [autopilot] section?If it works it'll solve soo many peoples problems with the ILS on the merge.Here:PSS one (currently being used in PSS POSKY 777 merge)[autopilot]autopilot_available=1 flight_director_available=1 default_vertical_speed=1800.0 autothrottle_available=1 autothrottle_arming_required= 1autothrottle_max_rpm = 108.5autothrottle_takeoff_ga= 1pitch_takeoff_ga=8 ;max_pitch=10.0max_pitch_acceleration=1.0max_pitch_velocity_lo_alt=0.7max_pitch_velocity_hi_alt=0.4max_pitch_velocity_lo_alt_breakpoint=11000.0max_pitch_velocity_hi_alt_breakpoint=25000.0max_bank=25.0max_bank_acceleration=1.4max_bank_velocity=2.8max_throttle_rate=0.08nav_proportional_control=11.00nav_integrator_control=0.17nav_derivative_control=0.00nav_integrator_boundary=2.50nav_derivative_boundary=0.00gs_proportional_control=22.0gs_integrator_control=0.530gs_derivative_control=0.02gs_integrator_boundary=0.70gs_derivative_boundary=0.00yaw_damper_gain = 1.0POSKY one:[autopilot]autopilot_available= 1flight_director_available= 1default_vertical_speed= 800.000autothrottle_available= 1autothrottle_arming_required= 1autothrottle_takeoff_ga= 1autothrottle_max_rpm= 110.000pitch_takeoff_ga= 0.000use_no_default_pitch = 1 // 0 = Default to current pitch mode, 1 = No default pitch mode.use_no_default_bank = 1 // 0 = Default to Wing Leveler mode, 1 = No default bank mode.default_pitch_mode=0default_bank_mode=0max_pitch=10.000000max_pitch_acceleration=1.000000max_pitch_velocity_lo_alt=2.000000max_pitch_velocity_hi_alt=0.300000max_pitch_velocity_lo_alt_breakpoint= 7000.000000max_pitch_velocity_hi_alt_breakpoint=24000.000000max_bank=30.000000max_bank_acceleration=1.200000max_bank_velocity=2.000000max_throttle_rate=0.030000nav_proportional_control=9.000000nav_integrator_control=0.250000nav_derivative_control=0.000000nav_integrator_boundary=2.500000nav_derivative_boundary=0.000000gs_proportional_control=9.520000gs_integrator_control=0.260000gs_derivative_control=0.000000gs_integrator_boundary=0.700000gs_derivative_boundary=0.000000yaw_damper_gain=1.000000Please help as it'll solve almost all my problems with the merge for my favourite plane.Cheers, any feedback appreciated.

Nandan,It may not be the autopilot, as I've never really had any issues with the default settings. The bahaviour you describe might be a feature of moments of inertia that are set too high. Make a backup of your aircraft.cfg file, then paste these lines into the [weight_and_balance] section, over-writing the ones that are there now. (These are from the FDE that I uploaded a few days ago.) If you post your original values here, we can make a comparison.empty_weight_roll_MOI= 7000000.00empty_weight_pitch_MOI= 20000000.00empty_weight_yaw_MOI= 17000000.00empty_weight_coupled_MOI= 1000.00See if it makes any difference. If the plane is nosing up and down rather than following the glideslope intercept smoothly, the pitch MOI may be set too high.;)

Microlight,Except for the 'coupled' moi, they are about the same. I don't believe that is the problem. It has to be section 1199 in the air file. The PSS and POSKY models have different values in that section.Nandan,Is this the air file you are using: 'PSSB777LR-GE' ? Just trying to help out. You have been trying to fix the 'merge' since November 2009, haven't you? What I see is a payware (PSS) and a freeware (POSKY) trying to 'merge', but I also see a lot of 'odd ball' advice out on the net. Did you ever get the panel (VC) working? Myself I would find a 'working' panel and forget about the 'looks'. You want function. Then work on it when you can. Too many nice models and panels out there to waste ALL your time on ONE aircraft. Good luck.CBNapamule

Yup, PSS .air fileThat is true-trying to get the merge as good as i can-but the is no 777 that is good enough for fs9 and there probably won't be. Plus it is my favourite plane and i do want to fly it...i also fly other planes too, but lets atleast try to make a reasonable 777 for fs9.The merge aircraft.cfg is basically the PSS one and the PSS 777-200LR ILS worked perfectly, just the POSKY PSS ILS doesn't intercept properly. Maybe the autopilot is where the main issue is, (also stated when you download this guy's FDE update: http://www.jdserver.mine.nu/johan/From his aircraft.cfg:[autopilot]autopilot_available=1 flight_director_available=1 default_vertical_speed=800.000 autothrottle_available=1 autothrottle_arming_required= 1autothrottle_takeoff_ga= 1autothrottle_max_rpm= 110.000pitch_takeoff_ga=15.000 use_no_default_pitch = 1 // 0 = Default to current pitch mode, 1 = No default pitch mode.use_no_default_bank = 1 // 0 = Default to Wing Leveler mode, 1 = No default bank mode.default_pitch_mode=0default_bank_mode=0max_pitch=15.000000max_pitch_acceleration=0.5000000max_pitch_velocity_lo_alt=2.000000max_pitch_velocity_hi_alt=0.300000max_pitch_velocity_lo_alt_breakpoint= 5000.000000max_pitch_velocity_hi_alt_breakpoint=20000.000000max_bank=30.000000max_bank_acceleration=1.200000max_bank_velocity=1.5max_throttle_rate=0.030000nav_proportional_control=15.00nav_integrator_control=0.25nav_derivative_control=0.00nav_integrator_boundary=2.50nav_derivative_boundary=0.00gs_proportional_control=10gs_integrator_control=0.5gs_derivative_control=0.000000gs_integrator_boundary=0.200000gs_derivative_boundary=0.005yaw_damper_gain=1.000000Maybe that is the reason, I don't think the weights etc should matter too much cause it is basically the PSS aircraft.cfg and the PSS air file. And autopilot controls interception etc so it might work. (If you change the rate at which the plane banks to intercept etc the LOC interception could be much smoother-or something like that.)Anyways, we all have to help cause many of us loyal FS2004/fs9 users want this aircraft so badly...(me!)All the problems could be solved. (also how the heck do you correct fuel flow in the merge! It is so "not burning enough fuel" -using the PSS fuel_flow_scalar= 0.950)Cheers

Er, you could try the FDE for the Posky 777-200 I uploaded a week or so ago... :(

Microlight,Are your initials 'B.D.H'? And if so, did your FDE's address or modify section 1199 (Autopilot) section of air file?CBNapamule

Where's the FDE uploaded?

What we refer to 'FDE's' is actually the 'aircraft.cfg', COMBINED AND MATCHED with (ie: cfg line 'Sim=xxx' line), the 'air' file. Those two comprise the aircraft's 'FDE'. Microlight said: 'Er, you could try the FDE for the Posky 777-200 I uploaded a week or so ago...'. This might work. You would sub his air file for what's in there (rename it) and/or just change 'Sim=xxx' (xxx being the name of the new air file, without 'air' extension). I wish he had given us a zip file name as we can't verify it's 'his' (we don't know what name he used to upload). You can have an aircraft.cfg for a 737 and an air file from a 747 and the 'FDE's' would be suspect, or not even 'work' with each other. So in your 'merge' you would need to have a 'match' (name and model related specs) for those 2 files. When you do a 'switch' of air files (like I believe they did with this particular 'merge'), one air file might not have a 'good' autopilot section (1199). Therefore you autopilot would not 'work right' due to differences in 'specs'. You can open air files, and do right click on SPECIFIC section (ie: 1199) then do 'Copy to Clipboard', go to the other air file and right click (anywhere) and do 'Paste from Clipboard'. But you have to delete the 'bad' section first, as with this operation nothing gets 'overwritten' and you would wind up with 2 identical 'name' sections, which is not good practice. We're here to learn. There is nothing in SDK telling you about this either (just in case a SDK'er wants in).CBNapamule

Where is the FDE-name and site? I know you need the right .air file etc. So i'll see the .air files, by opening them up etc. I'm using the PSS .air file not POSKY, so I thought since the autopilot section of aircraft.cfg is PSS's the ILS should work fine. But it doesn't, that's the problem. So maybe I could open the .air and use POSKY's autopilot section in the air file, will that work? Or just change the autopilot specs in the aircraft.cfg.Cheers, thx for replying!

Nandan,Now you're getting 'warm' (ie: 'So maybe I could open the .air and use POSKY's autopilot section in the air file, will that work?'). (I understand. You are just learning. I'll see you thru, this as much as I can, even though I don't have the PSS files). YES, that is what I am saying. Can you do this? That would probably be the 'fix'.Or not. I don't know if there is some other air file out there that is more 'suitable'. But taking ALL the AutoPilot sections (not just the 1199 section) and doing copy/paste over would be best. It can't hurt anything and it might help. (Be sure to save the air file you are now using-just in case). When you are done do a 'Save As' (NOT a 'Save') and browse to the correct folder (where you want it to wind up).Microlight droped a 'bomb' on us and the abandoned us. That '777-200' air file might work GOOD. Depends. And NO you would not do any good getting into JUST the cfg file to fix this type problem. But it would not hurt to put the autopilot section you are now using so I can look at it. Might be something there that is missing or incomplete (it happens). So there are specs in the cfg file that DO effect the ILS approach, such as the RADIOS section. We are getting 'deeper' now-right? Well, that is how it goes with the 'tweeeeeeeeeeeeeeeeeeeeeeking!).CBNapamule

Napamule,Dropped a bomb? No, don't think so. Sorry if you think I abandoned you; not the case. I just get around a little. A bit of intuitive searching in the library would have helped you out, as I posted here when I uploaded the FDE a few weeks back. So go to the Avsim search page, type in '777-200ER replacement' and you'll find it. No, my initials are not BDH, you must be thinking about somebody else. You're right about the FDE (flight dynamics engine, or flight model) being a combination of the aircraft.cfg and the .air file, and the replacement FDE contains both. The .air file itself in the upload is nothing more or less than pretty much the default Microsoft 777-300 .air file, and no, I did nothing to amend section 1199 - I didn't need to. You mention that .cfg and .air files from different planes might not work with each other; I don't agree with the blanket statement. Except for a very few parameters that are not modified by the aircraft.cfg file (e.g. parking brake strength, engine temperature), what the .air file specifies is largely over-written by the .cfg file contents during the loading process. Here's my take on it.FS9 loads the air file first as a general frame of reference for the plane concerned (simplistically that it has two wings, undercarriage etc that are defined to act in a certain way). Then it modifies all of the detailed operating characteristics from the .cfg file. In other words, the way a plane flies is almost totally dependent on what the .cfg file defines. This is different to earlier incarnations of FS such as FS2000 where all the .cfg file effectively did was include [fltsim.X] sections for individual variant identification. So in FS9 I've constructed many FDEs from scratch and the way I do it is to take a default FDE and modify the .cfg file to produce the appropriate flight model. Then if there are any adjustments necessary to the few parameters in the .air file that need to be done, then it's done at that point. I don't use FSEdit (a buggier piece of default software I've yet to come across!); my tools are Notepad, AirEd and a knowledge of what the changes to the .cfg file actually do. So the .cfg file is matched with the .air file from the perspective that they started life together.So what do you do when you're designing a flight model that's not reflected in the default models, such as a tri-jet? Simpler than you might think, and this is where the evidence of what I'm saying can be found. Because the .cfg file defines all of the major operational systems, it doesn't seem to matter if you use an .air file from a different design of plane; I just make sure that it's approximately the right size and of the same propulsion type. So, I have previously put together FDEs for three-engine 727-100 and -200 FDEs from the default 737-400 .air file, also DC-10s and MD11s from the default 777-300 .air file - and they all work fine. Proof of the pudding.Above, you recommend swapping out my .air file with the one that Nandan already has (the PSS one); this is not likely to make any difference because as I said, it's effectively the default MS one. The .cfg and .air files should be used as a matched pair. While the .air file is important from the perspective of laying down the basic template and defining the few characteristics that the .cfg file doesn't modify, it's the .cfg file that's the critical one regarding flight characteristics. It's possible that my .cfg file would work with the .air file that he already has, but it's not good practice to do that. So if he uses the file pair and simply inserts his [fltsim.X] sections into the .cfg file (it even shows you where to put them), then he should be good to go. All the data adapting it for the Posky model (contact points and so on) are already pre-set. ILS interception (like ground handling) is influenced by aspects of the FDE design, beyond the autopilot.Nandan - is the point of the merge to use the PSS flight characteristics with the Posky model, or to be able to use the PSS panel with the Posky model? If it's just that you're not happy with the original model FDE then I'd suggest using my alternative FDE to see whether you prefer it, and whether you still get interception problems. You shouldn't do (because I don't), and if you do then the problem may lie elsewhere in your installation. Or perhaps you might need to re-think your approach strategy - are you approaching the interception point at too high an airspeed?This is just a suggestion - the use of the alternative FDE is entirely optional! Just make sure you make backups of your original FDE before you do anything. You may be interested to know that the alternative FDE allows the 777-200ER to autoland if used with the autoland option in my AutoEnvironment v1, also here in the library.;)

Microlight,You said: '.. you recommend swapping out my .air file with the one that Nandan already has (the PSS one)'. Not so. I never suggested any such thing as I (or Nandan) don't have your FDEs. At any rate, I ONLY suggested swaping Section 1199 and keeping the cfg and air he has now. I located a file by 'BDH' so that one is not yours. No mix up. Just wondered if you might be 'him'.Not sure if you are aware of this particular 'merge' of the PSS and the POSKY and the problems that developed. There were panel (VC) problems. And Nandan has a problem with ILS approach. There is some reference (here and there) on the net about this 'merge', but they all say the same thing: 'Use MY mods for ....'. And no reply or feedback. And this is since Nov 2007, if you can imagine that. So Nandan wants this 'merge' to work, as he likes the model, in spite of bugs, and is trying to find solution(s). I just trying to give him ideas with my 2 cents worth as I don't have the PSS version.Will look for your FDEs, but for me I don't have any problems with big iron models. I don't buy ANY payware models-period. So maybe I should just bow out while I'm ahead. And it's very possible Nandan is doing something wrong. Otherwise, if you have everything 'right' you should be able to do ILS in FS9. It's too bad-so sad. I'm out.CBNapamule

Napamule;Check out your post (5 above this one) from 8.33 yesterday, second sentence.Anyhoo, not an issue. I'm trying to help also, which is why I uploaded the FDE in the first place, as there was a request - might have been from Nandan himself, can't remember. If he wants to use the Posky model (and why not, it's a cracker) and is having a problem with a merge with the PSS FDE, then my suggestion is not to use the PSS FDE...Over and out.;)

Nandan,Now you're getting 'warm' (ie: 'So maybe I could open the .air and use POSKY's autopilot section in the air file, will that work?'). (I understand. You are just learning. I'll see you thru, this as much as I can, even though I don't have the PSS files). YES, that is what I am saying. Can you do this? That would probably be the 'fix'.Or not. I don't know if there is some other air file out there that is more 'suitable'. But taking ALL the AutoPilot sections (not just the 1199 section) and doing copy/paste over would be best. It can't hurt anything and it might help. (Be sure to save the air file you are now using-just in case). When you are done do a 'Save As' (NOT a 'Save') and browse to the correct folder (where you want it to wind up).Microlight droped a 'bomb' on us and the abandoned us. That '777-200' air file might work GOOD. Depends. And NO you would not do any good getting into JUST the cfg file to fix this type problem. But it would not hurt to put the autopilot section you are now using so I can look at it. Might be something there that is missing or incomplete (it happens). So there are specs in the cfg file that DO effect the ILS approach, such as the RADIOS section. We are getting 'deeper' now-right? Well, that is how it goes with the 'tweeeeeeeeeeeeeeeeeeeeeeking!).CBNapamule

I've posted the aircraft.cfg [autopilot section] already i think...look at the first few replies to this thread. If not this is what i'm using:[autopilot]autopilot_available=1 flight_director_available=1 default_vertical_speed=1800.0 autothrottle_available=1 autothrottle_arming_required= 1autothrottle_max_rpm = 108.5autothrottle_takeoff_ga= 1pitch_takeoff_ga=8 ;max_pitch=10.0max_pitch_acceleration=1.0max_pitch_velocity_lo_alt=0.7max_pitch_velocity_hi_alt=0.4max_pitch_velocity_lo_alt_breakpoint=11000.0max_pitch_velocity_hi_alt_breakpoint=25000.0max_bank=25.0max_bank_acceleration=1.4max_bank_velocity=2.8max_throttle_rate=0.08nav_proportional_control=11.00nav_integrator_control=0.17nav_derivative_control=0.00nav_integrator_boundary=2.50nav_derivative_boundary=0.00gs_proportional_control=22.0gs_integrator_control=0.530gs_derivative_control=0.02gs_integrator_boundary=0.70gs_derivative_boundary=0.00yaw_damper_gain = 1.0Maybe if I change the max_throttle_rate so when it intercepts it won't put too much throttle that the aircraft climbs or descends etc...But look up at the previous replies, ive put another [autopilot] sections that might work, or maybe the POSKY [autopilot] instead of the one i'm currently using might solve the problem...As for using the POSKY FDE for the merge, it won't work, ytou have to use the PSS FDE for the panel to work correctly with the POSKY plane. Otherwise i believe there are many problems as in previous threads and i've tried it also-landings etc are difficult.

I've posted the aircraft.cfg [autopilot section] already i think...look at the first few replies to this thread. If not this is what i'm using:[autopilot]autopilot_available=1 flight_director_available=1 default_vertical_speed=1800.0 autothrottle_available=1 autothrottle_arming_required= 1autothrottle_max_rpm = 108.5autothrottle_takeoff_ga= 1pitch_takeoff_ga=8 ;max_pitch=10.0max_pitch_acceleration=1.0max_pitch_velocity_lo_alt=0.7max_pitch_velocity_hi_alt=0.4max_pitch_velocity_lo_alt_breakpoint=11000.0max_pitch_velocity_hi_alt_breakpoint=25000.0max_bank=25.0max_bank_acceleration=1.4max_bank_velocity=2.8max_throttle_rate=0.08nav_proportional_control=11.00nav_integrator_control=0.17nav_derivative_control=0.00nav_integrator_boundary=2.50nav_derivative_boundary=0.00gs_proportional_control=22.0gs_integrator_control=0.530gs_derivative_control=0.02gs_integrator_boundary=0.70gs_derivative_boundary=0.00yaw_damper_gain = 1.0Maybe if I change the max_throttle_rate so when it intercepts it won't put too much throttle that the aircraft climbs or descends etc...But look up at the previous replies, ive put another [autopilot] sections that might work, or maybe the POSKY [autopilot] instead of the one i'm currently using might solve the problem...As for using the POSKY FDE for the merge, it won't work, ytou have to use the PSS FDE for the panel to work correctly with the POSKY plane. Otherwise i believe there are many problems as in previous threads and i've tried it also-landings etc are difficult.

I am noob at those codes but I can tell u that my FS2004 PSS/POSKY 772/773 (its not mine,got it sumwhere I forgot LOL) works well on APP/FLARE/ROLLOUT mode. Let u test IT first.I will post it here if u want.