I never noticed that before but I get this drop in frames when mouse is visible also on some other airplanes (I don't have iFly 737) like Turbine Duke.

I never noticed that before but I get this drop in frames when mouse is visible also on some other airplanes (I don't have iFly 737) like Turbine Duke.

I get it on pretty much every addon plane, but with one aircraft it's more pronounced than with another. iFly seems to be one of the worst, though.

Same here. Only after reading the reports, I've tried this on some of my other planes and they all show this drop. That's a strange thing, can any of the devs explain some technical background there?I mean, I was happy with the frames so far, but they really get better when the mouse is over a 2D popup or in the menu bar.

Same here. Only after reading the reports, I've tried this on some of my other planes and they all show this drop. That's a strange thing, can any of the devs explain some technical background there?I mean, I was happy with the frames so far, but they really get better when the mouse is over a 2D popup or in the menu bar.

Could the problem be VSYNC? For example, say your refresh rate is 60Mhz, and your frames are hovering around 30FPS, is it possible, bringing the mouse into view, could lower them to just below 30FPS, in which case VSYNC will knock them down to 15FPS? (Half, the nearest frames divisible by the refresh rate)

Good idea indeed, but my vsync is forced to off.

This should work in the same way as on the MCP thing. Look at the window where the 2D Overhead is defined. Exclude all the gauges you don't need there, resize the whole panel to that, now, smaller size and then think about the placement you'd like for those switches.If you're speaking about the Overhead popup and an additional window for the lights only, you would just add another window title then, leaving the full overhead popup intact and just adding your light switches popup.In SimObjects\Airplanes\iFly 737-600\panel.wide, there's the panel.cfg again. Make a backup and then start using Notepad on it.The window itself may look like this. It contains the lights and the engine start switches as a popup.

[WindowXX]background_color=0,0,0size_mm=876,119position=4visible=0zorder=99gauge00=iFly737-600!Light_1,0,0,334,119gauge01=iFly737-600!Light_2,597,0,279,107gauge02=iFly737-600!Engine_Start,335,0,261,107

You see those gauge names again, containing 600? Right, you have to change the names there when using it on the 700, 800, BBJ and so on. Same method as on the MCP popup.Another thing is the window number in WindowXX. This has to be a free one and you also have to add an entry at the [Window Titles] section. Here's mine for example, I've used Window01 for that MCP popup and Window02 for the lights. Those windows aren't free ones when editing the default panel.cfg file, I've freed them up since I don't use the full 2D cockpit at all.[Window Titles]Window00=Dummp PanelWindow01=MCPWindow02=LightsThe whole thing looks like this and, depending on the window number you've used, comes up at e. g. Shift-3 (this would be window02 then).If yours looks different, something went wrong. Start over again or leave those mods out. :(So feel free to experiment a bit, but always be aware that, if problems arise, you first have to revert back to the original backup file (panel.cfg) to check if the problems are caused by those modifications. They shouldn't, but to rule out any chance then, please heed this advice.I've read in the forums that they are on a VC enhancement since quite some users complained about the current VC clickspots. So see my rough modifications here as a thing to maybe use in the meantime, not as anything more than that.I have no doubt that Steve and his friendly staff will find a better, nicer and easier solution since their support attitude looks outstanding so far.But they can't, won't and don't have to support user modifications, to be perfectly clear.No problem and thanks for the nice words. I must admit, that the VC operation thingy was the only downside on the 737 so far and with those small modifications, she's pure fun to fly and operate.I have to stress again that I've got the impression that they are taking the complains about the VC clickspots as severe ones and are really on it. Maybe we'll see some popup options on a future config tool.With their fine support attitude, I have no doubt that they are listening to customers. That's a big part in liking a product in my eyes.A tip for you guys is that free sound gauge for the iFly, adding some nice clicksounds and e. g. ones for the wipers. See details and a video here (registered forums section) and get the nice thing here. Easy installation and 100% function so far. Now works in FS9 and FSX.

Richard, since you've quoted my whole post please note the part where it says

But they (iFly) can't, won't and don't have to support user modifications, to be perfectly clear.

So please do not post any support issue over at the iFly forums there since this is user made stuff. If it doesn't work for you, leave it out, please. Use your backup file and revert back.Also, this modification is done for the FSX version of the plane (as you are in the FSX forums and the thread also says 'fsx'). I don't know anything about the FS9 one.Maybe I should ask the Avsim mods to remove my post if people mix them up and also produce support issues when trying to follow them although it is clearly stated that any user mod (naturally) forbids official support issues to be filed. :(Please don't put extra strain on the nice iFly support people there.

Richard, since you've quoted my whole post please note the part where it saysSo please do not post any support issue over at the iFly forums there since this is user made stuff. If it doesn't work for you, leave it out, please. Use your backup file and revert back.Also, this modification is done for the FSX version of the plane (as you are in the FSX forums and the thread also says 'fsx'). I don't know anything about the FS9 one.Maybe I should ask the Avsim mods to remove my post if people mix them up and also produce support issues when trying to follow them although it is clearly stated that any user mod (naturally) forbids official support issues to be filed. :(Please don't put extra strain on the nice iFly support people there.

Hi just to be right i DID NOT post this on ifly forum,i posted on there last weeki only asked here today and am sorryso if you can remove my query i would appricate that.RegardsRichard.once again sorry for posting here!Richard.

Those are my mods to the superb IFLY 737 fsx, I added RealityXP weather radar in 2D and VC cockpit plus the HUD in the 2D cockpit, they work like a charm.

Good idea indeed, but my vsync is forced to off.

I still think VSYNC is the issue. I just tested it (My VSYNC is off as well. I get between 23 and 28 (Sometimes 30) fps, Once though my mouse is active frames consistently drop to 15FPS precisely. I find that too much of a coincidence. I think what is happening, is when the mouse is in focus, VSYNC is activated, no matter what it's set for.

Richard, no harm taken so far. If the iFly guys don't see any user mod related topic in their forums I'm actually very happy. It just sounded like you are asking for help over there while using some of the user mods.

I still think VSYNC is the issue.

My frames get reduced slightly but there's no drop to half (since I don't use vsync), so maybe vsync just adds another factor to the equation then, on some systems.I've only recognized the small fps drop while reading about it. So it's marginal, but knowing about it leads me to park my mouse on the window title now, using any plane in the sim. :( So a nice but distracting finding there.

My frames get reduced slightly but there's no drop to half (since I don't use vsync), so maybe vsync just adds another factor to the equation then, on some systems.I've only recognized the small fps drop while reading about it. So it's marginal, but knowing about it leads me to park my mouse on the window title now, using any plane in the sim. :( So a nice but distracting finding there.

Is the drop though down to the next level divisible by your refresh rate? For example if you were getting say 35fps, does it drop to 30FPS or is you were getting 20 did it drop to 15, consistently? That is what I'm seeing. Google searching mouse and VSYNC, it seems to be an issue with other games as well, usually though when VSYNC is on it causes mouse lag.

No, no constant thing here. E. g. at the airport, getting around 27 fps with the mouse in the title bar, going to 24 when within the window or something. Same inconsistent behaviour on other planes there, only few fps lost, so I didn't recognize it at all so far, only the reading about it lead to some tests.I usually have that fps counter off and rely on my fluent impression from the sim, still do.In the above scenario, the vsync will reduce e. g. 27 or 24 fps to 20 when running at 60hz, right?

Those are my mods to the superb IFLY 737 fsx, I added RealityXP weather radar in 2D and VC cockpit plus the HUD in the 2D cockpit, they work like a charm.

Hi Futurnet,What HUD did you use, and what are its numbers? (horiz/vert/width/height)? I've added the NPSimPanel's 737NG HUD to the 2d panel, and managed to get it lined up pretty well, but it's a little bit small. The RealityXP WXR is very cool too...I may have to get that! What settings did you use for that?Thanks!Jim

Being tested by a real life pilot doesnt mean much tho. Real life pilots are rarely engineers and you need engineers to build simulators. There's no use for "seat-of-the-pants" feeling when it comes to engineering, its all about math. An addon being tested by a real life pilot has more to do with marketing than trying to get things as realistic as possible

Not very accurate at all.A flight model is best created by an engineer that fully understands what each parameter of the flight model does and how it interacts. But an engineer alone would not be able to create a good, or even useable, flight model without knowing how this works in FS; knowing the real numbers alone simply isn't good enough, but an aerospace engineer with plenty of FS flight model experience should get you a flight model that "hits the numbers".That's only a small part of the story though.Where the "tested by real pilots" should become relevant is in the feel of the flight model and sadly, I'd have to say the phrase is indeed more often used as a marketing thing that increasingly means very little. That said, there are some aircraft that are developed with good feedback from real pilots that also use FS and it's usually quite obvious when something is right, or not.