Build 7628 P3D V5.1 HF1 issues [partial workaround]

robains

Member
Networked Setup - EA On
1. Flight plan does not auto load when option is set to autoload
2. Weather doesn't load at the defined intervals ... I tried 5, 10, 15 mins and the weather did not update to real world (per Foreflight). If I go to Debug option and do a manual refresh the weather does load but will never update after that regardless of interval set
3. Still only seems to be one cloud layer being rendered when I have max 5 layers set and doesn't match METARs

Cheers, Rob.
 

mpo910

Member
1 and 2 I can confirm on my end too. EA on, P3D V5.1 with HF.

Number 3 I am not sure at. I thought today at FALE I saw more than one cloudlayer. But I am not sure anymore.

Marcus
 

robains

Member
I think I found the problem and possible work around and it appears to be an LM problem and I've notified them.

None of the Client, Content, Scenery update installers will replace the VolumetricClouds.cfg file for the older P3D V5.1 version with the newer one that contains the [Global] section and possibly other changes.

Delete Generated Files will NOT delete the VolumetricClouds.cfg file.

As a result this entire section is missing from VolumetricClouds.cfg and/or other changes to [Cumulonimbus], [Cirrus], [Stratus], [Cumulus] are not there. The only way to work around this is to manually delete the VolumetricClouds.cfg and then start P3D which will then regenerate this file with the correct sections.

I'm almost certain this is the cause for users indicating "missing" clouds/weather, especially those using HiFi ASP3D. My other concern is there possibly anything else not updating correctly from the installers and/or not being deleted with "Delete Generated Files" (which is a prepar3d.exe command line option)?

[Global]
render_grid_x_km_low = 0.3
render_grid_x_km_med = 0.3
render_grid_x_km_high = 0.2
render_grid_x_km_ultra = 0.15
render_grid_z_km_low = 3.0
render_grid_z_km_med = 3.0
render_grid_z_km_high = 3.0
render_grid_z_km_ultra = 3.0
cloud_resolution_low = 256
cloud_resolution_med = 512
cloud_resolution_high = 512
cloud_resolution_ultra = 768
max_cloud_distance_km_low = 200
max_cloud_distance_km_med = 250
max_cloud_distance_km_high = 300
max_cloud_distance_km_ultra = 350
num_slices_low = 128
num_slices_med = 128
num_slices_high = 128
num_slices_ultra = 128
cloud_shadow_strength = 1.5
cloud_shadow_range_km_low = 100.0
cloud_shadow_range_km_med = 175.0
cloud_shadow_range_km_high = 250.0
cloud_shadow_range_km_ultra = 300.0
cloud_shadow_texture_size_low = 256
cloud_shadow_texture_size_med = 512
cloud_shadow_texture_size_high = 1024
cloud_shadow_texture_size_ultra = 2048
crepuscular_ray_strength = 1.0
edge_noise_wavelength_km = 2.5
worley_texture_size = 64
cell_noise_wavelength_km = 2.7
max_fractal_amplitude_km = 3
cloud_threshold_distance_km = 0.2

This entire section is missing, such that ONLY a full clean install of P3D will get the correct VolumetricClouds.cfg.

WORK AROUND is to manually delete VolumetricClouds.cfg location example: C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v5


Cheers, Rob.
 

joepoway

New member
I think I found the problem and possible work around and it appears to be an LM problem and I've notified them.

None of the Client, Content, Scenery update installers will replace the VolumetricClouds.cfg file for the older P3D V5.1 version with the newer one that contains the [Global] section and possibly other changes.

Delete Generated Files will NOT delete the VolumetricClouds.cfg file.

As a result this entire section is missing from VolumetricClouds.cfg and/or other changes to [Cumulonimbus], [Cirrus], [Stratus], [Cumulus] are not there. The only way to work around this is to manually delete the VolumetricClouds.cfg and then start P3D which will then regenerate this file with the correct sections.

I'm almost certain this is the cause for users indicating "missing" clouds/weather, especially those using HiFi ASP3D. My other concern is there possibly anything else not updating correctly from the installers and/or not being deleted with "Delete Generated Files" (which is a prepar3d.exe command line option)?

[Global]
render_grid_x_km_low = 0.3
render_grid_x_km_med = 0.3
render_grid_x_km_high = 0.2
render_grid_x_km_ultra = 0.15
render_grid_z_km_low = 3.0
render_grid_z_km_med = 3.0
render_grid_z_km_high = 3.0
render_grid_z_km_ultra = 3.0
cloud_resolution_low = 256
cloud_resolution_med = 512
cloud_resolution_high = 512
cloud_resolution_ultra = 768
max_cloud_distance_km_low = 200
max_cloud_distance_km_med = 250
max_cloud_distance_km_high = 300
max_cloud_distance_km_ultra = 350
num_slices_low = 128
num_slices_med = 128
num_slices_high = 128
num_slices_ultra = 128
cloud_shadow_strength = 1.5
cloud_shadow_range_km_low = 100.0
cloud_shadow_range_km_med = 175.0
cloud_shadow_range_km_high = 250.0
cloud_shadow_range_km_ultra = 300.0
cloud_shadow_texture_size_low = 256
cloud_shadow_texture_size_med = 512
cloud_shadow_texture_size_high = 1024
cloud_shadow_texture_size_ultra = 2048
crepuscular_ray_strength = 1.0
edge_noise_wavelength_km = 2.5
worley_texture_size = 64
cell_noise_wavelength_km = 2.7
max_fractal_amplitude_km = 3
cloud_threshold_distance_km = 0.2

This entire section is missing, such that ONLY a full clean install of P3D will get the correct VolumetricClouds.cfg.

WORK AROUND is to manually delete VolumetricClouds.cfg location example: C:\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D v5


Cheers, Rob.
As usual Rob you are a genius. I did not perform a clean install and sure enough that entire section was missing and I couldn't get any clouds. I'm running the latest P3Dv5.1 HF and all the latest ASP3D and ASCA and nothing worked. I deleted the cfg file and it regenerated correctly and now all is good!

I would suggest posting this link over on the P3D Avsim forum for everyone else to see. I sure hope LM didn't miss other things as well.

Take care, stay well and thanks for ALL you bring to our hobby!

Joe
 

mpo910

Member
It does not solve it entirely for everyone. I think we have different issues for those who have no clouds.. I did check this also and have the updated version also created after deleted the prior one. Clouds will not reload with ASP3D.....they disappear and come not back all though they should regarding metar. Damian is aware of certain issues as well.

So for some users not having any clouds at all it may be the cause and solution. But there are further issues with reloading weather with ASP3D as well.

Marcus
 
Top