smo0ths

Performance tweaks for extra FPS.

583 posts in this topic
22 hours ago, IrOnTaXi said:

enabling foliage occlusion would actually make squad run slower as the list of occluders would ballon by 2-3x and going through the occlusion list is EXPENSIVE. often more expensive than the act of occluding (but about #2 or 3 in terms of expensive things) the most expensive being our base pass.

 

do you also consider movable objects like players & vehicles as occluders?

 

I suppose not?!

Edited by sgt_froug

Share this post


Link to post
Share on other sites
9 hours ago, sgt_froug said:

 

do you also consider movable objects like players & vehicles as occluders?

 

I suppose not?!

object by object support but there is some tweaking on which moveables occlude as well

 

we generally dont have enough movers to make an impact .. ie they are bad occluders generally anyway as they move.. they add little benefit. 

 

 

 

Share this post


Link to post
Share on other sites

ok, thanks for clearing that up. so the earlyzmovables doesn't have any impact either.

Share this post


Link to post
Share on other sites
8 hours ago, sgt_froug said:

ok, thanks for clearing that up. so the earlyzmovables doesn't have any impact either.

not as far as I can tell in our case. 

 

Share this post


Link to post
Share on other sites
Quote

 

 

 

Did another test with earlyzpass after some reading in the documentation. 

 

On Chora is certainly makes a noticeable difference. 

 

See below setting it to 2 (default) and 3 - This could result in 3-7 ish more frames (it fluctuates a good bit) on my system. 

 

I will set the squad default to 3. Good find!

 

 

 

early.png

Share this post


Link to post
Share on other sites
4 hours ago, IrOnTaXi said:

2FOC7FAx.pngearly.png

 

Edited by Skul

Share this post


Link to post
Share on other sites
12 hours ago, IrOnTaXi said:

 

 

Did another test with earlyzpass after some reading in the documentation. 

 

On Chora is certainly makes a noticeable difference. 

 

See below setting it to 2 (default) and 3 - This could result in 3-7 ish more frames (it fluctuates a good bit) on my system. 

 

I will set the squad default to 3. Good find!

 

 

 

 

But in your screen '3' has less frames?

Now i'm confused. Which is better?

Share this post


Link to post
Share on other sites
50 minutes ago, zeep said:

But in your screen '3' has less frames?

Now i'm confused. Which is better?

That's not frames. That's time in ms needed to process everything in the list. Meaning lower number is better.

Share this post


Link to post
Share on other sites
17 minutes ago, Skul said:

That's not frames. That's time in ms needed to process everything in the list. Meaning lower number is better.

Exactly. So in that screenshot the earlyzpass = 2 average roughly computes to 1000 / 28.3 = ~35fps and earlyzpass = 3 to 1000 / 25.6 = ~39fps.

Edited by sgt_froug

Share this post


Link to post
Share on other sites

Posted (edited)

Just wanted to comment.  I had much better luck altering options in the .ini file on my own then I did with the in game options.  Since vehicles my FPS went down to the low 20's which is absolutely not playable for me. 

 

With in game options all set to low and knocking my resolution down I had no improvement.

 

I altered some graphical lines in the .ini and my FPS is in the 40-50 range now which is playable and oddly enough I didn't notice much of a graphical change, aside from shadows. 

 

I didn't follow this guide though, I only altered a few lines just based on which ones I thought would help. So I'm just saying that this strategy can definitely help.  I'll look at my ini when I get home and try to remember which lines I changed and post them here.

 

 

Edited by Converge

Share this post


Link to post
Share on other sites
38 minutes ago, smo0ths said:

yes you can still change them the same way @iDrag0n

I mean I need the settings themselves. Like - shadows, post process, folliage, overall draw distance etc. they were in  Scalability.ini in v8

like these:

 

 

 

[ [email protected] ]
r.LightFunctionQuality=1
r.ShadowQuality=3
r.Shadow.CSM.MaxCascades=3
r.Shadow.MaxResolution=4096
r.Shadow.RadiusThreshold=0.03
r.Shadow.DistanceScale=0.45
r.Shadow.CSM.TransitionScale=0.8
r.DistanceFieldShadowing=0
r.DistanceFieldAO=0
r.AllowLandscapeShadows=0

Edited by iDrag0n

Share this post


Link to post
Share on other sites
Just now, Major Trouble said:

Just delete scalability.ini and verify your game files. It should download the default.

tried it few times since v9 release. Scalability.ini  is still empty for me. I thought devs removed it for some reason. Can you check if you have it?

Share this post


Link to post
Share on other sites

after you unpack the file like i explained just open them using this

 

windows key + R:

copy paste this

%SystemDrive%/Program Files (x86)/Steam/steamapps/common/Squad/Engine/Config/BaseScalability.ini
%SystemDrive%/Program Files (x86)/Steam/steamapps/common/Squad/Squad/Config/DefaultScalability.ini

 

@iDrag0n

Share this post


Link to post
Share on other sites
1 minute ago, smo0ths said:

after you unpack the file like i explained just open them using this

 

windows key + R:

copy paste this

%SystemDrive%/Program Files (x86)/Steam/steamapps/common/Squad/Engine/Config/BaseScalability.ini
%SystemDrive%/Program Files (x86)/Steam/steamapps/common/Squad/Squad/Config/DefaultScalability.ini

 

@iDrag0n

 

Sorry, but I've missed the post where you expalin how to unpack something and can't find it. Could you please give me the link?

Share this post


Link to post
Share on other sites

What's the recommended driver to play Squad and/or UE4 games?

In v8 we could see this in BaseHardware.ini:

Spoiler
Quote

[GPU_NVIDIA]
; a newer one is out but has issues (see below)
SuggestedDriverVersion="361.75"

; Seems this driver was not setting uninitialized global variables
; (static, non const) to 0 but leaving them uninitialized.
; Also blacklist future driver versions until QA has verified them to work.
; NOTE: UE-25096 has been fixed and verified by QA.
;+Blacklist=(DriverVersion=">=361.43", Reason="UE-25096 Viewport flashes black and white when moving in the scene on latest NVIDIA drivers")

; To prevent problems with older drivers.
; We might have to adjust that further.
+Blacklist=(DriverVersion="<=347.09", Reason="Crashes with Paragon content using more recent GPU features")

 

Now I can see this in my BaseHardware.ini:

Spoiler
Quote

[GPU_NVIDIA]
; a newer one is out but has issues (see below)
SuggestedDriverVersion="372.90"

; Seems this driver was not setting uninitialized global variables
; (static, non const) to 0 but leaving them uninitialized.
; Also blacklist future driver versions until QA has verified them to work.
; NOTE: UE-25096 has been fixed and verified by QA.
;+Blacklist=(DriverVersion=">=361.43", Reason="UE-25096 Viewport flashes black and white when moving in the scene on latest NVIDIA drivers")

; To prevent problems with older drivers.
; We might have to adjust that further.
+Blacklist=(DriverVersion="<=347.09", Reason="Crashes with Paragon content using more recent GPU features")

; UE-35288, GPU hangs in 4.13 binary release.
+Blacklist=(DriverVersion="==372.70", Reason="This driver version has many known stability issues")

 

In v8 I was using 361.75 and it was kinda  Ok-ish or whatever but now I am completely confused because these commentaries contradict with each other and even with themselves...

Edited by Skul

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now