FLIR - FPS killer

[KansasCS]

What if you turn vsync on?

No need, I have a Gsync monitor.

[Gary]

Can I just ask a very simple question please??

 

Has this been reported as a bug yet or not?

 

We are on page 11 of this discussion now!!

 

Thanks...

 

Gary

[NineLine]

Unfortunately I am not sure what to report, I cant reproduce, it seems like most people, not all, but most people are experiencing this with 2gigs or less vram, so without being able to reproduce, I have nothing to give to the devs, they wont be able to produce either most likely. If its a vram issue, well, 2gig is the minimum, as with any minimum, you may experience performance issues.

[too-cool]

Unfortunately I am not sure what to report, I cant reproduce, it seems like most people, not all, but most people are experiencing this with 2gigs or less vram, so without being able to reproduce, I have nothing to give to the devs, they wont be able to produce either most likely. If its a vram issue, well, 2gig is the minimum, as with any minimum, you may experience performance issues.

I'm getting a error pop-up when attempting to install DCS 1.5 beta, ( the source file is corrupt ) I've downloaded DCS_World_OpenBeta_1.5.0.45208.37-11.exe five times from Http and ftp and always the same error, all 7 files are in the same folder, any help would be appreciated. Thanks TC

[VAF [136] Striker]

Mine is set to just over 16GB of vram and I'm experiencing the same problem. Everything is fine until I turn on the TGP and switch to WHOT. Then I get terrible stuttering and freezes. They go away mostly but slowly although there's still some presence all the time.

 

I was running the cockpit displays at 1024 every frame and when I switched to 512 every frame the problem gets much better but it's still present. I still have the partially transparent vehicles in WHOT mode though.

 

I'm running a GTX970 and I have 16GB of Ram on a i7 Quad Core.

[wolle]

Unfortunately I am not sure what to report, I cant reproduce, it seems like most people, not all, but most people are experiencing this with 2gigs or less vram, so without being able to reproduce, I have nothing to give to the devs, they wont be able to produce either most likely. If its a vram issue, well, 2gig is the minimum, as with any minimum, you may experience performance issues.

 

Hi Sith,

 

Not sure I agree with you. Most of us report that things are fine (or at least acceptable) if we use FLIR in CCD mode, and the drop in FPS occurs only if we switch to WHOT or BHOT IR mode. If all three were causing low FPS, I'd buy it that it's an issue of low VRAM, but it is not clear to me at all that on the same system CCD works fine, but not IR. Wouldn't understand why IR is more VRAM intensive, unless there's a bug or something like this. And to say it again, I have 4 gigs of VRAM.

[ody81]

Hi Sith,

 

Not sure I agree with you. Most of us report that things are fine (or at least acceptable) if we use FLIR in CCD mode, and the drop in FPS occurs only if we switch to WHOT or BHOT IR mode. If all three were causing low FPS, I'd buy it that it's an issue of low VRAM, but it is not clear to me at all that on the same system CCD works fine, but not IR. Wouldn't understand why IR is more VRAM intensive, unless there's a bug or something like this. And to say it again, I have 4 gigs of VRAM.

 

My sentiments exactly, I went back to 1.2 just to fly the A-10 and to see if I was imagining this but I'm not. In 1.2 you get a few frames drop (about 5 fps) using CCD, when I switched to FLIR there was no further drop.

 

The issue seems to be FLIR specifically, and everyone here has seem the issue, but given enough gpu/vram grunt the just aren't as affected.

 

Surely ED can reproduce it, even if it's still very much playable for them on their super machines? It is a huge drop after all, you only have to run fraps or the like to see that.

[Sim Flyer]

I am having exactly the same problem, running with a 3gb ram gpu, runnning around 80 - 120 FPS in the cockpit of the A10C but as soon as i switch to BHOT or WHOT on the targeting pod my FPS drops to around 30 - 40.

[Punisher74]

Sith,

 

I reviewed every lua file with ing the a-10c cockpit scripts folder. Thinking the issues had to be somewhere in the execution of the FLIR aft and Foward boat switch settings and most of the code matches from 1.2 to 1.5. Minus a few lines of code. So my conclusion is its either somewhen in the DLL's of dx11. As for me I may have 2gigs of vram, but when I look at the FPS detailed view in game it show over 3gigs more towards 4gigs. I assume it's because I have 2 cards running because I have not disabled my crossfire profile and on card is running at full clock speed and one a silent clock speed (300MHz). But they are right going back to DCS 1.2 has a small change 5fps and in DCS 1.5 it's as high as 60 FPS. People are used to vsync in DCS 1.2 being a massive FPS killer when it comes to a age where almost everyone records or streams gameplay. The issue is there. As for reproducing the issues, we all can or have provided evidence via YouTube video on this thread. To include myself. Granted it could be a memory leak, AMD issue, Nvidia SLI, or AMD crossfire issue. We are just reporting what we are experiencing, it's a beta where we are the beta testers reporting the issues. Like I stated before, it's like taking your car into the repair shop, it never happens in front of the technician. It's simple match the specs of any AMD system running a 4 gig or more card without vsync or gsync, or any FPS locking system and you'll see if you are flying at for example 120 FPS and you turn on the TGP and go thru the different TGP modes and you will get FPS drops. Then turn on the Mav and then again run thru the modes again and you'll see that the FPS drops even greater. Also please just report this using the video evidence provided in this thread.

 

Another thing, as the size of the vram counts. The other thing to consider is the clock speed of the GPU. For example nvidia cards can clock the cards in the 1200's as most high, medium, and low end AMD cards can be clock in the 1000 to 1100's without doing serious damage to the video card. Ie my card's are clocked at 1120 each, and that's almost in the red for over clocking my card. To compensate I run my GPU fans at 90%. Sith I believe you said your card was nvidia? I can almost guarantee you put in a AMD R9 270x even with 4gig's and you'll be able to recreate the issue with ease. We all know there is a current issue between the way DCS 1.5 handles AMD cards over Nvidia. Nvidia being the card to have in DCS, but in reality both cards shouldn't have issues running unless you're running a AMD R7 or less. The current R9 300 series is a rebrand of the R9 200 series. Excluding the R9 Fury X series. Which actually completely doesn't work on DCS (at least I think that want was said in another thread.) What I'm saying is as some cards are different they should all work the same.

 

If I get 90+ FPS flying on a busy mission with the TGP and MAV off. With max or at least high settings. I should have the same or close with them on. Not a drop to stable 14 FPS, then turn them off and just back to a stable 90+ FPS. "THATS JUST A EXAMPLE."

Edited October 20, 2015 by raptorsim

[ody81]

@raptorsim

 

Ta for looking into it some more, and I completely agree.

Everyone is experiencing much higher frame drops in 1.5 regarding FLIR regardless of their setup, although a better rig apparently seems to make it unnoticeable to the naked eye.

But the videos and stats don't lie, surely ED can see the fps drops on their own hardware, even if it doesn't affect them visually, they should be able to see a major fps drop in the performance readings.

 

Surely that's enough to report, this and the Shkval's similar fps issues cannot seriously still be an issue when 2.0 eventually rolls out. I'd have to say farewell to DCS personally, I'd rather not have to spend $1000aud for a graphics card I don't absolutely need to overcome what seems like a major software bug.

[NineLine]

Lets review after the next patch, also I will take vysnc off tonight and see if I get a major drop then, but right now, when I run with vysnc off, I see a drop of 1 or 2 FPS, then its pretty steady 60FPS through out...

[Punisher74]

Lets review after the next patch, also I will take vysnc off tonight and see if I get a major drop then, but right now, when I run with vysnc off, I see a drop of 1 or 2 FPS, then its pretty steady 60FPS through out...

 

The most on vsync I see now is 5 FPS which is great, but with things like streaming, recording are out of the question. Also I noticed when I went to 1.2 is that it automatically started in crossfire full screen mode. I found that weird because in 1.2 it's disabled.

[NineLine]

The most on vsync I see now is 5 FPS which is great, but with things like streaming, recording are out of the question. Also I noticed when I went to 1.2 is that it automatically started in crossfire full screen mode. I found that weird because in 1.2 it's disabled.

 

We shouldn't spend a ton of time comparing with 1.2, its a different engine now, the same things may not apply between the two...

 

As for streaming and such, are you sure? Most of the time, streaming and recording, your FPS is locked anyways, you may have the same experience as using vsync.

[codefox]

I'm running on a GTX 560 Ti which is, most probably, worse than others experiencing the bug posted here. I don't have any issues with my TGP.

[ody81]

I'm running on a GTX 560 Ti which is, most probably, worse than others experiencing the bug posted here. I don't have any issues with my TGP.

 

Really?

So confused. I've always had trashy performance (pretty bad compared to every other module) in the A-10 tbh, Just the FLIR's making it worse. Are you using WHOT/BHOT on the TGP?

[Punisher74]

We shouldn't spend a ton of time comparing with 1.2, its a different engine now, the same things may not apply between the two...

 

As for streaming and such, are you sure? Most of the time, streaming and recording, your FPS is locked anyways, you may have the same experience as using vsync.

 

Fraps is ok, but I don't like running afterburner. DXTROY I'm looking into. OBS crashes the game in 1080p recording plus cannot record in crossefire unless monitor capture & downgraded to 720P. Also the recording uploaded to YouTube never processes to HD. I'm not the only one having recording issues too most of the community YouTubers haven't recorded much data just because DCS isn't there yet. And that's not my words it was a quote from one of the. Anyway off the main topic.

 

But you did bring up s good point when comparing the older version, maybe the new engine is the issues. For example: the TGP render multiple passes in both verions is set to true. Maybe the issue is that the multiple passes isn't needed with the new engine. I can create a mod of the code to test. To see today. I'll use the jsgme mod aspect so I don't mess the core code up.

[NineLine]

Fraps is ok, but I don't like running afterburner. DXTROY I'm looking into. OBS crashes the game in 1080p recording plus cannot record in crossefire unless monitor capture & downgraded to 720P. Also the recording uploaded to YouTube never processes to HD. I'm not the only one having recording issues too most of the community YouTubers haven't recorded much data just because DCS isn't there yet. And that's not my words it was a quote from one of the. Anyway off the main topic.

 

But you did bring up s good point when comparing the older version, maybe the new engine is the issues. For example: the TGP render multiple passes in both verions is set to true. Maybe the issue is that the multiple passes isn't needed with the new engine. I can create a mod of the code to test. To see today. I'll use the jsgme mod aspect so I don't mess the core code up.

 

It is still beta after all ;)

[Punisher74]

It is still beta after all ;)

 

I know.

[codefox]

Really?

So confused. I've always had trashy performance (pretty bad compared to every other module) in the A-10 tbh, Just the FLIR's making it worse. Are you using WHOT/BHOT on the TGP?

 

Yes I do, my performance is good with 30-50 fps.

[Punisher74]

Dropped 10 FPS after hot fix 3 with both TGP and MAV with vsync, msaa 4x, ATFaa 16x, flat shadows, high on everything but heat blur(off), water medium. Before hot fix FPS was solid 60 with vsync. Panning cockpit was ok, and startup FPS ok.

 

Without vsync FPS was 90 FPS with above settings, dropped to 50 FPS With TGP and MAV on.

 

Thats with 1 card 1120mhz and other card 300mhz.

[WolfpackOfficial]

I'm running on a GTX 560 Ti which is, most probably, worse than others experiencing the bug posted here. I don't have any issues with my TGP.

 

Seriously? whats your settings? Im running a 560ti 1gb with an i5 4670k and the milisecond I switch on FLIR or the MAV screen everything becomes Powerpoint (depending on the mission and amount of vics)

 

I was running a 650ti 2gb, but it died a few months back, and with 1.5 It feels smoother seems to run better than what I experienced in 1.2.x. excluding the FLIR issues stated previously.

[super_baloo]

I have no issue at all with my TGP but a big drop of FPS with the maverick camera on (wether tgp is or isn't on simultaneously)

[tobyeez]

I also concur. GTX 780 I7-950 @ 3.65 16 gigs. Game run beautifully in a10 and bS until flir comes on. A slide show. I won't even go back in until this is fixed. Total immersion killer. No issues with the other DCS world versions.

Edited October 28, 2015 by tobyeez

[NineLine]

I also concur. GTX 780 I7-950 @ 3.65 16 gigs. Game run beautifully in a10 and bS until flir comes on. A slide show. I won't even go back in until this is fixed. Total immersion killer.

 

Works fine here. Only difference in our specs is my processor is a little beefier... How is ED supposed to fix that with the info you gave?

[Toxic]

Any news of this being worked on lately? I've been still getting a huge fps drop.

 

~Thanks :)