Chapa

I am not a sound specialist, nor Mig-21 one but I love your sound mod. I just watched the video but I will try it when I come back from holidays. The Mig-21 is even more badass with this mod! Good job, thank you to share it

AWACS + Tanker to go in pair with all the new technologies added/planed to the game: dynamic campaign, integrated audio, new ATC, etc. The combined arms module for the air: Air Tactical Support Module

Here is a track. The stutters are presents at the start of the mission because the siwtch is enable. Near the end of the track, I stop to bank few seconds, disable the switch and bank again but without stutters. UPDATE: I tried to create a movie with my iphone from one of the lens but it's not visible... too bad quality, unstable and hard to be on the optical path... I checked if it is only visibile in stereoscopic vision by closing one eye in the HMD. Each eye see stutters. UPDATE 2: I said that I was able to reproduce these stutters with most of the russian planes. The Mig-15 suffers the same issue and it appears that it's even more interesting with this beauty because it has separate switches for the radio altimeter and beacon navigation. I can switch ON/OFF the stutters by turnig ON/OFF the ARC switch this time. Turning ON/OFF the radio altimeter switch change nothing. It tends to confirms my feeling about an issue related to the kHz beacons I will try to reproduce the issue in other map near one of the rarer kHz beacon. One player says that he has issue with the Mig-19 in Caucasus map but not in the others. We will see. Note that I share the exactly same CPU with this player: i7 8700 (non k version) Thank you for the time you give me L39_stutters.trk

Hi Bignewy, Thanks you for your help. You'll find in attachment the log and dxdiag files. The log correspond to a very short session: - Load DCS - Load the mission in attachment in the first post with the L-39 - Bank left/right with the MRP-RV Switch enabled => stutter - Bank left/right with the MRP-RV Switch disabled => no stutter - Bank left/right with the MRP-RV Switch enabled => stutter again - Exit DCS Hope it will help. Best regards, Chapa dcs_log.txt DxDiag.txt

McDonnell Douglas T-45 Goshawk

Lovely news, you rock

@Bignewy Hi Bignewy, Do you have some other idea about this issue, please ? I did some monitoring in VR with the provided mission and L-39C to analyze the CPU/GPU usages. It appears that with AWS Off, FPS 80Hz, the usage are: CPU: about 26% stable GPU: about 70% stable It means that the CPU/GPU achieve easely the 80Hz with the defined graphical settings. However, the stutters are present and when I disable the MRP-RV they disapears. When enabled, the FPS is 80Hz but fall down to 73 for a fraction of second and come back to 80 and falldown soon after to 73 again etc... With the switch disabled, the FPS is 80Hz perfectly stable. Switching ON/OFF has no impact on the CPU/GPU usage. I don't see any change in the graphs of the 6 CPUs/ 12 Threads nor the GPU graph... VR Headset (at least the Rift S) don't like when the FPS isn't 80Hz or 40Hz, all FPS in between create stutters. Something behind the MRP-RV switch create a FPS drop with a duration shorter than the time constant allowing AWS to trig. If AWS is forced, it avoid the proper creation of the interpolated frame... It's my supposition... Very short job computed on the main loop ? Thanks in advance for your help, Best regards, Chapa

I can understand your skepticism and the reason behind it, even fair given the facts and waiting bugs. But you are trapped in an infinite loop of deception, complaint and it appears non sense... To start, you have a backlog (work planned for more than one year for sure): - Mig 23 - F 15 - Bronco - Super Tucano - Bo 105 - Finishing current modules And we have also some priorities and rough dates announced (start too look as a developer roadmap): 1) 2020 finishing the mirage, harrier and mig 19 2) Probably one new plane among the list in 2020 but I don’t remember the year clearly written as a promise somewhere, nor which plane Your skepticism induced by a lack of confidence is fair but is also YOURS. The fact that you have hard time to live with the uncertainty of the order in which planes will be released is also YOURS. Don’t merge the facts with your own hopes and fears... My guess is that the Bo-105 will take precedence over the F15 and to be honest I hope it will be the case. I love Razbam and the fact they give us non US planes (or at least not exclusively US). However, I am like you and I also wait that the current modules are at least fixed and I also find the delay too long, I would prefer less hype news and more basic bug fixes like the missing bindings for the Mig19 and I will also ask myself the question if I will buy the next modules if the current state don’t change.... No reason to be anxious... At the end, you will buy the next modules or not... And this choice will be driven by how Razbam manage the whole things... If they have already lost you, you should not be anymore in this part of the forum and add negative noise. In the contrary case, the facts are well known, your opinion, hopes and fears have been heard and you are for sure not alone and they know about it for sure... @Razbam I am really happy by the Bo news and the idea to have a german helicopter ! Sooner will be better than later in your backlog :) But guys... don’t replicate the Gazelle story, please fix asap the basic bugs. It is as important, even more, than the amazing VR pilot, new mirage cockpit etc.

Hi Bignewy, Thanks for your answer and suggestion. Unfortunatly, adding this instruction, confirmed by the log, doesn't solve the issue. I reinstall all my system from scratch, erase everything, clean install, the minimum required to play DCS in VR: - Windows 10 64 bits 1909 (up to date) - Nvidia 441.87 drivers (up to date) - NVidia Control Panel all with default settings - Oculus 12.0.0.306.268 (the beta version doesn't solve the issue) - Virpil software and firmware (up-to-date) - No other softwares running like Voice Attack, Chrome, etc... - No mod installed, never installed - USB ports used only by joystick, throttle, rudders - Rift S connected on its dedicated PCIe USB card, powered directly by the alimentation (no issue at startup) Overall, my rig works like a charm and I am the kind of VR happy player with never an issue concerning performances, hardware etc... I am quiet confident that there are no easy settings (BIOS/DCS graphical settings/NVidia) that could solve the issue. However, I also try the following settings but without success: - Disable Hyperthreading in the BIOS - Increase the VR pre-rendered frames in NVidia Control Pannel - Enabling/Disabling Windows Game Mode, Full Screen Compatibility mode With my setup, I can easy reproduce the issue with the mission provided in the first post, with the L-39C. - Launch the mission with L-39C - Bank left and right by looking the terrain as a pendulum - Even with 80Hz (AWS OFF) or 40Hz (AWS ON) stable, there are big stutters like if the true FPS was 10 - Turn off the MRP-RV (Marker Beacon Receiver and Radio Altimeter) Switch, the stutters disappears and everything is smooth - Turn it on and the stutters come back In 2D, the FPS instability is also visible from the FPS counter but because the FPS is so high, it's not noticible from a gameplay perspective. The fact that I can turn on/off the stutters by enabling/disabling some L-39 avionics tends to proove that some process behind the scene create the stutters, or at least push my CPU (probably) outside its allowed flying envelope :) Note that I discovered this issue and workaround because I just bought the Mig-19 and notice these stutters from its Caucasus free flight mission. By investigating in the forum, some people says that the Mig-19 bad VR performances was visibile only on the Caucasus map and it appears to be relatively true for me also... I deduced from there, that RSBN, kHz beacon, specific stuff for russian planes was specific to the Caucasus map and without surprise, I reproduced the issue with most of the old russian planes. The L-39 is good because I can disable the stutters but I really think that there something serious behind the scene. Hope you will be able to reproduce the issue. If there are some metrics, measures, monitoring, debug tool to install and insight I could provide, don't hesitate to ask, I have time and would be happy to help. Best regards, Chapa

@moderator: I miss to publish this thread in the bug report section... could you please move it there :doh:, or other part of the forum because it's probably not related to the Caucasus map, indirectly maybe... Concerning the L-39C, the issue is clearly related to the avionics system behind the MRP-RV (Marker Beacon Receiver and Radio Altimeter) Switch, the stutter immediatly disappears when I turn it off, and reappears when turned on. Turning of these systems in the Mig-19 doesn't solve the stutters. However, I tend to think that in the Mig-19, only the refreshing of the gauges is turned off but not the underlying processes/API calls. It's important to note that, all my graphical settings are at the lowest possible values, the FPS is 80Hz stable with my Rift S, nvidia drivers up to date. My i8700 CPU could be the limitation factor by beeing not enough powerfull to hide the underlying problem. The fact that the issue seems to occurs only in the Caucasus map let me think that it's more related to the beacons in the kHz range, less present in the other maps...

I though it was a specific Mig-19 issue but it appears that this bug affect most of the russian planes. I observed this bug in VR with a Rift S. I don't know if it occurs also in 2D. The bug is reproducible with the mission provided in attachement. Flying in the mountains near tbilisi create stutters, specially strong with the Mig-19 but clearly visible with the following planes: - Mig-15 - L-39C - Mig-19 But the same spot, don't affect the F-86, F-18, M2000 It's probably caused by something specific to russian planes: ARK ? In VR, even with every graphical settings at low, 80Hz stable or 40Hz stable, the stutters occurs. The Mig-19 shows the strongest effect. The issue seems to avoid AWS to trig (with higher enough graphical settings). The Mig-19 has maybe other issues on top of this one... Concerning the context: - saved games folder recreated by renaming the older one - metashaders/fxo dropped - clean/repair done - uninstall/reinstall the Mig-19 module - Occulus Rift S current driver and beta drivers tested I hope you will be able to reproduce this bug :) Best regards, Chapa bug_caucasus_VR_stutters.miz

No wish to sell VKB at all but saying that they shall be combined with a Russian grip with the brake lever is not true. For sure, it would be better and more realistic but a simple button works well. I use a TM F18 stick and bind the VKB rudder brake modifier on my throttle. I also use Virpil stuff and find these pedals a good match regarding their quality/precision without breaking the wallet. IMO, in the budget, can’t go wrong with CH or VKB

I also noticed more than 9 GB of VRAM used. Same feeling than you.

I am happy with the VKB, much much better than my previous TM TFRP. Loosing the toe brakes was also a concern but I decided to push the trigger and I don’t regret it. In fact you can bind a modifier key and when depressed, your rudder will works as differential brakes (like Mig). In fact, with this binding all the plane can be taxiing has if they had differential brakes instead of toe brakes. No totally realistic but it works well and the VKB are top quality, a pleasure to use when flying. However, I can’t answer your precise questions, no experience with the Saitek/Logitech or mix setup

@Gman109 Unfortunatly, I can't really answer your questions because it's my first VR lenses. In theory, the blue filter has the effect to change the color balance with more yellow. Having glasses with blue filter, I am already accustomed, so can't give feeling about it.

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