investigating Low FPS

[sasquatch98]

9 minutes ago, TFS said:

Same, I have a 14900k, 4090, 64gb 6400 ddr5 ram, m.2 and this is the first time I've seen dips in FPS in VR on a quest 3. Everything else is butter, still playable, but no where near anything it's fine, get near <profanity>... throws a fit. Gotta be the huge textures in the cockpit, don't get me wrong, the cockpit is extremely good looking, but I'd rather a smoother experience. 

Do you normally fly with msaa on? I do and my performance wasn’t as good as I’d like till I noticed the update turned it off, as soon as that was turned on I was back to normal. 

[fjacobsen]

5 hours ago, Darcaem said:

Is this the parking brake text you were referring to? This is in pancake mode with the higher settings I use for mission making, I don't see anything odd... No idea what could be happening

 

null

Yes exactly these.

For me they become Black.

I will PM You.

 

[TFS]

1 hour ago, sasquatch98 said:

Do you normally fly with msaa on? I do and my performance wasn’t as good as I’d like till I noticed the update turned it off, as soon as that was turned on I was back to normal. 

I do, I'll have to check that I didn't even think that would be a thing. 

[Yurgon]

Just a hunch here. I just found a few airports on the Marianas map where the CH-47F and the OH-58D will drop to single digit FPS for me when I fly very low over the airports buildings, and in some cases the same happens near airport buildings. As soon as I get above circa 30 feet, or as soon as I get clear of the buildings, FPS skyrocket to whatever max I'm getting.

Those with really bad FPS, can you try other missions or other starting locations? I tried a bunch of airports on the Caucasus map and found no issues there; with Caucasus being generally the least taxing map right now, it might give you a chance to at least get to fly the CH-47 for now.

Oh, one more thing to improve FPS: Exclude both your DCS installation directory and your Saved Games\DCS directory from your antivirus. I did that last year and immediately got better FPS and less (micro-) stutter.

[benny8421]

PROGRESS!!

So this morning I noticed my Quest 3 software was running the latest v68, but the headset itself wasn't. I've updated it and all now seems to be well. Picture was taken on the Nevada Chinook IA Runway Start mission. Also runs really well on Caucasus. Not tested any other maps yet.

I have had to drop TEXTURES to medium to hold 72hz, and ASW only kicks in now and again. It can run at HIGH textures, but barely. Hopefully with a bit more optimisation I'll be able to crank them back up to HIGH.

Doesn't explain how all the other modules were running fine, but at least it's now working.

If you have a Quest 3, hope this helps

Edited August 11, 2024 by benny8421

[Raven (Elysian Angel)]

15 hours ago, sasquatch98 said:

Do you normally fly with msaa on? I do and my performance wasn’t as good as I’d like till I noticed the update turned it off, as soon as that was turned on I was back to normal. 

Oh I need to check that then. The combination of MSAAx2 and quad view normally works brilliantly for me.

 

*edit*
I just noticed ED removed the “cannot reproduce” tag

Edited August 11, 2024 by Raven (Elysian Angel)

[ddc196]

Stuttering is really bad. All other aircraft are fine. 

[Tomcatter87]

With the Chinook, I get FPS-drops now and then - it happens quite suddenly, without any obvious reason and then the frame drop to 7 or worse. 

[dogsbody59]

4090 24gb  i7 32gb ram 12fps come on guys where has my other 98 gone?

 

[PFT_Orph3us]

CH47 is unplayable in VR! The massive drop of FPS, from 80 FPS to 25-40 FPS (of course drops to 1-2 FPS also happens).  I've got almost every single module in DCS and Chinok is crap in performance sense. F4E without performance option enables, 60-80FPS on the Halfghanistan map.  I wonder if someone from ED tested Chinok in VR, it is a rhetorical question, of course, that is NOT. 

My rig: Oculus Rift S, Ryzen 7 5800X3D, RX 6800XT, DDR4 64GB 3200Mhz, PCIE M2 2TB only for DCS.

[fjacobsen]

11 hours ago, PFT_Orph3us said:

CH47 is unplayable in VR! The massive drop of FPS, from 80 FPS to 25-40 FPS (of course drops to 1-2 FPS also happens).  I've got almost every single module in DCS and Chinok is crap in performance sense. F4E without performance option enables, 60-80FPS on the Halfghanistan map.  I wonder if someone from ED tested Chinok in VR, it is a rhetorical question, of course, that is NOT. 

My rig: Oculus Rift S, Ryzen 7 5800X3D, RX 6800XT, DDR4 64GB 3200Mhz, PCIE M2 2TB only for DCS.

With the massive Cockpit texture size, You GPU will run out of VRAM, especially in VR, and then it will start using system RAM, which are much slower, thus the bad FPS.

Try to lower Textures to Medium, cause that will almost half Your VRAM usage with little graphics quality loss - in VR more or less unrecognizable.

Edited August 12, 2024 by fjacobsen

[Marshallman]

Reduce Cockpit visuals to 256Mb

No visual difference to me, BIG improvement in VRAM

Regards

[Nealius]

I'm finding the externals to be an FPS killer and stutter-fest-inducer as well. Point the TGP from any of the jets towards a scene with just one -47F and the game turns into a slideshow for a couple seconds. 

[DrBob]

On 8/10/2024 at 9:42 PM, Marshallman said:

OK Ive got mine sorted now..

Clearly dont need the high level of settings I was flying with in the past

40% Vram....... Hope this helps someone

Regards

Try setting Resolution (1st row) to lowest. Thats what shows on screen and u don't need it when flying vr. 

[Tomcatter87]

For me, the fps killers seem to be on the outside. When experiencing a lag, I paused, zoomed in the view and looked at the FPS changing in relation to where I looked. On te inside, I still got about 40 fps - when looking outside (nothing special happening there, no smoke, explosions or something like that) I got 7 fps. After a little while, everything went back to normal. The chinook is the only aircraft where this happens .

[Slippa]

I’ve been to the stutterfest too with the Chinook. Yesterday I even went VIP to the crash to desktop afterparty. Not a lot of joy and I went more than once.

Other modules perform better, choppers seem to suffer more and I don’t necessarily have to be flying one to suffer.

I blame the update we got a while back. I think we’ve had three updates or patches since the stuttering and crashes became a regular occurrence. Every session in MP is trouble. I spend more time clearing out the fxo folder and reloading it than I do flying and it’s hit and miss as to whether or not there are any slots available as that’s massively bugged too.

The Chinook performed as I’d expect in SP thankfully but there are far more laughs to be had in MP so I’d rather it was fixed. I’m blaming the update more than the module though.

I’ll have a go at lowering settings too so cheers for posting the help.

[Nealius]

Since it's initial release into Early Access I doubt the LODs are optimized yet. Par for the course, I guess. Other modules are in the same boat, but the Chinook just seems more egregious.

[N0XID]

I noticed when I was sitting in the AH64D and a CH47 passed me (taxiway) that my FPS dropped to 1-2FPS for about 20 seconds

Edited August 12, 2024 by N0XID

[BIGNEWY]

Hi all, 

I have spoken with the team and during early access we will see some more optimisations. 

It seems to be very system specific, with medium to lower end system seeing most of the issues with performance, but thank you for your feedback we appreciate it as it makes the modules better. 

 

[firefox121]

hace 4 horas, BIGNEWY dijo:

Hi all, 

I have spoken with the team and during early access we will see some more optimisations. 

It seems to be very system specific, with medium to lower end system seeing most of the issues with performance, but thank you for your feedback we appreciate it as it makes the modules better. 

 

Hi, my system specs are almost like yours, only I am using still the reverb G2, and chinook is unflyable for me, the others modules runs well , like before the update.....will try the medium graphics textures and see.

Waiting for some update optimisation. Thanks for all your efforts

[BIGNEWY]

21 minutes ago, firefox121 said:

Hi, my system specs are almost like yours, only I am using still the reverb G2, and chinook is unflyable for me, the others modules runs well , like before the update.....will try the medium graphics textures and see.

Waiting for some update optimisation. Thanks for all your efforts

Can you attach your dcs log and a short track replay showing a fps dip. I have shared others with the team and they are looking and reporting issues. 

thank you

[MAXsenna]

Can you attach your dcs log and a short track replay showing a fps dip. I have shared others with the team and they are looking and reporting issues. 
thank you

I'm by no means a graphics expert. But could you have the team explain to us in an official statement why the textures are made this way, when users like @Taz1004 @fjacobsen, @Darcaem and others have fixes.
Cheers!

Sent from my SM-A536B using Tapatalk

[Darcaem]

Well, technically in my case I do not have a fix, I just tried to resize the textures that in this particular model weights a lot more than other aircrafts. I imagine this textures would be awesome for 8K in supercomputers, but since I cannot see them anyways...

[Vee.A]

On 8/10/2024 at 10:57 AM, Darcaem said:

 

 

Please, do correct me if I am missing something or I'm doing something wrong, as I have only basic knowledge.

 

This is what I have done:

1.- Extract all .dds from Cockpit_CH-47F_Textures.zip

2.- Load all of them in "XnResize" https://www.xnview.com/en/xnresize/#downloads (the first one I found, there are probably better options out there)

3.- Action -> Preset 50% and Action -> Rotate unchecked

4.- Output -> select folder and Output -> Format: same as original

5.- Convert (took ~10min on my end)

6.- Zip all the dds created back into the original Cockpit_CH-47F_Textures.zip overriding them, and then paste back the file into [..]\Eagle Dynamics\DCS World\Mods\aircraft\CH-47F\Cockpit\Textures

I don't do multiplayer, but I assume it won't pass integrity check

 

EDIT: needless to say, make a backup of the zip file before overriding it

 

No need to back up unless you want to. You can just run the repair tool and it'll sort it out

[Nealius]

Does resizing the textures simply involve reducing the file dimensions, e.g. 4096x4096px to 1024x1024px, and preserving the mipmaps?