Jump to content

dgraham1284

Members
  • Content Count

    869
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by dgraham1284

  1. Just saw the was another update or hotfix for 3.2. No change log that I could find
  2. I see you are new here. PMDG does not and nor will they ever give release dates.
  3. I understand where you're coming from. That being said, people have long complained about fsx not utilizing their expensive hardware. Now it will use everything one can throw at it. It's hardware demands are now equal to that of a current AAA title game. Your mileage may vary. I never thought I would live to see the day where my flight sim would consume nearly 90% of 6GB of vram. On a regular basis too. I'm not at all throwing stones. We all come from different backgrounds and have different priorities. For me, it's quickly turning into everything I have desired in flight sim for years.
  4. It would take an act of god for me to even think about going back to FSX/FSX-SE
  5. He's a work around for soft clouds. Don't use the program to install them. Just go to the corresponding texture folder and drop it into the P3D texture folder. That way you avoid it installing the broken cloud.fx file. That's not "official" but that's what I did and it's working well.
  6. That is called LOD. You can restore the textures from the backup rex made.
  7. I see no problem. That is what REX waves look like...
  8. Clear them anyway. I would...
  9. 1. Did you clear your shaders? 2. I would try a clean install using DDU (http://www.guru3d.com/files-details/display-driver-uninstaller-download.html) to remove the graphics drivers and installing the most current driver (http://www.guru3d.com/files-details/geforce-364-51-beta-driver-download.html) Also, I would advise to run all 3 installers. I know it's not the easiest, most convenient route. But it eliminates any potential issues. I did all three and am very happy. The only extra work was reinstalling FTX Global, which in the end, isn't that big of a deal.
  10. For $35 you really cannot go wrong. This BLOWS away anything Carenado could come up with.
  11. Lol, I thought the same thing. Wow, it's unusually clear everywhere today.
  12. Another one who didn't read the change log.
  13. My screen shots provide some performance insight provided you have some power in your rig
  14. It's working better than ever. About to start a journey in the Q400 pro from FlyTampa LOWW to Digital Design Salzberg If you have OpusFSI it is working fine for weather. Temp stopgap while waiting for ASN. David, I suggest reading the original change log that came with 3.0. The installer was broken into 3 parts so you don't need to clean install any longer.
  15. I think you may have had some old registry values.
  16. 3.1->3.2 I personally did client and scenery. Which then means I had to reinstall FTX Global. Which I knew. Uninstall the client then scenery. Re-install each, fire it up, reactivate. I didn't want to miss this: mainly the first one and 3rd Prepar3D Scenery General UpdatesImproved vegetation alpha to coverage Fixed bug where registry values would be written to the wrong location on 32-bit Windows versions Fixed bug causing visual artifacts with certain mission objects Fixed visual defects with glass and z-fighting with certain buildings in KATL
×
×
  • Create New...