TheKardinal

I have seen this too - Grayflag and on a single player TTI mission - it appears to be the laser from JTACs - I don’t know why it is suddenly appearing - but I have never seen it before 2.9 update. I have, like many people turned on DLSS and been messing with a number of settings - feels somewhat likely that this is a result of something in 2.9. I use Pimax crystal i9 with 4090 GPU - open XR render scale at 120% - DLSS on with performance setting - SSS on or off(still seen either way) shadows on high and terrain shadows at default.

Same here. Bonkers amount of extra frames in VR. Am averaging over 60fps now from what was 40fps last week on single threading. Thanks ED.

For me the MT works very well. Reverb G2, 4090RTX, 64GB, i9900k OpenXR. Instant increase from what was 40-45 fps average to about 65-70fps average. It’s only been a day, so probably more to learn but at one point I had 80fps in the harrier over Iran in a liberation mission that I was using the same computer to host as a server for me and a couple of mates. Utterly amazing - whole experience was phenomenal. I hope that that others with issues can resolve them. I see some with similar specs to me can still not see such gains as me. I am lucky, I don’t know why it works so well for me - I have graphics setting that include good levels of detail so, these figures are not achieved because I run DCS on minimums, because I don’t - it looks and ‘feels’ amazing in comparison to single thread. Thank you ED and am sure you will work to optimise MT for those who need to - it has got to be the way ahead. I just wanted to say thanks for this important leap forward.

Oculus Rift S Frame drop Persian Gulf 2.5.6 Just finished a session on Operation Snowfox single player- this mission on User files.. I have experienced frame rates of around 10 FPS when on ground at Khasab and Rays-al-Khaimah These low frame rates linger for a few minutes and then recover. Looked in my log folder but nothing appears for today’s date...am I missing something when it comes to the naming of these files? If I send a track is that any use? My system is i7 8700k at 3.5ghz, Aorus z390 Master-CF motherboard, 32 Gb DDR4 (1066MHz) and a 2080Ti.

What did you change your curves to?

I have used the Harrier a great deal in BlueFlag PvP. It has some issues like the Maverick cool down which was a bit annoying when you have ingressed past a few enemy players and then cannot hit a target as a result. It does not happen all the time though and all things considered I still love it, and the challenge it is to fly - the VSTOL elements of flight cannot be found in other modules (standfast helicopters) which give it some great flexibility in multiplayer games. Having said all of this I do, more generally, feel that early access is a polarising and increasingly outdated strategy for developers to rely on. I understand the idea of it...but there are two things involved that can piss people off. 1. The developers get all of my money on the first day. 2. The developers are not contracted to abide by a date by which the module reaches an agreed completed state. So, I am a bit conflicted....but I suspect the F16 will be the last time I fall for early access.

Thanks, this seems to be working now. Legend. Thanks.

I am failing at step1: I do not normally have trouble updating the open beta...it does not even tell me there is an update due even though I know there is one. Tried a restart..did not work. Have not got to step 2 to refresh my available modules. puzzled.

Using Rift S with few problems with most of the stuff I need to read in the Harrier. Some smaller analogue gauges are a bit tricky. Probably the same in real life to be fair as they are quite small. Some pages on MFDs are harder than others...as someone else has said maybe some brightness and contrast controls on MFDs will help. Of course the other thing that might help is that if you might need corrective lenses in your headset....especially if you happen to need glasses IRL.

Thanks. Good idea

I got the Rift S a couple of days ago and mine has been exhibiting the blackouts quite often. You put the headset on and nothing displays at all. Have been through many fixes and, repairing software and turning off USB power management. When my Rift S decides to stop working....and this happens every time I turn my PC on.....I fix it by doing this. Unplug Rift S USB 3.0 cable and graphics card connector. Wait 20 seconds. Plug Rift S USB 3.0 back into the same USB port. Wait 20 seconds. Plug Rift S graphics connector into graphics card. Rift then works. Frankly, I am very frustrated that I need to do this every time I want to use my Rift S. When it works, yep, it is a pleasant upgrade, but this situation is unsatisfactory and I hope they fix it. Other points are that, thanks to the halo design it does feel a bit warmer to wear for long periods..I have steel series headphones on over the top...it ends up covering a lot of your head which, for me has made it hotter to wear than CV1. Also, the sweet spot of clarity totally eliminates the nose gap. I never realised how much I used the nose gap in CV1 Rift to use my keyboard. Trouble is to see the keyboard I now need to unscrew the halo headband, lift headset and use keyboard. It’s a bit of a faff. Other than that you can, for some simple key presses obviously use your keyboard by ‘feel’.

+1. Utterly amazing. Will be even better when I upgrade my Rift this year. Thanks guys.

I agree that explosion animations are much better than they were in the past. They look pretty good now. I would say, as has been mentioned earlier I think, that I would very much like to see blast radius and fragmentation effect modelled a bit more realistically. Some large bombs on instant fusing seem to have very limited area of effect even close to non armoured targets.

Great stuff

That’s an interesting point..apologies for the misleading term of friendly. In which case this little IFF faff will definitely cause plenty of confusion. I am glad the fix seems to be already in the pipeline from ED. It’s a bit annoying, but it is OB too.