Jump to content


  • Content Count

  • Donations

  • Joined

  • Last visited

Community Reputation

2,901 Excellent


About GSalden

  • Rank
    Member - 5,000+

Profile Information

  • Gender
  • Location

Flight Sim Profile

  • Commercial Member
  • Online Flight Organization Membership
  • Virtual Airlines

Recent Profile Visitors

11,348 profile views
  1. If you do it as I explained it yesterday you can fly with the same profile. Myself however I have a third party nightlighting system and to get the best I lower the LOD and AG density settings, so I can set the AG range to high. This causes my lights to show till the horizon. Therefore I use 2 P3D.cfg files which imho is the best you can do.
  2. The system is stable, Tested it in the Amsterdam region with TE NL + FT Amsterdam + EA overcast weather… In a few days I will try 1.31 and if that is stable 1.30….
  3. This thread has brought me one thing : checking the CPU temps. My server has low temps ( LQS) but my left view client showed 85-92 under max load. It has a 8700 @ 5 Ghz and when I overclocked it I left VCore to auto. So I changed it to Manually and set it to 1.32 and now the temps are 75-79 under max load. So this thread has brought me a good thing 😀
  4. Your CPU has been opened up and the top part has been taken off… We simple simmers are having closed default CPUs… 😊
  5. Come on Dirk. You are cheating : a delitted CPU 🤠…
  6. With HT off it has the same temp range as you have with it on. With HT on I have too much heat because of the many cores I have and to avoid that I need to downclock too much, so the benefit of HT then is gone. I have a 240 EKWB cooling system with push and pull fans (2 extra fans, so 4 in total))… https://www.ekwb.com/shop/ek-quantum-power-kit-d-rgb-p240
  7. With HT on I have 28 and a lot of heat extra. Now it is like yours.
  8. Pay attention to your temps as HT on results in higher temps. My 14 core 7940X cannot handle HT very well because of that. The difference with HT off is almost 15 degrees Celsius and to prevent that I need to lower my OC my 0.4 Ghz..
  9. Just change the 0.4 to 0.9. In the formula (= expression) you see EnvShadeNightgradient which lowers or rises the Daytime saturation value for the Night. By changing the 0.4 value to a higher value you lower the Daytime saturation value for the Night. So you will have to find a balance between the EnvShade Terrain Saturation value in the menu and the value for the EnvShadeNightgradient . So both values.
  10. Multiple users in this thread and at the LM thread have reported the more CPU load / less GPU load issue. And I am one of them as I showed with a vid. According to Marcus the HF is solving this so load will be back to v5.1 level. Myself I prefer they take it one step further and take more load of the main thread core and put it on the GPU. The 30 series are capable of so much more than what they need to do now. Even with 2x 4K as one wide view and all GPU taxing settings at max. Hopefully LM will release a HF that all of us pleases ✈️
  11. This looks good. Your main thread core will always be taxed more than the others. As long as it does not stay at 100% then you will have headroom and no stutters. Heavy regions have more objects, more AG, detailed PR scenery. If you set your sliders so that in the heaviest situation you do not have 100% continues load then you are good to go.
  12. Ray, it is good to see that your system is now running better, but the main issue as the title says, that the CPU is more taxed in v5.2 and the GPU less in v5.2 compared to v5.1 remains. If I have read it correct you simply had HT enabled without a correct AM. Others, like me, with a good working AM are still seeing the issue. So writing that that issue is Solved might be a little premature…
  13. After trying a lot of things : - Disable Auto Exposure . Auto Exposure is a camera feature where according to an algorytm shuttertime , diaframa, brightess, saturation ect are automatically being set. Duringf Daytime it is working quiet nice and sepertelay during nighttime it is working nice. The same HDR settings with AE On for both Day and Night show too saturated roads at night. With AE disabled you open Envshade : - set the Nightbloom to Minimum and Apply .Close EnvShade In the P3D root, open the Terrain.fx file (make a backup first) which you will find in the HLSL Shaders folder Look for : Envshade_Terrainsaturation_Multiplier + 0.20 - (cb_View.fPrecipitationLevel * 0.2) - 0.4*EnvshadeNightGradient The value 0.4 is the value that determines the saturation of the roads (and terrain). If you increase it the roads will be less saturateed. If you decrease it the roads will be more saturated. Save the Terrain.fx file. Each time you want to try another value for the roads saturation start with opening EnvShade and then simply Apply and close it. It will delete your Shader cache for you so you don't have to do it manually. - - - - - - If you want AE enabled at night you will have to set the HDR brightness inside P3D to about a 20-25% lower value. And in Envshade you can adjust the roads saturation according to what I have described above. To make it more simple ; make a second P3D.cfg file Profile (can be done inside P3D) and name it Night. So you have one for both Day and Night. Myself I have 2 : late dawn--day-early dusk and late dusk-night-early dawn
  14. Both. Your setting is very high so everything is very saturated. Just try with different settings.
  • Create New...