Page 1 of 2
Problem mit the board
Posted: Tue Dec 27, 2016 5:49 pm
by BHGP
Hi,
quite often the board in COW is destroyed, look for this screenshot:

- COW_Board.JPG (55.74 KiB) Viewed 17454 times
Bernd
Re: Problem mit the board
Posted: Tue Dec 27, 2016 6:13 pm
by MikeCrockett
Yes, I had this problem too using Build 66 on a Windows 10 machine. It seems to occur when starting a new eBook. I sent Mike a bug report on it but I don't know if he's seen it yet.
I was able to get past the issue by clicking on one of the candidate moves. Once I did that, the graphics corrected itself. In your screen shot you have the move 1. e4 showing. Try clicking that and see if it helps correct the problem.
Re: Problem mit the board
Posted: Wed Dec 28, 2016 3:48 pm
by MikeAtBookup
Thanks for reporting this one. One person reporting such a strange this is an anomaly. Two people are a pattern.
I've not been able to reproduce this problem and I don't have a guess as to what might be causing it.
I'm glad it goes away as soon as the diagram is re-drawn.
Re: Problem mit the board
Posted: Tue Jan 03, 2017 3:09 am
by cfan
MikeCrockett wrote:Yes, I had this problem too using Build 66 on a Windows 10 machine. It seems to occur when starting a new eBook. I sent Mike a bug report on it but I don't know if he's seen it yet.
I was able to get past the issue by clicking on one of the candidate moves. Once I did that, the graphics corrected itself. In your screen shot you have the move 1. e4 showing. Try clicking that and see if it helps correct the problem.
I have the same problem on Windows 10. Mike's solution fixes the display.
Re: Problem mit the board
Posted: Fri Jan 13, 2017 7:21 pm
by MikeAtBookup
I'm curious as to whether build 68 still behaves this way on your Windows 10 computer.
Re: Problem mit the board
Posted: Fri Jan 13, 2017 8:31 pm
by MikeCrockett
MikeAtBookup wrote:I'm curious as to whether build 68 still behaves this way on your Windows 10 computer.
Mike - I'm still using version 66 and I'm on day 12 of a 13 day eBook rebuild that got corrupted from a PGN import. Unfortunately I had not done a back-up to fall back to.
Anyway, when this finishes, I will install your latest release and get back to you. I wanted to mention that the display issue might be a Windows 10 Video Card / Driver issue. There reason I think so, I was recently looking at some games on chess.com and had a very similar display issue with the chess board graphic using Microsoft Edge. The issue might not be with COW itself, but with the video card/driver.
My Toshiba Satellite is using a Intel(R) HD Graphics 3000 display adapter. Driver version 9.17.10.4229.
Re: Problem mit the board
Posted: Sat Jan 14, 2017 11:57 am
by MikeAtBookup
Yeah, I'd recommend making a backup copy of any important ebook before doing anything with a big impact (such as a large PGN import).
Thanks for the heads up on the graphics card driver idea. Ultimately I'd like the program to work great no matter what the graphics card might do in the optimization department. COW isn't rendering 3D full motion.

Re: Problem mit the board
Posted: Sat Jan 14, 2017 8:41 pm
by MikeCrockett
MikeAtBookup wrote:Thanks for the heads up on the graphics card driver idea. Ultimately I'd like the program to work great no matter what the graphics card might do in the optimization department. COW isn't rendering 3D full motion.

Mike, I installed COW Version 68 on Microsoft Windows 10 and, so far, I was not able to reconstruct the distorted graphics issue. It's hard to say if the new release actually fixes the issue or not, but so far, so good. We can keep our fingers crossed and hope no one else encounters the same issue and we can call it good.
Re: Problem mit the board
Posted: Mon Jan 16, 2017 1:37 am
by cfan
MikeAtBookup wrote:I'm curious as to whether build 68 still behaves this way on your Windows 10 computer.
Mike
I still have the problem with build 68, but not always (Windows 10). Resizing the board also cause the display to be corrupted.
Re: Problem mit the board
Posted: Wed Jan 18, 2017 4:25 pm
by MikeAtBookup
T'hanks for that feedback. I imagine it's a driver problem. I will have to test on a number of Windows 10 machines, resizing the diagram until I can get it to happen here.