mcphailtom

This issue is still present for me following the last patch. It isn't a complete deal breaker but I would love to not have it 🙂 The pass the team recently did on the A300 has been experience altering for me in VR, none of these sorts of issues and improved performance to boot.....if you could do the same on the 340 🙂

Hey @IniSteve Just wanted to check in and see if you had any suggestions. If there is something I can do configuration wise to mitigate I am happy to try.

Hi Steve, hope this one helps. It is from a slight lean forward in the seat.

Hi Steve, Pimax Crystal Super. It's not all of them, but it is the majority of the alphabet keys. I'll see If I can get some through the lens pics now.

Unfortunately there remain some difficult to deal with LOD issues in the A340 post update when using VR. Of these the most frustrating is that 90% of the MCDU buttons are missing labels unless you move your head right up to the unit (which is mostly impractical). Any idea if these are on the fix radar? Many thanks.

Can confirm it is looking great again

@IniSteve This is wonderful news thanks for sharing

Do you have any indication of what this means for VR users and future products like the A340?

@ScarfaceUKCompletely fair! I think we're all with you on the sentiment and perhaps have been more forgiving only because many were here to witness the way the change was dropped on the developers. That being said you are right, it's an expensive add-on and it's reasonable to expect it works as advertised.....I am right there with you.

Understand, thanks for keeping us up to date none the less. Very saddening. Out of interest is there an expected impact on future releases for VR users?

Any updates on this @Eddie ? Understand this is an issue imposed upon you guys but any indication of a timeline would be great as the plane is an unusable investment for those of us that only fly in VR

I think PMDG said they have a few additional changes to come for a complete fix. Looks like it might be the same here

I also tried a complete clean install to no avail

Almost seems like it didn't make it into the patch despite notes maybe, when I said it looked better I think I was perhaps letting optimism sway my judgement. It pretty much looks the same.

Still seeing the same issues here as well. Looks "better" but still a lot of holes in cockpit and missing switches"

Thanks @Eddie .... I'm not sure it gets said enough but the work you guys do is great and the continued attention is top notch and much appreciated. Knowing that you're invested as a team is good enough for me 👍

@Eddie Just wondering if you have any take on this one as far as MS/Asobo being the ones liable for correcting the issue? Based on the discussion on the MSFS forums it really seems like at least some of the developers of third party aircraft were taken quite by surprise with this change. Both the A350 and PMDG's 777 are terribly affected and a number of other aircraft like the Citation X perhaps slightly less so but still not unscathed. Is it really encumbant on you as devs to rework your aircraft if they are already using the SDK correctly? I work on a completely different type of software but if we did this to a customer by rug pulling our API with zero notice .... heads would be rolling.