A patch is a small file with only your edits (operations tied to coordinates and definition names) from the original scenery up to your version, with a name, author, description and license. The recipient replays it on their own DSF of the same tile. Instead of the whole edited DSF you share only your work.
Creating a patch
DSF › choose a version › History › Patch… at the version.
Fill in Name, Author, Description, License / author note.
For an inserted DEM choose Bundle input files (GeoTIFF of an inserted DEM) – the patch is larger but self-contained; otherwise it only refers to the file and the recipient needs their own. For third-party data check that you may share it. Input note – data source and license.
Create patch › Download .rfpatch (in the app window a Save as window should open; the file is also stored in the Studio cache, the message shows the path).
Paths from your computer are not stored in the patch (for a DEM only a reference to the attachment, elsewhere only the file name).
Applying a patch
DSF › choose your DSF › History › Apply patch….
Patch file (Browse…) › Load, or upload a file, or pick from Loaded earlier.
Your base DSF – the open DSF is preselected; or a path to a DSF (only from the allowed places as the source in DSF edits, e.g. the X-Plane installation or the Other DSFs folders). Name of the new version.
Preview: whether the base is the same as the author's (then the result will be byte-identical), or different (the patch is tried, check the result). For each operation will apply / no change / skipped with a reason, and a Where it changes map. For a DEM without an attachment enter your own GeoTIFF, otherwise the step is skipped.
Write new DSF (progress and Cancel writing while it runs – no new DSF is created then) – a new version in the cache with a patch badge, in History also with a list of skipped operations. Try in X-Plane… opens Operations with the version preselected.
A patch is data only (no program). When loading, its structure, size, allowed operations and attachment digests are checked; a dangerous or damaged file is refused.
License Avoid sharing edited DSFs of the Laminar Research default scenery or of third-party packs – it may conflict with their license. A patch contains only your edits. See License and sharing.
Not verified: scope of patch verification The byte-identical result on the same base is verified on synthetic data for heights, raster heights, deletion, added objects, retexturing, the terrain brush and an inserted DEM. It has not yet been verified for water, airports, roads and defect repairs or on large real DSFs.
Based on the RF Studio manual (F1 › Manual, version 0.12.0-beta). Post your questions and experience in this thread.
Patches (.rfpatch)
A patch is a small file with only your edits (operations tied to coordinates and definition names) from the original scenery up to your version, with a name, author, description and license. The recipient replays it on their own DSF of the same tile. Instead of the whole edited DSF you share only your work.
Creating a patch
Paths from your computer are not stored in the patch (for a DEM only a reference to the attachment, elsewhere only the file name).
Applying a patch
A patch is data only (no program). When loading, its structure, size, allowed operations and attachment digests are checked; a dangerous or damaged file is refused.
Based on the RF Studio manual (F1 › Manual, version 0.12.0-beta). Post your questions and experience in this thread.