updated docs for the crop option to reference --check-tiles
This commit is contained in:
@@ -387,15 +387,15 @@ values. The valid configuration keys are listed below.
|
|||||||
once it has been rendered once.
|
once it has been rendered once.
|
||||||
|
|
||||||
For an expansion to the bounds, because chunks in the new bounds have
|
For an expansion to the bounds, because chunks in the new bounds have
|
||||||
the same mtime as the old, tiles will not automatically be updated. You
|
the same mtime as the old, tiles will not automatically be updated,
|
||||||
may need to use :option:`--forcerender` to force those tiles to update.
|
leaving strange artifacts along the old border. You may need to use
|
||||||
(You can define the ``forcerender`` option on just one render)
|
:option:`--forcerender` to force those tiles to update. (You can use
|
||||||
|
the ``forcerender`` option on just one render by adding ``'forcerender':
|
||||||
|
True`` to that render's configuration)
|
||||||
|
|
||||||
For reductions to the bounds, because there is currently no mechanism to
|
For reductions to the bounds, you will need to render your map at least
|
||||||
detect tiles that shouldn't exist but do, old tiles may remain and will
|
once with the :option:`--check-tiles` mode activated so that tiles that
|
||||||
not get deleted. The only fix for this currently is to delete that
|
should no longer exist will be detected and deleted.
|
||||||
render directory entirely and render it again with
|
|
||||||
:option:`--forcerender`.
|
|
||||||
|
|
||||||
``forcerender``
|
``forcerender``
|
||||||
This is a boolean. If set to ``True`` (or any non-false value) then this
|
This is a boolean. If set to ``True`` (or any non-false value) then this
|
||||||
|
|||||||
Reference in New Issue
Block a user