St4rgun

The most hyped feature of 2.7 (introducing the new weather system by implementing volumentric clouds first) appeared more than a month ago after two initial re-scheduling. Beside of that in the original changelog they already stated that the cloud jittering / aliasing are well known for the devs, thus eliminating them are priority since then. What meaned to me, that those problems should be "well known" at least for months. I honestly hoped they will introduce a hotfix at least within a week after original release because of the severity of these bugs. Three more versions came after that with the clouds still in the same state. But what is most alarming for me is the radio silence (or let's say "lack of detailed feedback") upon the status of this bug fix procedure. I understand that with OB we have the rights to do our best to report any bugs for the devs to help them, but we are not entitled to have any percentage-like progress report on the development. The best reply we can get as an answer like "it will be ready, when it is done", and "it is well known, we are working really hard on it", maybe some "it's priority". Now we should only hope that the problem is not originated in the roots of the entire applied volumetric cloud rendering technology (i.e. impossible to fix without changing the whole system), because that would be really sad. I think the community here deserves some real feedback about what's going on behind the scenes. If these are bad news, then let it be, we will wait for the fix anyway. But the people here are spending countless hours with writing really useful professional feedbacks and detailed bug reports for free just to help the devs. We are not flaming, just do our best to help, so sometimes it would be kind to get some progress report back. Anyway thank you for the 2.7 version, it's the best DCS up to date.

The issues with the reflections on the first example image are: the reflected clouds seem much different than the ones they mirror (different shapes, colors, sizes and positions) - almost to a degree it seems like the reflection is some kind of "cloudy" texture which does not match if in a given situation the water reflectivity can be so high then the contours of the mirrored clouds also should be much more defined. If the mirrored clouds are blurry (because of the waves on the surface) then the reflectivity also should be much subtle. - like in the last example photo. You can not have both - high reflectivity with blurriness. lack of Fresnel (changing the reflectivity based on viewing angle) makes it difficult to guess altitude

Changing those values does not help at the COLOR of the outside of the mask (black vs transparent), only turning on MSAA does. But changing MSAA on really switches the mask to black as intended.

Yes, I also experience this bug. It can't be seen directly, but only detected by your periperal vision mainly at the bottom of the screen in the HMD. Very annoying indeed.

That's really unfortunate, because I use 3Dmigoto mod which requires MSAA to be turned off... Shall we count it as a bug? It can't be intentional, the mask should be black all the time not transparent.

Check out the rudder position in the cockpit at start. For me after the 2.7 update every plane starts with full left rudder instead of correctly syncing with the position of my pedals. As long as I momentary press the rudder pedals it syncs immediately to the center.

The right phrase to look for is Fresnel Effect. The water's reflectivity should change upon viewing angle to be able to correctly sense the height from the surface. Of course this would be highly complicated to implement fully, but some approximations should me made.

The clouds of 2.7 are much better than the rotating half-eye-rendered puffs of 2.5.6 was, but they are only "a promising start" right now in VR. Some feedback: low resolution (blockiness) at the half-transparent edges of the clouds, it's much worse in external views than in cockpit heavy aliasing, vertical jittering and low resolution at distant clouds - but the 2D mirrored image and screenshots do NOT reflect these artifacts, the mirrored image is perfect, so the issue only affects the HMD the whole cloud layer jitters vertically and at the edges of terrain/clouds separation some white aliased pixels can be seen the gamma should be dialed from 2.0 to 1.7 for my liking to have better details in clouds Reverb G2 here, PD 1.0, SteamVR 50%, GTX 1070 (457.30), i7 10700k, 32 GB, Win10 20H2 (19042.928) Looking for the next hotfix. :) Keep up the hard work guys, this version will be phenomenal!