Lehmen

Clarity is not that much better, especially if you if you turn on any kind of antialliasing. You still need to be quite close to an object to figure out what it is. VR zoom helps, of course. There is a very long way to get comparable image in VR as on 4K screen. Currently we are around 1980x1080 screens or so.

In Video tab there is a manual override checkbox for supersampling.

I not sure how beneficial foveated rendering would be for Vive. You need wider FOV, to have where to move your eyes inside HMD, while having significant portion of the image you not focusing on. So, most probably it will be used to animate avatars and stuff like that.

So, I did more tweaking with DCS, and I can share what I came out with. I have some things I do not want to compromise on, such as ultimate visibility range or shadows. Other thing I found to be necessary is MSAA, at least 2x. Because currently DCS on Pimax 5K+ can't take it all even on very powerful system, other compromises need to be make. So, for me it came to SteamVR supersampling to go as low as 55% (PiTool and DCS at 1.0) and HMD refresh rate as low as 72 Hz. Currently, those are the best compromise between imagery and performance I came out.

It is second gen because of the FOV. Regarding resolution, current hardware having troubles to keep up even with Pimax. 2-3 times higher resolution with even wider FOV and less distortions would be 3rd gen already. But we need at least couple more generations of GPU for that to work.

I never tried Vive Pro, previously I had owned Oculus Rift, so I can not tell anything about how is Pimax resolution compared with Vive Pro. I totally agree that DCS performance currently is not perfect: I can make everything smooth and sharp, but it require too much compromises for my taste. And although their latest PiTool with smart smoothing is definitely a step in the right direction, we are not quite there yet. Another 20-30% of performance, and hopefully I'll be satisfied. But still, I can not go back from wide FOV, not anymore. My biggest problem with Oculus was that I was unable to properly look around without breaking my neck.

But this is exactly how it works. SS is only active when current FPS is more than 1/2 of refresh rate. It immediately inactive when fps drops lower and active again when fps is sufficient for SS to work. At first you need someone to tell you when it active or inactive from PiTool window, but very soon you will learn to see the difference. Normally you don't see this effect when looking straight ahead. But it is very visible when you looking at the side. And this is how you can tell if SS active or not. When it active, there is no blurriness at all (which, in fact, double rendered objects, shifted a little). As soon as objects on the sides became blurred - you know that SS is inactive. When they become sharp - you know that SS is active.

You get blurry picture when SS is not active. It became perfectly sharp when SS is active. To properly test it, you need someone looking at PiTool window and report to you when smart smoothing is active or inactive.

Foveat renderering do not work for me, screens on HMD just turned black and stayed black until power off-on. Do not recommend it to try. No, I do not use any mods.

Quick update on performance. Tried beta Pitool with beta brainwarp. And I can tell, they are definitely getting there! When it active, world seems almost as smooth as it was with Oculus Rift. Unfortunately, it is not always ON on very demanding scenes (such as a low level flight over a city on F-18C in Caucasus map), probably because fps is not sufficient for it to work. Or maybe it is just a bug of current implementation. Lowering HMD refresh rate helps, on lower refresh rate BW is ON most of the time, even on very demanding scenery and plane (F-18C, low level flight over city) and world is almost perfectly smooth. So, just a little more, and we will be there. Was testing with pretty much everything maxed out. Only MSAA and SSAA were off, and terrain objects shadows were flat. Pimax FOV was set to normal (very easy to check your six!).

Amiga is Amiga, and Sinclair ZX Spectrum is completely different thing. I started with Spectrum too.

Regarding performance, don't take me wrong. DCS is useful with Pimax, especially at small FOV (which is still light years ahead of Oculus), but you need to make some compromises with settings. You won't get same smoothness as with Oculus, but it is a very pleasant experience, nonetheless. I will never fly DCS with Oculus again. It is just there is lot of room for improvement in performance department.

Got my Pimax 5K+ too. It looks great in DCS, but performance is quite bad. And I'm talking about machine that is still in 3Dmark Hall of Fame (means in the top100 in the world) on Fire Strike Ultra in single GPU category (my score is 9455), for several months now. So, something need to be done about optimization for those new generation VR's to work properly in DCS.

It doable, on both Huey and Mi-8. Fly slow (try 80 knots, not working, than 60, or 40. You should be able to do it at 40), use your stick only to change pitch, keep roll neutral at all time. Use only pedals to change the direction. However, sling cargo physic in my opinion is still not even close to a real thing.

Finished the campaign, really liked it. Would recommend to anyone who want to become better Mi-8 pilot, or just like flying more than blowing stuff. No glitches worth mentioning, except on the last mission: for some reason NDB on landed helicopter do not work. Or maybe I just did something wrong. In the end had to fly approximately in the area and use labels to locate the chopper.

So, it seems now there is no way to enable Russian voice-over in English DCS without reinstalling whole DCS. Previously, when different languages missions versions were in separate folders, it was possible just to change English missions files with Russian, and that it. Unfortunately, after ED implemented so called multi-language support for missions, they effectively destroyed even those rudimentary multi-language capabilities that DCS had. Too bad. It is strange to hear Maksimych speaking in English, and not just any English, but with lovely British accent too! But I got used to it. Sort of.

You don't have to deliver all the cargo to proceed in the campaign. I broke 2 of 4 on landings, but still completed the mission with 80% score. To my understanding, you can only deliver only one cargo (for example, most easiest one, F4 by default, couple of light barrels), and be able to proceed. PS What can go wrong in this mission? 1. Do not try to land the cargo TOO fuel efficient, this is how I broke one. But do not use more fuel than you must, I got emergency fuel warning right before landing at Maykop. 2. When you landing cargo near red smoke, do not listen to commands that you should move left/right/forward, just put it down where you are. 3. Watch for that oil tower when you putting cargo down.

To my understanding, "Unable to comply" message is related with Rearm request (you ask to Rearm and Refuel not just to refuel). You can see that ground crew is refueling right away, if you check fuel quantity gauge: needle is starting to go up almost immediately after request. And I didn't had to shut helicopter down, BTW.

How do I enable Russian voice over in the campaign? I have English DCS, but I can understand Russian perfectly.

Я очень слабо знаком с редактором, поэтому даже не рассматривал такую возможность. Но, подредактировал, сработало. Может даже слишком хорошо сработало: пока я добрался до базы, 28-е там уже всё вынесли, мне осталось только домики взорвать, пристроиться к вертолёту и нашпиговать его из пушки :) В любом случае, спасибо, компанию отмучал.

Ради интереса решил ещё раз командировку пройти, на 2.5 Компания под него не оптимизирована, но правдами-неправдами добрался до последней миссии. А там засада - база теперь стоит в густом лесу, расстреливать здания вихрями нет никакой возможности. Пробовал НУРами, тоже не вышло.

I have to take it back. Since I get more familiar with VKB config utility, there is absolutely no problems with VKB controls: it do exactly what I want and how I want.

Probably they are. But the money are on the Western market, not Russian, so I guess they can't just ignore it. VKB have great products, but with some weird decisions. As an example, trim hat on their MCG, already mentioned. Another one, slew stick on MCG. It look cool and comfortable to reach, but it works somehow strange. I ended up with using factory slew control on Warthog throttle. Which is terrible, but still feels much more natural.

No need. My problem was, I couldn't understand why do we always have that much additional collective and power, that can't be normally used, so I was thinking that Huey is broken. Now that I know that it is intentional (and if you think about it, having some additional power always available is a smart thing for helicopters) - I know that DCS Huey is not broken, it is indeed become much better after implementation of EGT. Anyway, it was a very long time since I had fried my Huey engine, it is not that hard to fly respecting the limits.

This is where the problem lays. For me it is hard to grab the concept, that significant part of control input is deliberately made to be damaging to the machine. But if you say that it is really so for Bell helicopters - I'm not arguing anymore.