Interface not working on my Windows 10 pc

popojan / goban

3D igo/baduk/weiqi/go game board and GUI for GnuGo and other GTP engines ray traced by GLSL shader

https://hraj.si/goban

GNU General Public License v3.0

47 stars 3 forks source link

Interface not working on my Windows 10 pc #22

Closed gebeleizis closed 4 years ago

gebeleizis commented 4 years ago

I've been trying to run the app, but what I'm getting is this: goban 2020-05-20 10-23-18-11 Any help would be greatly appreciated! Thank you very much in advance!

popojan commented 4 years ago

Looks familiar, please see #4, and then let's have a look on your graphics card specs.

gebeleizis commented 4 years ago

I checked the post and the fix with the graphic card. Unfortunately, I can't find out in what file is the default card set. My laptop uses an Intel HD Graphics 520 card.

popojan commented 4 years ago

Well, it might even be the only graphics card in your laptop. Good opportunity to find out what is wrong with the shader on some integrated cards.

Please try:

switching to other shaders using V key (is the flat one with gray background also distorted?)
look for error message in the black background window when goban starts
run dxdiag and save the report, attach it if you don't mind
report of opengl capabilities would be most helpful, if you didn't mind installing a tool like https://www.realtech-vr.com/home/glview

It probably has to do with goban grid lines antialiasing...

popojan commented 4 years ago

Please substitute data/glsl/fragment.glsl with this file: fragment.glsl.txt (remove the .txt extension) and let me know, if anything changed. Thank you.

gebeleizis commented 4 years ago

No error messages on background except 2 warnings related to the sound (but the sound works OK). The dxdiag got me the parameters below: Capture Changing the fragment.glsl file didn't make any difference. I also find curious that an app this small takes a dozen seconds or more to start on my pc. The result ov pressing the V key: goban 2020-05-20 13-54-57-94 goban 2020-05-20 13-54-45-77 I really appreciate all your help. Please take your time to reply, it's not urgent. I'm puzzled myself about the app behavior, as I've never had such issues with any software on this pc.

popojan commented 4 years ago

OK. Thank you for your patience. The long start is caused by slow compilation of the huge single-file shader (not a good practice by it was my design choice to implement all the geometry there), Subsequent starts should be faster, as your card should cache the compiled fragment shader code (until you change it). I will prepare several other versions of the shader and politely ask you to try them one by one to narrow down the issue.

Have you tried placing stone on such broken board? Please do.

gebeleizis commented 4 years ago

Placing stones works fine. I can also hear the sound. However, they look like this ^_^: goban 2020-05-20 14-13-33-64

popojan commented 4 years ago

Thank you, that is another clue for me :-)

popojan commented 4 years ago

One more thing to try before I delve deep into the shader mess. Please replace precision lowp float; by precision highp float; in both data/glsl/fragment.glsl and data/glsl/vertex.glsl. It sits on second line in either file. (Be careful if editing in notepad, it must not add .txt extension). Thank you.

gebeleizis commented 4 years ago

Amazing! It worked like a charm! Thank you very, very much! You've made a great piece of software for the lovers of GO!

popojan commented 4 years ago

Thank you! I am glad it helped.

I will increase the default precision in the next release. It is easier than making the code numerically robust :)

Please do not hesitate to report other bugs or glitches, the software is in early stage of development - considering features and quality of the code base, not time it's been in existence.