Patch discussion September 2024

[sleighzy]

52 minutes ago, Delta-canard said:

Does it still work with the non-omnicept G2?

It happens in a layer before it even reaches your OpenXR runtime or headset, so yes this should work for that.

[draconus]

9 hours ago, Boosterdog said:

I think you may be getting your bits and bytes mixed up.  The DCS updater shows speed in MB/s (megabytes/second). Your download speed is shown in Mbps (Megabits/second). There's 8 bits in a byte. So what you are seeing (9.8 MB/s) is about right.  

I already asked about it and he confirmed the speed but his calculation still stinks - he cannot download whole DCS (over 100GB) in 5 hours with 1.2MB/s speed

Edited October 10, 2024 by draconus

[Pillowcat]

Weirdo bug with dancing and disappearing static kiowa saw today in multiplayer

 

Spoiler

 

[westr]

On 10/8/2024 at 11:56 PM, 5ephir0th said:

I dont know hoy you guys got a big gain on quadviews, maybe i get a lower gpu frametime but the increase in cpu one is insane

I don’t get any gain from it. 

On 10/8/2024 at 10:27 PM, Delta-canard said:

I may have missed some obvious things as I was away from the sim and my computer for most of the summer but I still feel my performance took a hit, I have more stutters and certainly no major progress in fps, it is about 60 if everything is fine, more like 40 with spikes in m/s per frame and stutters in more challenging moments. Not sure how to alter my settings in order to get some benefit from the new patch. Also, it seems the loss of the OpenXR Toolkit does bring a hit (I've been using fixed foveated rendering). I'm running a 5800X (not 3D), a 6900XT and a Reverb G2.

I saw no gain after the update. Loaded a few flights this morning and had terrible performance I need to do a repair build and try again I think. But don’t think everyone has seen a VR gain. 

[Gunfreak]

1 hour ago, westr said:

I don’t get any gain from it. 

I saw no gain after the update. Loaded a few flights this morning and had terrible performance I need to do a repair build and try again I think. But don’t think everyone has seen a VR gain. 

I saw i drop. Last week i flew the F4 on Kola had good preformance even with 200 units.  After the update. The preformance was so bad the vr screen actually lagged(when you see black bars when you move your head side to side. This happened in the F16 and Viggen. So not an F4 thing.

I then tested the A-10C on Caucasus with just 5 ground units and i had equally bad preformance as in Kola. So not a Kola problem either. But seems to be universal across aircraft and maps.

I've tried fildeling with Quadview settings. And there is a clear preformance drop. So much so I had to check my ram, and CPU hadn't done something odd. I have 64gig  ddr5 ram, i7 13700k at 5.2hz cpu and 3090 with 24gig of vram. So if terrain optimisation related to vram and ram. I should have noticed it.

[T24_Martin]

Maybe this...

Quad Views (Pimax version) stops working after a while

 

[Boosterdog]

9 hours ago, draconus said:

I already asked about it and he confirmed the speed but his calculation still stinks - he cannot download whole DCS (over 100GB) in 5 hours with 1.2MB/s speed

 

I thinks he's just got it a bit mixed up.  Which TBF is pretty understandable given how similar the units are denoted. I would imagine the 9.8 figure he quoted is taken from the download progress bar (so MB/s). In fact Im pretty certain as 9.8MB/s was around the median I got on my 70-85Mbps line (time of day dependent).  So he is downloading at just about the full rate his line is capable of. 

[Mistermann]

On 10/10/2024 at 9:13 AM, Pillowcat said:

Weirdo bug with dancing and disappearing static kiowa saw today in multiplayer

 

  Reveal hidden contents

 

Had the same thing happen last night on my MP dedicated server on the Supercarrier with other aircraft.  Very strange.  Will see what I can gather and post.

[Qcumber]

On 10/10/2024 at 5:28 PM, Gunfreak said:

I saw i drop. Last week i flew the F4 on Kola had good preformance even with 200 units.  After the update. The preformance was so bad the vr screen actually lagged(when you see black bars when you move your head side to side. This happened in the F16 and Viggen. So not an F4 thing.

I then tested the A-10C on Caucasus with just 5 ground units and i had equally bad preformance as in Kola. So not a Kola problem either. But seems to be universal across aircraft and maps.

I've tried fildeling with Quadview settings. And there is a clear preformance drop. So much so I had to check my ram, and CPU hadn't done something odd. I have 64gig  ddr5 ram, i7 13700k at 5.2hz cpu and 3090 with 24gig of vram. So if terrain optimisation related to vram and ram. I should have noticed it.

I tried the hot start in the F4 on Kola just after the update. It was terrible 25-32 fps. I then noticed some issues with QVFR even after disabling OXRTK etc. the eye tracking did not seem to be working properly. I ended up reinstalling it and ran it again yesterday. 72 fps 90% GPU use. Very smooth. 

QP with quest link cable meta set to resolution x1.3. QVFR 1.4 centre 0.4 edge, 0.3x0.3. DLSS preset E with 0.9 scaling. 

Edit: spoke too soon. In more challenging situations everything crashes. I think it might be VRAM overflow. 

Edited October 11, 2024 by Qcumber

[Bulldogg]

SMUDGE 12 O'CLOCK HIGH!!

The "improved" spotting dot is a disaster for realistic VR - e.g. any beyond visual range work is ruined and most other a/c on a/c.  

ED please implement an option to REMOVE all spotting effect as before this last update.  Thanks.

[sleighzy]

7 hours ago, Qcumber said:

QP with quest link cable meta set to resolution x1.3. QVFR 1.4 centre

You're applying resolution multipliers in two different places so may effect things as well, e.g. multiplying things multiple times. Will also cause both GPU and CPU load (QVFR is gonna be more CPU load). Could try dropping the Quest to 1.0 and then bumping up higher in QVFR instead. YMMV. 

(...my comment above may be a little off-topic for this thread)

Edited October 11, 2024 by sleighzy

[Qcumber]

8 hours ago, sleighzy said:

You're applying resolution multipliers in two different places so may effect things as well, e.g. multiplying things multiple times. Will also cause both GPU and CPU load (QVFR is gonna be more CPU load). Could try dropping the Quest to 1.0 and then bumping up higher in QVFR instead. YMMV. 

(...my comment above may be a little off-topic for this thread)

 

Thanks. I have tried that option before but did not seem to make much difference. Could be worth trying again though. 

[gonvise]

On 10/12/2024 at 8:59 AM, Qcumber said:

Thanks. I have tried that option before but did not seem to make much difference. Could be worth trying again though. 

Try meta quest pro x1.5 and QVFR x1... For me is the best.

[Evilone]

Please ED can you ensure that there's an option available to switch spotting dots OFF? 
Whether it's a setting in options, or a line in the autoecec.cfg file like we had before the last update, or whatever other method, please don't make them mandatory.
Since the update they're stuck on all the time regardless of settings, and while I understand some people use them and that's great, on my system they're unnecessary and unwanted.
The unrealistic ability to spot a tiny jet from 15+ miles away (only for them to almost disappear at 3 miles) really hurts immersion for me.  


 

[draconus]

Yes, please, just give us the option with a quick hotfix. It's supposed to be study combat flight simulator - give us the realism and challenge back!

[some1]

6 hours ago, Evilone said:

please don't make them mandatory

They're not mandatory, ED botched the settings. Dots can be turned off in 2D, stay always on in VR.

[draconus]

2 minutes ago, some1 said:

They're not mandatory, ED botched the settings. Dots can be turned off in 2D, stay always on in VR.

Which results in the forced setting on VR - that's what was meant.

[BIGNEWY]

there is a planned patch today for campaigns only, this thread will be closed and a new one opened for October. 

 

[BigBorner]

„First“ Patch?