Jump to content

Viggen Performance


Emilio_Ger

Recommended Posts

Hmm.. don’t think so, look at post #42 by Cobra. Looks like a specific Heatblur patch.

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

The framerate variance fix should be in this one, but I can't confirm at present.

Works like a charm again, thank you! :thumbup:

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

The framerate variance fix should be in this one, but I can't confirm at present.

 

I have updated to 2.5.1 a few hours ago. I have to prove it a few times more but for me this seemes to work like a charm too.

 

The frame drop from 60 (vsync'ed down from 90 to 60) to approx 40 when flying near trees is gone ... YESS! :joystick:

 

EDIT: I finally managed to find out the problem on my machine.

Many trees, Default Terrain Shadows and AntiAliasing together killed my frame rate.

It was not related to anything else I think.


Edited by TOViper

Visit https://www.viggen.training
...Viggen... what more can you ask for?

my computer:
AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TPR | Rift CV1

 

Link to comment
Share on other sites

Strange just did a clean installed today and just took the Viggen for a test flight. Radar on I get maybe 5 frames a sec and freezes galore unplayable. No mods running. Vanilla DCS. Never as bad as it is now (for me that is). Prior to the update it was a bit sluggish but nowhere near the slide show I'm experiencing now.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, MIG-21bis, FW-190D9, F-86F, MIG-15bis, M-2000C, AJS-37 Viggen , AV-8B Night Attack V/STOL , F-5E Tiger , L-39 Albatros.

Link to comment
Share on other sites

Strange just did a clean installed today and just took the Viggen for a test flight. Radar on I get maybe 5 frames a sec and freezes galore unplayable. No mods running. Vanilla DCS. Never as bad as it is now (for me that is). Prior to the update it was a bit sluggish but nowhere near the slide show I'm experiencing now.

 

What is your computer's specification?

 

Using the lowest possible settings of all time I have 28-32 frames on my laptop with 1.5.8., and had 5-7 frames with 2.5.0 (tested it a week ago or so). So it was literally unplayable with 2.5.0. The main problem with my laptop is the graphics card, which is at the lowest possible minimum requirement. And the loading time was approx an century for a simple mission :music_whistling:

 

But my power machine is able to handle 2.5.0 (and 2.5.1) very well after knowing about the issue with the trees, the terrain shadows and anti aliasing.

 

Hope you can find out a setting that works better than slideshow.:noexpression:

Visit https://www.viggen.training
...Viggen... what more can you ask for?

my computer:
AMD Ryzen 5600G | NVIDIA GTX 1080 Ti OC 11GB | 32 GB 3200 MHz DDR4 DUAL | SSD 980 256 GB SYS + SSD 2TB DCS | TM Warthog Stick + Throttle + TPR | Rift CV1

 

Link to comment
Share on other sites

What is your computer's specification?

 

Using the lowest possible settings of all time I have 28-32 frames on my laptop with 1.5.8., and had 5-7 frames with 2.5.0 (tested it a week ago or so). So it was literally unplayable with 2.5.0. The main problem with my laptop is the graphics card, which is at the lowest possible minimum requirement. And the loading time was approx an century for a simple mission :music_whistling:

 

But my power machine is able to handle 2.5.0 (and 2.5.1) very well after knowing about the issue with the trees, the terrain shadows and anti aliasing.

 

Hope you can find out a setting that works better than slideshow.:noexpression:

Well solve the slide show issue thankfully. For some reason it was on 512 sync every frame. Moved it to 512 and it solved that problem.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, MIG-21bis, FW-190D9, F-86F, MIG-15bis, M-2000C, AJS-37 Viggen , AV-8B Night Attack V/STOL , F-5E Tiger , L-39 Albatros.

Link to comment
Share on other sites

The framerate variance fix should be in this one, but I can't confirm at present.

 

It would be useful to us all if you could confirm one way or the other!

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

Super happy these forums are so helpful, I've just played mission 3 in the Red Flag campaign and was encountering some serious frame rate issues - PC spec is decent (4600MHz cpu, 32 gigs of ram, 1080ti & SSD) and it's the first time I've had performance drop off that bad, its good to see that its a known issue and that Heatblur are on the case as I absolutely adore this module - big thanks to Cobra847 and the team who respond so quickly to problems like this.

System Specs: Intel Core i9-9900K 3.6GHz @ 4.8GHz, Gigabyte Z390 Aorus Master, 32 GB G.Skill Trident Z DDR4-3600 RAM, GeForce GTX 4090, Crucial SSD (750 GB), TrackIR 5, TMWH, TM T-Flight Rudder Pedals, Samsung 49” Odyssey G9

Link to comment
Share on other sites

It would be useful to us all if you could confirm one way or the other!

 

Considering that my min FPS while taxiing to the runway went from 17FPS to 44FPS, no driver update in between. So if ED has nothing improved on their side regarding the Viggen only i would say the fix is in.

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

Considering that my min FPS while taxiing to the runway went from 17FPS to 44FPS, no driver update in between. So if ED has nothing improved on their side regarding the Viggen only i would say the fix is in.

 

Not everyone is seeing that. There may have been ED improvements. We just need the devs to confirm rather than us all speculating on yes or no!

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

I only see this FPS improvement with the Viggen, so my guess is it's in. But you are right, an answer would be nice.

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

Well the memory manager change and anything in 2.5.1 beta affected my load time immensely. Yes there were changes, perhaps not directly to Viggen, but engine optimisations. Those were publicly listed, but unfortunately lack detail on what you might see, since it affects hardware differently.

 

So not sure if you will ever get the answer you want, but you may have got the result you needed.

___________________________________________________________________________

SIMPLE SCENERY SAVING * SIMPLE GROUP SAVING * SIMPLE STATIC SAVING *

Link to comment
Share on other sites

Yes my loading times are also better(in all modules), because of the memory manager i guess. But i have a little AG and anti-shipping training mission, i start from the same airfield with different airplanes and only the Viggen had bad performance on my PC and flying low level since DCS 2.5, not before 2.5. After the 2.5.1 OB update it's back to the same performance i get in the other planes, i didn't see any FPS improvement with DCS 2.5.1 in other planes for me, only in the Viggen. Thats why i'm guessing that the fix is in. But without an official answer you are right, it could be an problem in the engine that ED fixed and the HB fix is not implemented yet. Makes no difference in the end for me, because it work's now fine.

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

Yes, the fix is in. :) I actually confirmed it in the changelog itself, but failed to post here seperately.

 

Glad to hear it has dramatically improved the issue!

Thanks Cobra, good to have it confirmed.

Any news on the Kneepad issue that features in a few threads?

Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box

Link to comment
Share on other sites

  • Recently Browsing   0 members

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