You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Differentiate "undo/skip split" from "previous/next image"
Skip/udo will now actually call command
This makes grouping option obsolete as user now has finer control anyway
UI is a bit cramped, but that should be resolved with UI revamp
Updated README
Copy file name to clipboardExpand all lines: README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,9 +33,9 @@ This program can be used to automatically start, split, and reset your preferred
33
33
34
34
- Microsoft Visual C++ 14.0 or greater may be required to build the executable. Get it with [Microsoft C++ Build Tools](https://visualstudio.microsoft.com/visual-cpp-build-tools/)
35
35
- Node is optional, but required for complete linting (using Pyright).
36
-
- Read [requirements.txt](/scripts/requirements.txt) for information on how to install, run and build the python code
36
+
- Read [requirements.txt](/scripts/requirements.txt) for more information on how to install, run and build the python code
37
37
- Run `.\scripts\install.bat` to install all dependencies
38
-
- Run the app directly with `py .\src\AutoSplit.py [--auto-controlled]`
38
+
- Run the app directly with `.\scripts\start.bat [--auto-controlled]`
39
39
- Run `.\scripts\build.bat` to build an executable
40
40
- Recompile resources after modifications by running `.\scripts\compile_resources.bat`
41
41
@@ -59,9 +59,9 @@ This program can be used to automatically start, split, and reset your preferred
59
59
- Once you are happy with your capture region, you may unselect Live Capture Region to decrease CPU usage if you wish.
60
60
- You can save a screenshot of the capture region to your split image folder using the Take Screenshot button.
61
61
62
-
## Max FPS
62
+
## Avg. FPS
63
63
64
-
- Calculates the maximum comparison rate of the capture region to split images. This value will likely be much higher than needed, so it is highly recommended to limit your FPS depending on the frame rate of the game you are capturing.
64
+
- Calculates the average comparison rate of the capture region to split images. This value will likely be much higher than needed (unless you [Force Full-Content-Rendering](#Full-Content-Rendering)), so it is highly recommended to limit your FPS depending on the frame rate of the game you are capturing.
65
65
66
66
## OPTIONS
67
67
@@ -72,6 +72,10 @@ This program can be used to automatically start, split, and reset your preferred
72
72
- Histograms: An explanation on Histograms comparison can be found [here](https://mpatacchiola.github.io/blog/2016/11/12/the-simplest-classifier-histogram-intersection.html). This is a great method to use if you are using several masked images.
73
73
- pHash: An explanation on pHash comparison can be found [here](http://www.hackerfactor.com/blog/index.php?/archives/432-Looks-Like-It.html). It is highly recommended to NOT use pHash if you use masked images. It is very inaccurate.
74
74
75
+
### Full Content Rendering
76
+
77
+
- Certain windows (namely hardware accelerated ones) won't always render their content. To work around this, you can "Force Full Content Rendering". This option is not reocmmended unless you really need it. It will cause a 10-15x performance drop based on the size of the complete window that's being captured (not the selected region, but rather the actual window size). It can also mess with some applications' rendering pipeline.
78
+
75
79
### Show Live Similarity
76
80
77
81
- Displays the live similarity between the capture region and the current split image. This number is between 0 and 1, with 1 being a perfect match.
@@ -142,11 +146,9 @@ The start image is similar to the reset image. You can only have one start image
142
146
- All of these actions can also be handled by their corresponding buttons.
143
147
- Note that pressing your Pause Hotkey does not serve any function in AutoSplit itself and is strictly used for the Pause flag.
144
148
145
-
### Group dummy splits when undoing / skipping
146
-
147
-
If this option is disabled, AutoSplit will not account for dummy splits when undoing/skipping. Meaning it will cycle through the images normally even if they have the dummy flag `{d}` applied to them.
149
+
### Dummy splits when undoing / skipping
148
150
149
-
If it is enabled, AutoSplit will group dummy splits together with a real split when undoing/skipping. This basically allows you to tie one or more dummy splits to a real split to keep it as in sync as possible with the real splits in LiveSplit/wsplit.
151
+
AutoSplit will group dummy splits together with a real split when undoing/skipping. This basically allows you to tie one or more dummy splits to a real split to keep it as in sync as possible with the real splits in LiveSplit/wsplit. If they are out of sync, you can always use "Previous Image" and "Next Image".
150
152
151
153
Examples:
152
154
Given these splits: 1 dummy, 2 normal, 3 dummy, 4 dummy, 5 normal, 6 normal.
@@ -192,13 +194,11 @@ The AutoSplit LiveSplit Component will directly connect AutoSplit with LiveSplit
192
194
- Click the Browse buttons to locate your AutoSplit Path (path to AutoSplit.exe) and Settings Path (path to your AutoSplit `.pkl` settings file) respectively.
193
195
- If you have not yet set saved a settings file, you can do so using AutoSplit, and then go back and set your Settings Path.
194
196
- Once set, click OK, and then OK again to close the Layout Editor. Right click LiveSplit -> Save Layout to save your layout. AutoSplit and its settings will now open automatically when opening that LiveSplit Layout `.lsl` file.
195
-
- If you are using any dummy splits, it is recommended that you check the "Group dummy splits when undoing / skipping" checkbox when using LiveSplit integration so that your LiveSplit splits stay in sync with AutoSplit.
196
197
197
198
## Known Limitations
198
199
199
200
- For many games, it will be difficult to find a split image for the last split of the run.
200
201
- The window of the capture region cannot be minimized.
201
-
- Capturing a hardware accelerated window or using Windows 11 altogether will cause performance drops. But as long as the window you are capturing (not the selected region, but rather the actual window size) is not too large, you should still be able to obtain a Max FPS of over 60.
0 commit comments