Page 1 of 1

GUI blinks constantly blue/grey

PostPosted: 03 Aug 2016, 08:47
by mryome
Hello

I encounter a problem that is probably due to my graphic chipset. When using Black Ink, the user interface blinks constantly. The boxes containing tools become blue, then go back to grey (the original color).
I tried to change the DirectX version used but the problem is still there.

I run this on a Intel HD 5500 with a Core i7-5600 and 8 Gb RAM and a 1920x1080 (14") screen.
I've updated my graphic card driver.

Here are the first lines of the BlackInk.log file:
--- Harmony LogFile ---

<HARMONY> Application = BlackInk Beta ( WinMain.cpp Ln 27 )
<HARMONY> Version = 0.249.2089 ( WinMain.cpp Ln 29 )
<HARMONY> OS = Microsoft Windows 10 Professionnelversion 6.2 '' (Build 9200) ( BlackInkWnd.cpp Ln 309 )
<HARMONY> Processor type = Intel(R) Core(TM) i7-5600U CPU @ 2.60GHz / Intel64 Family 6 Model 61 Stepping 4 / GenuineIntel / 2594MHz ( BlackInkWnd.cpp Ln 311 )
<HARMONY> Memory = 7.70 Go ( BlackInkWnd.cpp Ln 315 )
<HARMONY> NbTask Thread = 3 ( BlackInkWnd.cpp Ln 321 )
<HARMONY> Keyboard layout = French ( 0000040C ) ( BlackInkWnd.cpp Ln 329 )
<HARMONY> D3D11 API is available ( BlackInkWnd.h Ln 472 )
<HARMONY> D3D10 API is available ( BlackInkWnd.h Ln 472 )
<HARMONY> D3D9 API is available ( BlackInkWnd.h Ln 472 )
<HARMONY> GL41 API is available ( BlackInkWnd.h Ln 472 )
<HARMONY> LoadCacheDatabaseIfPossible ( in r2dCachedShadersEx, r2dCachedShadersEx.cpp Ln 365)
<HARMONY> Database loaded at 'C:\Users\gmeunier\AppData\Roaming\Bleank\BlackInk\Cache\Shaders.cache' ( in r2dCachedShadersEx, r2dCachedShadersEx.cpp Ln 396)
<HARMONY> StartSplashScreen ( BlackInkWnd.cpp Ln 414 )
<HARMONY> StartSplashScreen -> Finished ( BlackInkWnd.cpp Ln 420 )
<HARMONY> Try to load D3D11 ( BlackInkWnd.h Ln 498 )
<HARMONY> Frame[000000000000] ( BlackInkWnd.cpp Ln 119 )
<HARMONY> Wintab interface version 1.4, nbdevices =1, nbcursors=6 ( in d2dTabletInput, d2dTabletInput.cpp Ln 429)
<HARMONY> lcName =

Thank you for your help.

Re: GUI blinks constantly blue/grey

PostPosted: 04 Aug 2016, 09:52
by u2bleank
:desperate: Yes it's a know problem and we will work on it for the next release. Thanks for the report indeed.