📌 What to test in the beta

💬 0 replies

Before you start

  • Do not pass the beta on. Do not give the installer or the program folder to other people; refer anyone interested in testing to RFstudio@simulators.cz (license agreement, Beta section).
  • Non-commercial use only. The license agreement (version 1.2) allows RF Studio to be used only non-commercially; commercial use, including creating sceneries that are sold, only with prior written consent (see License and sharing).
  • Install as described in Installation and go through First start – ideally with Open the demo and the guide.
  • The Studio never overwrites source files. Put results into X-Plane with Test in X-Plane – a test can always be fully undone.
  • Features nobody has seen in X-Plane yet have an orange Not verified: … box in the manual. Your check in the simulator is most valuable exactly there.

What to test

Area Steps What to look at
Installation and updates Installation: install, a new version over the old one, uninstall; if possible also on Windows 10 the installer downloads nothing, the data stay after an update, SmartScreen and OneDrive warnings
Guide and demo Welcome and the guide the six steps go through without errors, the paths to the demo files work
Insert detailed DEM Insert DEM shape and height of the hill, no step or crack at the area boundary, objects and roads stand on the terrain
Airport smoothing in the editor Airport flattening: area (draw or Prefill with runway…), Smooth the marked area, Preview, Write new DSF runways and pavement without bumps and steps, an aircraft at a stand sits level, a smooth transition into grass
Airport check and batch flattening Airport check, Batch flattening: automatic area, Adjust in editor, the Before → after table the rating matches the look in X-Plane, the Improved / Caution, got worse rows make sense
Orthophoto Orthophoto: variants A and B, the Edge and colours (optional) section the photo sits in place, its edge blends into the terrain, the colours at the edge match the surroundings
Bottom photo and shore strip (RenderFarm ortho DSF) Bottom photo, shore strip and beaches: a water edit at the shore or a beach type change in an ortho DSF with a bottom photo, Write; Try in X-Plane "recomputed" after the write; the shallow bottom with the photo joins the land without a seam, the beach sand is hidden by the photo, the beach water part makes a soft edge, no photo over land nor a hole at the new shore
Overlay editor and OSM Overlay and OSM import, Export for WED buildings have sensible models and heights, nothing floats or sinks, Ctrl+Z undoes the whole import
Polygon exclusion and terrain flatten Editor › Entities and tools: an L-shaped exclusion over default buildings, a terrain flatten on a slope; Try in X-Plane buildings disappear only inside the polygon (in the corner of the bounding rectangle outside the L they stay), the terrain in the polygon is level at the chosen height and has no crack at the edge
Importing the default scenery Importing the default scenery into an overlay with Replace original on; Test in X-Plane the original disappears in the range and your copy stands in its place, nothing is doubled (except forests across the range edge, which the preview points out)
Editing the base scenery Editing the base scenery: New project › Edit the base scenery, delete or move a building, Export DSF… › Base copy (like terrain); Test in X-Plane the edited buildings, autogen and forests are in place, the deleted ones are gone; the surrounding scenery and airports are unchanged – nothing else disappeared or doubled
Merge with another DSF Merge with another DSF: a densified place of the second DSF › Use › Write merged DSF the transferred mesh sits in place, the blend band has no crack or step
Patches Patches: create one, apply it to another DSF the preview correctly tells a same / different base, the result matches the original edit
Test in X-Plane Test in X-Plane, optionally Before and after screenshots X-Plane loads the pack (Log.txt), after End test… everything is as before
Map without RenderFarm Map: a tile from the list and a typed one (e.g. +50+014), DSF source, layers DSF terrain (zoom in) and Forest in DSF (precompute “dsf”), Hillshade from the DSF, orthophoto from Custom Scenery, OSM base map, Difference of two DSF versions the label Used by X-Plane matches what you see in X-Plane, forest and terrain fit the orthophoto, greyed-out groups have an understandable explanation
Base map Base map: tile picker of a new project, the OSM toggle in the editor, Offline – cache only the map shows, the attribution is next to it, without internet only tiles from the cache
Texts, help and manual the CZ / EN switch, help F1, the manual (search, Save as HTML, Print / PDF) clarity, typos, places where the manual does not match the app

For each scenario note what you did, what you expected and what happened.

How to report

  1. Click Report a problem in the help header, or the small Report button next to a red error message.
  2. Fill in What happened?, What were you doing right before? and What did you expect to happen?. Show contents… shows exactly what the file will contain (version and build, system, the end of the log, recent errors; paths and the user name are replaced with placeholders).
  3. Save report (zip) and send the zip as an e-mail attachment to RFstudio@simulators.cz. The address is also in (Copy address, Write an e-mail).
  4. If it is about the look of the scenery, add an X-Plane screenshot and the GPS of the place (the Studio can copy it, e.g. Copy GPS at a defect or the GPS of an airport check finding).
  5. One report = one problem. Send ideas and comments (also about the texts and the manual) to the same address or post them in the discussion forum simulators.cz/forum.

The Studio sends nothing by itself – you send the file. When the application does not start at all, the error window offers Create an error report? and saves the zip on the Desktop. Details in Problem reports.


Based on the RF Studio manual (F1 › Manual, version 0.11.2-beta). Post your questions and experience in this thread.