w6kd

Moderator
  • Content count

    5,053
  • Joined

  • Last visited

Community Reputation

370 Excellent

About w6kd

  • Rank
    Global Forum Moderator

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    Other
  • Virtual Airlines
    No

Profile Information

  • Gender
    Male
  • Location
    Woodland Park, CO

Recent Profile Visitors

10,608 profile views
  1. I think you could upgrade just the GPU and find you have a decent performing system with P3Dv4. P3Dv4 moves a significant amount of workload from the CPU to the GPU, and with any of the better aircraft and airport add-ons you do really need 4GB of VRAM as a rock-bottom minimum and really 6GB or more to maintain a comfortable amount of headroom. A 1080 or a more powerful 1080Ti is expensive, but a pretty much necessary step up over a 770 when moving to the 64-bit P3D environment. The 4790K Devil's Canyon CPU is still very capable when stacked up against the current front-line consumer CPUs (e.g. i7-8700K), probably within 10-15%, and not screaming for an upgrade. If I were building new, I would go with at least 16GB of RAM, but honestly, I'd try it out with your current 8GB config first, because it's likely you don't really need more, and if you do, you'll want to replace (not add to) the 8GB you have with a larger set, as mixing and matching RAM is a generally bad idea, and it's not likely you can find a good match for your current older DIMMs now. I absolutely would NOT switch to Win 10 until you have to (e.g. because you build a new PC with a motherboard that's sporting a chipset not supported by Win 7). There is no advantage to running Win 10 over Win 7 when running P3D, and plenty of butt pain associated with Win 10's nannybot automatic unwanted OS and driver updates, learning the new interface, etc. Regards
  2. FSX to P3D V3 or V4

    Yup, you're right...I see where there are now dropdowns for the older versions on their store page. Regards
  3. P3D V4 black ground textures

    In FTXCentral, near the bottom of the Settings page in the Tools section (you may have to scroll down off the first page in Settings), there is an option to force a remigration of the unified lclookup--I would try doing that. The FTX regional products use a custom landclass map and some custom landclass texture files, and if that is boogered up, you'll see black tiles. Regards
  4. FSX to P3D V3 or V4

    FWIW, P3Dv3 isn't an option, anyway, as Lockheed Martin does not continue to sell new licenses to older versions once a new version is released. The two biggest benefits to P3Dv4 over FSX, and they *are* big, is the pretty much complete elimination of the OOM problems associated with the 4GB 32-bit VAS limit, allowing flights with complex acft and scenery limited only by the PC's capability, and the move from DirectX9/10 to DirectX11, which puts much, much more of the power of modern GPUs into play. Regards
  5. ...and it requires dynamic lights to be turned off at night because the flood lighting is too bright (?)
  6. You can get yourself a very nice 55" 4K TV for well under $1500 these days. That's what I use here, and it's been the best solution I've ever had since I started simming in the early 90s. Regards
  7. Southwest Accident

    The lack of a band of shrapnel damage on the fuselage in the same plane as the obvious damage to the compressor section suggests to me that the containment ring largely did its job here. The diagonal stripe of removed paint traversing the inboard top of the cowl in the picture above suggests to me that something pretty substantial skidded across the top of the engine cowl towards the fuselage/wing root area. A compressor or turbine wheel failure can occur suddenly, without vibration or warning. Cracks in the blade structure propagate slowly until they hit a critical length, after which point they propagate very rapidly. Regards
  8. Southwest Accident

    The failed window is 10 rows aft of the lateral plane of the cowl damage...doubt that this was "shrapnel" per se (uncontained pieces of a disintegrating compressor/turbine wheel), but more likely a large piece or pieces of the engine/cowl separating and striking the fuselage well behind the engine. Most modern turbine engines have a kevlar belt around the compressor and turbine sections to prevent the high-speed rotating components from grenading into the rest of the aircraft. It also looks like the aft edge of the failed window frame is deformed. At cruise altitude, those windows have more than a ton of force being applied from the inside due to pressurization, so if the window frame were damaged by impact from a large piece of engine debris, the force of pressurization could well do the rest in removing the window from the jet, causing the kind of explosive rapid decompression they experienced. All that said, muerto es muerto... Regards
  9. Sim-Wings' P3Dv4-specific Pro version of Fairbanks International, Alaska (PAFA) has been released. 66% discount for owners of the old FSX Fairbanks-X scenery. Available at Aerosoft, Simmarket, et al. Regards
  10. Win 10 Home or Pro

    The only means I have been able to find that consistently block automatic updates in the Home version are external to Windows, not "in" Windows, per se...OO Software's OOShutup utility, for example. Regards
  11. FlythemaddogX Updated

    In the interest of accuracy, Remote CDU is *not* freeware as stated in this article. It is available in the library, but it requires the user to buy a (relatively inexpensive) key for it to function beyond just displaying the CDU.
  12. Win 10 Home or Pro

    One thing the Pro version does that the Home version does not is allow you to disable automatic Windows updates (via the registry). If I had it to do over again, I'd probably go with the Pro version for that feature alone. Disabling auto-updating is an ongoing gun battle in the Home version. There have been several bad forced updates that broke P3D and required a lot of work to go back and fix. Regards
  13. Assuming you're still using 32-bit P3D, regardless of how much RAM you have, it runs in a maximum of 4GB virtual address space, as 4GB is all you can address with the 32-bit address fields coded in the software. The OOM is triggered when P3D asks Windows to allocate a block of address space larger than the largest available block of contiguous address space within that 4GB bubble. You could have 128GB of RAM on your computer, and even though your 64-bit Windows will be able to see and use all of it, each individual 32-bit process running under Windows is still going to get no more than 4GB of its own VAS to work in. Regards