Motomouse

radioactive glow, watches used to look like this in real life too radium power

I also can not stand reprojection. Fluid 60 FPS are much better.

nice benchmark, thanks

How do you change your plane in an instant action mission?

G2 roooocks! Or not! Looking forward to the specs :-)

If you want to reach the supposed 40% intel overclocking advantage you need 4133 memory. Than you have perhaps a 40% advantage at 720P ;-)

Just put in lodAdd 2000 and lod 0.1 and enjoy fluid 90 FPS now. Does not look like digital combat flight simulator anymore, but it is fun for one time.

You dont understand the shadow settings correctly yet. Shadows off, flat, low, medium, high setting controls the quality/type of the shadows. These are applied to your own plane and scenery objects (planes, bunkers, airfield objects ...). The terrain object setting controls if terrain objects (trees, towns, ...) also use shadows. The thread is about restricting the shadows to in cockpit shadows only. This will for example increase VR FPS from 40 to 60 FPS. (Alternative is no shadows at all for 60 FPS.). There is no such cockpit only shadows setting in DCS yet. It would be a nice addition and very welcome.

Sensor of interest selected?

Picture is only rendered once (this is the arduous part). Then it is shown on two devices (this much less arduous even if some scaling is involved).

There are some complains about fps and looks of VR from people with unrealistic expectations or too ambitious settings. Nevertheless I can not remember my VR ever looked close to a potato. I do not even like potatoes. In contrary I enjoy fluid frame rates that provide an amazing experience of speed in low level flight and fabulous immersion during aerial maneuvers. In fact we are blessed to be the first to enjoy this level of simulated flight at our homes. I am grateful for this and I am also looking forward to the future develpment of VR software and hardware. But now is the time to enjoy what we have at our hands ;-)

earpieces are for the bin, cans are for the ears there will always be a setting where you dont reach the 60 FPS and there will always be a setting where you reach the 60 FPS

check if you have an axis assigned to it. (For example the rotary wheels by accident.)

I have solved it, sadly not compatible with multiplayer: Just a change in the cloud.lua file LODdistance = 100000, -- max distance getting from float smCamera_Implement::GetDistance(viFlag mask=viCloud) = 100000 LODdistance = 70000, -- max distance getting from float smCamera_Implement::GetDistance(viFlag mask=viCloud) = 70000 -- original 100000 ED please implement this easy fix. Thank you.

ED has to add it to the official options, else you can not play multiplayer.

If you want more frames per second, one easy way to achieve this, is to turn off the shadows. But many do not like DCS shadowless. If you are ready to loose the world shadows, but love your cockpit shadows, there is a way if you are bold enough to edit your lua config files: In the ... Eagle Dynamics\DCS World OpenBeta\Config\Effects\shadows.lua file I changed the values from {0.02, 2.5, 25.0, 250.0, 1500.0, 7000} to {0.02, 0.5, 0.6, 0.7, 0.8,1 }. This reduces the shadow range drastically and improves performance dramatically :thumbsup: (I choose to modify the shadows high settings for my purpose) { --high 4096, {0.02, 25.0, 100.0, 400.0, 1500.0, 7000}, {0.02, 0.5, 0.6, 0.7, 0.8,1 } -- original: {0.02, 2.5, 25.0, 250.0, 1500.0, 7000} }, With 3600X & 1080Ti & Reverb for example you can have high cockpit shadows and still achieve constant 60 FPS! (Disadvantage: No multiplayer)

When the problem is in the left lense for example: If you look direct at the faulty object or with a slight deviation (about 5 degrees) it is not rendered. If you turn your head in any direction more than this deviation the faulty object is suddenly rendered in both eyes. Perhaps this helps identifying the source for our problem.

You are welcome :-)

You can not have the same settings because the OpenBeta has additional settings and features.

We are talking about users not developers ;-)

+1 Would be very nice in VR to read the JDAM coordinates from the briefings without pause.

You can not have the same settings in OpenBeta ans Stable right now. Perhaps you like to start exploring there.

It is just a rabbit hole if you constantly try to improve image quality in VR and the time spent with this futile activity stops you from actually flying with your headset. I have seen many poor simmers falling down this hole. ;-)

Everybody is free to say all his complaints and problems. I just like to give the little advice: You miss out if you wait for all your expectations to be fullfilled. Sometimes there is more happiness in reach if you lower your expectations a little bit ;-)

Now you can put everything high again step by step and enjoy!