I have posted this mod for everybody to use in the Mods section.

My hunch is that I think the changes are at a code level and may have little to do with those two xml files. I tested the MajorDensity of LOD 17 to 0.00142 (which is way more than the 0.00006), over London in quick mission and I still get 54 FPS. In WOFF UE, that setting would have been impossible over London without the game CTD.

orbyxP,

That is you opinion, but this mod works no matter what you say, just like my UE version did that a lot of people used.

What you have forgotten is that AnKor improved his Shaders which allows us even better FPS over the years.

Yes, agreed. Just mentioning that in case you want to increase the density in your files because I think it's ok to do it without affecting the FPS and get more eye candy to boot.

I found in testing, the higher the scenery density, the lower the FPS and greater the game pauses when loading new scenery that comes into view, so that is why I have the numbers I do in the mod

Good point. Which gives me an idea on something else to try with adjusting a few numbers around inside your MOD and maybe..... to eliminate the stutters.

Thanks for your work on the MOD, Panama Red!

Thank you and I hope you enjoy it.

Have you tried increasing the ringdim value as opposed to the major density. I would assume this would give better results. Not sure, testing it shortly.

Between my original UE mod and this PE mod, I tested just about all the different variations to see which ones worked the best.

I wish you the best of luck if you can improve the mod.

Hey there Panama, I think I've kindda figured out why I was getting poor performance even though my hardware and drivers are all good.

It maybe ties in to the setting you have in compositetexturebudgets and Ankor's terrain.fx file. When I adjust the numbers, I get constant FPS, no CTDs (so far), no cloud popping and detailed ground textures.

I have the PatchPixelDim set to 1024 like you have it inside your MOD, but also have the fTextureSize set to 4096 for improved ground detail. Setting the patchpixeldim above that number causes the ground textures to be stretched and deformed. Also, setting fTextureSize above 4096 makes no visual difference in ground detail.

I think with the improved distance and ground detail we now have in the game, the devs might want to take another look at these two values and maybe consider adjusting them. At least it's making a positive impact with my game.

Hi Orbyx,

If you're tinkering with different settings in your compositescenerybudgets and compositetexturebudgets files, I also recommend checking over the relevant sections under my "WOFFue on a Mac" post under the stickies thread - check over the compositetexturebudgets numbers under the "WOFFue in Win10 in BootCamp" section of the post (it works well in my ver. 4.18 install to give crispy graphics especially at low flight level). Under the "Further Modifications to WOFFue in WineSkin..." section, you will find low-end-graphics-card settings for the compositescenerybudgets file that improve fps by about 10-15 fps. Logically, if using the higher-end compositetexturebudgets numbers listed under the "Win10" section, use together with stock settings in compositescenerybudgets, not the low-end scenerybudgets numbers...although, it might be interesting to use low-end scenery numbers and high-end texture numbers...and see what happens - might give slightly less trees on the horizon but fps will probably imrpove. Also, if experiencing CTDs, try running WOFF.exe in Win7 compatibility mode, but let CFS3.exe run normally in Win10 mode (as per suggestions under my long post). Hope some of this info. helps.

Happy flying,
Von S

P.S. For the record, I am still flying ver. 4.18 of WOFFue with sweetFX tweaks installed, but I will get PE when my PayPal tops up towards the end of the year. The advice above should work in PE too.

Thanks for the link VonS, yes it did help.

I tried to dig a bit more and found that MajorMagee's formulas (in a prior thread) weren't being applied correctly in the texture budget file. Also, the patchworlddim and ringdim values were not coinciding with the scenery budget files. This appears both in the MOD and in the original PE xml files.

For example, in the scenery budgets, the PatchWorldDim of "1024" would have a RingDim value of "21" while the texture budget file would have that ringdim value set at "13". The formula was correctly used, but the values were off. In the MOD, I found both the values were off and the formula wasn't being used. So, I matched all the values (and used the formula to calculate the mask) and made my edits to the files and can happily report no more problems with WOFF PE after several missions.

....I have another several tests to perform to try and tweak a bit more, but it will be for another day.

Good God man!



What the hell are you talking about?

Look, whatever it is I hope it goes well. Report back in English. I'm off to the Barmy club.

The rules behind the formulas came out of the CFS3 SDK, but it took me a good while to understand what they were doing and how to properly apply them to get the results I wanted.