Well, the first lucky company is starting the sales now since the thing is released! :(

sigh. little disapointed with the FPS to be honest. Its almost as bad as the LH Maddog. Its a very noticble drop in frame rates when ever the mouse is moved I lose around 10 to 12 fps and im getting 30fps with default scenery and as soon as the mouse is moved it drops to sub 20s and thats on an i7 pc (Gtx460)Now before you mention its a problem with FSX and not the aircraft the PMDG MD11 has this same issue but its only 3 or 4 FPS drop and its a much higher FPS overal at the same airport..Also what im not too happy about is the displays are sometimes too dim to read and there is nothing you can do other than use the pop up for that display =(Looking forward to the PMDG 737 though hehe. They seem much better at getting the best out of thier stuff.

Can you post a screenshot with those low fps on default scenery? She's one of the lesser fps eating complex birds on my system so far, so I'm a bit surprised about your report. I'm running the MD11 too and she's eating more of that fps cake here.Maybe we can spot the error there or in your settings and it can easily be ruled out since all the guys are very happy with the iFly FSX fps so far. Hoping you get back to normal soon. :smile:The displays are all dimmable, so you can adjust their contrast. I don't have any problems here, so I would suggest a screenshot there too.Makes the talking much easier since everybody can see what you are describing.

sigh. little disapointed with the FPS to be honest. Its almost as bad as the LH Maddog. Its a very noticble drop in frame rates when ever the mouse is moved I lose around 10 to 12 fps and im getting 30fps with default scenery and as soon as the mouse is moved it drops to sub 20s and thats on an i7 pc (Gtx460)Now before you mention its a problem with FSX and not the aircraft the PMDG MD11 has this same issue but its only 3 or 4 FPS drop and its a much higher FPS overal at the same airport..Also what im not too happy about is the displays are sometimes too dim to read and there is nothing you can do other than use the pop up for that display =(Looking forward to the PMDG 737 though hehe. They seem much better at getting the best out of thier stuff.

I'm running about 48 fps consistently. If you think you're going to get better fps with the PMDG model, uh....., I wouldn't count on it (it's possible I suppose). Best regards,Jim

its not just me =(. Other people on the forum are having issues too. I turned off all mouse themes as advised by the devs but it made no diffrence. Even the J41 runs very very well, much better that the iFly and the J41 is one of the more demanding aircraft for FSX. I cant imagine whats causing my issues but I really really would like a fix for it :( I did alot of digging in the past when I had the same issue wuth the LH Maddog and found out its a problem with the core of FSX that only Microsoft could fix and they never did.

Other people on the forum are having issues too

I can only see one guy, not getting tired of stressing that especially PMDGs run better on his system. Doesn't match my aircraft interchange view here.Well, I guess systems are different, people are too. :( Lets hope for a "fix" then. :biggrin:My only trouble is the operating philosophy in the VC so far. But it will take time to get used to it although I may drop a wish for becoming more stringent on the use of the mousewheel for example.The 2D panels are nice, fast and precise on the clickspots, especially the MCP, the VC one currently gives me headaches though.But lets give her some days to get used to me. ^_^I'm still impressed about the appearance and the details, especially when looking at all the variants included and that nice price point.Docs and tools are great too, I wished it was weekend again.

Wondering how it will compare to the NGX.

It should compare 1:1. It is the NGX.Ray

I can only see one guy, not getting tired of stressing that especially PMDGs run better on his system. Doesn't match my aircraft interchange view here.Well, I guess systems are different, people are too. :( Lets hope for a "fix" then. :biggrin:My only trouble is the operating philosophy in the VC so far. But it will take time to get used to it although I may drop a wish for becoming more stringent on the use of the mousewheel for example.The 2D panels are nice, fast and precise on the clickspots, especially the MCP, the VC one currently gives me headaches though.But lets give her some days to get used to me. ^_^I'm still impressed about the appearance and the details, especially when looking at all the variants included and that nice price point.Docs and tools are great too, I wished it was weekend again.

Make it two...and plenty more on the Ifly support forums fellas. They have some optimization to work on. Hopefully in the first patch.

Make it two...and plenty more on the Ifly support forums fellas. They have some optimization to work on. Hopefully in the first patch.

I'll chime in with a couple of OOMs. Not absolutely sure they're entirely the aircraft's fault, but I'm fairly disappointed with the FPS. I'll give them 29 days and ask for a refund if there's no patch. If I do, perhaps I'll rebuy it once the patch is out.

Just completed a quick circuit - hand flown, nice and no problems :(

Yes, be sure to enter the coupon code FSX737 to receive 25% off!As promised, I am uploading a video of the iFly in dense scenery, New York to be precise. It should be finished uploading in about 45 minutes.

Jeremy,You should make an FS2Crew video!

Despite what I said previously about skipping the iFLY and waiting for the PMDG, my curiosity had gotten the better of me and I decided to buy it, knowing that their is a 30 day refund option. I am for the most part impressed with this NG, especially for a first time payware product from a newcomer.But I have some reservations, here's a list of some from 2 flights between KPHL and KATL:1. The VC click spots are hard to use, and not very intuitive. I suppose I just need to get used to it, but I much prefer the VC button interaction in the MD-11, which includes helpful cursors and precise click spots. In the iFLY, its hard to gauge where to put your cursor to interact with the buttons.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.

That 'autopilot modes cutting out' issue was a problem with the FS9 iFly too. there are two workarounds: you can either drop the sensitivty of your stick in the FS options, and widen the null zone a bit, or, you can hit Control K to knock off the stick when in autopilot and hit it again when you want it back. Moving the yoke on most aircraft in real life will disengage the autopilot, but with the iFly you can do it by breathing near it.Personally, I think they need to come up with a solution for it, since no other FS aircraft I have does that, meaning it must be possible to sort it out. I can live with it, but I'd prefer to not have to.I agree that the click spots could have better definition in the VC too. You do get used to it, but then again, it would be nicer if you we not have to. These problems are far outweighed by the plus points of the iFly, on both the FS9 and FSX versions, which is why I like them, but I would like them more if it was addressed.Al

I have to agree on the VC clickspot/philosophy thing since especially the MCP is a pain when just wanting to change heading or altitude.With Bryans nice FS2Crew, you can workaround that stuff a bit, but when you open the 2D panel, you see how it's done while the VC leaves you with a rather slow and not precise clickspot experience so far. It would also be fine to get away from the older + and - clickspot technique over to a left click/right click one and/or one which allows the moursewheel to be used for switches too.The mousewheel gets used on the MCP, but changing a 3 position switch on the Overhead and thereby catching the right clickspot for his + OR - position change really is a task, and I'm talking about the situation on the ground, not the maybe shaking one in flight.Of course, these are personal viewpoints of mine and if nobody comes up with them in the iFly support forums (I've just registered there), they will stay in this status and don't describe a flaw of the product at all.But I've hit the wrong switch more than once now, my favourites are 'no, not the APU Master Switch!' and 'no, not that engine Gen!'. :( My favourite one on the MCP is not hitting the HDG clickspot but the one for the bank angle limiter.How was the FS9 version doing there?And thanks for that input about the joystick sensitivity. I was questioning myself why I always lose a stable AP operation here and there.That's my current (default) setting there, I may have to try a lesser sensible one then.I've checked those fancy hall sensors for spiky output signals, but they are clear and the iFly is the only bird complaining so far.

well im glad its not just me hehe. It seems they (the guys at iFly) have been able to reproduce the FPS/Mouse issue and it sounds like they might have a fix. I wont link here but check out thier forum for the support topic. I posted some pics there too =)