Boris

I'm no longer sure about the exact wording, bit I remember recently that Wags said on a podcast that it's up to third parties if they want to make eastern (Russian) aircraft. In the J-11A we'd technically be talking about a license built Chinese aircraft and it also would be developed by a Chinese studio. So, in theory, it would be doubly removed from any restrictions that ED has. I'd much rather see a fully modeled J-11A than the JF-17.

I just remembered that I sent my Oculus Rift back twice, once for connectivity issues and once for pixel faults, before getting a working unit. Apparently cable issues were a big thing with earlier Rifts. Such things don't seem unusual in VR and Pimax is now going through the same process.

That actually sounds like really good customer service and that it's the hardware and quality control which is at fault. I was lucky with my headset and it's completely flawless so far. So feel free to increase your sample size to three :)

Yes, the communication menus should be visible. If not, it's probably because you've had VAICOM disable them. Decide if you want to use VAICOM or not. To start off with, it's probably best to use the standard menus to familiarize yourself with the structure and the selections. You don't need the F keys to interact with the communication menu. It's clickable with the mouse. Most DCS VR pilots use a HOTAS and mouse and don't bother with the touch controllers. It's actually really easy to click the switches with the mouse in VR. I have a mouse on the right and a track ball on the left next to my throttle. Lastly, don't lose patience. DCS's learning curve can be very steep, but it's also very rewarding. Flying in VR is the ultimate in flightsimming experience.

Thanks for this! It's a really important step for useability of the F-14 in VR. Very, very small critique on my part: I like the fact that the fonts are slightly larger, but being a purist I don't particularly like that some wordings have been abbreviated and and the typeface is a little blocky compared to the more rounded original Tomcat font. Great mod though and I can't wait for it to work as a custom livery. Many other modules could benefit from a similar treatment.

I honestly don't care much about the technical background as long as I get 50% more fps :lol:

The Pimax headsets are gen 2 and currently work fairly well with a 2018ti in DCS. It'll only get better with the upcoming VR optimization and Vulkan.

It would be interesting to have the optimization for Causcasus to see the difference as compared to other maps.

So are you going to model this effect? :D

Damnit, why did I go for the 5k? :doh:

They could have just stuck to fixed wing, not trying to tap into every genre

Soooo, according to the latest open beta patch notes the custom cockpit livery option has been added for the F-14B :thumbup: Looks like we'll now be able to have cockpit mods pass IC :) EDIT: Looks like Japo32 is already on it... https://forums.eagle.ru/showthread.php?t=238582

:cry:

This is why we need native radio functionality in DCS. SRS works well, but inevitably not everyone will have it.

The site is still up. But I'm totally with you - The writer has no more information than us (at least it seems that way). I'd be very happy for it to be the next update though. If it's really a 50% increase, I'd say yes.

While smart smoothing doesn't work as well as it did on the previous versions, somehow I get the impression that overall performance is improved.

Two weeks...

Many games these days tend to have advanced graphics options where you have many more possibilities to tweak settings via sliders. It's possible to tweak some of the DCS lua files to get good improvements in visuals or performance. It would be great to have more official options accessible via the GUI, in order to not break the integrity check. Some suggestions: Shadow quality slider (cockpit shadows are heavily aliased even at high settings right now) Shader quality slider Different (more) types of AA

Hmmm, I was looking for why cockpit shadows are so pixelated, even on high settings, and came across this thread. Strange that they don't just make a setting for it. It would take them 10 minutes max.

This is what I'm thinking too. This behaviour is typical for having multiple input devices and forgetting to clear unused axes on unused devices. ED could solve this by getting rid of the standard axes bindings and keeping them blank by default.

Do you mind posting some screenshots of your DCS controller settings? It seems logically impossible for an axis (your Z axis) to act as a throttle without being assigned as a throttle.

Does smart smoothing even work at all in this latest beta? I don't get the characteristic distortion of the Spitfire gunsight, so this would indicate it's off.

Haha! That's got to be the weirdest one yet :D

They don't really do the same job. I mean, they kind of do, in the sense that both methods mitigate aliasing, but the results are very different. In DCS VR, higher pixel density will give you a clearer image, but you have to go very high in order for the effect to have a significant impact on aliasing. Even maxing it out to 2.5 will not get rid of shimmering and pixelation very well. The performance impact of PD at 2.5 is extreme. That's why most people find a balance between MSAA and PD for optimum image clarity and fewest jaggies.

I think it's interesting that deleting these folders is becoming standard practice and is even being suggested by ED staff as standard practice. For many this seems to have quite a significant impact on performance. Wouldn't it be a good idea to have DCS-updater purge these folders?