- User Since
- Feb 10 2019, 4:01 AM (10 w, 2 d)
Thu, Apr 11
Hope I'm not encroaching, but I had a look at it too. Changing Render Settings > Shadows > Method from ESM to VSM seems to solve it for me. Presumably a limitation of the ESM algorithm? Seems like an unrelated issue to the one originally reported?
Your Light has its Clip Start set to 1 meter, so the start of the shadow is casting from around half way down the box. If you reduce the Clip Start to something lower, it'll fix it. Or move the top of the box down, away from the light.
Wed, Apr 10
This sounds similar to what I was seeing in T61389 - but in my case it was an Array modifier used inside a collection instead of parenting. Perhaps it's the same root cause though?
Wed, Apr 3
Tue, Apr 2
Forgive cross-posting on this one, but the other task is unassigned so I don't know if it'll get seen.
I downloaded the 2.8 source and edited the GHOST_WindowWin32.cpp file and made a patch that removes the WS_POPUP flag references and changed the getState() function logic that determines what state the Blender window is currently in (I think?). Instead of checking for WS_POPUP, it now checks if the window has both WS_DLGFRAME and WS_MAXIMIZE, as WS_DLGFRAME doesn't seem to be present when in fullscreen, according to WinExplorer. I don't know if that's a safe way of doing things as I have no experience in this area and this is the first time I've ever done this.
Sat, Mar 30
So I've done some poking around and testing with an old freeware app called WinExplorer, which lets you inspect and alter various window state/style properties. Here's what I've found:
Mar 21 2019
@LazyDodo (LazyDodo) apologies, wasn't my intention. Just seemed that whatever is causing the flicker and the other windows/message boxes being hidden were both related to the same issue, as the fullscreen behaviour seems different compared to 2.79. I see a very similar flicker other applications/games that use a fullscreen context instead of a borderless window.
@LazyDodo (LazyDodo) are you able to confirm the issue when opening the preferences window too? E.g. the window appears behind/invisible, but is actually there and clickable? It seems to be about 80% of the time, if done repeatedly.
Mar 20 2019
Another dupe of T59802 ?
Mar 16 2019
Already reported here: T59802
Mar 14 2019
I thought this was intentional? It works well if you're using a boolean workflow and want to see your mesh, or drawn a reference outline or an outlined custom bone handle or something...
Mar 12 2019
I've been seeing this for a while too. It shows the verts on the mesh, but the selection acts like you're selecting edges, like the selection mode and the selection type are out of sync.
Feb 10 2019
Same issue here, since the earliest builds, screen flickers black when opening Preferences (appears in front momentarily and then disappears until alt-tab), switching Shading modes or doing things like adding Materials. No issue with 2.79b or earlier. GTX 1080/Win 10.