mirror of
https://gitlab.com/OpenMW/openmw.git
synced 2025-01-17 01:10:10 +00:00
Clarify object paging merge factor docs
This commit is contained in:
parent
28d6159b86
commit
15f4b5515d
@ -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
|
||||
----------------------
|
||||
|
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user