Jump to content

cdv0007

Members
  • Content Count

    59
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

10 Neutral

Flight Sim Profile

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

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. It seems that starting from version 5.2, P3D has become very CPU-intensive, and has reduced its dependence on GPU. Previously, the CPU usage was only about 65%. Now the CPU will continue to work at 100% under cloudy conditions. I use FSlabs from WFSS product ZSPD——ZSNJ. The reason for consuming CPU may be too many ground buildings or too many volume clouds.
  2. I upgraded and installed P3D V5.2 HF1 in win11, but because win11 is too bad to use, I can only go back to the original win10 by restoring. After restoring, in the program manager, P3D is back to version 5.2, and Unable to run, unable to uninstall. I deleted P3D through manual file cleaning and registry cleaning. After reinstalling it, it seems that it was not installed again. Restart the computer, uninstall, and install again, it succeeds. offensive initials not allowed win11
  3. https://prepar3d.com/forum/viewtopic.php?f=6312&t=142906&p=243834#p243834 The volume cloud problem was reported in the LM forum. If you encounter the same problem, please ask for help.
  4. I completed the update and conducted a test flight. The problem that volumetric clouds cannot cover the terrain during certain rotation angles still exists. I don't want to go back to the old texture cloud, because it will affect some performance and cause stuttering when it is overcast. I will continue to report to LM.
  5. Thank you for your report, and hope to continue to pay attention to the resolution of this issue. It turns out that this is indeed a problem, and it exists among all users.
  6. This is a very sad news, this is the most fatal problem in P3D V5.2.
  7. Today, Win11 was pushed as scheduled, and I updated it. After the update, P3D V5.2 works well. It is hoped that LM can solve the terrain penetration problem caused by volumetric clouds in the near HF1.
  8. will they fix the bug of Volumetric clouds cannot block the terrain in some viewing angles ?
  9. No matter how many ideas you have, you have to wait for an update gamble in half a year.
  10. don't using Envshade it will cause ghost night lights and low FPS
  11. Do they help volumetric clouds?
  12. P3D has been updated to 5.2. First of all, let's talk about PC space, 1080ti+9900K+32G memory, all of which have been properly overclocked. LEBB airport using Orbx closed dynamic vehicles and characters, using fslabs A320, the weather was cloudy and rainy. The shader has been cleaned up. The maximum viewing distance on the ground is 69 miles, and the maximum viewing distance in the air is 199 miles. I use ASCA for the traditional cloud, and the cloud resolution is 1024*1024 DXT. During the landing of LEBB Rwy30, there is a slight visible stuttering, and the FPS is not ideal. The screen will occasionally jump. When using volumetric clouds, although volumetric clouds have the bug that they cannot block the terrain, they are also rendered full sky clouds, but the FPS is significantly higher. When I adjusted the cloud resolution to 256*256 in ASCA, the FPS increased slightly and the stuttering phenomenon was slightly alleviated. Summary: EA's volume cloud optimizes performance to a certain extent, but there are bugs. I hope that HF can be repaired, and I still prefer to use volumetric clouds in the future. The hierarchical transition of volumetric clouds is terrible, and there has been no effective improvement since the release of P3DV5.
  13. In my opinion, the P3D development team can barely tolerate, but I cannot tolerate the overall level of the P3D test team. Very obvious BUG, very obvious stuttering, very obvious inhumanity, even will not report. Maybe the test team is the early version players of HF products, not the testers who really have a sense of responsibility for improvement. No complaint, no complaint, no complaint.
×
×
  • Create New...