2. Not sure if its my joystick or not, but in my two identical flights, I am constantly losing LNAV and heading select, and when this happens the CWS system kicks in. But even then it's difficult to regain control manually via CWS, and even when I eventually get back LNAV, it just keeps disconnecting. I have had no joystick "noise" problems with all my PMDG or Level D products, but now I am fighting to keep LNAV under control. I fear stepping away from the simulation, two times so far when lateral guidance was lost the a/c banked out of control and dropped out of the sky. This is very disappointing to see. Even during a CAT I approach, the autopilot lost the glideslope/localizer guidance and I had to revert to manual control. VNAV works as advertised, but lateral modes are a tossup, at least on my system. 3. When I use spoilers during descent, when I close them the rumbling sound they make is still there, even though I know for certain they are in fact closed.I'll see what others have to say on IFLY's support forum, but so far I am the only one to have these issues.

Thank heavens somebody else also experienced this behaviour.I thought I was doing something wrong or it was a bug in the aircraft because I kept having to re-connect LNAV time after time, and all that on a short flight too from EHAM-EGCC.Again,perhaps I'm not doing something right but having done it successfully in the default aircraft, I don't think so, but why is it despite being at the correct approach altitude,etc,selecting APR, correct ILS frequency,etc, I still cannot get it to capture the glideslope,and have to hand-land it as I can clearly see that I'll overshoot my destination runway?Ditto on spoliers too.

<br />Before this NG was launched, lately I've done most of my tube flying in the Quality Wings 757.  I've noticed a HUGE difference in both power and performance between this new 737NG and the 757...<br /><br />The 757 is much faster to accelerate and also seems tighter in turns.  Is this true to life, or is it just discrepancies in the flight models?<br /><br />The iFly NG 'FEELS' much heavier than the 757.<br /><br />Thanks<br />

<br /><br /><br />I believe the 757 has one of the best power to weight ratios out of most commercial airliners.

I am glad to see others chime in on the yoke sensitivity and click spots issues, while many have agreed the clickspots are troublesome, for a while I felt like I was the only one with the lateral mode disconnect issue. I must say, for the price and considering it's iFLY's first payware release for FSX, its a phenomenal aircraft. However, these two issues really ruin the whole experience for me, and I'm really not sure I can live with them, especially since it's a given that PMDG's VC clickspot technique will be far more intuitive and easier to use. I will try to adjust the sensitivity of my yoke according to suggestions here and on iFLY's forum, so hopefully that issue will be resolved. I appreciate that they are trying to simulate the real world behavior of the NG's autopilot not enabling when it senses any pilot input on the yoke or trim, but this is out of hand. It is just too sensitive, and I'm sure they will be fielding plenty of support requests about this issue much to their chagrin. I use FSUIPC to calibrate my hardware (CH Products Yoke and Pro Throttle, and Saitek pedals), but I have no clue how to have FSUIPC recognize a null zone. I will have to research further on how to do this, or maybe go back to having FSX handle the joystick calibration where I at least know how to setup a null zone.When it comes to the clickspots, I'm really doubtful that I can get accustomed to iFLY's behavior. They are hard enough to use in a still aircraft on the ground, but its 50 times worse when I'm in the air when the pressure is on AND EZDOk is enabled. I'm getting sick of stumbling around trying to determine if I am in the + or - zone, if I have positioned my cursor over the right switch. 2 out of 3 times when I was starting the engines, I ended up shutting off the APU before the 2nd engine could be started, all because of this silly clickspot issue. And the NG has so many of these switches to pull, compared to other tubeliners I have used like the 747/767/MD-11. So this issue is even more prevalent on the NG, and as a result iFLY really needs to fix this or improve their technique if they want to avoid a deluge of refund requests!I have to wonder if it's possible for iFLY to "rewrite" their clickspot technique, to make it like most other modern simulated aircraft and use the logical left-right click and/or allow more mousewheel usage. Is this even possible to fix in a service pack? I would think this type of programming is deeply imbedded in their code and cannot be easily replaced. I sure hope they can rectify this one issue, because apart from that I find no other major "gamestopper" issues. The price is right, they offer all of the NG range, the models look great and the hand flying/ground performance is butter smooth. If iFLY manages to refine the clickspot code to be on par with the compeition, it would be a big step in the right direction and would ensure that PMDG doesn't corner the FSX NG market.

The 757 is well known for being very fast and is in fact very maneuverable for an airliner. I actually saw a pre-delivery BA 757 being thrown about like a fighter at an airshow once. It took off from EGCC and did the display at the airshow at EGCD, and it was one of the best displays I've ever seen any aircraft do because it was so unusual to see an airliner doing that. I thought the pilot was going to try a stall turn in it at one point, and he came pretty close to doing so, amazing stuff, and it had twelve people on board the thing at the time too apparently!Al

I'm not surprised that someone would notice the NG is not as nimble in the simulator as the 757. That is a testimony to the accuracy of a 757 flight model, she truly flys like a rocket ship. The NG is also notorious for using a higher speed on finals compared to others of similar size, both the NG and MD-11 have the fastest VAPP speeds during final approach for airliners.

Spoiler troubleThis may be related to the analogue driving of the spoiler axis. The sound of the spoilers stays there after retracting them, analogue, but it goes away if you use the spoiler key. Try it. Surely a small fix to do.AP troubleThere's a sensitivity setting in the iFly config tool, where you set up all the display options and stuff. Move that slider a bit to the right and you will be fine. I had that problem too, a notch of movement of that slider helped.Note that the slider can/has to be set for every variant and every livery. But you can alter the template to be used when going to \iFly\737NG and edit the Styles file. There's a JoystickSensitivity=xxx setting, higher numbers there actually mean lower sensitivity. Works fine here and doesn't influence the fine hand flying capabilities of the bird.Clickspot troubleThat's a bigger chapter of course. I saw the first threads coming up over at iFly's, so to either avoid a complete rework or at least enable some precise operation with popups, one can edit the panel.cfg a bit.The bird has a full VC and a full 2D cockpit, so why not use the 2D stuff as popups then? I'm e. g. flying the MD11 (which has good clickspots) via the AP popup because it's easier, faster and even more precise.To get a nice MCP popup (where the mousewheel works nice and fast) just edit the [Window01] entry in the panel.cfg and exclude everything you don't need there. I only have the MCP, the EFIS together with PDF, ND and upper DU there and the thing pops up when using Shift+2.You will be amazed how well the 2D stuff works and ask yourself why they went so far off on the VC clickspots and philosophy for example.A precise Overhead popup will be done via [Window05] where you can exclude that background gauge. Same for the upper Overhead in [Window06], just exclude the background gauge there.Shift+5/6 therefore gives you the Overhead, with precise clickspots. I can offer some screenshots later, but if you backup your panel.cfg, you can easily try it yourself. Just be aware that every variant has it's own panel.cfg, so if you edit the 737-600 one only she will show the enhancements.Other tweakingI think that e. g. the yokes or the HUD can also be hidden/added in the simple gauge way since they are all "just" defined as some VC gauges. Haven't tried so far though, but I'd like to see the HUD in the commercial variants for example.That whole 2D cockpit stuff (if not used as popup) can be excluded to maybe free up some resources. They even recommend that step for the guys with the strange mouse pointer problem.So if you don't fly 2D and use the mentioned popups only, you can e. g. exclude the full 2D cockpits from the FO (there's a VFR and IFR one), some of the Captain's instruments, the 2D yoke and so on.I'm using these exclusion together with FS2Crew and it doesn't affect the operation at all, so there may be a harmless way of cleaning up some resources.FS2Crew works directly on this plane so it isn't dependent on some popup windows and simulated mouse clicks like on the MD11 for example. Therefore, you can safely get rid of any unused 2D stuff.All the above tweaking techniques are roughly done and only act as a workaround of course. But I think that e. g. a clear VC preference (and therefore exclusion of all the 2D stuff) could easily be established with an update of the nice iFly config tool, so guys then can choose their preference there and get VC+popups or 2D only, just as they like it.I've tested the mentioned things some hours now and I'm more than happy with the operation now. No APU or engine was harmed so far. :biggrin:Also, the panel.cfg changes are persistent and don't get changed when you use the config tool. Just backup the original file and edit the other one, the changes stay fixed then.

Another issue of concern is the clarity of the flight mode annunciators on the PFD, relative to other complex models. It's very hard to read. At first I thought it could be a font issue on my system, but I've noticed it on the preview videos as well, as well as FS2004 model videos.

You mean that white or green on the grey?

You mean that white or green on the grey?

Mostly the Green on grey.

Sounds like a point to add, you are right.Although that female colour expert in my household tells me that most males are weak on the green side of the colour space, I think that this can easily be tweaked by the iFly devs.Time to start posting over there, huh?No deal breaker on the 737 so far and maybe some useful input to enhance it here and there. I also saw that the user input and mod side is allowed and active there. One guy posted some additional sounds for the gauges which were impressive.

Other tweakingThat whole 2D cockpit stuff (if not used as popup) can be excluded to maybe free up some resources. They even recommend that step for the guys with the strange mouse pointer problem.So if you don't fly 2D and use the mentioned popups only, you can e. g. exclude the full 2D cockpits from the FO (there's a VFR and IFR one), some of the Captain's instruments, the 2D yoke and so on.I'm using these exclusion together with FS2Crew and it doesn't affect the operation at all, so there may be a harmless way of cleaning up some resources.FS2Crew works directly on this plane so it isn't dependent on some popup windows and simulated mouse clicks like on the MD11 for example. Therefore, you can safely get rid of any unused 2D stuff.All the above tweaking techniques are roughly done and only act as a workaround of course. But I think that e. g. a clear VC preference (and therefore exclusion of all the 2D stuff) could easily be established with an update of the nice iFly config tool, so guys then can choose their preference there and get VC+popups or 2D only, just as they like it.I've tested the mentioned things some hours now and I'm more than happy with the operation now. No APU or engine was harmed so far. :biggrin:Also, the panel.cfg changes are persistent and don't get changed when you use the config tool. Just backup the original file and edit the other one, the changes stay fixed then.

I'm very interested in this tweak. I use VC with Ezdok/Track IR and have no use for most 2d windows (with the exception of the overhead, and popups for the FMC and MCP) Can you provide instructions, or a link to the iFLY topic on this subject? Do the 2d windows (even if they are never used) have an impact on performance? I'm only interested in taking this on if I can save some fps when I'm in the VC. <br>

Can you provide instructions, or a link to the iFLY topic on this subject?

Sure, Michael has set up a collection of the maybe too much 2D windows here.I can't report about any difference on the fps side though since I was and still am happy with them.I'm currently collecting some bugs and questions regarding this nice plane to be posted over at the iFly forums.She's a pretty bird and very well done on the systems so far in my eyes. I've done a small MCP only popup and added that free sound gauge (check out their library) which really adds something to the plane, great work there.With the popups for the Overhead and the MCP she's a treat to be operated.Since I've tweaked nearly all my birds (including the PMDG ones), I don't have any trouble to add or delete this or that in the config files to get "my" plane.I saw that they allow user mods and uploads over at Flight1, which is great since it allows such nice addons like that sound gauge to be made and shared. So maybe we can expect quite some additions and features coming from the fans alone while the devs are working on improvements too. So far, the mood over there looks very, very good.

Sure, Michael has set up a collection of the maybe too much 2D windows here.I can't report about any difference on the fps side though since I was and still am happy with them.I'm currently collecting some bugs and questions regarding this nice plane to be posted over at the iFly forums.She's a pretty bird and very well done on the systems so far in my eyes. I've done a small MCP only popup and added that free sound gauge (check out their library) which really adds something to the plane, great work there.With the popups for the Overhead and the MCP she's a treat to be operated.Since I've tweaked nearly all my birds (including the PMDG ones), I don't have any trouble to add or delete this or that in the config files to get "my" plane.I saw that they allow user mods and uploads over at Flight1, which is great since it allows such nice addons like that sound gauge to be made and shared. So maybe we can expect quite some additions and features coming from the fans alone while the devs are working on improvements too. So far, the mood over there looks very, very good.

How did you manage to do the MCP popup?

How did you manage to do the MCP popup?

Well, since the full 2D cockpit is at Shift-2 (for the Captains version), you just have to throw out all the gauges except for the MCP there. Then make sure to adjust the size and also exclude the window "ident" since it seems to trigger the disappearing VC gauges when the popup is active.So it's mainly a work of looking into the corresponding folder, e. g. for the -600. This would be SimObjects\Airplanes\iFly 737-600\panel.wide. That's the widescreen panel file. Make a backup of the current panel.cfg and look at [Window01] then. You can use Notepad there.Delete the whole [Window01] entry and replace it with this one.

[Window01]background_color=0,0,0size_mm=659,143position=4visible=0zorder=1gauge00=iFly737-600!MCP_CAPT,0,0,659,143

See the gauge's name? iFly737-600!MCP_CAPT, that's the description which differs from model to model, so the -700 gauge would be iFly737-700!MCP_CAPT and the one for the BBJ iFly737-BBJ!MCP_CAPT and so on.If you edit the panel.cfg for every variant, you will get the MCP coming up via Shift-2. It has much better clickspots and also is very fast when changing the settings.I'm using this method on the MD11 too. The advantage there is that it's already there while the current iFly only has the full cockpit.It should look like this. If not, use your backup panel.cfg and start new or forget about the thing. :(If you want to use the overhead panels as popups too, while excluding the background graphics there, just exclude the OVHD-Wide!OverHead_background gauges in Window5 and 6 with a

//

in front of the line.//gauge00=iFly737-6700-OVHD-Wide!OverHead_background,0,0,1680,1050,1They are at Shift-6 and 7 then, allowing a quick operation on the overhead.Of course, there won't be any official support for these changes since they are user made. So don't annoy the nice Flight1 guys with questions when the problem is related to my/your work on the panel files. :wink:They may come up with an official solution or workaround for the VC clickspot issues soon, so instead of doing the manual edit, you may also want to wait.I'm happy with the popups though.

Very nice! Thanks.

Before this NG was launched, lately I've done most of my tube flying in the Quality Wings 757. I've noticed a HUGE difference in both power and performance between this new 737NG and the 757...The 757 is much faster to accelerate and also seems tighter in turns. Is this true to life, or is it just discrepancies in the flight models?The iFly NG 'FEELS' much heavier than the 757.Thanks

That's with all respect there is no realistic 757 for FS at this point in time ;-)