From 91825764327962926db7c7fb9ce9ad50fd3010d3 Mon Sep 17 00:00:00 2001 From: "John G. Cross" Date: Wed, 19 Jun 2024 17:11:32 -0700 Subject: [PATCH 1/2] Update spanning-multiple-monitors.md I'm suggesting giving example names to the two displays so that they line up with the MPF slide example at the bottom of the page. I think this will help people connect the dots that these MPFDisplays steps are creating the MPF "targets". --- docs/gmc/guides/spanning-multiple-monitors.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/gmc/guides/spanning-multiple-monitors.md b/docs/gmc/guides/spanning-multiple-monitors.md index a17db7ac13..796cea7fea 100644 --- a/docs/gmc/guides/spanning-multiple-monitors.md +++ b/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 -``` \ No newline at end of file +``` From 8b36491a174b722798b26bd9dd7ebd11c2cc98cb Mon Sep 17 00:00:00 2001 From: Anthony van Winkle Date: Wed, 17 Jul 2024 13:01:46 -0700 Subject: [PATCH 2/2] Update release notes for MPF 0.57.2 --- docs/versions/release_notes.md | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/versions/release_notes.md b/docs/versions/release_notes.md index f06f09892f..81d243a0e4 100644 --- a/docs/versions/release_notes.md +++ b/docs/versions/release_notes.md @@ -14,9 +14,9 @@ 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 @@ -24,15 +24,19 @@ MPF 0.57.2 includes improvements to ball search. * 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