30 fps difference in between A-10C 1.0.0.8 and World 1.2.2

[FZG_Immel]

Another very important issue is the tree presence...

 

while version 1.0.0.8 still has better FPS, it also have MANY MORE trees in the map.

 

I was comparing FPS and stuff in the "sitting ducks" mission...

 

in version 1.0.0.8, before you reach the target (so north of the targets), you have to fly above a big forest.. many trees down there...

 

in 1.2.2, the map is darker, but no more trees to see ... why is that ?

 

and not, its not a tree visibility setting, as both are set to 5000m in both versions of the game... the trees are just not there anymore.. only the ground texture is different.

 

 

 

Another question.... the 3rd setting on the right of the system option.. the "preload raidus"... what does it do exactly, and how to set it up ???

[winz]

What helped me a lot (12fps -> 30+fps) was decreasing the "preload radius" from max to around 90km.

[Rider1]

Thanks Winz for that tip. I will try it when I get home. And I have tried praying as well. That didn't help my FPS issues at all. :)

[enigma6584]

What helped me a lot (12fps -> 30+fps) was decreasing the "preload radius" from max to around 90km.

 

Interesting winz. When I migrated over to DCS World from the stand-alone products I noticed that the preload radius was a new feature in the option settings. Never had to set this option before so I just naturally set it to max. I will try this as well.

 

Also, can anyone tell me (or us) here exactly what this setting does in the game? I mean what is the benefit to setting it to max as opposed to setting it to something smaller?

 

In addition, in the stand alone products, as said we didn't have this option so what was it set to before in those stand alone products? In other words, what was the standard setting in DCS, set by the developers automatically?

[Mustang]

From what i understand the preload simply loads all textures around the players startpoint before entering the sim, helping to reduce stutters when loading scenery on the fly.

[SkateZilla]

Obviously no one grasps the phrase "transitional period" FC3 is in Beta, DCSW 1.2.2 is transitioning, there's gonna be builds that are rock solid stable, and builds that are playable but have issues.

 

as more code is added, activated and older code de-activated and removed, bugs are gonna pop up like pokemon.

 

in which case, Pikachu!, I Choose You!!!!!!!!!!!!!!!!!!!!!!!!!!!!

 

wait a Sec, ED is Russian... ChariZard!!!!!!!!!!!!!!!

 

hahaha.

[ALDEGA]

Another very important issue is the tree presence...

 

while version 1.0.0.8 still has better FPS, it also have MANY MORE trees in the map.

If I recall correctly, that version didn't have tree shadows or cockpit shadows yet, things that impact performance. To make the comparison of such old versions with DCSW fair, you have to use similar settings.

[winz]

What helped me a lot (12fps -> 30+fps) was decreasing the "preload radius" from max to around 90km.

Well, looks like a false alarm after all, set it back to full for a quick test and experienced no FPS hit.

So, I'm puzzled where that FPS increase came from, as I had aroun 10-15fps when on the ground, and now I have 30stable :huh:

[Slayer]

Preload , cockpit shadows , tree shadows...maybe TSSAA? I think they also changed the water IIRC? Heck I don't even think they had the ground clutter/bushes implemented yet in 1.08

 

Turn it all off and then try testing again. Apples to Apples lots has been changed since then...

 

People want more eye candy, then they give it to us then they complain when there is an FPS drop...