docs: update translation

This commit is contained in:
MistEO
2022-06-18 21:33:47 +08:00
parent bf180e1252
commit c8a77f2869
4 changed files with 11 additions and 11 deletions

View File

@@ -54,7 +54,7 @@ Talk is cheap. Show me the pictures!
### Basic Settings
1. Follow the [Simulator Support](docs/en/SIMULATOR_SUPPORT.md) to configure your simulator.
1. Follow the [Emulator Support](docs/en/EMULATOR_SUPPORTS.md) to configure your emulator.
2. Unzip the archive file to an **ASCII-only** directory
3. All settings are not changeable after running except `Auto shutdown`.

View File

@@ -13,7 +13,7 @@
1. Download and install `Visual Studio 2022 Community`. Select `Desktop development with C++` and `.NET Desktop Development`.
5. Double-click to open the file `MeoAssistantArknights.sln`. Visual Studio will load the project automatically.
6. Run a build to test whether the development environment has been configured correctly. Chosse `Release` & `x64`, right-click `MeoAsstGui` to set it as the startup project, and run it. If the build is successful, the `MeoAsstGui` window will appear. You can connect to the simulator in order to confirm again that the development environment has been configured correctly.
6. Run a build to test whether the development environment has been configured correctly. Chosse `Release` & `x64`, right-click `MeoAsstGui` to set it as the startup project, and run it. If the build is successful, the `MeoAsstGui` window will appear. You can connect to the emulator in order to confirm again that the development environment has been configured correctly.
7. Now you are free to contribute to MAA.
8. Remember to commit once you have proper number of changes. Don't forget to write a commit message.
9. After development, push your local changes to the remote (of your repository).

View File

@@ -1,4 +1,4 @@
## Simulator Support
## Emulator Supports
### Bluestack
@@ -14,7 +14,7 @@ Compatible.
- Turn on `Settings` - `Advanced` - `Android Debug Bridge`.
- Bluestack Hyper-V port changes frequently. Here is a simple hack:
1. Find `bluestacks.conf` in the installation location of the simulator.
1. Find `bluestacks.conf` in the installation location of the emulator.
2. Launch MAA, which generates `gui.json`. Open it.
3. Add a new field `Bluestacks.Config.Path`, with the value of the full path of `bluestacks.conf` (backslash should be escaped like `\\`).
4. LinkStart!
@@ -33,7 +33,7 @@ Compatible but:
- Requires MAA to "Run as Administrator" to get ADB path and address (since MuMu runs as admin).
- You can also fill in the ADB path and address if you do not wish to run as admin.
- It has a chance that MAA may stuck at the main screen and prompt mission failed, which is probably related to the rendering method of MuMu. Recommend to change other simulator.
- It has a chance that MAA may stuck at the main screen and prompt mission failed, which is probably related to the rendering method of MuMu. Recommend to change other emulator.
### MuMu Mobile Game Assistant

View File

@@ -15,20 +15,20 @@
### Connection error/not knowing how to fill in ADB path
Tips: please refer to the [Usage](../README-en.md#Usage) section to ensure that you are using your simulator correctly.
Tips: please refer to the [Usage](../README-en.md#Usage) section to ensure that you are using your emulator correctly.
#### Approach 1
1. Make sure that MAA `Settings` - `Connection Settings` - `adb path` is automatically filled in, if it has been filled in, please ignore this step. If not filled in:
- Option 1: Find the installation path of your simulator, where there may be a file named `adb.exe` (or something similar, e.g. `nox_adb.exe`, `HD-adb.exe`, `adb_server.exe`, etc., EXE files with `adb`). Simply choose the file in the connection settings of MAA!
- Option 1: Find the installation path of your emulator, where there may be a file named `adb.exe` (or something similar, e.g. `nox_adb.exe`, `HD-adb.exe`, `adb_server.exe`, etc., EXE files with `adb`). Simply choose the file in the connection settings of MAA!
- Option 2: Download [adb](https://dl.google.com/android/repository/platform-tools-latest-windows.zip) and unzip it, select the `adb.exe`
2. Confirm that your connection address is filled in correctly, you can Google what the adb address of the emulator you are using is generally in a format like `127.0.0.1:5555`
#### Approach 2
Change another simulator, such as [Bluestacks international version](https://www.bluestacks.com/download.html) Nougat 64 bit
Change another emulator, such as [Bluestacks international version](https://www.bluestacks.com/download.html) Nougat 64 bit
#### Approach 3
@@ -39,13 +39,13 @@ Try restarting your computer
Tip 1: The `Current Stage` of auto battle that costs Sanity requires you to go to the screen with the start button. Please confirm they are not related.
Tip 2: Follow the steps below until the problem is solved.
1. Confirm that your simulator is supported in the [List of the Supported Simulators](List of the Supported Simulators.md).
1. Confirm that your emulator is supported in the [List of the Supported Emulators](EMULATOR_SUPPORTS.md).
2. Change the DPI to `320 dpi`.
3. Change the resolution to landscape, `1280 * 720`.
4. Try with another simulator, such as [Bluestacks international version](https://www.bluestacks.com/download.html) Nougat 64 bit. (Please note that you are required to switch on ADB in Bluestack simulator.)
4. Try with another emulator, such as [Bluestacks international version](https://www.bluestacks.com/download.html) Nougat 64 bit. (Please note that you are required to switch on ADB in Bluestack emulator.)
5. Submit an issue to us if the problem still exists.
### Custom Connection
- Download [adb](https://dl.google.com/android/repository/platform-tools-latest-windows.zip) and unzip it.
- Go to `Settings` - `Connection Settings`, and select the location of `adb.exe`, fill in the address of ADB (with the format of IP+port, e.g. `127.0.0.1:5555`), and choose the type of your simulator.
- Go to `Settings` - `Connection Settings`, and select the location of `adb.exe`, fill in the address of ADB (with the format of IP+port, e.g. `127.0.0.1:5555`), and choose the type of your emulator.