Chapa

Visual Studio Code is a good one Notepad++ do the job

It’s announced as known bug in the 2.5.6 release notes. Should be fixed soon, imo

Do you have disabled the new SSLR graphic settings ? With it ON, it is stutter fest with my Rift S but without everything seems ok

The pilot is just amazing. Thanks !

The avionic must be enabled and it seems that you need to be in range of a beacon to experience the stutters. There are a lot of beacon in the Caucasus map and very few in other Maps in the kHZ range. In other plane, you can disable the avionic and shutdown the stutters but in the mig-19, even if you turn off the switch, it doesn’t really disable it and the stutters remains. The gauges stops indicating the bearing however.

Hi DST, This issue is in fact not a Mig-19 issue but impact other aircraft like the L39 and Mig15. I submited another bug report to ED and it has been reproduced and reported to the dev team. We have to wait now but it will solve these stutters. Here is the link to the full story: https://forums.eagle.ru/showthread.php?t=261940 @Moderator/Razbam This thread can be closed

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...

Thanks for your answer. The stutter issue appears to be related to the Marker Beacon Receiver and/or Radio Altimeter. As I said, I am able to reproduce the stutter issue with the L-39C. In the L-39C, if I disable the MRP-RV (Marker Beacon Receiver and Radio Altimeter) Switch, the stutter immediatly disappears, when I enable it, they come back. Of course, I tried to disable these systems in the Mig-19, turning off most of circuit breakers but it doesn't solve the stutters. My opinion is that these circuit breakers shut down the gauge display but don't really stop the underlying processes that compute the altitude/beacon bearing... I am pretty sure that the Mig-19 is suffering the same issue because using shared API with the L-39C or something like that 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. There is behind the scene a process that interrupts the rendering pipeline. My i8700 CPU could be the limitation factor by beeing not enough powerfull to hide the underlying problem but not the 1080ti. I need to invest more about it but if you could confirm/reject my supposition regarding the fact the disabling the avionics system don't really stop the underlying process/APIs calls, it could help. 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... P.S I use the Open Beta version (up to date) P.S. The mission to analyze the issue in the same condition than me is available here: https://forums.eagle.ru/showthread.php?t=261940 (first post in attachment)

By observing that the issue occurs mainly in the mountain near Tbilisi and less in other map than Caucasus, I found that the issue seems to impact other russian planes in the same region. The effect are clearly stronger with the Mig-19 and in general, the VR performance seems worse with this plane but however, it is probably related to something else. For the people interested to check the issue with other planes, I submit a new bug report here with a mission to reproduce it with the Mig-15, L39, Mig-19: https://forums.eagle.ru/showthread.php?t=261940 This bug report can probably be closed...

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

If someone has the Mig-19 and fly it in VR, with Rift S even better, I would be really grateful and happy to hear some feedback about your flying experience in the Caucasus free flight mission :) I did more test tonight and to be sure, I put every graphical setting to low, the lowest possible, Pixel density at 1.0 and tested many planes:, all working at 80Hz stable (F-18, F-16, P-51D, Mirage 2000, Harrier) Even with everything at low, with the Mig-19, the issue is the same: the FPS isn't 80Hz stable, it oscillate between 70-80Hz, AWS doesn't trig and forcing AWS ON don't remove the stutters... I try the Oculus beta drivers but it don't solve the issue. I try to change the Mig-19 special settings (Radar Static, check/uncheck other checkboxes) without success... I try to turn off the avionic systems but same issue... This plane is lovely and seems to have interesting flight model and give the feeling to fly a machine like the Viggen and Mig-21 but it appears to be totally broken in VR, at least with the Rift S.... Hope to read some feedbacks and be the stupid guy in the story :doh:

I just bought the Mig-19 and immediatly noticed bad performance in VR (Rift S), stutters, big stutters !!!. I have all the planes except the Gazelle, everything works fine with all other planes/heli. So, I am confident that it's not related to too high graphical settings. However, I try to disable some of them, to be sure that the bug is not related to the presence of shadows for example, or lens effect... No, it works as bad with or without them :) I noticed that the Mig-19 is the only plane that seem to broke AWS. The behaviour isn't the same. With all planes, the behaviour is as follow: The FPS is 80Hz if it's possilbe or if the charge is too high, it immediatly fall down to 40Hz. No value in between or during a fraction of second. The Mig-19 has a different behaviour: The FPS is 80Hz if possible but it will not fall down to 40Hz as quickly as it should when the charge is too high. The FPS can oscillate between 60+ and 80Hz during long period of time as if something avoid AWS to trig. Forcing AWS ON don't fix the issue. The FPS appears to be 40Hz stable as it should but the big stutters remains.... No plane has this behaviour.... Maybe related or not, I also noticed that the radio compas oscillate quickly with large amplitude without stopping in the Caucasus free flight mission. I have the feeling that there are high frequency interruption somewere. I have of course try to repair, drop shaders, no mod, I have also restarted the computer and also compare during the same session with other planes, all working perfectly.

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.