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...

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?