zubillagajose

thanks for your help, do you mean vsyn or gsync? or leave the synchronization fixed?

change the driver, the stutters continue

I do not have AI traffic, no scenarios FSDT, I'm going to try with the nvidia driver

Razer Sofware no, the nvida drivers I was checking if it was also affecting at this moment I have the 511.23, I'm going to download the ones you say and try

thanks, i have orbx products: south america LC, mesh, global, trees hd active sky pmdg 737 ngxu my system i7-9700K 4.6Ghz , my affinity mask is [JobScheduler] AffinityMask=254 P3DCoreAffinityMask=254 MainThreadScheduler=1 RenderThreadScheduler=2 FrameWorkerThreadScheduler=4

hello friends, I have version 5.3, but I experience some times micro stutters, when I am in virtual cokipt the move the camera, it happens to me a lot with pmdg 737 ngxu, the frames are good in general I have a 1440p monitor and an rtx 3070, I don't know if you can help me

take into account when changing settings with ea off or ea on, like ea on, the cabin brightness if adjusted from higher to lower

hello, you can show your settings please?

i download active sky beta with modified file, share a pic https://easyupload.io/yfbk57

Legacy clouds, estrange movements in VC when move tne camera, is normal?

Hi Gerard, I published my cfg of volumetrics clouds, you asked me to send screenshots, I really gave up, I returned to 5.1, I think 5.2 came out with many errors, the clouds when they join mountains looks fatal, according to the forum from p3d they are going to launch an hf but I don't know if that will be fixed, the avsim forum is the error of the clouds with the mountains, I do not know if you saw it and I cannot stand it and I decided to return to 5.1, I congratulate you for tun great work towards the community, a hug

nice

My cfg [Global] render_grid_x_km_low = 0.1 render_grid_x_km_med = 0.1 render_grid_x_km_high = 0.2 render_grid_x_km_ultra = 0.2 render_grid_z_km_low = 1.3 render_grid_z_km_med = 1.3 render_grid_z_km_high = 1.3 render_grid_z_km_ultra = 0.2 cloud_resolution_low = 512 cloud_resolution_med = 768 cloud_resolution_high = 1024 cloud_resolution_ultra = 1024 max_cloud_distance_km_low = 200 max_cloud_distance_km_med = 200 max_cloud_distance_km_high = 200 max_cloud_distance_km_ultra = 100 cloud_shadow_strength = 0.5 cloud_shadow_range_km_low = 100.0 cloud_shadow_range_km_med = 175.0 cloud_shadow_range_km_high = 200.0 cloud_shadow_range_km_ultra = 200.0 cloud_shadow_texture_size_low = 1024 cloud_shadow_texture_size_med = 1024 cloud_shadow_texture_size_high = 1024 cloud_shadow_texture_size_ultra = 2048 crepuscular_ray_strength = 1.0 edge_noise_wavelength_km = 2.0 worley_texture_size = 256 cell_noise_wavelength_km = 2.0 max_fractal_amplitude_km = 2.0 cloud_threshold_distance_km = 0.5 [Cirrus] max_density_gm3 = 0.15 distribution_base_layer = 0.05 distribution_transition = 0.95 worley_noise = 0.55 worley_scale = 1.0 diffusivity = 1.0 persistence = 0.63 octaves = 3.0 upper_density = 0.95 simulation = 0.0 cloud_width_km = 30 cloudiness = 0.15 base_noise_factor = 0.95 edge_worley_noise = 0.0 fractal_amplitude = 1.5 edge_sharpness = 0.05 churn = 1.2 [Stratus] max_density_gm3 = 0.75 distribution_base_layer = 0.2 distribution_transition = 0.5 worley_noise = 1.5 worley_scale = 3.5 diffusivity = 18.0 persistence = 4.0 octaves = 1.0 upper_density = 1.0 simulation = 0.0 cloud_width_km = 100 cloudiness = 0.15 base_noise_factor = 0.1 edge_worley_noise = 0.1 fractal_amplitude = 5.0 edge_sharpness = 1.0 churn = 200.0 [Cumulus] max_density_gm3 = 0.75 distribution_base_layer = 1.0 distribution_transition = 0.2 worley_noise = 0.6 worley_scale = 3.0 diffusivity = 5.0 persistence = 0.63 octaves = 1.0 upper_density = 1.0 simulation = 0.0 cloud_width_km = 100 cloudiness = 0.15 base_noise_factor = 0.3 edge_worley_noise = 0.1 fractal_amplitude = 4.5 edge_sharpness = 1.0 churn = 1.0 [Cumulonimbus] max_density_gm3 = 1.0 distribution_base_layer = 0.45 distribution_transition = 0.30 worley_noise = 0.6 worley_scale = 5.0 diffusivity = 20.0 persistence = 0.63 octaves = 1.0 upper_density = 1.7 simulation = 0.0 cloud_width_km = 20 cloudiness = 0.15 base_noise_factor = 0.25 edge_worley_noise = 0.15 fractal_amplitude = 4.0 edge_sharpness = 1.0 churn = 1.0

Hi Folks In active sky in settings simulator depiction options enable detailed EA Clouds, enable and ready

hello Dan, thanks

hello Dan, you are absolutely right I wrote to navigraph and they sent me to the pmdg forum, saying that the airac was fine, edit the procedure directly in the file and made the flight perfectly calculating the anticipated turn without doing fly over, I do not know why in the file it says to turn to the right to the waypoint, I do not think navigraph makes that correction I am going to write again, thank you very much for your comments, can you explain me what is ARINC 424? regards

hi russell the pmdg does fly over, I do not change anything

Hi guys, thanks for your comments, I know the difference between both concepts fly by and fly over, I ask concrete is in the fmc of pmdg does a fly over, I do not know if it is correct or is a calculation that the fmc does to make the turn, for example in the airbus mcdu does fly by something wrong but does not fly over. thank you guys for your opinions

Hi guys, there are RNAV procedures where there are fly-by and fly-over waypoints., Looking at the charts for SKBO, the arrival TOLIM2E the waypoints are fly-by, when I do that procedure and I load it in the FMC of the 737 PMDG the waypoint NOR05 does fly-over. Is it an airac error?