Jump to content

[CHK] FPS Issues with JF-17 Cockpit


paco2002

Recommended Posts

I noticed lower fps too in the JF-17 cockpit compared with other planes, just in parking at hot start without radar or tgp running.

Yeah, the only "bummer". FPS is worse compared to other modules, not that much of a problem in 2D for me but in VR noticeable.

 

I can also confirm there is massive fps drop with AG radar. The problem started after 2.5.6.

 

My FPS drops from 60 to 10.

 

This has to be fixed please.

 

For me the fps drop to single digits when lights on the warning panel are present.

 

Could you two post your PC specs and DCS settings? I can use the AG radar without any significant fps loss. I can see a big fps loss if i do the light test, from the 80s to the 40s in 2D, didn't tried it in VR yet.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Sure! I don't see fps drops either using the AG radar, only during the lights test.

 

GTX 1080 Ti, 16 GB DDR4, Ryzen 7 2700x, 1 TB EVO 970 SSD

 

However, generally speaking, I can say that fps are worse compared to the Hornet or F-14 for example. Now that the newest DCS beta has worse performance overall, it is more noticeable.

 

My DCS settings are highest except motion blur off, MSAA 4x at 1440p, flat shadows, grass to half, tree vis 80%, preload half, smoke density 5, visib range one below ultra, cockpit displays 512, lens effect off, SSAA off and the newest setting is off as well, no idea how it is called - sorry.


Edited by Manuel_108
Link to comment
Share on other sites

Sure! I don't see fps drops either using the AG radar, only during the lights test.

 

GTX 1080 Ti, 16 GB DDR4, Ryzen 7 2700x, 1 TB EVO 970 SSD

 

However, generally speaking, I can say that fps are worse compared to the Hornet or F-14 for example. Now that the newest DCS beta has worse performance overall, it is more noticeable.

 

My DCS settings are highest except motion blur off, MSAA 4x at 1440p, flat shadows, grass to half, tree vis 80%, preload half, smoke density 5, visib range one below ultra, cockpit displays 512, lens effect off, SSAA off and the newest setting is off as well, no idea how it is called - sorry.

 

 

Is that sp or mp

 

Fps is very bad in the cockpit especially in MP and as soon as AG and DL are on

 

 

Sent from my iPhone using Tapatalk

Link to comment
Share on other sites

  • 2 months later...

Bump

 

Any news regarding the JF-17 and the bad VR performance? With the latest OB patch 07-15-2020 it's worse than ever for me. It doesn't matter if i have all 3 mfd's off or showing TGP/Radar/Datalink at the same time, the VR experience in the JF-17 is horrible for me now. :cry: Constant FPS jumps from 40 (Rift S cap) down do 20's and back up (33 - 37- 23 - 33... on runway/ 40 - 37 - 40 - 33 - 40... in the air 10k and up) and every head movement is just a stutter fest down on the ground and up in the air. This is now my only module i ever got sick in since owning a VR headset, never ever had this happen before in any VR game/DCS module :cry:

I don't have these problems in VR with other modules i own, so i :dunno: what else i can do beside bringing this up to you attention again. :beer:

 

Edit: This is only in VR, on monitor i don't have any performance problems. Yes i already deleted fxo/metashaders2, i do this after every patch.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Update: It looks like that the setting "Terrain Object Shadows = Default" was causing the stutter fest in the JF-17 for me. If i set that setting to Flat instead of Default the stuttering is reduced drastically, but the JF-17 is still the worst VR performer. :cry: But atleast it's back to playable in the air with that setting. I don't get why other modules don't suffer(stutterin) from this setting in VR :dunno:

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Update: It looks like that the setting "Terrain Object Shadows = Default" was causing the stutter fest in the JF-17 for me. If i set that setting to Flat instead of Default the stuttering is reduced drastically, but the JF-17 is still the worst VR performer. :cry: But atleast it's back to playable in the air with that setting. I don't get why other modules don't suffer(stutterin) from this setting in VR :dunno:

 

Update 2: It looks like the JF-17 doesn't like if i run Pixel Density(PD) at 1.6. I used to run 1.6 without problems in DCS 2.5.5 version but with 2.5.6 and the cockpit work it looks like this is to much for the JF-17, again no problems in other modules running PD=1.6. I lowered it to 1.3 and it now works most of the time ok for the Jeff(stuttering mostly gone).

On the bright side, i could enable MSAA=2x with the lowered PD.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

I can totally confirm that when running very high supersampling, the JF has HUGE frame drops as soon as I turn on the battery. If the battery is off, runs butter smooth. When SS is turned down and MSAA is on, I don’t notice it. I should add that I have no problem running even higher supersampling in modules like the F-14.

 

I recommend trying a VR setup with high resolution to reproduce . I doubt there is an issue otherwise.


Edited by laertesson
Link to comment
Share on other sites

maybe it's the warning lights, which cause heavy FPS loss

Very quick test in 2d(monitor not VR) because i have not much time right now, Batumi airport:

- on ramp cold and dark - fps stable at 121

- turning on battery, flashing warning lights - fps jumps 101-110

- closing the canopy, flashing warning lights - fps jumps 80-88

- starting at the same location with "hot on ramp", same view/time - fps at 88/89

 

Thats totally fine for me in 2d/monitor, my problem is only in VR. Turning on battery and closing the canopy drops my fps to 31-33(thats below the 40 fps of the Rift S and it's very unpleasend with stuttering). Not that much any more with my new setting(in signature + PD set to 1.3 instead of 1.6) but still worse than other modules F-14/16/18. Atleast my fps are back up at 40(VR, most of the time) in the air with the new settings.

 

I don't know if you can do something about it, but it would be greatly appreciated.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Link to comment
Share on other sites

Id be happy to use simplified warning light shaders mode for VR. They look fantastic if you have the performance headroom but I don’t think DCS VR users almost ever do. I’ll double check it once I extinguish them all if the frames go back up when supersampling, but the startup process almost makes me sick the FPS is so low when PD > 1.5.

Link to comment
Share on other sites

  • 2 months later...

Yes, i can confirm that as soon as i turn on the batteries on the JF my FPS drops to 30 and i am on VR .. And i tried it with the latest beta, other modules works pretty fine ( but i noticed slight fps drop in the harrier when turning on the lights)

Link to comment
Share on other sites

  • 2 weeks later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...