I reported that a while ago, it should be in the bug tracker system.

Oh god, the day X-Plane has that, I won’t be able to get back to real life anymore 🙂

The freezing necessitates me manually having to restart my Mac by holding the power button. I can still hear aircraft sounds, but there is no visual movement and the entire system becomes unresponsive.

Just wanted to check this is not a known bug?

Completely agree with this, however at this stage, people want the short-term solution.

Unigine managed to get a pretty good volumnetric cloud rendering system in : https://www.youtube.com/watch?v=tui5-x2i2zw

Maybe one day when our tech is on steroids 😉

“X-Plane 10 introduced a new, accidental, unwelcome behavior: it snaps certain datarefs (E.g. the autopilot VVI and altitude) to a fixed grid every frame. If you use DataRef Editor to set the autopilot altitude to 10,001 feet, it will jump back to 10,000.

The goal of this code was to allow panel knobs to freely spin an autopilot value for smooth animation – if the physical display in the cockpit is an animated mechanical roller, not snapping to the grid makes it look like it’s turning. When the user finishes spinning the knob, it “lands” on an even number like 10050 feet, just like the real aircraft would”

I’m not sure how important the label on the rendering tech of cloud systems is. In the end:
– Pretty much anything that responds to camera location is at least somewhat 3-d.
– Anything that is on your computer monitor (without VR goggles or stereo-LCD like NVidia was promoting on gaming laptops) is distinctly 2-d.

Particle systems are usually rendered via billboard, and billboards are one of multiple ways of rasterizing a theoretically 3-d thing onto a 2-d screen. And rasterizing 3-d volumetric data with with billboard clouds goes way back to both the Wang paper that was the foundation of MSFS’s clouds and the academic paper that Austin found that formed the foundation of X-plane 7’s. (I don’t recall the original paper Austin used, but it was the original “make a point cloud, sort to the camera, and rasterize it to capture self-shadow.” What we do now is quite a bit different in terms of lighting, but it’s still a 3-d point cloud approximation of a mathematical 3-d volume rasterized as 2-d billboards.)

For every cloud system in this bucket, it’s like Penn-and-Teller – no one has made a ball disappear from reality, but there’s considerable art to slipping it into your coat pocket in a way no one can notice. Having fought like hell with our cloud system for years, I appreciate anyone who can make a volume->particle->billboard system look good.

The “big” jump in cloud tech is for the systems that are using ray marching/volume tracing. This skips the particle and billboard step completely and directly attempts to trace the underlying volume on the GPU. It’s way more expensive in terms of compute resources, but it’s a better fit than particles for what the GPU is good at, and gets a bunch of other nice rendering properties too.

better screenshot (png) : https://s29.postimg.org/5gzak43vb/b738_1.png

[IMG]http://i65.tinypic.com/e6ruwx.jpg[/IMG]

no, they don´t use particle system at the moment. This clouds are 2D clouds. I have created the last two weeks for XEnviro new alternate alternate clouds.

http://forums.x-plane.org/index.php?/files/file/36688-xenviro-experimental-clouds-for-payware-xenviro/

link: http://forums.x-plane.org/index.php?/forums/topic/117903-improved-cockpit-shadows/#comment-1141682