September 16, 20169 yr Stunning effects Robert. It all looks very real. Calibrating the scattering to exclude the ever present border makes a huge difference.
September 16, 20169 yr Author Stunning effects Robert. It all looks very real. Calibrating the scattering to exclude the ever present border makes a huge difference. I think so, yes. Thanks! It helps that I am obsessed with tweaking these parameters excessively Here's another shot of the scattering at FL360. Rockies. - Currently giving X-Plane 12.10 a spin on Shadow PC. 10 years with X-Plane now, since 10.20
September 16, 20169 yr Darn I'm getting the visibility reduced to zero while using beta 4 (critical bugfixes).
September 16, 20169 yr Author Darn I'm getting the visibility reduced to zero while using beta 4 (critical bugfixes). Did you install the latest NOAA dev version? While Beta 3 was working great for me, Beta 4 seems to cause some trouble on my machine. The visibility always gets reduced to the absolute minimum. Looking at the PythonInterfaceLog.txt I see the same error gets traced over and over again: Script 'PI_noaaWeather.py' successfully loaded. TypeError: rget_cb() takes exactly 5 arguments (2 given) TypeError: rget_cb() takes exactly 5 arguments (2 given) TypeError: rget_cb() takes exactly 5 arguments (2 given) TypeError: rget_cb() takes exactly 5 arguments (2 given) TypeError: rget_cb() takes exactly 5 arguments (2 given) TypeError: rget_cb() takes exactly 5 arguments (2 given) [...] I will check if this also happens with the tweaked official NOAA version. I am pretty sure this is a bug in the NOAA dev version. Sent this to Joan, we'll see. I have no idea what causes this, works fine for most people. - Currently giving X-Plane 12.10 a spin on Shadow PC. 10 years with X-Plane now, since 10.20
September 16, 20169 yr I get the same error: D:/X-Plane/X-Plane 10/Resources/plugins/PythonScriptsAfter Modules InitSearching for Standard ScriptsScript 'PI_noaaWeather.py' successfully loaded.TypeError: rget_cb() takes exactly 5 arguments (2 given)TypeError: rget_cb() takes exactly 5 arguments (2 given)TypeError: rget_cb() takes exactly 5 arguments (2 given)TypeError: rget_cb() takes exactly 5 arguments (2 given)TypeError: rget_cb() takes exactly 5 arguments (2 given)TypeError: rget_cb() takes exactly 5 arguments (2 given)TypeError: rget_cb() takes exactly 5 arguments (2 given)TypeError: rget_cb() takes exactly 5 arguments (2 given)TypeError: rget_cb() takes exactly 5 arguments (2 given)
September 16, 20169 yr Author Alright, I confirmed that the latest NOAA dev version breaks communication with Ventura Sky. Here's a link to the earlier dev version that's working, everyone on Beta 4 use this for now, please: https://www.dropbox.com/s/t08yvioie7x85h9/noaa_dev_working.zip?dl=0 - Currently giving X-Plane 12.10 a spin on Shadow PC. 10 years with X-Plane now, since 10.20
September 16, 20169 yr Alright, I confirmed that the latest NOAA dev version breaks communication with Ventura Sky. Thanks! I can confirm that the earlier dev version of NOAA fixes the problem. Beta 4 is running fine now.
September 16, 20169 yr Commercial Member I noticed the water reflections are switched off by default now in beta 4. Had to switch them on again in the lua file. Just in case somebody is wondering. Mario Donick .:. vFlyteAir
September 16, 20169 yr Author Thanks! I can confirm that the earlier dev version of NOAA fixes the problem. Beta 4 is running fine now. working now It's just a minor typo in the NOAA .py, it will be fixed for the final 2.3 version. I noticed the water reflections are switched off by default now in beta 4. Had to switch them on again in the lua file. Just in case somebody is wondering. Yes, that happens when I copy the script right out of my setup. - Currently giving X-Plane 12.10 a spin on Shadow PC. 10 years with X-Plane now, since 10.20
September 16, 20169 yr Commercial Member I positioned myself at 30000 feet using the local map and then lost altitude very fast. I soon noticed that only a grey "soup" was around me, until I crashed into the ground. There, I could only see a few meters. When I re-positioned myself at my starting airport near my crash site, visibility was good again. Unfortunately I was not able to re-produce this behavior yet, but something must have been wrong... maybe because I changed time of day several times during my placements? Mario Donick .:. vFlyteAir
September 16, 20169 yr Author The visibility algorithm is not working when you're jumping to any altitudes above 10000ft. I think it's the only restriction of the script. Any other ways to start your flight should initialize Ventura Sky just fine. Philadelphia, day / night. I think Beta 4 is done. - Currently giving X-Plane 12.10 a spin on Shadow PC. 10 years with X-Plane now, since 10.20
September 17, 20169 yr Please a link!!! Can you deploy direction and size in the waves? it should be nice. Thanks for your great work.
September 17, 20169 yr Here's a link to the earlier dev version that's working, everyone on Beta 4 use this for now, please Nice, works fine now. Thank you!
September 17, 20169 yr Hello, Screenshots are really amazing! I need to try this new program, the look is perfect! However, I uninstalled SMP and RWC some months ago because I was not satisfied with the look of the cloud layer when flying at high altitude. It looked like a carpet with clear boundaries following aircraft movement. Maybe I should try the newest SMP and RWC versions with Ventura and see if it improves things regarding cloud layers display. Maybe Ventura does a good job to fade out the cloud layer at the horizon in order to reduce the carpet effect of SMP (Just like Active Sky in FSX). Could someone please post some screenshots of Ventura with an overcast cloud layer below an aircraft flying above FL300 to see what the horizon looks like? Best regards, Pierre
Archived
This topic is now archived and is closed to further replies.