2.5 Settings Comparisons and GPU Impact - Page 5 - ED Forums
 


Notices

Reply
 
Thread Tools Display Modes
Old 02-13-2018, 08:25 AM   #41
StrongHarm
Senior Member
 
Join Date: Jan 2010
Location: USA, EST
Posts: 2,029
Default

Valium, this is probably because you're loading textures and objects into memory as you encounter them. I like to speed this along by hitting F11 to change view to a few airfields and spin my point of view around before taking off. This used to be very useful several years ago before ED optimized object load.
__________________
User Missions I've Created
StrongHarm is offline   Reply With Quote
Old 02-13-2018, 08:42 AM   #42
Decibel dB
Member
 
Decibel dB's Avatar
 
Join Date: Dec 2014
Location: Doha Qatar
Posts: 504
Default

Wow should be stick for further reference. Thank you for your hard work Slideslip

Once we are on the subject I have a few questions on the graphic setting that some might have the answer.

Heat Blur. Do we have any penalty using them?

Res of cockpit displays. What is it doing? I never seen any difference and if so, again what is the penalty.

Depth of field Another area where I can't see jack shit as difference, visually nor performance wise.


Disable aero interface Same here.


o7

Last edited by Decibel dB; 02-13-2018 at 08:56 AM.
Decibel dB is offline   Reply With Quote
Old 02-13-2018, 08:46 AM   #43
Valium
Member
 
Valium's Avatar
 
Join Date: Jan 2013
Location: Katowice, Poland
Posts: 303
Default

Quote:
Originally Posted by StrongHarm View Post
Valium, this is probably because you're loading textures and objects into memory as you encounter them. I like to speed this along by hitting F11 to change view to a few airfields and spin my point of view around before taking off. This used to be very useful several years ago before ED optimized object load.
Thank you, I'm going to check this. Perhaps, it'll help.



Yes, hear blur takes fps when it's on. When it set on high, it takes more.
Anyway, it doesn't take too much fps in my opinion. Sometimes when you're staying at the airport, got heat blur on high and turn on the external camera, you may have fps drops or something like that so my suggestion is to set in on low.

Depth of field - I haven't tested it in 2.5 but even in 1.5.8 it took too much.
Valium is offline   Reply With Quote
Old 02-13-2018, 01:15 PM   #44
nessuno0505
Member
 
Join Date: Jul 2017
Location: Italy
Posts: 164
Default

Very interesting post sideslip!

I've done some math, tell me if I'm wrong:

- You play 3440x1440=4953600 pixels and with your settings you obtain an average 70 fps with a gtx 1080.
- I have a gtx 1070. If you consider 1080 an average 25% faster than 1070 (this is approximately what all benchmarks show), I should obtain about 56 fps at your same resolution and with your same settings (125:70 = 100:X; X=56).
- But I play in VR with oculus rift, so I have 1080x1200 pixels per eye that is a total resolution of 2160x1200=2592000 pixels. That is 52.3% of your resolution, just over half of yours!
- Considering that I need at worst 45 solid fps to avoid stuttering with rift (assuming a pixel density = 1), I should be able to set your settings even with a pixel density of 1.4 - 1.6 without loosing fps, or alternatively keep pixel density = 1 but get solid 90 fps.
- With an increased pixel density maybe I should set no AA, since supersampling is a sort of antialiasing method (is it worth to use both?) and thus gaining another bunch of fps.

Are these maths correct? Now I should test...

Last edited by nessuno0505; 02-13-2018 at 01:22 PM.
nessuno0505 is offline   Reply With Quote
Old 02-13-2018, 01:57 PM   #45
sedenion
Senior Member
 
sedenion's Avatar
 
Join Date: Jul 2008
Location: FR
Posts: 1,126
Default

Quote:
Originally Posted by nessuno0505 View Post
Very interesting post sideslip!

I've done some math, tell me if I'm wrong:

- You play 3440x1440=4953600 pixels and with your settings you obtain an average 70 fps with a gtx 1080.
- I have a gtx 1070. If you consider 1080 an average 25% faster than 1070 (this is approximately what all benchmarks show), I should obtain about 56 fps at your same resolution and with your same settings (125:70 = 100:X; X=56).
- But I play in VR with oculus rift, so I have 1080x1200 pixels per eye that is a total resolution of 2160x1200=2592000 pixels. That is 52.3% of your resolution, just over half of yours!
- Considering that I need at worst 45 solid fps to avoid stuttering with rift (assuming a pixel density = 1), I should be able to set your settings even with a pixel density of 1.4 - 1.6 without loosing fps, or alternatively keep pixel density = 1 but get solid 90 fps.
- With an increased pixel density maybe I should set no AA, since supersampling is a sort of antialiasing method (is it worth to use both?) and thus gaining another bunch of fps.

Are these maths correct? Now I should test...
You maths forgot something fundamental: With VR you are not only changing resolution, but you also render the scene twice from two points of views, this change almost everything...
__________________
If i say something, this is either because this is true, funny or logical, or all that together.
sedenion is offline   Reply With Quote
Old 02-13-2018, 02:18 PM   #46
Sideslip
Member
 
Join Date: Oct 2017
Location: Where it's f-ing cold
Posts: 172
Default

Quote:
Originally Posted by Decibel dB View Post
Wow should be stick for further reference. Thank you for your hard work Slideslip

Once we are on the subject I have a few questions on the graphic setting that some might have the answer.

Heat Blur. Do we have any penalty using them?
Yes there is, but I have yet to measure it. You will only get a performance drop if it is actively blurring, which you wont see unless you are fairly close to another aircraft (A2A refuel, formation, maybe really close dog fighting). So the majority of the time it wont hurt FPS.

Quote:
Originally Posted by Decibel dB View Post
Res of cockpit displays
What is it doing? I never seen any difference and if so, again what is the penalty.
This is the resolution of things like the Shival TV. If you use trackir and lean into the screen, or zoom in on it, it will look better with a higher resolution. 512 is fine to use it as intended. The "per frame" I think refers to the framerate of the display. Don't quote me on this, but I think if it is not set to "per frame" it might run at like half frame rate or something. Again, really doesn't matter considering what it's designed for. Performance impact can be very high depending what you are looking at through the TV.


Quote:
Originally Posted by Decibel dB View Post
Depth of field
Another area where I can't see jack shit as difference, visually nor performance wise.
Do not use this setting. It does nothing in the cockpit, it only affects your exterior views. It blurs the SH*T out of everything. It also tanks my FPS from 70-80 to 20-30. It's only use is for making cinematic videos. There must be a way of controlling the depth, but I've never cared to look.


Quote:
Originally Posted by Decibel dB View Post
Disable aero interface
Same here.


o7
Just ignore this. I imagine this is an old setting from when Windows Vista first released (2005?). I can't believe that the aero interface (makes the edges of windows transparent and stuff) could have any impact on performance if you are even capable of running DCS.

Windows Aero Wikipedia
__________________
System specs: i7 3820 @4.75Ghz, Asus P9X79LE, EVGA GTX1080SC @2100mhz, 16GB Gskil DDR3 @ 2000mhz, 512GB 960EVO m.2, 2 X 512GB 860EVO SATA3 in RAID0, EVGA Supernova 850W G2, Phantek Entho Luxe White. CPU and GPU custom water-cooled with 420mm rad and lots of Noctua fans. ASUS PG348Q. Saitek X-55 and MFG Crosswind.

Last edited by Sideslip; 02-13-2018 at 02:31 PM.
Sideslip is offline   Reply With Quote
Old 02-13-2018, 02:25 PM   #47
Sideslip
Member
 
Join Date: Oct 2017
Location: Where it's f-ing cold
Posts: 172
Default

Quote:
Originally Posted by sedenion View Post
You maths forgot something fundamental: With VR you are not only changing resolution, but you also render the scene twice from two points of views, this change almost everything...
Yes, as stated above, the resolution is not 2160x1200 but 1080x1200 TWICE. In DCS settings, next to monitor choose "3 screen". You will have the same resolution as before but it is being split and rendered for 3 different views. You will notice an impact to your FPS. This is also similar to what happens with Mirrors and Res of cockpit displays.

However, I know Nvidia was supposed to work some black magic with up to 16 viewports (viewpoints really) with the current 1000 series but I don't know how effective it is or what is required for it to work.
__________________
System specs: i7 3820 @4.75Ghz, Asus P9X79LE, EVGA GTX1080SC @2100mhz, 16GB Gskil DDR3 @ 2000mhz, 512GB 960EVO m.2, 2 X 512GB 860EVO SATA3 in RAID0, EVGA Supernova 850W G2, Phantek Entho Luxe White. CPU and GPU custom water-cooled with 420mm rad and lots of Noctua fans. ASUS PG348Q. Saitek X-55 and MFG Crosswind.

Last edited by Sideslip; 02-13-2018 at 02:28 PM.
Sideslip is offline   Reply With Quote
Old 02-13-2018, 02:26 PM   #48
Decibel dB
Member
 
Decibel dB's Avatar
 
Join Date: Dec 2014
Location: Doha Qatar
Posts: 504
Default

Quote:
Originally Posted by Sideslip View Post
Yes there is, but I have yet to measure it. You will only get a performance drop if it is actively blurring, which you wont see unless you are fairly close to another aircraft (A2A refuel, formation, may really close dog fighting). So the majority of the time it wont hurt FPS.



This is the resolution of things like the Shival TV. If you use trackir and lean into the screen, or zoom in on it, it will look better with a higher resolution. 512 is fine to use it as intended. The "per frame" I think refers to the framerate of the display. Don't quote me on this, but I think if it is not set to "per frame" it might run at like half refresh rate or something. Again, really doesn't matter considering what it's designed for. Performance impact can be very high depending what you are looking at through the TV.




Do not use this setting. It does nothing in the cockpit, it only affects your exterior views. It blurs the SH*T out of everything. It also tanks my FPS from 70-80 to 20-30. It's only use is for making cinematic videos. There must be a way of controlling the depth, but I've never cared to look.




Just ignore this. I imagine this is an old setting from when Windows Vista first released (2005?). I can't believe that the aero interface (makes the edges of windows transparent and stuff) could have any impact on performance if you are even capable of running DCS.

Windows Aero Wikipedia
Thank you sir
Decibel dB is offline   Reply With Quote
Old 02-13-2018, 03:17 PM   #49
nessuno0505
Member
 
Join Date: Jul 2017
Location: Italy
Posts: 164
Default

Quote:
Originally Posted by Sideslip View Post
Yes, as stated above, the resolution is not 2160x1200 but 1080x1200 TWICE. In DCS settings, next to monitor choose "3 screen". You will have the same resolution as before but it is being split and rendered for 3 different views. You will notice an impact to your FPS. This is also similar to what happens with Mirrors and Res of cockpit displays.

However, I know Nvidia was supposed to work some black magic with up to 16 viewports (viewpoints really) with the current 1000 series but I don't know how effective it is or what is required for it to work.
In fact with your settings and PD = 1 I obtain quite solid 45 fps and not always 90, maybe that's because 1080x1200 pixels x 2 is different from 2160x1200 pixels, even if the mere pixel count is the same.
nessuno0505 is offline   Reply With Quote
Old 02-13-2018, 04:11 PM   #50
StrongHarm
Senior Member
 
Join Date: Jan 2010
Location: USA, EST
Posts: 2,029
Default

Nessuno0505, where VR is concerned, try kicking your PD up to 1.2, it makes a big difference. I wouldn't go over MSAAx2 though. The considerations for the various settings are very different for VR. Drill into quoted post for VR specific quality/performance analysis.

Quote:
Originally Posted by StrongHarm View Post
VR PD = 1.2
MSAA = 2x
Anisotropic Filtering = 2x
Deferred Shading = ON
Terrain Shadows = FLAT
Cockpit Global Illumination = ON


__PD__
_MSAA_
_Quality_
Performance
1
0
0
10
1.2
0
2
10
1.4
0
4
10
1.6
0
4
10
1.8
0
4
8
2.0
0
6
6
1
2
6
10
1.2
2
8
8
1.4
2
8
6
1.6
2
10
4
1.8
2
10
2
2.0
2
10
2
1
4
8
4
1.2
4
8
4
1.4
4
8
2
1.6
4
10
0
1.8
4
10
0
2.0
4
10
0
1
8
8
2
1.2+
8
10
0
__________________
User Missions I've Created
StrongHarm is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT. The time now is 10:35 PM. vBulletin Skin by ForumMonkeys. Powered by vBulletin®.
Copyright ©2000 - 2018, Jelsoft Enterprises Ltd.