NavFLIR being always rendered? (Just a theory/also possible cause of lower framerate)

[BlowTorch]

This first part is just an introduction, but important to see why I think this is happening.

 

In my current situation, I'm not able to get a real computer, and I'm limited to a laptop. 16Gb of ram, but Intel HD Graphics 4000 integrated graphics card, which is probably what causes this "incompatibility". Since I started flying in DCS, I experienced a graphic bug anytime an infrared optic was used, be it the A-10C, the Su25T with the LLTV pod,... I was already used to it and just avoided using these systems, as I know it's my fault for running DCS in such a low end PC, in fact I feel lucky the rest of it works alright.

The bug itself meant that whenever I turned on any infrared system that provides video feedback (FLIR modes in the litening, FLIR mode in the gazelle, -D or -G mavericks,...), the whole texture of the terrain would just "light up", as if it was unaffected by time of day, weather, shadows,... and remaining like that until DCS was closed.

 

Don't know if I'm explaining it correctly, so see for yourself:

-This is how a normal night looks:

https://imgur.com/f3aGJGu

 

-The same in the A-10C before using FLIR:

https://imgur.com/JttRVjG

Notice that I am using the TGP but the CCD mode, you can only see because of the runway lights.

https://imgur.com/zJoGU6E

 

-The same image, just after turning the black hot mode on (the same happens in white hot):

https://imgur.com/f1TIuet

 

So this is what happens in my case, not complaining, just so you know where this deduction comes from.

Now what happens in the harrier:

-The same exact mission, at the same time, and just after takeoff, no button clicking at all:

https://imgur.com/Bi1Ak0u

https://imgur.com/1u4EICG

-When turning on the NavFLIR:

https://imgur.com/aVqKmvb

In this case turning on the FLIR didn't do anything as the effects of this particular bug were already in place since the beginning. The same happens with a cold start, or in any situation, really.

 

What you have seen is what lead me to think this:

Is it possible that the NavFLIR is being rendered in the background constantly, even if the system itself is turned off? That would explain why my "bug" with infrared looks this way in the Harrier, as something permanent instead of only after turning FLIR on.

Also it gave me the idea this could be related with the lower framerate compared to other modules (also experienced by me), and that seemed to be related with the aircraft location and orientation. So, maybe everything inside the pilot's FOV (including what should be outside of the sensor FOV) is being passed through the "IR filter simulation" (or however it works in DCS), even if the NavFLIR itself is switched off. This part would explain why the framerate is lower than other modules, which shouldn't be even with the NavFLIR on. Also why it looks so dependant on position and heading, being really dependant on how cluttered/how many objects are in line of sight/inside your FOV.

 

 

This whole post shouldn't be read like a complaint, since I accept that the bug that allowed me to see this is my fault and there is nothing any dev could do about it (other than giving me a free better PC?). Instead it is intended to provide a possible cause of a problem others have experienced, the low FPS.

Any thoughts?

 

(BTW, what is wrong with the screenshots that can't be uploaded in a normal way? Here are all the screenshots: https://imgur.com/a/3wnZc)

[Esac_mirmidon]

I think you are right.

 

I have a 1060 and playing at 1920x1080, 16G RAM.

 

The thing with the Harrier for me is that i have 60 FPS when im heading to the sea or the Sky over terrain but when the nose is pointing to the terrain my FPS are going down to 45.

 

So It depends where my Harrier is pointing i have more or less FPS, and then when the TV or the FLIR is on not a single FPS lost. So i think something is related with what you see.

 

Something that Razbam could take a look.

Edited November 30, 2017 by Esac_mirmidon

[Zeus67]

Yes. With Ed's help we discovered that video output for all MPCDs and HUD is always being rendered.

[Esac_mirmidon]

Thats a great discovery. Thanks a lot Zeus for telling us. And thanks BlowTorch for the report.

[Zeus67]

https://forums.eagle.ru/showpost.php?p=3305607&postcount=2

[ben_der]

Yes. With Ed's help we discovered that video output for all MPCDs and HUD is always being rendered.

 

Is this only with the Harrier or all Planes in 1.5.8.?

 

Great the root cause has been tracked down :thumbup:

[BlowTorch]

Well, good news that you already found the cause, that's a fast working team.

 

Is this only with the Harrier or all Planes in 1.5.8.?

 

Great the root cause has been tracked down :thumbup:

 

 

I'd say only the Harrier, haven't flown much other planes, but the A-10c felt normal

[Mustang]

Great to hear Zeus67 I hope a quick hotfix can be made soon!

[T.Eason]

Yup lets hope the fast working team can also get out fast hotfixes!