Chapa

Same experience with VR Optician, very happy with the lenses. I added the blue filter. I have large spherical correction 5.25/4.0, so it was more expensive but definitively worth their price.

Small city, simple bug => no need.... ED will find them with a simple query... Don’t hesitate to chase their coordinates if you want. Would be more usefull than chasing posts. As developer I used to solve bug report explained in a mail subject only. ED know well its job and I will provide more proof if they ask and need. In VR, I never checked how to take screenshots

In the UI Layer control setup menu there are 3 nice bindings for VR: - recenter - zoom - spyglass zoom

@Viper You can fix the issue without breaking the IC. Here is how: 1. load a plane 2. change the default view a little bit with rctrl + rshift + numpad keys (2/4/6/8/etc.) 3. save the view with ralt + numpad 0 4. DCS will generate the file snapviews.lua in your save games/dcs/config/views folder 5. this file contains all the default views for all planes, find the JF-17 section and update the 14th view (VR) 6. Enjoy To adjust the view, you don’t have to exit DCS. Exit the mission, adapt view in snapviews.lua, reload the mission. If you don’t find the file, try to change/save a custom view multiple times. try to exit DCS because the file could be generated during closing. I have a doubt and don’t remember. As soon as the file exists, views can be adapted without exiting DCS

There are some flying cranes in Kislovodsk :) Seen from the M-2000C Caucasus free flight mission and reproduced from the mission editor.

You will probably not use the hand controllers but the mouse to hit the switches. For the switch in front of you, the cursor moved with the head tracking and the mouse buttons binds to HOTAS is very efficient and feel relatively natural. For switches on the side, mouse is often better to don’t break your neck. I use this combination with a mouse on my right and a small industrial trackpad with two physical button on my left, glued on the throttle arm support. It helps to reach the switches when I want to keep my hand on the stick. I also use it to enable the mouse cursor to move it with my head. The fact that I need to reach out the trackpad button and remove my hand from the throttle give some nice immersion at low cost

Your description let me think to this thread: https://forums.eagle.ru/showthread.php?t=259662 If my memory is good and not confused, Wicked has also a true IPD that is not possible to reach with most of the HMD on the market and can't have confortable vision with the Reverb for 1mm difference between it's true IPD and setting available. For him, only the Valve Index seems to works well. He could probably give you more info if I am not wrong or try to read his feedbacks in the Valve Index thread as a hint

Playing at 80Hz stable is only possible with low settings and PD. I play with these settings when flying warbirds on MP because chasing an enemy with AWS on induce lot of ghosting effect and the propeller lot of artifacts. In this case, I play in mode 1 but I need sometimes to switch in mode 3 or 4 in scene when stutters appears. Take off/Landing in general... When flying jets, I tend to up the settings and PD so playing at 80Hz becomes more rare, high altitude, over sea etc. Mode 4 or mode 3 are the only choice possible and the mode 4 is only interesting if AWS doesn’t trig on/off to often because the trigger create one stutter each time. In general I fly in mode 3 and will only change to mode 4 if I chase other plane in sky to avoid the ghosting effect. It sounds complicated but it becomes quickly easy to anticipate the mode to use. It’s flexible and easy to do with voice attack. I just say VR mode X and enjoy. On the paper, the mode 2 should be the best with stable 40Hz and AWS off but in practice it creates a lot of ghosting effect and is totally useless in DCS at least...

Yes, same for me... So no more idea why it doesn't work for you.

Yes it’s the CES and they need a nice communication with just enough proved working games and no risk to have bad feedback during this period. They state that Developers won’t need to add VRSS support. So it should be possible to test it soon with every games. It will be a nice technology for sure, I even think it could definitively put all the RTX GPU ahead the 1080ti

look at if your numlock and/or scrLock key are activated. I remember having issue with shortcut not working with my bluetooth surface keyboard because not always activated by default. or if the shortcuts are not bind to plane functionalities

Yes I use these shortcuts. In fact, it’s because they exist I stopped using OTT. I am playing only DCS so no need to manage multiple VR profiles

I use the game shortcuts to change the AWS mode on a daily basis. I even made voice attack commands for that and it works perfectly. I don't use Oculus Tray Tool or other launcher tools. Except enabling the ScrLk key on your keyboard to enable the Numpad, checking the app managing your keyboard if you use gamer keyboard and try a DCS repair, I don't see any reason why it doesn't work for you. Just to be sure, the shortcuts are done with the Right Control key

Nice to see some investment in VR but I ask myself why only Turing GPU ? I have the feeling that these kind of features like it is the case for ray tracing, will become the arguments to sell new generation of GPU because it becomes hard to improve performances without crazy Watts and GPU size requirements. Concerning the list of supported games, it’s look bullshit because customers are able to test their games by themself... Love the NVidia stuff but they give me the same bad feeling than a lot of GAFA that seems ti think that they always know better than their customers (i.e. the stupid forced update of our oculus, Apple bad design choices etc... :)

DCS is not in the GeForce Experience list but it is in the list of Nvidia Control Panel/Nvidia inspector profile list: The profile name is : Digital Combat Simulator: Black Shark With some default settings applied and different than the global default profile

No, it has only effect in the Oculus app.

IPD settings in DCS should be called world scale. In summary, set your inter-pupillary distance in the Rift S app. In DCS, set the Force IPD settings the way the scale seems right for you. Stick size is generally a good way, pilot hand size when there is a pilot. To mesure your inter pupillary distance, there is an iOS app (probably android also) that works very well. The App name is EyeMeasure. 0.1 mm difference with the IPD mesured by optician for me Note that the IPD settings in DCS should be adjusted each time you fly a different plane

I found that: https://forums.eagle.ru/showthread.php?t=255963 It could be related. I don’t have this plane so can’t help you more. To compare things, build a mission and fly the same path with different planes to be sure and to be able to maybe isolate the issue.

You have a nice workaround so it’s ok but I think that the issue could be solved by some bios settings because it seems related to startup sequence. For example, it’s not rare that the PCIe x4 port bandwidth is shared with something else (SATA port or front panel usb port). Other idea is to verify in the device manager that the power management settings is not enabled at the PCIe USB ports level. Note that I find stupid that the oculus services are started by default at startup. I like your workaround that looks like s better design overall and avoid battery drain also

@Jopasaps Please don’t answer without knowing you have given new opportunity to Viper to express his frustration. Unsolvable bug... @moderator Close the thread ? :)

I am more curious to try if the same command but for 60Hz works. It would give 3/4 real frames and maybe less ghosting

Same, no problem with the latest

The new cockpit is gorgeous! I agree about the lightning issue, it’s really annoying. I am starting the basic qualification campaign and even with lights on, I see nothing in VR, too dark. Concerning the view, I did a snapview and it seems to do the job for the moment. The issues will be solved, no need to worry and be so rude...

I understand your workaround with the Hub turned on after... not a good idea even if it can work. Just don’t be surprised if you have stutters because the bandwidth sharing. Note that depending the motherboard and electronic quality, the issue can stay the same... Exemple with my Rog Strix z370 egaming: 1 controller is ASMEDIA, so it created stutter and was not able to handle the Rift alone. 1 controller for USB 2.0 so not able 1 controller USB 3.0 that could in theory handle it BUT... I discovered that the bandwidth was in fact shared with the bluetooth and because my keyboard is bluetooth, I had sometimes the issue.... Using other USB 2 keyboard, no more issue... Because I was not able to free the USB to keep the controller for the Rift, I bought a PCIe card. Hope your hub will solve your issue.

Your connection problem don’t come from Oculus but the way you have connected it. The Rifts S needs a dedicated USB 3.0 controller, the full bandwidth it provides. Your motherboard has probably 2 or 3 USB controllers. The USB 3.0 ports are linked to the controllers but there are always more than one USB port per controller, so the bandwidth is shared, so the issue... There are two ways to solve the issue: 1) you are able to free some USB ports to isolate one controller and plug your Rift on it. Your motherboard manual can give some hint. The device manager allows to display the devices list by connection and really see to which USB controller things are connected 2) Buying an external USB 3.1 gen1 PCIe card. It must have a dedicated alimentation (not directly from the PCIe port) and you must buy a card with controller not from ASMedia, so avoid all cards with USB 3.1 gen2 and USB-C port because the controller is most of the time ASMedia one. This one has solved the same issue for me: https://www.exsys.ch/de/pcie-karten/usb-3.0/standard/pcie-usb-3.0-karte-2-ports-renesas.html (if you go this way, there is a jumper on the card to move to give it power from you alimentation. According to your alim, it is possible that you will need a Molex to SATA adapter) For sure, VR is not really plug and play and requires good understanding about the settings and tuning depending your needs in DCS. But as you said, when tested difficult to come back on monitor