hazzer

I have experienced this also. It appears if the host has it enabled it will be enabled for all players as well. When really it should just be either player option OR not allowed.

+1 especially leaving the rpm with a fully closed throttle. In lots of aircraft this will fowl the mags and if just after starting the engine will fail.

This is the issue though. You clearly see there are lots of people irritated about this. So surely the natural thing to do would be to communicate this and then form a plan with the ED Team to work on it once more and finish the Yak? Coming back with the no plan isn't a good enough answer for anyone here.

They aren't like that on other maps, maybe this is specific to the new map?

Hi all, I assume this shouldnt be so low res? Any idea how to fix?

Hi, On the latest open beta I am having an issue where my cursor disappears in VR and locks onto clickable items. The cursor appears occasionally before vanishing again. This happened last updcs.logdate in the Hind only, now appears to be in all aircraft. Cannot attach log as it is too large. Using WMR/Steamvr

Issue is still present with the canopy and prop in latest open beta

I will look forward to giving them. I hope you do understand my frustration as the Yak has been missing many fundamentals of the sim, namely an effective LOD model meaning it effects people in multiplayer who aren't even flying it. Generally I love the Yak but it shouldn't be wip for this long. Many thanks, Harry.

You and your team need to come up with some specifics other than being vauge as usual. It has been out now for 3 years with essentially 0 updates. As a customer it is only fair to expect these products to be completed in a reasonable time frame. Obviously the Yak wasn't as popular as the others but leaving it this long with the same statement being made for the last 2 years is just not acceptable. The last thread on this subject was locked, I think it is fair to leave this open for updates and comments to be pushed through here. I will look forward to future updates on this aircraft.

This sounds like the same issue I have had here I can see a few threads with this issue. But no support from ED? Hopefully it gets reported and fixed.

Yeah I am aware. But it is the same horrible flicker effect that the prop has along with the canopy and window flicker I am getting. They all happen when glancing around the cockpit and all appear at exaclty the same time. However only changing the aircrew.fx fixes the effect for the prop and not the others. I am wondering if there is another .fx file that may fix the flickering for the rotor blades and windows?

Still not fixed for me. EDIT: Also getting it on the heli rotor blades

But we don't?... I haven't seen any in all the years of me intentionally abusing the engines.

Such a fire would lead to actual aircraft damage, not just flames. Mags can fowl when idling at a too low rpm and too fuel rich. Poor engine management, that's how.

This is exaclty true. @BIGNEWY @NineLine @Wags We would appreciate a timeline/actual sign of action being taken to fix and pull the Yak out of beta.

They have rubbed enough salt in the wounds, although at this point them trying to sell us a yak 52 II with the promise of it being fixed wouldn't suprise me. Heck they might even fit the unfinished ns430 to it as the icing on the cake!

Can someone please look into this from ED and fix.

Is this being investigated? Not sure why it is marked as "opinion" becuase it is not.

Would love this fixed also

The issue with the sounds has now progressed to drowning out other aircraft in multiplayer.. A CEII shouldn't be louder than 2 p-51s

It is so disappointing to see it all laid out like that. No comment from ED on this either. I remeber sometime near the end of the year one of them stated some of the team would be working on the yak at the start of this year, which then was pushed back further. It seems they are treating customers like mugs and take advantage of people's willingness to take a gamble on early access.

Glad to see it isn't just me having this issue. Yeah that's the only solution I have found to stop it just to test I set my page file stupidly high and no difference. Seems like a memory leak associated with vr

The whole physics of aircraft flying off field needs to be looked into. I imagine it is at the bottom of the list of priorities however. Some aircraft like the f18 for some reason can taxi, land on any grass, even almost 80° slopes on Mountian sides! But then other aircraft touch the grass and either explode, stick to it, or get stuck. The warbirds which should be fine on grass have a very weird feeling where the grassy areas are glue like and the aircraft easily crash. We need some consistency with what should/shouldn't work. Then the ability to add off airport operations would work much much better.

Do you have the flicker on other objects like the canopy, light housings as well? I seem to get that, the airscrew fixes the prop issue but not this secondary issue for me

Ah, that's understood