Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

报告一起0613版的假杀 #8

Open
fsssosei opened this issue Aug 2, 2023 · 4 comments
Open

报告一起0613版的假杀 #8

fsssosei opened this issue Aug 2, 2023 · 4 comments

Comments

@fsssosei
Copy link

fsssosei commented Aug 2, 2023

h8h9h6i10i6i9g9g8j11i7i8k8j9h7j7j8h10f8f7l10g6f6k10l8l11m12j12i11j13j10k9l9m8m13h5i4k6j6i5j5k11i13i12k14l6n11j15j14g4f3m10o10l13h12g11
这个用拉菲230613版,默认参数未改过,启用了数据库,点扫描防守算出g2防点有杀守不住
给出的线路如下
g2j4k3e11h3f1i14n9k12h14e4d5i3g3f11f9g13f14d12m6n7d7e8d8d9c7e7d6d4c4m14l14c8e5f4e9f10g10h11n6o6l12l15e6b3b6a5b8a9c6a6c5c3
实际线路末端无杀。拉菲以为是四三了,实际横线不是活三而是会长连。“没看到”长连而假杀

关于复现
删除给出的错误线路后,点计算,给出了一个同样长度M67的杀,这次给的线路是真杀了

上一个版本拉菲230112
同样局面,点计算,给出了一个M27的杀线路,并且是真杀
但数据库内容不一样,所以不好评价两个版本如何

@dhbloo
Copy link
Owner

dhbloo commented Aug 3, 2023

Hi, 我使用230613版测试了一下,貌似没能复现这个假杀问题
分别用以下两个局面测试(分别开启和不开启数据库),都没能出现:

h8h9h6i10i6i9g9g8j11i7i8k8j9h7j7j8h10f8f7l10g6f6k10l8l11m12j12i11j13j10k9l9m8m13h5i4k6j6i5j5k11i13i12k14l6n11j15j14g4f3m10o10l13h12g11
h8h9h6i10i6i9g9g8j11i7i8k8j9h7j7j8h10f8f7l10g6f6k10l8l11m12j12i11j13j10k9l9m8m13h5i4k6j6i5j5k11i13i12k14l6n11j15j14g4f3m10o10l13h12g11g2j4k3e11h3f1i14n9k12h14e4d5i3g3f11f9g13f14d12m6n7d7e8d8d9c7e7d6d4c4m14l14c8e5f4e9f10g10h11n6o6l12l15e6b3b6a5b8a9c6a6

你可以找到一种稳定复现这个bug的方法吗?(最好是不开启数据库时能复现该bug的步骤)

@fsssosei
Copy link
Author

fsssosei commented Aug 3, 2023

我又试了试
这玩意随机性不低
默认settings.txt,只在yixing界面设置里设置了检查VC2

刚不开数据库,用扫描防守试了三次(每次都新开yixing),分别给出M40、M42、M52三种线路,和报告时一样,都是真杀,没有问题
然后开数据库,(每次都新开yixing)先删除分支,再点扫描防守,当发现G2出现M就点停,这样,复现了两次假杀。但给出的线路每次不一样
我把整个连数据库打包发你信箱,你看看

@fsssosei
Copy link
Author

fsssosei commented Aug 7, 2023

发现拉菲的假杀问题可能不是版本差异造成的,而是使用数据库后,算类似局面,就可能冒出假杀状况
因为刚刚使用230112版,也出现了假杀,同样是开启数据库时

@dhbloo
Copy link
Owner

dhbloo commented Aug 7, 2023

目前不太清楚是什么原因造成了这个问题,等后续有时间的时候我再仔细检查一下

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants