Eldur

What a history lesson! Should be included with the map

Never gets old...

Weird. I'm currently experiencing the same with my Quest 1. Even at the highest res setting (1.1 in Rift - 4128x2272 or High in VD - 4416x2400), it's utterly blurry and looks worse than my CV1 at PD 1.0. Can't even get Cable Link to connect, but I had that experience with both AirLink and VirtualDesktop. There sure is something not right at the moment. Not having such issues in other games though.

Bump. Immediately noticed the same when trying out my G2. And it's rather like 18-20cm, like having your hand on a stick. I'm literally about to try this just to have properly functional controllers for the time being. Also, even though not directly related, I also noticed this.

The buttons aren't mapped. Triggers, Grips and Ministicks work exactly like with the Oculus controllers, but the ABXY buttons do nothing, whereas on Oculus they're like this: A - VR Zoom B - nuffin' X - Esc menu Y - Recenter VR Especially buttons A and Y are mandatory for me and apparently there's no way to map that manually. But I see a "VIVE Controller" listed in the key mapper, that has everything greyed out. So it's the wrong one and I can't map anything. Looks like that is still WIP, hoping for things to speed up a little though.

I didn't even know there was a poll, but the result looks good. The Viper is going to be great. And I can finally read stuff in it with my new G2, so I'm able to enjoy all the good stuff that comes to the displays without having to zoom constantly

Just reporting back: I still had it on my 3570k rig after a forced update to 21H1 and it appeared on my 5800x as soon as I replaced that temporary 660 with my 1080 and it's switched off. I guess I'll leave it like that unless I run into some issues or get recommendations to activate it.

I'm having a rather severe problem after not having flown since 2.7.2.7910.1. Regardless of my Win 10 regions setting (German/Germany with both German and US keyboard layouts, usually using my native one), I get some kind of Japanese keyboard layout with latin letters (all the special keys are like OADG 109A though) in DCS now. This breaks quite a lot of my keybinds, especially all the stuff that's in between the letters and the Enter key. Switching in Windows from German to EN-US or back doesn't do anything. I don't even have any other languages installed... Anyone else experiencing this lately or having an idea of how to fix this? Edit: Outside of DCS everything is just fine Edit 2: Windows just forced an update to 21H1 (from 2004), but that didn't change anything But: I noticed that when I type something into the search box in the button/key mapping dialogue, it enters correctly, just what I type in by my German keyboard layout. But when pressing, let's say, ü (english: [ ) or + (english: ] ) to get the kneeboard next/prev keys, it doesn't react on ü/[ at all, brings [ on +/] though and I get ] when pressing # (directly below +) which normally brings up the general comms menu. Same in the sim, the key mappings are off. What an weird issue... I've uploaded a log, maybe that will help finding the root cause. Weirdly, DCS even generated a crash dump even though I exited it normally. PS: All that on my old 3570k rig, don't know yet if it's the same on the new one. I wanted to have DCS updated and running fine before taking it over to the new one - and replacing the GPU. dcs.20210728-182424.zip Edit 3: I could finally solve the problem, after I noticed it was not just DCS related. Had the same issue in DOSBox, didn't need to try other games to know it's not and DCS issue actually. Simple as-is: I went Win+I, devices, removed my Digital Media Keyboard Pro, a Logitech 106 keys keyboard (I don't even know I have or even had, I'm using the very same Microsoft keyboard since 2003) and a HID keyboard thingy (basically everything that identified as a keyboard), replugged the thing and it worked normally again. Anyway, the weird thing is that issue only appearing in games where the keys are polled directly. Edit 4: Now, that I've thunk about it, I might have found the reason. I was visiting my mom within the last few weeks (which is why I didn't run DCS for so long), and I always take my mouse with me when I do that. Because I ordered my new hardware to her location and built the thing there, I needed a keyboard - and I took a Logitech K520 she has and paired it to the dongle of my MX Anywhere 2 mouse with the Unifying Software. The thing is, that keyboard has a Swiss layout. Apparently the dongle still has it registered even though it's actually far away and switched off now and that might have changed the internal mapping somehow. I got the initial idea that it might be a Japanese layout because the key left of the alpha numbers reported back as "KANJI" in DCS. TL;DR: Tech issues can be weird. Very weird. I edited the title a bit and will leave the post, maybe someone will find it useful at some point in the future.

Something less exotic, but still "what if": I'd actually love to see DCS: Yak-41, based on the -141 prototypes. If we can't have the real modern, red toys, have some educated guesstimates on the toys that didn't become real.

What happened to this anyway? I had this setting in WIndows 2004, but it's not present in 21H1 anymore.

Another tail-sitter VTOL:

This thread literally cries for this one:

Made my day!

I'd love to get that variant later on as an upgrade like BS3 or A-10C II, but if I'd have to choose, I'd prefer the V. Getting both would be optimal.

Exactly how I'd like to see it. First finish the P, then bring the V as an upgrade. If doable, the VP would be great as well with the 23-2 turret. The V would be more important though.

Either that or via kneeboard while sitting on the ground with the ground crew being able to pick up that order.

Check SkateZillas Updater GUI. With that you can switch your standalone installation to any branch and version, given the update files are still present on ED's server.

Day 1 Preorder. Can't wait for the following Tornado IDS module. I mean, HB and TG have been the most probable 3rd parties that might be able to bring the Klappdrachen, and they still are. A collab is the cherry on top of the icing on the cake (Celestia entered the chat)

HλLF-LIFE³ conf... I mean, DCS: Tornado IDS confirmed

Looks like they fixed the negative drag. I remember the Viggen being faster than usual when bringing Winders after getting rid of them, similar to the Hornet back in the day with the Mk.83 when keeping the racks... was fun, but after all, having it all more realistic is better. That's one great step. Would be cool to have that for all campaigns, kinda like a demo for them. I've noticed that quite often because I was trying to set some manual depressions for the weapons that aren't being calculated like the 30mm grenades or S-24 rockets and was wondering if it was erroneous. Glad it obviously was. Finally, no empty "ADV-" box anymore? Tiny thing, but great! That missile jump was straight ugly. Glad it's gone now. That optimization sounds great, looking forward to see that next week.

That one definite answer.

Less than 5km from my home it looked like this... I'm glad to live ~100m above that valley, just had some groundwater gotten into the basement, could be worse.

Well said. I prefer the Hornet for the fact that all the avionics are legible while you need to bring a x23 telescope when flying the Viper to be able to read stuff on those mice cinemas. But if I don't need those displays at all, I prefer sitting in the Viper, clearly moar joy buzzing around.

Le me waiting for an MS SW FFB2 replacement...