Merge pull request #568 from bosh/patch21

Fix broken images

docs/game_logic/skill_shot.md

@@ -176,7 +176,7 @@ the group posts `skill_shot_lit_hit` and `skill_shot_unlit_hit` when a
 unlit shot is hit. To prevent races between the two events we use a
 state_machine called `skill_shot_success` which has three states:
 
-![image](/docs/game_logic/images/skill_shot_state_machine.png)
+![image](images/skill_shot_state_machine.png)
 
 When the mode started it starts at `start`. Then when either
 `skill_shot_lit_hit` or `skill_shot_unlit_hit` are posted in transitions

docs/gmc/installation.md

@@ -46,7 +46,7 @@ From the *Editor* menu select *Editor Settings > Text Editor > Behavior*.
   *  In the *Files* section **disable** the `Convert Indent on Save` option.
   *  If you wish to use spaces in your project and edit in the Godot editor, in the *Indent* section change `Tabs` to `Spaces`.
 
-![image](./images/editor-settings-indentation.png)
+![image](images/editor-settings-indentation.png)
 
 ### Other Good Things
 
@@ -67,7 +67,7 @@ In the Godot editor, select **AssetLib** from the top center selector. You may n
 
 You can download the GMC plugin from the MPF-GMC repository on GitHub. Visit https://github.com/missionpinball/mpf-gmc and click on the green **Code** button to show the Code dropdown, and select *Download ZIP* to download the plugin.
 
-![image](./images/gmc-download-zip.png)
+![image](images/gmc-download-zip.png)
 
 Extract the downloaded ZIP file and go to the *addons* folder, where you'll see a folder named *mpf-gmc*. Copy this folder into the *addons* folder in your Godot project folder.
 

docs/hardware/fadecandy/index.md

@@ -16,7 +16,7 @@ MPF allows you to use a FadeCandy LED controller to drive the LEDs in
 your pinball machine. A FadeCandy is a small, cheap (\$25) USB
 controller which can drive up to 512 serially-controlled RGB LEDs.
 
-![image](/hardware/images/fadecandy.jpg)
+![image](../images/fadecandy.jpg)
 
 You can use the FadeCandy in place of connecting your LEDs to a
 P-ROC/P3-ROC controller, or you can choose to drive some LEDs via your
@@ -141,7 +141,7 @@ physically connected to Connector 0.
 
 The following diagram explains how the numbering works:
 
-![image](/hardware/images/fadecandy_numbering.jpg)
+![image](../images/fadecandy_numbering.jpg)
 
 Consider the following config:
 

docs/hardware/fast/dmd.md

@@ -12,7 +12,7 @@ The FAST Core controller can drive traditional single-color
 pinball DMDs via the 14-pin DMD connector cable that's been in most
 pinball machines for the past 25 years, like this:
 
-![image](/hardware/images/display_mono_dmd.jpg)
+![image](../images/display_mono_dmd.jpg)
 
 It makes no difference as to whether you're using an LED or an original
 plasma gas DMD. (Also it doesn't matter what color it is.)

docs/hardware/fast/drivers.md

@@ -30,7 +30,7 @@ Nano Controller.
 When you're using FAST IO boards, drivers plug into individual IO
 boards. Then the IO boards are connected together in a loop.
 
-![image](/hardware/images/fast-io-3208.png)
+![image](../images/fast-io-3208.png)
 
 The `number:` setting for each driver is its board's position number in
 the chain, then the dash, then the driver output number. Note that the

docs/hardware/fast/leds.md

@@ -19,7 +19,7 @@ similar). You can buy them from many different companies, and they're
 what's sold as the "NeoPixel" brand of products from Adafruit. (They
 have all different shapes and sizes.)
 
-![image](/hardware/images/fast-nano.png)
+![image](../images/fast-nano.png)
 
 Most of the settings in the [Lights](../../mechs/lights/index.md) documentation apply to LEDs connected to FAST Pinball
 controllers, however there are a few FAST-specific things to know.

docs/hardware/lisy/connection.md

@@ -17,7 +17,7 @@ Gottlieb CPU board with the "LISY1" board.
     details. Basically you replace the MPU with the LISY board. You can
     still play the original ROM using PinMAME on LISY.
 
-![image](/docs/hardware/images/lisy80_board.jpg)
+![image](../images/lisy80_board.jpg)
 
 More details can be found in the [LISY user
 manual](http://www.lisy80.com/english/documentation-lisy/).
@@ -44,7 +44,7 @@ b.  Run MPF on the LISY hardware directly ("master" mode).
 
 See the following image for an architecture overview:
 
-![image](/docs/hardware/images/lisy_mpf_overview.jpg)
+![image](../images/lisy_mpf_overview.jpg)
 
 If you want to run MPF on the LISY controller itself, set DIP 4
 (option1) and DIP 8 (autostart) to 'ON' and all other DIPs on that
@@ -63,7 +63,7 @@ with the host PC running MPF, set DIP 2 to 'ON' for network mode or
     order to be able to reboot, as it will power the Raspberry Pi over the
     USB connection.
 
-![image](/docs/hardware/images/LISY_modes.png)
+![image](../images/LISY_modes.png)
 
 ## 3. Configure your Game
 
@@ -130,7 +130,7 @@ needed, a "normal" USB charging cable (Micro-USB cable) will do the
 job. Once connected to the host computer, it will (hopefully) identify a
 new serial device. This is usually `COMX` on windows:
 
-![image](/docs/hardware/images/lisy_windows_com_port.png)
+![image](../images/lisy_windows_com_port.png)
 
 Or `/dev/ttyACMX` on Linux:
 

docs/hardware/multimorphic/drivers.md

@@ -26,7 +26,7 @@ format:
 
 ## number:
 
-![image](/hardware/images/multimorphic_PD-16.png)
+![image](../images/multimorphic_PD-16.png)
 
 For PD-16-based devices, the numbering format is:
 
@@ -59,7 +59,7 @@ coils:
 
 ## Burst Switches as Local Outputs (P3-Roc only)
 
-![image](/hardware/images/multimorphic_p3_roc.png)
+![image](../images/multimorphic_p3_roc.png)
 
 If you want to use burst switches as local outputs set DIP switch 1 to
 `on` on the P3-Roc. You can use those 64 output as direct outputs:

docs/hardware/multimorphic/i2c.md

@@ -12,7 +12,7 @@ Related Config File Sections:
 The P3-ROC contains an I2C port (J17) which is accessible to MPF. You
 can use this port to control any I2C-based device.
 
-![image](/docs/hardware/images/multimorphic_p3_roc.png)
+![image](../images/multimorphic_p3_roc.png)
 
 You need to connect SDA, SCL and ground. You may not need the 3.3V from
 the P3-ROC as your controller might be a different voltage (which you

docs/hardware/multimorphic/leds.md

@@ -133,7 +133,7 @@ The PD-LED controls up to 84 individual LED elements, which can be used
 to control individual single color LEDs, or (more likely), combined into
 groups to control RGB LEDs.
 
-![image](/hardware/images/multimorphic_PD-LED.png)
+![image](../images/multimorphic_PD-LED.png)
 
 The PD-LED uses a "direct/parallel" connection method for LEDs, where
 each LED has connections for each color element running back to the
@@ -289,7 +289,7 @@ showing current saturation meeting the needs of the strip with a voltage
 between the gate and source (VGS) of 3.3 V or less. This is an example
 of such a circuit:
 
-![image](/hardware/images/FET-LEDs.png)
+![image](../images/FET-LEDs.png)
 
 Please make sure to connect your PD-LED and the FET to the same
 [common ground](../voltages_and_power/voltages_and_power.md) or your FET will smoke when connecting power.

docs/hardware/multimorphic/servos.md

@@ -13,7 +13,7 @@ Related Config File Sections:
 Starting with PD-LED v3 you can configure up to twelve steppers on a
 PD-LED.
 
-![image](/hardware/images/multimorphic_PD-LED.png)
+![image](../images/multimorphic_PD-LED.png)
 
 To enable servos you need to configure your PD-LED board in your `p_roc`
 section. Assuming your PD-LED has the ID 4 you can use the following

docs/hardware/multimorphic/steppers.md

@@ -15,7 +15,7 @@ PD-LED. You need an additional cheap external stepper driver to drive
 the load of the stepper. Those are sold for a few bucks as StepStick or
 DRV8825 on amazon, ebay, aliexpress or similar platforms.
 
-![image](/hardware/images/multimorphic_PD-LED.png)
+![image](../images/multimorphic_PD-LED.png)
 
 To enable steppers you need to configure your PD-LED board in your
 `p_roc` section. Assuming your PD-LED has the ID 4 you can use the

docs/hardware/multimorphic/switches_p_roc.md

@@ -12,7 +12,7 @@ Related Config File Sections:
 To configure switches on a P-ROC, you can follow the guides and
 instructions in the [Switches](../../mechs/switches/index.md) docs.
 
-![image](/hardware/images/multimorphic_p_roc.png)
+![image](../images/multimorphic_p_roc.png)
 
 However there are a few things to know about using switches with a
 P-ROC.

docs/hardware/multimorphic/win_x64.md

@@ -25,7 +25,7 @@ shot below. That should be ok.
 Download and run the setup executable from the "1" link in the screen
 shot.
 
-![image](/docs/hardware/images/ftdi_x64.jpg)
+![image](../images/ftdi_x64.jpg)
 
 ## 2. Now download and unzip the other package
 

docs/hardware/multimorphic/win_x86.md

@@ -22,7 +22,7 @@ Here's a screen shot of the download section of that page. Note that
 the actual version number of the driver might be newer that the screen
 shot below. That should be ok.
 
-![image](/docs/hardware/images/ftdi_x86.jpg)
+![image](../images/ftdi_x86.jpg)
 
 Download and run the setup executable from the "1" link in the screen
 shot. (We like to use that because it's easier than the manual process

docs/hardware/opp/cobrapin/index.md

@@ -7,7 +7,7 @@ title: CobraPin Pinball Controller powered by OPP
 --8<-- "hardware_platform.md"
 
 
-![image](/docs/hardware/images/CobraPinV0_2_isoSmall.jpg)
+![image](../../images/CobraPinV0_2_isoSmall.jpg)
 
 Features:
 
@@ -41,7 +41,7 @@ Video about cobrapin extension board:
 
 ## Power Input and Filter
 
-![image](/docs/hardware/images/CobraPinV0_2_VIN.jpg)
+![image](../../images/CobraPinV0_2_VIN.jpg)
 
 **J9:** 
 
@@ -58,7 +58,7 @@ connectors.
 
 ## Switch Inputs
 
-![image](/docs/hardware/images/CobraPinV0_2_switches.jpg)
+![image](../../images/CobraPinV0_2_switches.jpg)
 
 **J1, J2, J3:**
 
@@ -79,14 +79,14 @@ connectors. For example Molex KK254 series available for AWG 30-22. Each connect
 for the direct input return. If you measure the voltage between GND and
 a switch (in below picture 0-0-16) you should measure 3.3V.
 
-![image](/docs/hardware/images/Cobra_Voltage_Switch.jpg)
+![image](../../images/Cobra_Voltage_Switch.jpg)
 
 For that to measure only the micro controllers need to be powered up, no
 need to apply any other voltage on the Cobra board. To perform a simple
 test connect any kind of switch to one of the inputs and setup a little
 mpf test configuration.
 
-![image](/docs/hardware/images/Cobra_Switch_connected.jpg)
+![image](../../images/Cobra_Switch_connected.jpg)
 
 Do not apply any voltage to the switches, most likely that will destroy
 your CPU. For further details and fully working Cobra board
@@ -97,7 +97,7 @@ section below.
 
 ## Solenoid Outputs
 
-![image](/docs/hardware/images/CobraPinV0_2_solenoids.jpg)
+![image](../../images/CobraPinV0_2_solenoids.jpg)
 
 **J6, J7, J8:**
 
@@ -123,7 +123,7 @@ must be controlled by switch with number `0-a-b`.
 Each bank has an LED next to it to indicate if that bank has power.
 Check these if you are concerned you have blown a fuse.
 
-![image](/docs/hardware/images/Cobra_Coils_LED_Power.jpg)
+![image](../../images/Cobra_Coils_LED_Power.jpg)
 
 In above picture you see that the LED for bank A is alight but not for
 bank B. In order to have the LED alight you only need to have connected
@@ -138,7 +138,7 @@ voltage power or without the coils plugged in. Using these LEDs, you can
 verify that each output is being driven correctly, in the picture below
 coil 1-0-1 is being driven at this very moment.
 
-![image](/docs/hardware/images/Cobra_Coils_LED_Switch.jpg)
+![image](../../Cobra_Coils_LED_Switch.jpg)
 
 To run the above test, there is no need for a high voltage power supply
 neither for any coil. Only the mirco controllers need to be powered up.
@@ -184,7 +184,7 @@ To have a fully working example for setting up autofire coils see the
 
 ## Solenoid Power Output and Fuses
 
-![image](/docs/hardware/images/CobraPinV0_2_HVout.jpg)
+![image](../../images/CobraPinV0_2_HVout.jpg)
 
 **J13:**
 
@@ -205,7 +205,7 @@ The fuses are 5x20mm. Each fuse provides power to a bank of 8 solenoids.
 
 ## Neopixel Support
 
-![image](/docs/hardware/images/CobraPinV0_2_NEO.jpg)
+![image](../../images/CobraPinV0_2_NEO.jpg)
 
 **J10:**
 
@@ -227,7 +227,7 @@ The connectors J10, J11, J12 and J14 are JST connectors VH style. There
 are lots of Neopixels which come with a JST connector SM style. You
 might want to craft a little converter cable in such a case.
 
-![image](/docs/hardware/images/Cobra_Neopixel_JST_adapter_VH_SM.jpg)
+![image](../../images/Cobra_Neopixel_JST_adapter_VH_SM.jpg)
 
 There are two neopixel chains that support 256 RGB pixels each for a
 total of 512. RGBW pixels are also possible, but the number may be
@@ -240,15 +240,15 @@ fuse and are providing power for neopixels. For the LED to light up
 there is no need to run any MPF configuration, you don't even have to
 power up the micro controllers.
 
-![image](/docs/hardware/images/Cobra_Power_LED_Neopixel.jpg)
+![image](../../images/Cobra_Power_LED_Neopixel.jpg)
 
 When you order the micro controllers you have various options, one
 option to choose from is Regular vs NoGlow. If you order the Regular
 version then after power is provided for the Neopixel and the micro
 controllers are powered up (still no need to run any MPF on them), the
 LEDs of your strip will glow blue, which is a good first test.
 
-![image](/docs/hardware/images/Cobra_Neopixel_blue_glow.jpg)
+![image](../../images/Cobra_Neopixel_blue_glow.jpg)
 
 In order to addess the LEDs in MPF you need to know their address
 
@@ -268,7 +268,7 @@ generic LED section [LEDs](../../../mechs/lights/index.md) where as well the mor
 
 ## Microcontrollers
 
-![image](/docs/hardware/images/CobraPinV0_2_STM32.jpg)
+![image](../../images/CobraPinV0_2_STM32.jpg)
 
 The brains of the CobraPin are two STM32 microcontroller boards
 programmed with OPP firmware. They are connected to the host computer

docs/hardware/opp/oppcombo/index.md

@@ -7,9 +7,9 @@ title: OPP EM Combo boards
 --8<-- "hardware_platform.md"
 
 
-![image](/docs/hardware/images/O16I16_comps.jpg)
+![image](../../images/O16I16_comps.jpg)
 
-![image](/docs/hardware/images/O32_comps.jpg)
+![image](../../images/O32_comps.jpg)
 
 The aim of this project is to provide cheap hardware to control EM pinball machines:
 
@@ -30,9 +30,9 @@ The size of the board is about 150 x 125 mm.
 Several boards are required to drive an EM machine. 
 According to the complexity and your personal taste, 3-4 to drive the play field, 2-3 to drive the light box.
 
-![image](/docs/hardware/images/fast_draw_lb.jpg)
+![image](../../images/fast_draw_lb.jpg)
 
-![image](/docs/hardware/images/fast_draw_pf.jpg)
+![image](../../images/fast_draw_pf.jpg)
 
 ## Configuration
 
@@ -85,6 +85,6 @@ In the above example one would do:
 With those boards, I digitized a 1975 Gottlieb Fast Draw, which was presented to the [Pontacq Pinball Show](https://www.facebook.com/groups/154388563388625)
 on June 1rst-2nd, 2024, South of France, where it ran 375 plays without any software problem.
 
-![image](/docs/hardware/images/pontacq.jpg)
+![image](../../images/pontacq.jpg)
 
 

docs/hardware/pkone/connecting.md

@@ -12,7 +12,7 @@ roughly covers connecting the bus between the boards.
 
 Connect your PKONE NANO controller to your PC using USB.
 
-![image](/docs/hardware/images/pkone-nano.png)
+![image](../images/pkone-nano.png)
 
 Then connect the OUT port of your NANO to the IN port of your first
 board (Extension or Lightshow). Consequently, connect the OUT port of

docs/hardware/pkone/leds.md

@@ -20,7 +20,7 @@ generally known as "WS2812" (or similar). You can buy them from many
 different companies, and they're what's sold as the "NeoPixel" brand
 of products from Adafruit. (They have all different shapes and sizes.)
 
-![image](/hardware/images/pkone-lightshow.png)
+![image](../images/pkone-lightshow.png)
 
 Most of the settings in the [Lights](../../mechs/lights/index.md) documentation apply to LEDs connected to PKONE Lightshow
 boards, however there are a few PKONE-specific things to know.

docs/hardware/pkone/lights.md

@@ -21,7 +21,7 @@ individual Lightshow boards. Then the Lightshow boards are connected
 together in a chain with other add-on boards (such as PKONE Extension
 boards) to the controller.
 
-![image](/docs/hardware/images/pkone-lightshow.png)
+![image](../images/pkone-lightshow.png)
 
 The `number:` setting for each simple LED is its board's Address ID
 number in the PKONE chain, then the dash, then the simple LED output

docs/hardware/pkone/servos.md

@@ -23,7 +23,7 @@ When you're using PKONE Extension boards, coils plug into individual
 Extension boards. Then the Extension boards are connected together in a
 chain to the controller.
 
-![image](/docs/hardware/images/pkone-extension.png)
+![image](../images/pkone-extension.png)
 
 The `number:` setting for each servo is its board's Address ID number
 in the PKONE chain, then the dash, then the servo output number (11-14).

docs/hardware/pkone/switches.md

@@ -23,7 +23,7 @@ When you're using PKONE Extension boards, switches plug into individual
 Extension boards. Then the Extension boards are connected together in a
 chain.
 
-![image](/hardware/images/pkone-extension.png)
+![image](../images/pkone-extension.png)
 
 The `number:` setting for each switch is its board's Address ID number
 in the PKONE chain, then the dash, then the switch input number (1-35).