Merge branch 'main' of github.com:missionpinball/mpf-docs

docs/gmc/guides/spanning-multiple-monitors.md

@@ -33,7 +33,7 @@ Right-click on your new scene in the *FileSystem* window and select **Set as Mai
 
 ## Create Main Display
 
-The first display will be run on the main screen, and doesn't require extra setup. In your scene tree add a new node of type `MPFDisplay` and give it a name (this name will be how it's targeted in MPF `slide_player`).
+The first display will be run on the main screen, and doesn't require extra setup. In your scene tree add a new node of type `MPFDisplay` and give it a name (this name will be how it's targeted in MPF `slide_player` ex: 'primary').
 
 In the *Inspector* panel set `is_default` to true and select an initial slide. For most use cases, the default GMC initial slide will work (*/addons/mpf-gmc/slides/startup.tscn*). Expand the *Layout > Transform* section and set the size to be the dimensions of the main monitor.
 
@@ -55,7 +55,7 @@ Under the *Flags* dropdown, set the following:
   * **Unresizable**: On
   * **Borderless**: On
 
-Now create a new `MPFDisplay` child node of this `Window`. Set the same Initial Slide as the other, and under *Layout > Transform > Size* set the dimensions of the second monitor. Give this node a name that you will reference in MPF to target it.
+Now create a new `MPFDisplay` child node of this `Window`. Set the same Initial Slide as the other, and under *Layout > Transform > Size* set the dimensions of the second monitor. Give this node a name that you will reference in MPF to target it (ex: 'mini-display').
 
 In the Editor scene view, you should now see two copies of the MPF logo, one for each display.
 
@@ -71,4 +71,4 @@ In your MPF config files, you can now target a specific display using the name o
                 target: primary
             attract_mini_slide:
                 target: mini-display
-```
+```

docs/versions/release_notes.md

@@ -14,25 +14,29 @@ documentation for that specific release.
 
 ## 0.57.2
 
-*Not Yet Released*
+Release: July 17, 2024
 
-MPF 0.57.2 includes improvements to ball search.
+MPF 0.57.2 includes substantial upgrades to ball search, and numerous bug fixes and improvements.
 
 ### New Features
 * Switch `ignore_during_ball_search:` config option to prevent false positives during searches
 * Switch support for `playfield:` config option to propagate to devices (drop targets, shots, etc.)
 * Playfield `enable_ball_search:` now supports templates, e.g. `settings.enable_ball_search==1`
 * OPP: Support for `WING_SOL_8` wings with up to 32 solenoids
 * Virtual Pinball: Support for segment displays
+* Spinners: `max_events_per_second:` config option to reduce event load during spins
 
 ### Improvements
 * Playfield *playfield_active* event now includes the source of the active trigger
-* Better (more reliable) suppression of switch hits from Drop Target firings during ball search
+* Better (more reliable) suppression of switch hits from Drop Target firings during ball search with `switch.mute()`
 * Better error messaging for ball search on a playfield without iterator devices
 * Ball devices that mark playfield active can now inherit the playfield from their switch
+* Switches no longer post active events during startup
+* Shows now include debug logging for starting, stopping, and pausing
 
 ### Bug Fixes
 * Fixed a bug in ball search phase/iteration counting that miscounted the number of phases and iterations to perform
+* Fixed a bug in FAST LED channel numbering for rolling over channel offsets
 
 ## 0.57.1