JDWalley

I'm sure it's due to all the newly-implemented chemtrails in 2024.

While some IRL pilots might be manipulating their content for clicks, I find it ludicrous to claim that "long-time simmers" who have never flown an aircraft in real life would have a better grasp over whether a specific FS aircraft performs in a realistic manner than someone who actually handles that particular aircraft day in and day out.

Well, they certainly don't seem to have achieved what they want in 2024 so far...

They've already announced a sale - now, it’s only $324,999,999.99!

The $64,000 question, for me, is: if the new Dovetail simulator is a MS Flight-clone, as most people here are speculating, are they still planning on licensing and selling FSX:SE? Or will they let the license lapse and tell people who find their new product too simplified and game-like (if, indeed, that is how it turns out), "well, you can always shell out $200 for P3D if you don't like what we're offering"...?

Where is it? Can't find it on your site.

If you had finished reading the OP, you'd have realized that he was having the same problem with Aerosoft's A319 -- except that his memory problems with the A319 appeared much sooner.

Nice review. The iFly looks good, but...worse VAS performance than the PMDG 777, which is known as a VAS hog? Doesn't seem too promising. Has anyone tested that aspect of it with P3D v3?

I'm not affiliated with PMDG, but I thought it was standard policy for them to allow up to two different registrations/installations for a given product.

I tried using that program with Win7 64-bit -- when I hit Win+F11 with any other window, it does as you describe; when I try it with the FSX window, however, it does absolutely nothing. Does anyone have any idea what I'm doing wrong?

Not sure it would be that receptive to my question, since I would be asking about a trial version of one of their products that I decided not to buy... As it turns out, the question was irrelevant. After I abandoned my futile Revo Uninstaller attempt and rebooted, I started getting a BSOD every time I started Windows. Finally wound up having to run the windows system repair utility, which brought up system restore, at which point I opted to revert to a restore point from before I installed KLAS. That done, my system started working normally. I can only conclude that something in that KLAS install really hosed my system! I can also conclude that I won't be buying any FSDT airports unless I've already decided I really want that particular one, since I no longer feel confident that I'd be able to uninstall something after a trial.

Strange...I thought the big selling point of P3D v3 was that it had virtually eliminated OOMs.

I decided to try out FSDreamTeam's KLAS scenery. After a bit of testing, I found some incompatibility with my other scenery, so decided to uninstall it. I opened the Control Panel->Uninstall a program, and got the predicted program list. Picked out the FSDT KLAS, selected "uninstall," and...nothing. No uninstaller dialog, no sign that anything was happening. After waiting about ten minutes, I tried selecting "uninstall" again, and got an error dialog saying that I had to wait for the previous program to uninstall. Waited another ten to fifteen minutes -- still nothing. Looking at the task manager, it indicates that there is an "unins005.exe" in the list, but it's not taking up any processor time, and the amount of memory allocated to it is unchanging. I try terminating the process -- it automatically regenerates itself, still with no activity. Shut down the computer and try again -- same result. Shut it down and try Revo Uninstaller -- it progresses to the point where it triggers the built-in uninstaller and, you guessed it, goes into infinite-pause mode once again. Is there ANY way to get rid of this product?

According to Adam's guide (linked above), SweetFX works fine with the Fixer. Obviously, it might not without it.

Thanks -- I now see why unlimited might be problematic. The issue, then, once again becomes what qualifies as the "minimum" framerate? If you base it on the lowest I get in the toughest possible scenario of PMDG/Orbx/AI/GSX/Rex4/ASN in one of the most intensive areas of the FSX world, we're talking around 25 which, by the rule of thumb you mentioned above, would require me to limit frames to 12 (which would be ridiculous for virtually every other situation) and hope there's a "1/5th of refresh rate" setting in NI (I've never thought to check). Or should I go with 20, even though that's more than half the "minimum" in the worst-case scenario? Keep in mind that this is a system which, in a generic area with a generic aircraft, gives me frame rates in the 200s!

Well, after setting things up with NI using the guide's recommendations, with no VSync and unlimited frames, I try the C172-at-Page scenario and…holy #*^%! Around 200 FPS!!! Of course, that's at Page, with nothing else going on. So, I move to KSEA under Orbx PNW scenery, with MyTraffic 6, GSX, and Rex4 textures. In that near-worst-case scenario, framerate is way down, but still in the high 30s to low 40s; very impressive for that locale. So, of course, I take it from near-worst-case to absolute worst-case, and swap the default C172 with the NGX, and throw ActiveSky Next weather into the mix. I don't see any FPS lower than the mid-20s, increasing into the 30s on takeoff. As that's actually a few ticks higher than I was getting under DX9, and with a lot more VAS headroom, I'm quite happy. My only question has to do with fixing framerate. What should I use to set it? The minimum with my fully-loaded NGX scenario (which would result in an absurdly-low limit), or the higher rates I was seeing in a more "stock" scenario? Or should I just forget about VSync and fly unlimited, considering the wide variance between 25 and 200+ frames per second, depending on the presence or absence of every heavy add-on in the book?

No offense, sparkle66, but, if you had read my OP, you would have noticed that I was using DX10 Fixer -- a fact I mentioned in my replies as well. SteveW, if I set the VSync to 1/2 refresh rate in NI, but have it unlimited in FSX itself, the "downstream" nVidia drivers will force the actual display rate to 30 FPS -- but the sim itself will show the unlimited count via Shift-Z, even if the video card is limiting it, right? Also, if you're getting a framerate of 50-240, why aren't you choosing 1/2 refresh rate and 30 FPS instead?

Well, to answer my own question: I did some more experimentation, and found that the FPS drop is entirely due to the NI settings from Mutley (or, perhaps, my own screwing them up when inputting them? -- not sure yet). With keeping the exact same NI settings as DX9 (and even using the same FSX.cfg file I was having problems with before), there's no FPS drop in DX10, and maybe even a couple of frames improvement. The minute I import the saved "DX10 profile settings" into NI...bam! FPS drops from 60 to 30. For the moment, I've rolled everything back to DX9, and will try reconfiguring the DX10 Fixer and NI settings according to the material others here have suggested...but not tonight, since it's half-past-one already! And, to answer KingAir_Fan's post, I would prefer to stay with DX9 for the simplicity of the matter, except that I've found that DX10 gives me about about another half-gigabyte of VAS overhead over DX9, due to using video card memory. Even though FSX-SE apparently does a better job of memory management than the boxed version, I've found that, if I try even a semi-torture-test flight with full scenery, add-ons, and NGX (by which I mean a flight through Orbx PNW scenery from KSEA to CYVR, overflying KBFI, KPAE, and CYYJ on the way), by the time I land, I'm down to about 370,000 VAS with reasonable settings -- and, if I go with sliders hard right, I OOM while passing KPAE. Even at my current settings, which allow me to complete the flight, I worry about trying to do longer flights; the extra VAS space saved by DX10 would seem to offer a lot better margin of error.

Thanks for the various suggestions. I've downloaded Adam's guide, and will look over the codelegend.com recommendations as well. Just one question, though...would those affect the FPS of DX10, or just its visual quality? Most of what I'm seeing there involves setting things like AA and AF. Now, I can understand how vital they are to having FSX look good, but would they also affect the framerate positively? Forgive me if this is a completely screwed-up assumption, but, even if I hadn't tweaked the settings at all, shouldn't the framerate not drop just by switching to DX10 at all? I mean, if didn't even use DX10 Fixer, but just invoked the "Use DX10 Preview Mode" within FSX without changing anything else, would there be a reason for the FPS to drop by something drastic like 50%? Maybe, if I didn't use the Fixer or change Inspector settings, the anti-aliasing would look awful, and there'd be all sorts of visual glitches, but I would think that the framerate wouldn't drop drastically just because I'd made the switch. Or is there something I'm not taking into account?

Tried a shader rebuild. No luck. FPS still at around 30-31, with the occasional spike to around 197 and dip to around 6.4.

Well, I deleted my .cfg and let FSX build a new one (since it immediately asked to include a bunch of assets as "trusted," I can't call it completely "clean," but it certainly wasn't including anything I wasn't running under DX9. Started up FSX, set DX10 preview to on (which, of course, meant restarting) and display resolution to my standard 1920x1080x32. Shut down FSX, and set WideAspectView (or whatever it's called) to true. Tried again -- still no better than 28-30 overall, with very rare spikes into the 100 range. Thanks for the shader suggestion. Will try when I get home.

Now that I have my i7-6700K/GTX 980 system up and running, and FSX-SE tuned well in DX9, I thought I'd try DX10 preview mode and check the results. For my text, I went with a simple scenario of the default C172 at Page Municipal in Arizona. FTX Global and Vector were installed, along with FSGenesis mesh, but no other add-on scenery. Using the most recent nVidia drivers, and DX10 was set up with Steve's DX10 Fixer and the defaults (FSX.cfg and Inspector) recommended in the Mutley's Hanger review of that product. Obviously, framerate was set to unlimited. Using DX9, the framerate was 59-60, with occasional spikes to 119. Using DX10 preview mode, the framerate dropped to 28-30, with very rare spikes to 179. Now, I've heard DX10 results are very system-dependent, but it's usually been in the sense that one person will claim a doubling of framerate, while another will report no significant difference. This is the first time I've heard of FPS being cut in half. Am I doing something wrong, or do I just have to accept that, for whatever reason, FSX-SE and DX10 just don't play well with my particular system?

So, what else did you expect with aircraft from Boing?

Where did you get your 6700? I haven't found a single one around here, except for Japanese "imports" selling for around $500+.

Well, if you need WAAS to do an LPV, and Carenado doesn't support it, I can see why I wasn't getting anywhere. I'm almost getting the sense that what I've been experiencing has been, when I invoke APR on 34L, the Carenado is actually grabbing the ILS on the reciprocal 16R (even though I don't have NAV1 properly tuned), and is trying to fly a 16R ILS approach 180 degrees reversed, putting the intended touchdown point at the north end of the runway. As weird as that would be, it would seem to fit what's been happening. In any event, if LPVs aren't possible with this aircraft, I won't bother with APR mode, but just let NAV mode set me up laterally while controlling the descent manually.