Chapa

I totally agree. I tend to play with low settings with my Rift S to play at 80 Hz most of the time (so PD 1, no MSAA, no shadows, only textures at high and Anisotropic x16) But even with these settings, the FPS is just above 40 in the free F16/F18 free flight mission. Need to wait to really enjoy this beautiful and free map So as a last word, Thank you ED for your work and hope to have some fix in a near futur

For sure... And in dark cockpits, cockpit shadows reduce shimmering.

I can confirm the same issue with the Rift S at 1.2 supersampling. It is a general issue and not a case by case issue... I am just starting to learn the Harrier, so not a big deal but hope the issue will be fixed asap

It seems that the last patch has fixed the issue, no more stutters for me at least. I imagine it is related to this fix: Fixed bug in the global Radio that should have led to some improvement of game performance. Thanks you !

Hey, It seems that the last update has fixed the issue. No more stutters when banking left and right in the free flight caucasus instant action. Yay, it makes my day Update : The patch release say Fixed bug in the global Radio that should have led to some improvement of game performance.«

Just answer that you know how to fast erect your ADI and let the urologist google for it

+1

Yes it is. In the past, I have already extensively worked to try to classify this bug. ED seems to have agreed that the issue is more general. Here is the post : https://forums.eagle.ru/showthread.php?t=261940 It would be great if you can look at it. At least, be sure that the marker receiver is really shut down when we disable it in the plane.

What is good with this story and out of EA mistake is that the bug fixes list is really impresive and that it is great to have you on board ELMO. I have better feeling for the future concerning the Razbam modules that I love and without this story nothing would have changed soon. However, as a developer, I have unfortunately no other words than bullshit for the definitions of the « milestones ». I don’t really care to be honest but it sounds not a good idea to play with the definitions on which the business model is based. You have your internal processes but customers have only one: they buy in EA with the trust and knowledge that things will be added and bug will be fixed and one day, the module will be considered and aggreed as released because fundamentaly complete. One week later, people will start to ask new textures, refreshed cockpit etc. because lot of time passed between :) People want to see their favorite modules in the release note. This is the best process to create trust with us and it was the real issue before it was hidden by some not so usefull definition. But it seems things are changing, thanks

I think it would be better to : 1) extract all the bug post titles, post author, date and url and create a google doc with that. 2) sort the table by author and descending date 3) add a rating field : annoying, very annoying, terrifying annoying, missing feature 4) publish the google doc link here (keep a safe copy on your disk also :) 5) ask the authors to put a checkmark on bugs/feature that must be considered and rate them As you'll see, the bugs have been publish for the most part by the most knowledgable people about the Harrier and people not happy with the current state. Then, I would archive the current Bug section and create a clean new one with entries for each bug confirmed in the google doc Other subject and personal opinion that will not be very popular I think : Don't publish a bug tracker ! Customers must only be bound by trust, good communication, bug fixing, fair module description on the website and a working shopping cart to push the trigger. It works very well for some 3rd Parties. If you solve these issues, it will pay for sure. Not an easy start for you but I wish you the best !

Here is the not surprising but annoying news: https://www.theverge.com/platform/amp/2020/9/16/21422717/facebook-oculus-rift-s-discontinued-quest-2-vr-connect

Personally, I don't care about EA because it doesn't really reflect the state of affairs.DCS is in constant evolution and the modules must always to be adapted, fixed, enriched. EA is great to reflect a discount period with promises about features to come and of course the knowledge that some essential features are missing. After this period, as a customer and because we are all customers with different background, knowledge and mostly expectation about the realism of each module, what is important I think could be represented by badges : - Is this plane flying formation/patrol ready ? yes => badge - Is this plane Air to ground ready ? yes but not complete because missing Maverick => silver badge but not gold because not totally finished - Is this plane has a pilot for VR user ? Yes... you got it - Is the avionic complete ? Absolutly stunning, full complete as much as possible : Natops Badge Of course the idea is not to have 150 badges and create a management mess but It would be more transparent and I think also less frustrating and more encouraging for 3rd Parties because evolutions would be visible. People has some good reasons to be angry with Razbam but I don't forget also that their VR pilot is amazing and they do some stuff than no body has (or as good as they did).... There are issues with their communication and bug fixing rate/priorities (from our persective) but they also pay from my point of view, an EA process not so well defined and usefull as it is now.

All Razbam aircrafts are supported by Baltic Dragon training missions and will provide the best user experience. Rudel_chw has done an amazing job by providing training missions for the C-101 and JF-17. You can download them from the user files section in the DCS website The YouTube series done by Wags are also a good way to learn some of the ED aircrafts, i.e F-18

Are you sure that the clip is well fixed with no play at all. The pro support is so cheap and bad engineered...

Already reported here: https://forums.eagle.ru/showthread.php?t=261940 I really hope it will be solved by ED because the Mig-19 is particularly affected by this issue :( It’s effectively the marker receiver the root of the stutters/fps drop Mig-15, L39 are also affected

It would be instant buy.

Even with this method, the issue come back sometimes. But it's faster and a little bit less anoying

In the 2020 DCS manual, there is a Flanker on the cover and the first big picture is an Apache illustrating the Instant Action chapter, curious choice. So, let’s say it will be the Apache

Don’t have enough time to dig deeper enough to provide you valuable advices. I enabled the experimental engine rumble checkbox and if my memory is right, the default was not bad at all when I tested the P51. But it is with the default settings and the I-16 that I really feel the potential of the jetseat. As soon as I have something I like, I’ll share it in the post I created for that. I hope some other people will join

You always feel the effet without the dead zone. Disable the engine rumble to feel it. Applying deadzone allows to define at which G force you’ll start to feel the effect. For example by setting the positive range to 2 and negative to -1 means that the seat will shake only when G force > 2 or < -1. Amazing settings ! I tend to disable the engine rumble effect or at least to drastically reduce its strenght (<= 10) except for the warbirds because the engine tends to hide all other effects, effects giving useful information

Trying to help is never useless. Bashing people that try is. Teaching them how to improve their sharing could pay soon

Same issue with Rift S and water to medium

I don't think that the antialiasing settings have effect in game. AFAIK only FXAA and MFAA works. For MFAA, MSAA must be at least x2 in DCS. But maybe the recent Nvidia drivers update has changed this behavior...

No solution found on my side also. Only the DCS gamma settings have impact... I thought it was possible and that would explain the people playing with a gamma at 1 with their Rift S and me around 1.5, depending the map/time/weather.

Guardian is really annoying. I have also sometimes the issue. I noticed that it is often if I shake or grab suddenly the HMD or if I leave it too much time behind me on my bed. Note that it could be because I tend to let it fall (gently but too abruptly for him) on the bed... Could be a sensor thinking about a fall and reseting Guardian to avoid the next one... I'll make some tests...