"Cannot detect the reference pattern" (VS 2017)
isaksky opened this issue · 7 comments
I get this error when trying to use it on Visual Studio 2017, Windows 10 after hitting benchmark and switching to a Visual Studio code file:
I tested with Notepad++ and that works.
I'm getting the same result in both VS Code, atom, and vim.
Edit: here are my environment specs for good measure, too
- Distro: Arch Linux
- Window Manager: i3wm
- Compositor: compton (also attempted with compton disabled)
- Java: jre9-openjdk
Also tried to run this test with and without a ligature font (Fira Code vs DejaVu Sans Mono), with the same result each time
I have the same problem in Vim.
Arch, i3, jre10-openjdk.
Same issue on macOS (also VIM).
Env: macOS HighSierra: 10.13.3 (17D102)
VIM:
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Jul 26 2017 19:10:24)
Included patches: 1-503, 505-642
Compiled by root@apple.com
Same problem using vim and nano. Arch Linux, KDE plasma 5.15.3, jre10-openjdk, and Suckless Terminal set to solid underscore cursor. Hack font, pixelsize 13, xorg 1.20.4.
I see it type and remove the 5 dots.
Hoping these screenshots might help. These are empty, but I tried some also with data in editor. The first screenshot shows a block cursor, which st shows when it's not focused. Don't know if typometer grabs its before screenshot before or after it switches back to a solid bar cursor when I give it focus.
Tried all combinations of "Native API" and "Async"
Tried setting Hack font pixelsize 40. Tried using Oxygen Mono pixelsize 40.
Tried running through terminal Terminator. Tried xterm, with its default white background and black text.
EDIT: I am running 5 monitors, rotated 90 degrees counter-clockwise. I'm maximizing the terminal on one of those monitors.
It would be nice if this happens for it to ask if the images should be saved to disk.
It would also be nice if more specific output could be given.
There are different reasons for these to occur, and indeed the output is not helpful at all.
@jamespharvey20 in your case, the dot distance seems uniform, but the anti-aliasing is too noticeable. Can you try increasing the font size and/or disabling anti-alias?
Aside, I have a fork where I worked out color tolerance in the metric detection (see frarees@0bb2818). You could give it a try and see if it helps in your setup.
I have the same issue. And did some debugging and found that the error is caused by the Robot.createScreenCapture call returning a black screen. My environment is on Ubuntu with Wayland. It turns out it's a bug in JDK: https://bugs.openjdk.org/browse/JDK-8269245.
And it seems related to #8 as well.