Chapa

My opinion is that Virpil should consider a WarBRD throttle inspired from the current CM2 version and keep the CM2 name for a model keeping the strenght of the V2 model (with the lock button between the left/right throttles to avoid the software issue without it) Love my Virpil stuff anyway.

The thread you read was about blackshark 1. Blackshark 2 is compatible, I bought it last sales and use it with Rift S. Concerning your question, all plane are ok in VR. The Mig21 have issue if you look outside the cockpit (the outside of the plane is not modelized in VR) but the cockpit itself and module overall is awesome. As far as I know, all modules works in VR, I just miss three of them

From my test, the registry tweak has no impact at all. It even doesn’t change the fullscreen mode. But there is an impact with ALT+ENTER and it is visible in VR also with the Oculus HUD Render App Graph. For exemple, before alt enter, the FPS oscillate between 70 and 72.5. After alt enter, it is clearly more stable at 72.5 with drop at 70 clearly more spaced in time. UPDATE: With Rift S, pressing ALT+ENTER to have the mirroring view full screen improve the FPS, it can jump to the +2.5 FPS up range or simply stabilize. No registry and shortcut tweak required... Can avoid some AWS trigger so not so bad and cost nothing to press ALT TAB after launching DCS

I tooks time to do serious testing by following some repeatable protocol to compare FPS. First, the context: Windows 10 Pro 64 bits 1909 (up to date) Nvidia driver 441.66 (up to date) DCS Open Beta (up to date) Monitor 5120x1440 DCS settings: High Quality Preset DCS Custom settings: - Civ. Traffic = OFF (to avoid some imprevisible event) - Full Screen checked NVidia Control Panel: As default, no custom settings NVidia Profile Inspector: As default, no custom settings All test are done here: Plane: TF-51 Map: Caucasus Instant Action: Cold Start in Krymsk Move/View: No move, Cockpit view exactly as the mission is loaded Measure time: After 10s and before 60s because at 66s there are some event that change the FPS, so mesures can't be done and would be irrelevant Goal: Impact on FPS only. Loading time, TrackIR smoothness are not measured at all Settings compared: 1) Game Mode ON/OFF 2) Checking the "Disable Fullscreen Optimization" for All Users checkbox for the DCS.exe & DCS_Updater.exe shortcuts 3) Applying the Registry Tweak proposed in the first post in this thread Summary of the results (Remember Windows 1909): 1) No gain in FPS to disabling Fullscreen Optimization from the shortcuts and/or applying the proposed Registry Tweak 2) The only way to see Excusive full screen in action is by checking "Disable Fullscreen Optimization" from the shortcut. The registry tweak alone don't do it... 3) There is a small gain in FPS by doing this steps: - Launch DCS but with another windows already open (Not Chrome!!! but an empty txt file for example) - Launch your mission - Press ALT+TAB to swtich App and go back to DCS - Press ALT+ENTER Here are the tests, actions and results, I have obtained: Test initialization: - Set DCS graphic settings as describe in the context part - Exit DCS - Drop the fxo and metashaders folders in Saved Games - Launch DCS and the TF51 mission - (DCS recompile all the shaders, long loading) - Exit DCS - Prepare settings for the first test - Restart the computer TEST 1: No Registry tweak | DCS shortcuts with checbox not checked | Game Mode OFF FPS at launch: 83/84 FPS after ALT+TAB: 82/83 FPS after ALT+ENTER: 84/85 => Improvment being in fullscreen and after ALT+ENTER ------------------------------------ - Change Game Mode to ON - Restart computer ------------------------------------ TEST 2: No Registry tweak | DCS shortcuts with checbox not checked | Game Mode ON FPS at launch: 83/84 FPS after ALT+TAB: 82/83 FPS after ALT+ENTER: 83/84 => Improvment being in fullscreen and after ALT+ENTER => With Game Mode ON, the FPS tends to be more often on the lower value (-0.5 FPS) ------------------------------------ - Change Game Mode back to OFF (seems a little bit better without) - Check "Disable Full Screen Optimization for all users" checkbox for DCS.exe & DCS_Updater.exe shortcuts - Restart computer ------------------------------------ TEST 3: No Registry tweak | DCS shortcuts with chekcbox checked | Game Mode OFF 84/85 - At launch 82/83 - After ALT+TAB 84/85 - After ALT + ENTER => After ALT+Enter, the FPS tends to be more often on the upper value (+0.5 FPS) ------------------------------------ - Tweak the Registry as proposed - Restart computer ------------------------------------ TEST 4: Registry tweak | DCS shortcuts with chekcbox checked | Game Mode OFF 83/84 - At launch 81/82 - After ALT+TAB 84/85 - After ALT + ENTER => No change with Registry Tweak => The exclusive fullscreen mode is enabled. There is a delay with black scren when pressing ALT+TAB ------------------------------------------------------------------------ - Uncheck shortcuts: Disable fullscreen optimization checkbox - Restart the computer ----------------------------------------------------------------------- TEST 5: Registry tweak | DCS shortcuts with chekcbox not checked | Game Mode OFF 83/84 - At launch 82/83 - After ALT+TAB 84/85 - After ALT + ENTER => The exclusive fullscreen mode isn't activated by having only the registy tweak in place Probably nothing new here because I remember someone saying that he observed small increase in FPS by the ALT+TAB & ALT+ENTER sequence. Personnaly, I will apply the registry tweak and shortuct settings because less software layer between the gpu and the game can only be better and I suspect that the real win could be related to tracking (VR, TrackIR): less layer => less latency Sorry for the long post but I did the job for me, so why not sharing it.

Disabling Fullscreen optimization can be done without tweaking the registry. 1) Go to C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin 2) Right click on the DCS.exe file 3) Go to properties 4) Compatibility Tab 5) Click button: Change parameters for all users (I have french windows so the button could have different name) 6) Check Disable fullscreen optimization In DCS, check Fullscreen settings. ALT+Tab behaviour exit the fullscreen mode (if other window open before launching DCS). You have to press ALT+Enter to go back to exclusive fullscreen mode. These two links can interest you: https://community.amd.com/thread/226321 https://skymirrh.github.io/CompatibilityManager/ I try in VR but can't tell if it really improve performances (need to monitor with Oculus Huds) but it is not worse. I tend to think that it would be surprising that DCS can profit from the new Windows 10 fullscreen mode. So, if not worse, can only be better...

Windows 10 1909 here but this key is missing: GameDVR_FSEBehaviour, however all other exist. Something has probably changed between 1903 and 1909.

Interesting first feedback, thanks you. I read that hand tracking is available on Quest because it can use headroom from a Qualcom chip to do it without impacting FPS. However, it would not be possible with the Rift S because it don’t have this chip and no other way without impacting rendering. But I think as you, the Quest will become the flagship. The next iteration will just be better than both and keep the technologies initiated by the Quest

@flameoutme: you kick my butt to push the trigger. Was not easy to find reseller in Europe with price not to far from the US prices but job done. Have to wait now :)

There is probably a market with DCS but they should provide more serious youtube video. One of them being in a non clickable cockpit and the other one how to fly without a joystick are at least not well designed to appeal the people here and even the craziest beta testers :) Let me think that we are not really their target market but who know, maybe good news soon

You're welcome! I have the feeling that there are sometime bug that don't trigger new settings... (anistropic filter is sometimes capricious... and need restart... sometimes not) I took the habit now to quit/restart for every change and when I change textures settings, I also delete the fxo and metashaders2 subfolders in Saved Games\DCS folder. I lost too much time during tuning, thinking everything was ok to discover at the next startup that something was wrong again...

MSAAx2 and MSAAx4 makes a difference but more than 80% of the effect is done by MSAAx2. In non VR mode, it was not needed to quit/restart DCS but I found it necessary to do it in VR. I had the same issue than you at the beginning... Instead of MSAAx4, you can set MSAAx2 in game and in nvidia control pannel or nvinspector set: - Antialiasing-Mode: Enhance the application setting - Antialiasing-Setting: 2x [2x Multisampling] (2x displayed in control pannel) - Enable Maxwell sample interleaving (MFAA): On (Multi-Frame Sampled AA (MFAA) in control pannel) It has the same effect as MSAAx4 but at the cost of MSAAx2 in performances (near). An easy way to compare the settings is to launch the F18 free flight caucasus instant mission, F4 view and look at the sidewinder.

Have you quit/restart DCS ?

The only update info I found concerns the Rift Quest and the introduction of hand tracking: https://developer.oculus.com/blog/hand-tracking-sdk-for-oculus-quest-available/ It's maybe related... the Quest can be connected to PC

Ghosting effect is caused by AWS and/or not be able to maintain stable 80Hz. - AWS off, 80Hz stable: no ghosting - AWS off, 80Hz not stable (ex: 67fps): stuttering, ghosting, big mess - AWS on, no ghosting as soon as the movement can be reasonably linearly interpolated. Probably not an issue for A2G with modern jet and A2A missile fight But chasing a warbird with AWS on is near as mess as with AWS off and FPS < 80. But to have AWS off and 80Hz, no ghosting and no artifacts, you have to sacrifice a lot of nice graphical settings and there is always situation where you will have to activate AWS in game. There are shortcuts for that

I was also surprised the first time in the cockpit and I had the same feeling than in the MB339. VR is not the best way to judge textures, for sure. By looking more in detail, textures looks great overall and are not basic textures. However, the cockpit feel like if it was difficult to know in which material are things with a tendency to look like hard plastics, not interacting with lights as it should giving a flat appearence. Hard to describe... at the end not bad at all but something missing to really enjoyed

Disable all shadows, it should be better. If it solves your issue and you feel bad about the workaround, me too... In the wish list forum, I suggested to have dedicated settings for cockpit shadows and vehicules shadows. Here if you wish add a +1: https://forums.eagle.ru/showthread.php?t=256084

It’s artifacts caused by AWS, the technology allowing you to play at 40Hz and have smooth experience with good graphics overall. Disabling AWS is possible but you will have to put most of the graphical settings at low levels to keep the 80Hz most of the time. Read this forum and threads about Rift S to learn more about AWS and the settings at your disposal. But first, enjoy your Rift, fly with the smooth experience you already have. When you will have more feeling about AWS, you could choice if its ok for you because you accept the artifacts or if you will have to tune and break your mind to try to play at 80Hz. Most people play with AWS because it’s really hard to keep the 80Hz and have DCS clearly less beautiful as it could be. And it will depends also your specs

Using Voice Attack, I have bind vocal commands to change mode during the flight: VR Mode 1:RCTRL + Num Pad 1 (80 Hz AWS off) VR Mode 2:RCTRL + Num Pad 2 (45 Hz AWS off) (useless but...) VR Mode 3:RCTRL + Num Pad 3 (45 Hz AWS forced ON) VR Mode 4:RCTRL + Num Pad 4 (Auto) I tend to play in mode 1 but switch to mode 4 when it will be clear that AWS could be required. And mode 3 if it is even more clear that more than 40Hz is impossible and want to avoid potential switch between 40/80Hz and the stutter. Seems complicated but it becomes quickly a reflex. Note that I set the commands to answer OK as a feedback to be sure. Same for enabling/disabling the labels on MP servers for better identification. No need to have a Voice Attack Licence for that. The free version can do the job

Cool, hope it works well for you too. On my side, no issues since I have installed it.

Which USB PCIe card did you buy, finally ?

Love the sounds too, very good job ! Thank you !

In Oculus Debug Tool > Layer Properties > Layer 0 > Head Locked : Force True I don't know if it can be used to easely define the snapviews but the fact is that DCS don't follow anymore the head movement. DCS is fixed and when you move your head, it is like if your were looking in a keyhole. You have to adjust your head position to see the DCS screen According to your need, it's definitively not a user friendly setting to use

yes, and in this case, the hud projection start to be little too big and fill completly the HUD glass. As the A10C but in a less extend fortunatly

yes the bind to save the custom view (snapview) is RALT + Numpad 0. In VR the saved snapview is often a mess. With TrackIR, tracking must be disabled, you define the view, save it and reactivate the tracking. In VR it's not possible to disable the tracking... The only workaround I have found is to save the snapview, and then editing manually the snapview.lua file generated in saved_games/dcs/config/view folder. If needed, the default view settings can be recovered by looking at the views.lua file in the DCS installation folder: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\JF-17 Here is the default VR view: [14] = {--default view - VR viewAngle = 114.165154,--FOV hAngle = 0.000000, vAngle = -9.363433, x_trans = 0.127094, y_trans = 0.015877, z_trans = -0.003428, rollAngle = 0.000000, }, I tend to think that putting x_trans = 0 is better because the seat/stick positions relative to the pilot and its easier to see the front lights and center MFCD top buttons and screen. Of course there are workaround to solve this small issue but Deka as probably go inside a true JF-17 and if they can translate their experience/knowledge to the VR default view, it would be very nice. If it is already as it should be, it is a perfect answer for me and I will keep their settings :)

By following the clean/repair process from the link above, I am not able to reproduce crashes that tend to be easy to reproduce yersteday. Seems to have solve the issue I looked at the _backup folder corresponding to the cleanup and repare processes and it contains only lua files used by VAICOM PRO and its extensions. It's not a proof that was the cause but it would not be surprising. VR users tend to use Vaicom Pro, the JF17 beeing fresh new, temporary incompatibilty could be an answer... I encourage you to try the cleanup and the repair process, dont'relaunch Voice Attack before trying DCS and look at if crashes occur again.