Formatting fixes, use local images, add page for launcher, WIP test menu page

This commit is contained in:
Zsolt Zitting
2023-10-25 04:55:53 -07:00
parent 06a71e257b
commit 5556e90ece
28 changed files with 324 additions and 132 deletions
+3 -1
View File
@@ -1 +1,3 @@
site/
site/
.idea/
.obsidian/
+82 -83
View File
@@ -23,10 +23,11 @@ however there may be room for improvement.
### Things you'll need
- [<ins>***Game files***</ins>](#archive "internet archive moment") (The guide was written for 3.07.01, but should work with most versions)
- [<ins>***Game files***</ins>](#archive "internet archive moment") (The guide was written for 3.07.01, but should work
with most versions)
> FAILURE: **Unsupported versions**
> As of June 2023, **SDFE** 1.00.00 (Launch version) and all versions of **SDHN or SDJE** (Chinese version) do not
> work with the configuration laid out in this guide.
> As of August 2023, **SDFE** 1.00.00 (Launch version) and all versions of **SDHN or SDJE** (Chinese version) do not
> work with the configuration laid out in this guide, due to missing support in ST.
- Phillips #2 screwdriver, and ideally JIS #2 as well.
- An empty SATA SSD with at least 128GB of capacity (I use [this one](https://www.amazon.com/-/dp/B08CK7T9FG/) in mine)
- [An ISO of **Windows 10 Enterprise LTSB 2016 x64**](https://iso.massgrave.dev/pd/en_windows_10_enterprise_2016_ltsb_x64_dvd_9059483.iso)
@@ -37,22 +38,23 @@ however there may be room for improvement.
- A spare keyboard and mouse
- An external 1080p monitor that can swivel to portrait and has DVI input on it (oddly specific, not strictly required,
but a huge pain in the ass if you don't have it)
- [7-Zip](https://7-zip.org)
- [MAS](https://github.com/massgravel/Microsoft-Activation-Scripts)
(It's annoying having your cab nag you to activate Windows)
- [Motherboard Drivers](https://www.gigabyte.com/us/Enterprise/Embedded-Computing/MDH11BM-rev-10#Support):
- Intel Management Engine 11.6.29.3287
- Intel Chipset 10.1.1.38
- Realtek Audio 435
- Additional Drivers
- [Nvidia Graphics Drivers](https://www.nvidia.com/download/driverresults.aspx/141906/en-us/)
(Older version, newer versions might work? Probably not.)
- [FTDI D2XX USB to Serial](https://ftdichip.com/wp-content/uploads/2021/08/CDM212364_Setup.zip)
- [DirectX June 2010 Redistributable](https://www.microsoft.com/en-us/download/details.aspx?id=8109)
- [Visual C++ 2012 Redistributable x64](https://www.microsoft.com/en-us/download/details.aspx?id=30679)
- [Visual C++ 2015-2022 Redistributable x64](https://aka.ms/vs/17/release/vc_redist.x64.exe)
- [Hay1tsme's ST](https://gitea.tendokyu.moe/Hay1tsme/segatools)
([Pre-built version, preconfigured](files/mercury-cab.zip))
- These files on the flash drive:
- [7-Zip](https://7-zip.org)
- [MAS](https://github.com/massgravel/Microsoft-Activation-Scripts)
(It's annoying having your cab nag you to activate Windows)
- [Motherboard Drivers](https://www.gigabyte.com/us/Enterprise/Embedded-Computing/MDH11BM-rev-10#Support):
- Intel Management Engine 11.6.29.3287
- Intel Chipset 10.1.1.38
- Realtek Audio 435
- Additional Drivers
- [Nvidia Graphics Drivers](https://www.nvidia.com/download/driverresults.aspx/141906/en-us/)
(Older version, newer versions might work? Probably not.)
- [FTDI D2XX USB to Serial](https://ftdichip.com/wp-content/uploads/2021/08/CDM212364_Setup.zip)
- [DirectX June 2010 Redistributable](https://www.microsoft.com/en-us/download/details.aspx?id=8109)
- [Visual C++ 2012 Redistributable x64](https://www.microsoft.com/en-us/download/details.aspx?id=30679)
- [Visual C++ 2015-2022 Redistributable x64](https://aka.ms/vs/17/release/vc_redist.x64.exe)
- [Hay1tsme's ST](https://gitea.tendokyu.moe/Hay1tsme/segatools)
([Pre-built version, preconfigured](files/mercury-cab.zip))
### Helpful things
@@ -142,7 +144,7 @@ as shown in the picture.
> DANGER: **Do not change anything else!** You risk wiping your TPM key and make it impossible to boot from the
> original drive if you do!
Save and exit with F4 and select `Yes` when you are done.
Save and exit with <kbd>F4</kbd> and select `Yes` when you are done.
### Installing Windows
@@ -162,10 +164,10 @@ configuration should be the same as your preferred keyboard. For the privacy set
don't need any of that. It should now ask you for a username. This doesn't really matter, I just made mine `WACCA`.
**Leave the password blank so that the system will automatically log in and press Next.**
Wait a few moments and you should be presented with the Windows desktop. Ensure the files mentioned in the preface are
Wait a few moments, and you should be presented with the Windows desktop. Ensure the files mentioned in the preface are
your USB drive, and insert it back into the USB hub. You now want to run the 7-Zip installer, as many things will
require you to extract archives. Once you've done that, open 7-Zip, go to `Tools > Settings`, and change all the
extentions for your user to 7-Zip.
extensions for your user to 7-Zip.
Next, you'll want to run the MAS script. To extract it from its archive, you'll want to use the password `1234`. After
you run it, you'll want to select KMS38 and then select the first option. This will prevent Windows from screaming at
@@ -192,9 +194,9 @@ Now install the both Visual C++ Redists, and the DirectX Redist. Specify a path
### Serial Port Setup
Next, you should modify the buffer sizes for the COM ports on the ALLS. This is something that's done by the stock ALLS
system and it didn't seem to make much of a difference with or without it, but you might as well change it just to be
sure. Press <kbd>Win</kbd> + <kbd>X</kbd>, and open Device Manager from the list that appears. Open the `Ports` section, and do the following
for COM ports 1-4:
system, and it didn't seem to make much of a difference with or without it, but you might as well change it just to be
sure. Press <kbd>Win</kbd> + <kbd>X</kbd>, and open Device Manager from the list that appears. Open the `Ports` section,
and do the following for COM ports 1-4:
* Right click, click Properties
* Click Port Settings
@@ -204,8 +206,8 @@ for COM ports 1-4:
### Group Policy Changes
Next we will disable OneDrive and Windows Defender, as both of these are high memory background processes that just suck
up processing power for no real reason since this machine isn't a typical PC setup. To disable these components,
Next we will disable OneDrive and Windows Defender, as both of these are high memory background processes that will just
suck up processing power for no real reason, since this machine isn't a typical PC setup. To disable these components,
do the following:
* Press the Win key, type `group`, and open the entry that says `Edit group policy`.
@@ -216,7 +218,7 @@ do the following:
* Navigate back to the Windows Components section, and select `Windows Defender`.
* Double click on `Turn off Windows Defender` and set it to `Enabled` as well.
You should now reboot the machine **from the Start Menu** to make sure all of the changes have saved correctly.
You should now reboot the machine **from the Start Menu** to make sure all the changes have saved correctly.
> WARNING: Do not power cycle the cab until after the computer has shut down, as the changes may not save correctly.
----
@@ -234,73 +236,70 @@ choose `Rear Speaker Out` and disable the auto popup dialog. Press OK on both di
After that, shut down the system and flip the main cabinet power switch (by the test and service buttons). This is
mostly to make sure the file system changes are journaled correctly, as if they aren't, connecting the drive to another
computer will cause all files transfered to it afterwards to disappear when the system is booted again.
computer will cause all files transfered to it afterward to disappear when the system is booted again.
Now, detach the new drive from the system and connect it to your USB to SATA adapter, and then to your computer.
> DANGER: **Scary Red Text Zone**
> <span style="color: red; font-size: .8rem;">
> ***Again, as a reminder, do not under any circumstance connect the <ins>original</ins> drive to a Windows computer!***
> </span>
>! WARNING: **Old Method (kinda shitty)**
> *This part of the guide will be replaced soon, but it's alright to follow for now.*
>
> ----
>
> Once you have connected the drive, create a `WACCA` folder on the root of the drive, and then inside of it create
> another folder called `Reverse` (or whatever version you're using).
>
> **Please note, as of March 2023, SDFE 1.00.00 (Launch version) and all versions of SDJE (Chinese version) do not work with the configuration laid out in this guide.**
>
> Copy the game files into the directory you created. There should be folders named `bin`, `pxbin` and `WindowsNoEditor` in the folder, as well as a few files.
> **Eject the drive**, plug it back in to the cab, and power the cab on.
>
> Navigate to the folder with the game files, and then into the `bin` folder. Click View, and enable `File name extensions`, and click View again to hide the bar.
> Extract your copy of segatools into this folder. Now, in the address bar, it should say something like `This PC > Local Disk (C:) > WACCA > Reverse > bin`, click on the empty space to the right of bin,
> and type `write start.bat` and press Enter. Wordpad should open.
>
> In this document, copy the first taskkill line and paste it directly under, changing the exe to `explorer.exe`. Under the taskkill line at the bottom,
> add the line `start explorer.exe`. **If you are configuring a version that is pre-Lily (WACCA or WACCA S), you also need to change `Mercury-Win64-Shipping.exe` to `Mercury.exe`.**
> Save the file, if it asks you about text-only documents, select Yes. Close Wordpad, and now repeat the above steps to open `segatools.ini`
>
> In this file, you need to make a few changes as follows:
> - Change `enable` to 0 under the `[touch]` and `[elisabeth]` sections
> - Add `enable=0` under the `[io4]` section
> - Add an `[aime]` section at the bottom and add `enable=0` on that as well
>
> Save that file as well. We need to make additional configuration changes, but the files haven't been created yet so you have to launch the game.
> Launch the game by running `start.bat`. A big W should appear, the game should start, and the lights on the cab should light up. Both LED and Touch checks should be successful.
> It should then hang on the Network check, at this point you should press Alt+F4 to close the game.
>
> Open the file explorer again, and navigate back to the `bin` folder. There should now be an `appdata` folder. Navigate to `appdata\SDFE\Saved\Config\WindowsNoEditor`,
> right click on `Hardware.ini`, and click Edit. Add `OfflineMode=True` under the `[/Script/Mercury.MercuryNetworkSettings]` section and save the file.
>
> Start the game again, and note that the game now skips the network check and loads to the main menu successfully.
>
> Press the test button to open the test menu. Use the volume buttons to navigate up and down, and the test button to select. Navigate to `Device Test Menu > Test of Sound-Speaker`.
> Ensure the speakers are working by selecting `Replay BGM Sample`, picking `LEFT + RIGHT`. Plug some headphones into the jack to ensure that you can hear something from them as well.
> It will be quiet, but you should hear something. Once you have finished testing that, select `Return`.
>
> Navigate to `Test of Input Machine` and ensure the all of the panels light up as you touch them. Press test and service buttons at the same time to return.
> Navigate to `Test of Output Machine`, select `Control Panel LED` and ensure it lights up the front panel. Select `Aime Reader LED` and ensure that it also lights up.
> If it does not, consult the troubleshooting guide.
>
> Return back to the main test menu and navigate to `System Setting > Closing Time Setting`. Go down to `All Days of the Week` and change it until all of the times on the page say `OFF`.
> Select `Apply Settings and Reboot`. This will not actually reboot the system, it will only close the game.
>
> Now you have to set the game to automatically start when you start the cab. Press Win+R, type `regedit` and press Enter. Once it has opened, navigate to the
> `HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\IniFileMapping\system.ini\boot\` key. Double click the `Shell` value and change the `SYS:` to `USR:Software\`.
> Navigate to `HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\`. Right click in the empty area on the right, select `New > String Value`, and name it `Shell`.
> Set the value to `C:\WACCA\Reverse\bin\start.bat` **Ensure that you put the correct path for your configuration, because if you don't, the system will not boot correctly.**
Once you have connected the drive, create a `WACCA` folder on the root of the drive, and then inside of it create
another folder called `Reverse` (or whatever version you're using).
> SUCCESS: **New Method**
> Follow the setup instructions for the [WACCA Launcher](launcher.md) and then return here.
> FAILURE: **Unsupported versions**
> As of August 2023, **SDFE** 1.00.00 (Launch version) and all versions of **SDHN or SDJE** (Chinese version) do not
> work with the configuration laid out in this guide, due to missing support in ST.
Copy the game files into the directory you created. There should be folders named `bin`, `pxbin` and `WindowsNoEditor`
in the folder, as well as a few files. Navigate to the `bin` folder, and extract the ST zip into this folder.
Finally, you need to configure the cab's display for this new setup. Close all of the programs you have open, and then reopen NVIDIA Control Panel and navigate to `Display > Rotate display`.
If you are configuring a version that is pre-Lily (WACCA or WACCA S), you need to open the `start.bat` file
**with a text editor**, and change `Mercury-Win64-Shipping.exe` to `Mercury.exe`.
If you are ***not*** using the provided ST build, you will need to make some changes to `segatools.ini`:
- Change `enable` to 0 under the `[touch]` and `[elisabeth]` sections
- Add `enable=0` under the `[io4]` section
- Add an `[aime]` section at the bottom and add `enable=0` on that as well
**Eject the drive**, plug it back in to the cab, and power the cab on.
We need to make additional configuration changes, but the files haven't been created yet, so you have to launch the game.
Navigate to the folder you installed the game in, and launch it by running `start.bat`. A big W should appear, the game
should start, and the lights on the cab should light up. Both LED and Touch checks should be successful.
It should then hang on the Network check, at this point you should press <kbd>Alt</kbd>+<kbd>F4</kbd> to close the game.
Open the file explorer again, and navigate back to the `bin` folder. There should now be an `appdata` folder. Navigate
to `appdata\SDFE\Saved\Config\WindowsNoEditor`, right click on `Hardware.ini`, and click `Edit`. Add `OfflineMode=True`
under the `[/Script/Mercury.MercuryNetworkSettings]` section and save the file.
Start the game again, and note that the game now skips the network check and loads to the main menu successfully.
Press the test button to open the test menu. Use the volume buttons to navigate up and down, and the test button to
select. Navigate to `Device Test Menu > Test of Sound-Speaker`. Ensure the speakers are working by selecting
`Replay BGM Sample`, picking `LEFT + RIGHT`. Plug some headphones into the jack to ensure that you can hear something
from them as well.
It will be quiet, but you should hear something. Once you have finished testing that, select `Return`.
Navigate to `Test of Input Machine` and ensure all the panels light up as you touch them. Press test and service
buttons at the same time to return. Navigate to `Test of Output Machine`, select `Control Panel LED` and ensure it
lights up the front panel. Select `Aime Reader LED` and ensure that it also lights up. If it does not, consult the
troubleshooting guide.
Return back to the main test menu and navigate to `System Setting > Closing Time Setting`. Go down to
`All Days of the Week` and change it until all the times on the page say `OFF`. Select `Apply Settings and Reboot`.
This will not actually reboot the system, it will only close the game.
**If you are setting up multiple versions, repeat these steps for each version.**
Follow the setup instructions for the [WACCA Launcher](launcher.md) and then return here.
Finally, you need to configure the cab's display for this new setup. Close all the programs you have open, and then reopen NVIDIA Control Panel and navigate to `Display > Rotate display`.
Disconnect your monitor from the GPU and connect the cab's DVI cable. Press <kbd>Alt</kbd>+<kbd>Spacebar</kbd>, press <kbd>M</kbd>, and click and drag the window to the part of the display you can see.
Rotate the display to `Portrait (flipped)` and press Apply.
Reboot the system and the game should now start automatically. Congratulations, you've now set up your cab!
### TODO: Instructions for reassembling the cab, add shortcut to start game.
### TODO: Instructions for reassembling the cab
+9 -11
View File
@@ -15,37 +15,35 @@ Use DD to image the drive <https://linuxhint.com/make-disk-images-dd-command-lin
>
> Begin by installing lsscsi.
>
> `sudo apt install lsscsi`
> - `sudo apt install lsscsi`
>
> `lsscsi` lists all the drives plugged in, look for your wacca drive (if you have some kind of complex setup, do the command prior to plugging in the drive and then after to discover which one)
>
> `sudo fdisk /dev/sd<wacca-drive>`
> - `sudo fdisk /dev/sd<wacca-drive>`
>
> we want to access the wacca drive. replace `/dev/sd<wacca-drive>` with whatever you saw in the previous step
>
> `p`
> - `p`
>
> This will list all the partitions on the drive and the exact sector count. Important to note them.
>
> `q`
> - `q`
>
> quits out of fdisk
>
> `sudo dd if=/dev/sd<wacca-drive> of=/pathtostorage/wacca.img bs=100M conv=noerror`
> - `sudo dd if=/dev/sd<wacca-drive> of=/pathtostorage/wacca.img bs=100M conv=noerror`
>
> Creates a clone image of the specified input `if` to the specified destination `of`
>
> `ls -lh wacca.img`
> - `ls -lh wacca.img`
>
> Checks permission of the drive, should match the original
>
> `fdisk -l wacca.img`
> - `fdisk -l wacca.img`
>
> To compare the sector count, should match the original
> To compare the sector count, should match the original, then restore using
>
> then restore using
>
> `sudo dd if=<wacca.img> of=<newdrive> bs=100M conv=noerror`
> - `sudo dd if=<wacca.img> of=<newdrive> bs=100M conv=noerror`
>
> You'll want to restore on a 120gb or at most 240gb drive to be compatible with how a main storage format works at the moment. (but if you aren't doing that, any larger sized ssd can work)
>
+3 -1
View File
@@ -1,4 +1,6 @@
# Custom Charts
There's a chart editor called [BAKKA](https://github.com/Goatgarien/BAKKA-Editor/).
Join their discord for more information.
Join their discord for more information.
There also exists a browser-based chart visualizer called [MercuryPlayer](https://yellowberryhn.github.io/MercuryPlayer/), which can be used to view charts without opening them up in an editor. A nice way to preview charts made by others. The version linked specifically has support for previewing charts on a cab, if you so desire for whatever reason.
+1 -1
View File
@@ -1,5 +1,5 @@
# Custom LED Driver
<figure markdown>![WACCA LEDs](https://cdn.discordapp.com/attachments/568491469799817246/1144020876740808824/PXL_20230822_121850510.jpg)
<figure markdown>![WACCA LEDs](../img/custom_led_board_demo.jpg)
<figcaption>Look at how pretty this is! (don't mind the LED strip on the right)</figcaption>
</figure>
+1 -1
View File
@@ -16,7 +16,7 @@ So, you want to manufacture your own LED PCBs? Well, here's a good way to go abo
is SMD instead of THT. If you need THT, the previous August revision will do just fine.
2. [Download KiCad](https://www.kicad.org/download/)
3. Open `wacca_ws2813.kicab_pcb`.
4. `File` --> `Fabrication Outputs` --> `Gerbers (.gbr)`. Set your output directory appropriately.
4. `File > Fabrication Outputs > Gerbers (.gbr)`. Set your output directory appropriately.
5. Click `Generate Drill Files...` and ensure that the drill units are in millimeters.
Click `Generate Drill File` and `Generate Map File`.
6. Click `Plot`.
+10 -13
View File
@@ -3,10 +3,8 @@ getting color data, are dim, or are straight up not lit up. This is partly due t
There are a few good options for replacements:
[SpeedyLabs](https://www.speedylabs.us/product/wacca-ws2813-led-pcb/) is selling their revision of the PCB, you'll need
60 of them to replace all your touch units.
[CensoredUsername](https://docs.google.com/forms/d/e/1FAIpQLSfETDKtABUGxhhcBXFDWuHlz1cwHNNozOXztCPOOsENcN5KxA/viewform)
is another source for the EU.
[SpeedyLabs](https://www.speedylabs.us/product/wacca-ws2813-led-pcb/) is selling their revision of the PCB, you'll need 60 of them to replace all your touch units.
[CensoredUsername](https://docs.google.com/forms/d/e/1FAIpQLSfETDKtABUGxhhcBXFDWuHlz1cwHNNozOXztCPOOsENcN5KxA/viewform) is another source for the EU.
Alternatively, you can [make your own](led-pcb.md).
@@ -14,29 +12,28 @@ Alternatively, you can [make your own](led-pcb.md).
Remove the control panel by removing the single screw on the left and right side.
<details markdown="1"><summary>Click to show image</summary>
<details markdown><summary>Click to show image</summary>
![Control panel](https://cdn.discordapp.com/attachments/780283383069540393/1054935055333605457/PXL_20221221_013513863.jpg)
![Control panel](../img/console_side.jpg)
</details>
You don't need to remove the acrylic, just unplug the harnesses from inside the cab, feed them up,
and slide the control panel out.
<details markdown="1"><summary>Click to show image</summary>
<details markdown><summary>Click to show image</summary>
![Harnesses](https://cdn.discordapp.com/attachments/780283383069540393/1054948737845301338/PXL_20221221_022911966.jpg)
![Harnesses](../img/console_wire_harness.jpg)
</details>
After you have the outside plastic pieces taken off, disconnect the LED data only wires,
LED power on the middle LED board, and the touch board cable.
Then remove the two outside screws for the panel and pull it straight out.
<details markdown="1"><summary>Click to show image</summary>
<details markdown><summary>Click to show image</summary>
![Metal bracket screws](https://cdn.discordapp.com/attachments/780283383069540393/1054930972799414382/image.png)
![Metal bracket screws](../img/bracket_screws.png)
</details>
@@ -51,9 +48,9 @@ and pulling the tape through.
Be gentle here though, broken ribbons are no fun.
NOTE: You may need to remove the pop / marquee to get to the touch panels on the top of the machine.
This may require security torx bits.
This may require security Torx bits.
If the cab is powered on you will need to go to `CONNECTION TEST OF TOUCH DEVICES` and `RECONNECT TOUCH DEVICES` in the
test menu after re-connecting the touch board.
Video instructions: <https://youtu.be/iyhxQFl7XyE>
Video instructions: https://youtu.be/iyhxQFl7XyE
+121
View File
@@ -0,0 +1,121 @@
# WACCA Test Menu
The WACCA test menu has a lot of options, sometimes in confusing places. This page aims to explain what every option does. ***Not all of the options listed may be present in your version of the game.***
You can access the test menu by pressing the **TEST** button from inside the front panel of the cab when it's open.
## Test Menu
This is the menu you are initially presented with, which has a bunch of subcategories on it. You can scroll the list either by pressing the **SERVICE** button to scroll down, or use the **Volume Up and Down** buttons on the front of the cabinet next to the headphone jack (not the knob, lol). To select an item, press the **TEST** button with the item selected, which will be highlighted in red.
![](../img/test_menu.png)
## Credit Log
This menu shows you how many coin credits and service credits have cycled through the machine since the last counter reset. Pretty straight forward. **Under most circumstances, you don't want to be messing with this.**
![](../img/test_menu_credit_log.png)
### Credits Log Initialization
This option will reset all of the credit logs on the cab. There is a warning asking you if you're sure you want to perform this action. You probably don't.
## Log
This menu has a bunch of other logging data about plays, the status of the cab, and probably the most interesting to a cab owner, a log of errors encountered.
![](../img/test_menu_log.png)
### Total Play Log
This menu details how long the cab has been powered on, as well as play times. It provides the ratio of power on time to play time as a percentage, how many actual plays it's seen, the average time of a play session, freeplays, as well as another place that lists service credit count for some reason.
#### Average Play Times (Daily) {: #average-play-times-daily-total }
This menu provides a daily breakdown of the average plays for every play on the cab.
#### Average Play Times (Hourly) {: #average-play-times-hourly-total }
This menu provides a hourly breakdown of the average plays for every play on the cab.
### Play Log (Within The Period)
The name of this one is kinda confusing. This menu is similar to the Total Play Log menu, but it only shows the data since the last "period reset". The theoretical use of this is to be able to get a metric of how much playtime a cab is receiving starting from when you reset it.
#### Average Play Times (Daily) {: #average-play-times-daily-period }
This menu provides a daily breakdown of the average plays for every play within the period mentioned above.
#### Average Play Times (Hourly) {: #average-play-times-hourly-period }
This menu provides a daily breakdown of the average plays for every play within the period mentioned above.
### Play Count Log
This menu allows you to look at a per-day itemized log of how many sets were played, VIP memberships (bought?? used??), boosts used, as well as freeplay sets. Seems pretty useful.
### Service Switch Log
This menu logs the date and time of the last 20 times the service switch was used to add a service credit.
### Error Log
This menu logs the date and time of the last 20 errors encountered by the cab. This is where you can see a history of both blue or red errors.
## Device Test Menu
This menu is where many of the useful test menu stuff starts to come in. Here you can perform tests on the special hardware of the cab, as well as configure some settings.
### Test of Sound-Speaker
This menu has some options to test the playback of specific sounds, as well as adjusting the in-game (**Speaker Volume**) and attract volume (**Title Demo Volume**).
![](../img/test_menu_sound.png)
### Test of Input Machine
This menu can be used to test the individual sections on each touch panel, as well as testing the **TEST**, **SERVICE**, **Volume Up**, and **Volume Down** buttons on the cab. Each button press will start a timer to indicate for how long it was held. To exit this menu, you must press **TEST** and **SERVICE** simultaneously.
![](../img/test_menu_input.png)
### Test of Output Machine
In this menu you can test the lighting parts of the cab. Under the WACCA Console section, **All Lighting** will test the entire console at once, **Round Lighting** will test the 8 rows of LEDS independently, and **Lighting Separately** will run through each LED in order testing either forwards or backwards in sequence.
In menus with a list of choices on an option, to start changing an option, press **SELECT**, and then use either **SELECT** or **Volume Up/Down** to change the setting, and then press **TEST** to exit the selection.
![](../img/test_menu_output.png)
### Connection Test of Touch Device
This screen is similar to [Test of Input Machine](test-menu.md#test-of-input-machine), however this screen allows you to see the connection status of each of the 12 touch panels that make up the WACCA Console, as well as signal to the touch controller to reinitialize the touch panels, in case you disconnect one to work on it while the cab is still powered on. On this screen, you can also touch any of the panel sections to light the corresponding area on the ring displayed to test if they work and their sensitivity.
![](../img/test_menu_touch.png)
### Test of Color Display
This menu is used for display color calibration testing as well as display mounting position tests. Somewhat useful.
### Network Testing
TODO: come back and add something here.
### Test of Card Reader
This menu allows you to test the communications with the Aime card reader in the cab. You can scan cards here, and it should return success if it worked.
## Hardware Information
This menu tells you information about your cab's hardware. It provides you with the Housing ID, Aime reader firmware version, and touch controller firmware versions.
## System Setting
### Closing Time Setting
### Songs for 1-Play Setting
### Continue Times Settings
### Times for Free Time
### Event Mode Setting
### Language Setting (offline)
NOTE: This menu is only available in the offline mode patch, 3.10.00.
### Date and Time Setting
Binary file not shown.

After

Width:  |  Height:  |  Size: 588 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 586 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 244 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 61 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 3.8 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 2.4 MiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 360 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 717 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 359 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 672 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 230 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 224 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 307 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 243 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 233 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 226 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 255 KiB

+21 -19
View File
@@ -38,8 +38,10 @@ COM5: Keychip
COM6: Console Lights
```
Check out the [manual](manual.md) for more information about the system.
[Imaging Your ALLS Drive](../guide/alls-image.md)
Check out the [manual](manual.md) for more information about the system.
*See also:*
- [Imaging Your ALLS Drive](../guide/alls-image.md)
## Sound System
@@ -85,14 +87,14 @@ LFA150F-12-J1 150W 12V 50-60Hz 12.5A IN AC100-240V
LFA150F-5-J1Y 150W 5V 50-60Hz 30A IN AC100-240V
```
![Power supplies](https://github.com/jbamuro/waccamole/raw/main/img/DSC00812.JPG)
![Power supplies](../img/DSC00812.JPG)
These two units supply all the power needed for the PCB components (sound system, LEDs, touch controller etc).
My photos will look a little different at the bottom as we had to jerry rig an extension cable to feed power into the unit since I don't have the original cabling for it. Works fine on American power, there are also reports of it working fine in Europe.
R1 uses a 300VA but that's probably overkill.
![step down transformer](https://cdn.discordapp.com/attachments/267603668046446603/1045057845999173692/IMG_20221123_112537805_HDR.jpg)
![step down transformer](../img/r1_stepdown.jpg)
Hits about 200W during attract mode.
TODO: power info during songlist pull etc.
@@ -101,12 +103,12 @@ TODO: power info during songlist pull etc.
There are two of these and they each process 6 segments. Together they control the two halves of the touch controller assembly (for a total of 12 segments).
![Master Touch Unit Control Board](https://github.com/jbamuro/waccamole/raw/main/img/DSC00814.JPG "Master Touch Unit Control Board for the 6 segments on the right of the touch assembly (Can be determined thanks to it's ID, currently set to 8. The controller ID for the left segments is 7)")
![Master Touch Unit Control Board](../img/DSC00814.JPG "Master Touch Unit Control Board for the 6 segments on the right of the touch assembly (Can be determined thanks to it's ID, currently set to 8. The controller ID for the left segments is 7)")
Each segment of the touch controller is connected to the others with the help of RS485 through a ribbon cable.
The PCBs present on each segment are the exact same with the addition of a custom Pentel IC and some extra components needed to drive the tactile sensor array.
![Pentel IC](https://github.com/jbamuro/waccamole/raw/main/img/DSC00835.JPG "The custom Pentel IC handling tactile input")
![Pentel IC](../img/DSC00835.JPG "The custom Pentel IC handling tactile input")
*Here's a detailed component list of those boards :*
@@ -123,9 +125,9 @@ The PCBs present on each segment are the exact same with the addition of a custo
| RG1 | XC6206 662K 3.3V 0.5A Voltage regulator | 3.3V 0.5A Voltage regulator |
| RG2 | [178M05 91 03](https://datasheetspdf.com/pdf-file/614024/HitachiSemiconductor/178M05/1) | 5V 0.5A Fixed Voltage regulator |
<details markdown="1"><summary>Click to show a Top View picture of the PCB</summary>
<details markdown><summary>Click to show a Top View picture of the PCB</summary>
![Touch Unit Control Board](https://cdn.discordapp.com/attachments/568491469799817246/1143576271461302333/Top_View.jpg)
![Touch Unit Control Board](../img/Top_View.jpg)
</details>
@@ -133,7 +135,7 @@ The PCBs present on each segment are the exact same with the addition of a custo
It sends the pretty colors to the touch controller.
![LED Data board](https://github.com/jbamuro/waccamole/raw/main/img/DSC00813.JPG "An LED Data board, connected to the ALLS using usb")
![LED Data board](../img/DSC00813.JPG "An LED Data board, connected to the ALLS using usb")
Here's a rundown of what this board is made out of:
@@ -154,17 +156,17 @@ Pin 5 - 5V, VCC in
## 2.1ch Amp
![2.1 channel AMP](https://github.com/jbamuro/waccamole/raw/main/img/DSC00816.JPG "2.1 channel AMP (14-1466CR), Handles analog sound routing to subwoofer and tweeters")
![2.1 channel AMP](../img/DSC00816.JPG "2.1 channel AMP (14-1466CR), Handles analog sound routing to subwoofer and tweeters")
Handles analog sound routing to subwoofer and tweeters
## Headphone Amp
![Headphone Amplifier](https://github.com/jbamuro/waccamole/raw/main/img/DSC00815.JPG "Headphone Amplifier (00-1358AR), Handles audio output to the control panel")
![Headphone Amplifier](../img/DSC00815.JPG "Headphone Amplifier (00-1358AR), Handles audio output to the control panel")
Handles audio output to the control panel
## I/O Control Board (837-15257-01)
![I/O Control Board](https://github.com/jbamuro/waccamole/raw/main/img/DSC00817.JPG)
![I/O Control Board](../img/DSC00817.JPG)
The existence of this board is a bit overkill for what it's used for, likely it *had* to be used due to SEGA producing the cabinets for Marvelous. This is a newer version of the control board that has a USB port on it, almost all sega cabs use this now.
*Note: WACCA does NOT check for a coin counter, so the resistor trick is not needed to apply credits in game.*
@@ -188,7 +190,7 @@ The Aime card reader is model number **610-0955**. There are lots of good soluti
The touch controller assembly is composed of 12 segments divided into two halves
(6 per side, each having their own main controller board). They each have an individual channel ranging from 1 to 6.
![WACCA touch segment](https://media.discordapp.net/attachments/568491469799817246/1143565017216733204/PXL_20230822_151822250.jpg "Three segments on my small table")
![WACCA touch segment](../img/PXL_20230822_151822250.jpg "Three segments on my small table")
Each one of these weighs 1kg (2.2LBS) *(870g if the metal bracket is removed)* which totals to about 12kg (26LBS).
@@ -198,17 +200,17 @@ In total, there are 480 LEDs in the touch controller assembly
The sensor array is made out of 5 columns and 4 rows amounting to 20 touch zones par segment.
All 12 segments amount to a total of 240 touch zones.
![WACCA sensor array](https://cdn.discordapp.com/attachments/568491469799817246/1143575566423969812/Wacca_Sensor_Flexible_PCB_Lowres.png "A segment's touch sensor array. There are 12 of these.")
Click [here](https://cdn.discordapp.com/attachments/297114097546297354/1068442545727746078/Wacca_Sensor_Flexible_PCB-1.png) to download a higher resolution image.
![WACCA sensor array](../img/Wacca_Sensor_Flexible_PCB_Lowres.png "A segment's touch sensor array. There are 12 of these.")
Click [here](../img/Wacca_Sensor_Flexible_PCB-1.png) to download a higher resolution image.
Somehow I never really understood how MASSIVE these units are until I held an individual segment in my hand.
![This shit is massive](https://media.discordapp.net/attachments/568491469799817246/1143563743557591070/PXL_20230822_151247219.jpg "")
![This shit is massive](../img/PXL_20230822_151247219.jpg "")
Here are some scans of a segment that shows the curve profile.
<br><img src="https://github.com/jbamuro/waccamole/raw/main/img/concurve1.png" data-canonical-src="https://github.com/jbamuro/waccamole/raw/main/img/concurve1.png" width="150" height="150"/>
<img src="https://github.com/jbamuro/waccamole/raw/main/img/concurve2.png" data-canonical-src="https://github.com/jbamuro/waccamole/raw/main/img/concurve2.png" width="150" height="150"/>
<img src="https://github.com/jbamuro/waccamole/raw/main/img/concurve3.png" data-canonical-src="https://github.com/jbamuro/waccamole/raw/main/img/concurve3.png" width="150" height="150"/>
<br><img src="../img/concurve1.png" data-canonical-src="../img/concurve1.png" width="150" height="150"/>
<img src="../img/concurve2.png" data-canonical-src="../img/concurve2.png" width="150" height="150"/>
<img src="../img/concurve3.png" data-canonical-src="../img/concurve3.png" width="150" height="150"/>
### LED Boards
+72 -2
View File
@@ -1,7 +1,77 @@
---
title: WACCA Launcher
---
# WACCA Launcher
# Page under construction
WACCA Launcher is a tool that automatically launches the game for you
at startup, and also allows you to run multiple versions of WACCA on your cab and switch between them easily.
I'm still ironing out the details of the launcher, and then I have to write a guide too, so please be patient!
## Prerequisites
- Game files, set up with Hay1tsme's ST
- [The latest version of WACCA Launcher](https://github.com/YellowberryHN/WACCALauncher/releases/latest)
- Keyboard and mouse plugged into the cab
## Setup
NOTE: This guide assumes you already have your cab set up in a similar way to how is described in [the DiVER's Guide](guide.md).
Extract the `WACCALauncher.zip` into a folder outside your game files.
I personally have my folder structure set up like this:
```text
C:\
└─ WACCA\
├─ Offline\
│ └─ ...
├─ Reverse\
│ └─ ...
├─ Lily R\
│ └─ ...
├─ Lily\
│ └─ ...
├─ WACCA S\
│ └─ ...
├─ WACCA\
│ └─ ...
└─ <launcher files>
```
There should be a file called `wacca.ini`, you'll want to edit that file to point to the paths of your WACCA game files.
Here's what mine looks like
```ini
[general]
default_ver = reverse
num_customs = 1
[versions]
reverse = C:\WACCA\Reverse
lily_r = C:\WACCA\Lily R
lily = C:\WACCA\Lily
wacca_s = C:\WACCA\WACCA S
wacca = C:\WACCA\WACCA
offline = C:\WACCA\Offline
[custom_1]
path = C:\WACCA\CustomChartTesting
name = Reverse + Customs
type = reverse
```
You can confirm that the launcher works by starting `WACCALauncher.exe`. You should see some text that
says `LOADING...`. From here, it will load whatever you set as the default version in your config.
You can interrupt the startup if you press the `TEST` button inside the cab. This should bring up the WACCA Launcher
menu, where you can change your default version, as well as launch a version just once. You can navigate this menu just like you would navigate the test menu in-game.
Now you have to configure the cab to start the launcher when it boots. If you followed the folder structure described above, you should
just be able to run `SetShell.reg` and it will perform the below for you.
Press <kbd>Win</kbd>+<kbd>R</kbd>, type `regedit` and press Enter. Once it has opened, navigate to the
`HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\IniFileMapping\system.ini\boot\`
key. Double click the `Shell` value and change the `SYS:` to `USR:Software\`. Navigate to
`HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Winlogon\`. Right click in the empty area on the right,
select `New > String Value`, and name it `Shell`. Set the value to the full path of the `WACCALauncher.exe` file.
**Ensure that you put the correct path for your configuration, because if you don't, the system will not boot correctly.**
+1
View File
@@ -36,6 +36,7 @@ nav:
- Info:
- "The DiVER's Guide": guide.md
- Guides:
- Test Menu: guide/test-menu.md
- Replacing LED Boards: guide/led-replace.md
- DIY LED Boards: guide/led-pcb.md
- ALLS Drive Imaging: guide/alls-image.md