FoxTwo

There's a really ugly screenspace reflection artifact with the water in certain lighting conditions, mostly when the reflection in the water is dark or shadowed. The edge of the terrain "glows" with a white outline. Missions set in early morning, late evening, or rainy/overcast exhibit the artifact. This happens in VR and in flat screen, but it's really noticeable in VR. Look at the edge where the water meets the terrain and the shadow starts and you can see the glow. The effect in 2D: and in VR

Here's more. Damascus looks awful, please fix. Or acknowledge at least.

Seems like it's a thing on the Mi-24V/W(Hind-E) as there are photographic examples of a gun pod/rocket configuration but apparently not the Mi-24P Hind-F for whatever reason.

Because a picture is worth a thousand words, here is what I'm talking about. There's no smooth transition between mud and clear here, it's almost like it's just off then on. And mud sticks around FAR into the clearly visible range. Either the high resolution LOD distance needs to be increased or more transitional LODs need to be placed between the distance texture and the close range texture. Mud: Not mud:

I'm noting (particularly now that I'm flying more helicopters on Syria) that at low altitudes the texture LODs for buildings are only rendering at full resolution when you're very close to them. At distances that I would consider typical for normal LODs I'm getting what look like long range texture LODs (fuzzy and low detail) until I'm basically right on top of it. It's super noticeable at low speed low altitude flight. This happens to almost any building but is easily observable on the larger ones like hospitals and skyscrapers.

How fast were you going? Were you descending? Don't exceed 350 kph in the airframe or you will suffer a retreating blade stall.

Make sure you're running the beta and not the stable version then. The only reason you should still be seeing an error message is if you're running the wrong version.

Rocket launch effects are working for me. What pod were you using?

In flat panel, it's in the middle of my screen as I would expect. But in VR it's at the top of my view area. I have to look all the way down at the floor of the aircraft to center the overlay reticle.

He appears to be disabled in the firing range mission as well, which is a problem if you're trying to figure out how to use the ATGMs

This is a bug. With control sync enabled, the axis controls are ANYTHING BUT synchronized. With zero control input the game will pull full left/back stick and the collective will be forward. For some reason. I noticed this started in other modules a few patches back, it's just more pronounced with the Hind in the hot start missions because you just spawn and die.

Can we like... Calm down a bit when a new module is released? Just a bit. There is a workaround to get the mi-24 working, in the meantime, relax. He'll get to it when he has time.

Same as the Mi-8. https://www.mudspike.com/wp-content/uploads/guides/DCS Mi-8MTV2 Guide.pdf#[{"num"%3A108%2C"gen"%3A0}%2C{"name"%3A"XYZ"}%2C0%2C540%2C1]

Overspeeding the aircraft resulting in a retreating blade stall. Don't exceed the aiframe limit of 270 kph. https://en.wikipedia.org/wiki/Retreating_blade_stall

Well I guess I wish they'd just fix this bug in their lua. Maybe that's why it got moved. Maybe all bugs should end up under the wishlist. "I wish I got what I paid for."

And yet not assigned to the UN faction in DCS. Which I see as a bug but apparently the forum mods disagree.

The UN faction cannot use the UN livery in the mission editor. Why did you move this to wish list? It's a bug. The UN Livery is in the game, it's just not available for the UN faction. Eagle Dynamics\DCS World OpenBeta\CoreMods\aircraft\Mi-24P\Liveries\Mi-24P\United Nations\description.lua name = "United Nations " name_ru = "Организация Обьединенных Наций" countries = {"UKR","GRG","RUS",} B.U.G. Not wishlist.

Thanks for the radio guard channel fix!

I think that's debatable compared to the non volumetric clouds we had in the game before that would rotate based on camera angle.

For #1, the light leak is due to the face pad. They put cutout slots for glasses wearers I think? An aftermarket pad would fix this, but it feels like a bad decision. If you put your fingers up to the pad to block the slots, you can see that they are the problem. #2, The FoV increase is... subtle to say the least. Agree with 3. I prefer either none at all or whatever it is that WMR does, because the vive seems to turn it into an impressionist painting. And for 4, it's due to the lens overlap being reduced to increase the FoV. For me, the overall disorientation and eyestrain was NOT worth it.

The VR cloud jitter has been fixed. Every other aspect of the clouds is still in development and subject to change.

Fairly certain that this is a symptom of vram memory exhaustion and the inability of DCS to stream in assets without killing the cpu. Being single threaded, the IO operation consumes most of the cpu available for draw calls. Eventually it should settle down and return to normal but this can take several minutes. Maybe this limitation will go away when they move over to vulkan.

So previously in A-G mode when the SOI was the tpod the AG radar and the hud target diamond everything was coupled together. Now it seems like the hud diamond isn't following the tpod when I slew. If I hit undesignate and slew in the hud, everything moves together. Is this intended?

My TL;DR. If you have the G2 and you like it, you probably won't need to spend the money. I'm sending the vive pro 2 back as I found it uncomfortable to wear and disorienting to the point of slight nausea, which is odd as I have over 2000+ hours in other headsets and haven't had motion sickness in years. Color, contrast, and FoV are an absolute upgrade over the G2. Audio, visual clarity, glare, godrays/chromatic abberation, brightness, and comfort (for me) are downgrades. Durability is a question but so far it feels like the Vive would last longer than the HP with daily use. The stock face pad has what I assume are slots for glasses along the temples. This lets light come into the headset unless the room is pitch black, which (for me) is also a negative. If valve decides to make an Index 2 with these panels and their lenses I'd probably be all over it. If anyone cares, I was able to remove the earphones and use my headset/mic combo that I normally use (a pair of Sony MDR-V6s with a modmic). I had no issues fitting the headphone headband over the headset.

Firing the GUV 8700 gunpod in the Mi-8, I don't know if it's the projectile bounce or what, but the longer you hold down the trigger the less frames you get. Short bursts don't see to be a problem but continuous fire breaks the game, it's vomit inducing in VR.