- User Since
- Jan 22 2019, 4:19 PM (87 w, 2 d)
Feb 10 2020
Yes. It reproduced with Default setings too (I've checked on same 2.83 version as iw was last time )
But have 1 small difference. With default settings effect not so intensive and strong without X-ray mode.
Jan 30 2020
On new graphics card: Radeon RX 570 Series ATI Technologies Inc. 4.5.13586 Core Profile Context 19.12.3 26.20.15003.5016
and version: 2.82 (sub 6), branch: master, commit date: 2020-01-27 18:52, hash: rB507a331f0182 and 2,83
Jan 28 2020
Hi @Richard van der Veen (richard) Antalik
Dec 24 2019
🤔 I think @Daniel Bystedt (dbystedt), you know better what to do whith this task for further(if it will not reproduce by anyone)...
I've checked it just right now with (version: 2.81 (sub 16), branch: master, commit date: 2019-11-20 14:27, hash: rB26bd5ebd42e3) and it still reproduce.
Then I've checked it on last fresh (version: 2.82 (sub 6), branch: master, commit date: 2019-12-23 08:34, hash: rB708045eb40b9 ) and it still reproduce.
Nov 9 2019
Sep 11 2019
Thanks Michael. :)
To the developers: but in the file not only one shadow bug, but a couple another related too, I think. So check the file definitely
Aug 1 2019
Yes. For last version it is reproducable(win-64): version: 2.80 (sub 75), branch: master, commit date: 2019-07-29 14:47, hash: rBf6cb5f54494e
Jul 17 2019
Jun 17 2019
In last update (2019-06-16 23:08, hash: rB12da679fa094) bug gone. So I'm closing task
Jun 13 2019
@Sebastian Parborg (zeddb) I've just opened file in version (it's new if comparing with old new(2019-06-03 14:42, hash: rB0efe89bdd810) but not fresh) and looks... like bug gone. So you can close task :)
Jun 11 2019
@Sebastian Parborg (zeddb) - yeap
May 25 2019
May 14 2019
Thanks! You are superb guys ? :) I just have found new one (another type) bug in same scene :) I will create another ticket.
May 13 2019
Funny. In Version: 2.80 (sub 64), branch: master, commit date: 2019-05-13 16:17, hash: rB0264d8390fa2 - bug is gone [maybe, not sure]. But I have opened current file (and my old file - where it was) and it looks like normal.
Or maybe you have fixed it so fast?
May 10 2019
Hm.. even if this is part of algorithm, I don't see here any features how user can use it.... Dark side of it will be when some user change it accidentally and then will break his mind in searching way how to fix it)) So it will bring more bad then positive I think. Maybe better to give strong limitation (from 0.001 to N for example) where algorithm works and looks good (not like broken or weird) to avoid this hypothetical situation in future.
but... maybe I'm not right. Will be seen :)
May 6 2019
Apr 16 2019
Apr 15 2019
Thank you! :)
@Bastien Montagne (mont29) so I need post this at RihtClick site? Correct?
Sorry @Philipp Oeser (lichtwerk) don't clear understand (if it has some techical reason.. or maybe more deep side of usage advantages (on pro level) - maybe it usefull.. but I don't get the idea behind you explanations, sorry(have broken english level)). I just can said like from user side)) No more. For me now it's looks like shortcoming because it fast rubbish all pickers. Just imagine if you use for example 5 or more Scenes with different objects on it (and each of them contain hundreds named parts) Then you decided to copy that Scene to try something new in scene without sidtorsion of original Scene... and when you get what you whant and no need to use Copy-draft - you just deleated it. And when you continue work and suddenly need to change for example change origanal scene you will find that now you have 2 copy of names in pickers (in my case it even more, because I explored this behave after deleating some couple of scenes) So, now each time when you will open picker - you will have doubts wich one right to choose from parts - because they have same (+numbers) names.. and it create confusing effect.
And even more I' din't find (from outliner or Scenes menu; in mening easy way ) any way to clean them from this "rubish-ghousht" even after restarting file.
@Sebastian Parborg (zeddb) Maybe this info will shed light to the problem? When I open this file it always show me aware (in console) that it didn't found "buitin.transform" tool in Viewport
Apr 14 2019
Yes, I understand. Anyway thank for help (with UI way) :)
Great! Thank you :) Sorry but I really don't know what was lead to this, to give reproducing steps. I found it only when finished working with modeling objects and need to shoot them. So can't help more than provide to you file
@Sebastian Parborg (zeddb) How I can do this? "or just load the file without the "Load UI" option and it is fine" or where it possible to read, see? Thanks :)
Because I know only how to import inside.. but when I open file it always with UI.
Hi guys! Thanks for reply. Same situation. I did Brecht steps - but it still the same.
Apr 12 2019
Apr 10 2019
Done. Same result. I've installed this one: https://www.nvidia.ru/Download/driverResults.aspx/132986/ru
Apr 9 2019
Try please this file. I zoomed it to maximum to vertex. Just start zoom out.
Apr 7 2019
Confirm. In my cases both spheres dissapeared. But after scaling boxes just a bit (inside or outside) - cutting appears.
Apr 6 2019
Apr 4 2019
Thank you! Awesome :)
Apr 1 2019
I create new file [not my original]. But here are it reproduce on my PC. If you PC more powerfull - you will don't see it. So please just increase subdivisions on the object [when you fill the same slowing down as in the video]
Here is how it looks like: https://mega.nz/#!cLBQHIIa!UYt3WhuyBA0twL6P5J29fC5jnK7X97zjwRmbRM2c5m4
Btw, I checked it whith pressing 'Enter' key - and it works fine. But with mouse - not.
Mar 31 2019
Mar 30 2019
Mar 27 2019
Operating system: Windows-10-10.0.17134 64 Bits
Graphics card: GeForce GTX 560/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 391.35
Mar 25 2019
Mar 22 2019
Mar 20 2019
Mar 19 2019
Mar 18 2019
Mar 17 2019
Mar 16 2019
Same issue. It happens not only for preference window but I guess for all minor windows (for exemple Render - F12)
win 10 - 64 bit / NVIDIA GeForce GTX 560 [last driver version] / 2.80, dbfbd6b9043d, 2019-03-16
Mar 15 2019
Yes, they are.
Mar 14 2019
Mar 13 2019
Mar 11 2019
Mar 10 2019
Thank you! And sorry, it was a bit unclear at first (I mean 'null').. so I decided that it's lag.
Jan 22 2019
I did, hope all correct.