From 33d85635fd9294a89b633b8bffc4c312eeafdb35 Mon Sep 17 00:00:00 2001 From: psi29a Date: Thu, 18 Aug 2022 08:59:24 +0000 Subject: [PATCH] Merge branch 'terraindocs' into 'master' Clarify object paging merge factor docs (#5924) Closes #5924 See merge request OpenMW/openmw!2295 (cherry picked from commit 0d776d7009cbacbce7c234e6653f3b5333e10eed) 15f4b551 Clarify object paging merge factor docs --- docs/source/reference/modding/settings/terrain.rst | 11 ++++------- files/settings-default.cfg | 2 +- 2 files changed, 5 insertions(+), 8 deletions(-) diff --git a/docs/source/reference/modding/settings/terrain.rst b/docs/source/reference/modding/settings/terrain.rst index eb8ab37c45..0aa7d9bd1b 100644 --- a/docs/source/reference/modding/settings/terrain.rst +++ b/docs/source/reference/modding/settings/terrain.rst @@ -159,14 +159,11 @@ object paging merge factor :Range: >0 :Default: 250.0 -Affects the likelyhood of objects being merged. -Higher values improve the framerate at the cost of memory. +Affects the likelyhood of more complex objects to get paged. +Higher values improve visual fidelity at the cost of performance and RAM. -Technically this is implemented as a multiplier to the merging benefit, and since -an object has a lot of vertices, sometimes in terms of hundreds and thousands, -and doesn't often need as much draw calls to be rendered (typically that number is in 1 or 2 digits) -this value needs to be large enough, as this is what makes -the merging cost and the merging benefit actually comparable for the sake of paging. +Technically this factor is a multiplier of merging benefit and affects the decision +whether displaying the object is cheap enough to justify the sacrifices. object paging min size ---------------------- diff --git a/files/settings-default.cfg b/files/settings-default.cfg index 89090fa262..9c7efe165e 100644 --- a/files/settings-default.cfg +++ b/files/settings-default.cfg @@ -107,7 +107,7 @@ object paging = true # Use object paging for active cells grid object paging active grid = true -# Affects the likelyhood of objects being merged. A higher value means merging is more likely and may improve FPS at the cost of memory. +# Affects the likelyhood of more complex objects to get paged. Higher values improve visual fidelity at the cost of performance and RAM. object paging merge factor = 250 # Cull objects smaller than this size divided by distance