My wrong date I mean April 16, 2019. Not 26. @Brecht Van Lommel (brecht)
Its all my scenes weather there custom or not but heres on and moving characters or after a certain time it just crashes. It doesnt appear to be blender that crashes itself tho as it runs smoothly up
until its gone and or black screen altho pulling up the user preferences brings up the blender not responding panel b4 i can use it.
After deleting the plane and trying to set camera view - nothing happens.
However, when I shift-C - it starts working again, so I guess shift-C is a part of this bug.
That's fine :) If you plan to fix bugs you are more than welcome to get involved.
P.S. Thank you very much for the footer. This is going to help so much.
Made a patch D4718.
The shader node setup seems to be wrong, the color ramp alpha output should not be used as density, with this color ramp it is 1.0 everywhere. Instead the color output should be used as density for both volume nodes.
This is not enough information for us to investigate the issue. We really need a .blend and exact steps to reproduce the issue, otherwise there is nothing for us to go on.
For Eevee, you need to manually enable effects like screen space reflection, and add light probes for more accurate reflections.
Thanks for attaching the files.
Thanks for tracking down the commit. I committed a fix, but I was not able to reproduce myself so please test if it actually worked in the next build.
This one is a duplicate of T63698 (the errors are the same).
@George Vogiatzis (Gvgeo) If your going to triage reports then it's best to assign them to the respective developer and not just mention their usernames, as notifications get overlooked.
Can confirm this (T63698) and T63760 are related. As promised, I just got done doing a bisect search, and every time that clicking Materials caused a crash, selecting either Rendered or LookDev display modes would also cause a crash. They also both give me the exact same error output from the debug cmd scripts.
When cube object is member of "collection1" and "collection2", "unlink" can remove cube only from current selected collection. It is reasonable.
But when cube is grouped as "collection1" only, then unlink not remove cube only from "collection1" but unlink from "Scenecollection" then now cube becom as orphan data.
yes screen space reflection problem also occurs here
Tried again this morning, here the crash report:
I was browsing through and found this thread. I reported the same issue here a couple of days ago.
u have added the files as you instructed to do so
i would like to point out that moving "Mode and select mode..etc" to the tool settings bar is not ideal and here is why.
There is no need to be consistent with obscure internal names, the Python API should have readable names.
@Dalai Felinto (dfelinto), so there was an actual bug that cause existing objects to lose rigid body data, that was fixed in rBe760d37733e4: Fix T62913: datablock append removing unrelated rigid body objects..
Appears to work fine for me now. If it still doesn't work, we need a .blend with texture included, even if it's not the real one from the original file.
Not as high priority since it can be hidden now from the View menu, still should have some automatic fix for this.
Closing due to lack of information to investigate the issue, possible duplicate of T62947: Box selection not working with Intel HD Graphics 620.
OBJ import seems to work fine. From the sound of it, you are trying to do a very large file.
@Sebastian Parborg (zeddb) I just wanted to let you know I haven't forgotten, but as I do C# programming I don't have the C++ workload downloaded for MSVS 2017, and my connection isn't exactly the fastest. But I will try to get it done over the weekend.
I can confirm this on macOS.