- User Since
- Aug 30 2010, 3:36 PM (616 w, 5 d)
Tue, Jun 21
Can confirm this bug still exists in 3.3.0
version: 3.3.0 Alpha, branch: master, commit date: 2022-06-21 08:10, hash: ee78c860b8aa, type: Release
build date: 2022-06-21, 12:12:39
Sun, Jun 19
The issue is still present in
version: 3.3.0 Alpha, branch: master, commit date: 2022-06-18 22:14, hash: 575884b82786, type: Release
build date: 2022-06-19, 10:09:11
Sat, Jun 11
Wed, Jun 8
Sorry for chiming in, but since this is so very similar, I was hoping that my issue could be solved in a similar way: https://developer.blender.org/T86686 (has been closed because nobody could reproduce it, but I see it in 3.2/3.3 every day - probably thanks to my old AMD card and mesa).
before this patch:
after this patch: (did not get worse, it is just different each time)
Sometimes, fractions of images can be recognized that were once on screen (but have been closed hours before starting Blender), so it seems like some buffer is not cleared. The gravity of the issue seems to be affected by the mesa driver version, but it was not present in 3.1.2
Sun, May 29
Sat, May 28
May 25 2022
May 24 2022
Yes, it also crashes if the source.blend is available. This is from a larger project that crashed on opening, so I took out everything I could while keeping the crash.
Here I removed everything from source.blend but the linked mesh and merged it down to one point (hope it's still helpful in this state):
May 23 2022
May 17 2022
Oh, I did not notice that the driver was referencing the wrong armature, that explains a lot actually, thank you!
Thanks for fixing the crash! Now there is a greyed out, linked "OVERRIDE_HIDDEN" collection pointing to the "Dup" collection in the example file. Since there seems to be no documentation on this topic, could you please explain what that means and why linking the "Link this" collection now links the other collection, too?
May 15 2022
Apr 13 2022
Apr 9 2022
Oh sorry, seems like the 'save the blend file' step got lost in case (3) - I edited the first post.
Not sure if a separate report is needed since the older Blender versions won't get patched, but if you still think it makes sense, I'll open another report.
Apr 8 2022
While dragging the angle slider does not crash those older Blender versions, the file from case (3) crashes 2.93.0, 2.91.2 and good old 2.79b.
In these cases, the circular dependency leads to uncontrolled translation of the curve and cube if the angle slider is scrubbed quickly (probably to be expected).
Apr 7 2022
Feb 18 2022
Feb 15 2022
Out of the blue, the artifacts are gone in 3.2. They are still present in 2.93.0 and 3.0.1, so it seems to be due to a change in Blender, not to an OS upgrade.
With a buildbot build from the same date as my previous test, in most sessions the VSE artifacts are still there, but in some sessions, they are not.
Jan 21 2022
This seems to be a duplicate of https://developer.blender.org/T93987
This seems to be a duplicate of https://developer.blender.org/T93987
Jan 20 2022
Thanks for coming back to this issue.
Jan 10 2022
Dec 18 2021
I assumed that the audio has to be longer than 4 mins since the difference was only one frame with a 4 min audio file and there was no issue with a 3:48 file (http://dig.ccmixter.org/files/airtone/64427), but that has been disproved by the file from Pratik.
Dec 16 2021
Nov 30 2021
Nov 8 2021
The file also crashes if the mesh data is replaced with a plane.
Oct 12 2021
Ctrl-click to connect a viewer is actually not part of the addon, also happened with it deactivated as well as with blender --factory-startup and with blender --factory-startup + only NodeWrangler addon activated. Using ctrl-click is not necessary for the crash to occur, the nodes can be added from the Add menu.
Bug still there in 3.0.0 Alpha, branch: master, commit date: 2021-10-08 14:49, hash: rB94d2736dfb33.
Instead of falling back to "Screenshot" in such cases, could we please use the viewport camera instead?
Oct 5 2021
Sep 26 2021
Jul 8 2021
Retested with OpenGL: renderer: AMD VERDE (DRM 2.50.0 5.12.9-1-MANJARO LLVM 12.0.0) v: 4.5 Mesa 21.1.2: the backdrop/render does no longer disappear (in today's master and older releases), so this was a mesa issue that got fixed and the bounding box issue was fixed by today's commit.
May 31 2021
Seems to be fixed by "VSE: Fix missing cache invalidation" https://developer.blender.org/rBb862916eafc809cc1d93ffc8cdfc48402df30df0
May 28 2021
Thank you for the fix!
You are right, it only fixes the gizmo, so the report can be split.
The question is: can it not be reproduced by a user with an older amd card? As long as blender does not drop amd support, it can not be regarded as tested if no amd/mesa user tested it.
Currently I would assume that these issues belong together and that solving the bounding box issue might perhaps even solve (or hide) the other issue.
May 26 2021
It is definitely not resolved in version: 3.0.0 Alpha, branch: master, commit date: 2021-05-25 15:45, hash: rB45b28c0f8847
It does not help to provide a file because it can be easily reproduced with any (so far unused) image sequence following the steps from my earlier post (VSE layout, load sequence, press play).
May 18 2021
I am also having this issue from time to time, just start in VSE layout, import image sequence and press play, it stops at frame 2 (while still showing the stop button "Anim Player" on the bottom, preview keeps displaying 24 fps but the timeline does not mode). (Older blender versions played without problem)
Waiting does not seem to help, but if I restart blender and repeat it with the same material, at some point in time it works like normal. Also, there is no problem playing a single frame scaled to the length of the timeline.
Perhaps there is an issue using the new cache?
May 12 2021
Yes, the regression is still present in:
version: 3.0.0 Alpha, branch: master, commit date: 2021-05-12 12:20, hash: rB8dc95f61f3df
as well as
blender-3.0.0-65244ac1c3f1-linux64 from builder.blender.org
Operating system: Linux-5.12.1-2-MANJARO-x86_64-with-glibc2.33 64 Bits
Graphics card: AMD VERDE (DRM 2.50.0, 5.12.1-2-MANJARO, LLVM 11.1.0) AMD 4.5 (Core Profile) Mesa 21.0.3
May 3 2021
Apr 17 2021
Apr 6 2021
It did not lock up if I used one frame stretched to the whole duration, it seems to be necessary to use a real image sequence.
Since VSE can't pack images, you could try any image sequence you have on your harddisk (please don't delete & create but edit the path in the sequences, just to be sure). If you don't have one, you could use ffmpeg to convert e.g. a blender movie to single frames
ffmpeg -i input.mp4 -t 01:44 -vf fps=25 out%04d.jpg
Apr 4 2021
With my project, I can reproduce the issue quite reliably in 5 minutes, but sometimes it does not work.
I compiled a debug build and tried it in the terminal: no output on lock-up, so I ran the debug build from QTCreator and as Blender locked up, I clicked Interrupt GDB and copied the stack trace:
Apr 2 2021
Sorry, I downloaded https://builder.blender.org/download/blender-2.93.0-d91fec1a85d9-linux64.tar.xz but there is no blender_debug_log.cmd included.
Have you tried it with a larger project?
After replacing the missing images files, I also could not reproduce the issue with this blend.
My impression is that it is very difficult or impossible to reproduce with simple setups. It might be necessary to use a more real project like in my case 2500 rgba frames in 1920x1080 at 29.97 fps and even then it gets quite tedious, but sometimes the lock-up happened after just one minute.
Mar 31 2021
Mar 26 2021
On the right, both planes get darker if I deactivate diffuse on the lower plane because the light does not bounce back towards the upper plane and the camera, I believe.
Unfortunately, transmission is only vaguely defined in the blender wiki as "Transmission: the ray is generated by a transmission through a surface.", that is all I know, so I expect transparency and translucency to create transmission samples, but both do not react to the transmission ray visibility.
If you change the translucent shader on the upper plane to a transparent shader, then toggling transmission (on the upper or lower plane) also has no effect.
Mar 25 2021
New testscene: the selected objects (".. receiver") should receive Volume Scatter/Transmission rays and therefore be lit if the respective toggles are on. If the toggles are off, the selected objects should not receive light.
To me it always looks like this:
But if Transmission and Volume Scatter are off, I would expect it to look something like this:
So there is a visible change if you switch off Transmission on the plane above the cube? To me, it looks completely identical even in a F12 render.
Camera/Diffuse/Glossy/Shadow are fixed in version: 2.93.0 Alpha, branch: master, commit date: 2021-03-25 15:06, hash: rB5ebe74e77903
but Transmission and Volume Scatter toggles don't seem to have an effect.
Mar 19 2021
Mar 18 2021
Okay, I begin to understand that this is not about metadata from photo cameras (Nikon/Canon photo metadata is not displayed), but about metadata blender exports with it's frames using tEXt tags that are also used by inkscape, so this text is displayed. While the metadata display toggle has already been present in 2.92 it is only working in 2.93.
Mar 10 2021
Sorry, it is not fixed completely, retesting in version: 2.93.0 Alpha, branch: master, commit date: 2021-03-04 19:20, hash: rB1668f883fbe5 shows that the following problem is still present:
If you switch the Outliner to Scenes mode and drag a collection to another collection, "Link inside Collection" is displayed but in reality, the collection is moved and you have to press Ctrl to link it.
Jan 30 2021
So I found the reason of this issue: I have set a custom path for Temporary Files (in Blender Preferences - File Paths) in most older Blender versions that I had not set in some newer versions.
Blender does not seem to use the system clipboard but its Temporary Files location for storing copied content, so there were two separate clipboards, one using the default location and one using my custom location.
BTW: saving Auto Saves to /tmp by default which is automatically deleted upon boot isn't a good preset - if the computer crashes, the Auto Save is lost, too, so I had to change the directory.
Jan 24 2021
Jan 22 2021
Dec 16 2020
Nov 25 2020
Following the steps from the description, I could reproduce it again in 2.90.1 and version: 2.92.0 Alpha, branch: master, commit date: 2020-11-24 15:05, hash: rB256a9d983d48
An NLA strip on rig is lost, but an NLA strip on meta-rig is saved/restored properly.
Nov 20 2020
Nov 13 2020
@Luc Revardel (lrevardel)
That's it, thanks a lot!
So if there is no animation added to the source object, it should always be possible to add an animation to the override?
Because while it works in tests, it does not work in my project. I simplified my rig ("Problematic") and built a new version ("Working"). NLA strips can be added to the linked override of the new version and will be retained upon reload, but on the old version, NLA strips are gone upon reload (tested with today's master).
Perhaps you could have a look at my files, I fail to see the difference. If it is supposed to work, I can create a separate report if you like.
Nov 12 2020
Nov 10 2020
There are certainly more important problems, but a shortcut seemingly stopping to work for no apparent reason is quite irritating. So its a papercut.
Nov 9 2020
Pasting of the copied objects worked after factory resetting the originating blender instance event though I reactivated all plugins that were active before.
I never touched the keymap, and there was the "object copied to buffer" notification (and I can paste to a different instance of the same version), so the object was actually copied.
Yes, you can resize it as long as its visible, otherwise you have to resize the editor or use the tab. Biggest problem is that it is saved in the blend, so days may pass and suddenly N seems to stop working, while in reality just the panel got enlarged too much the last time that specific editor was used.
Nov 8 2020
Nov 2 2020
The problem seems to be in the earlier versions, not in 2.92: if I run the earlier version with --factory-startup I can copy/paste an object to 2.92. Without that, although I get the message "Copied 1 selected object(s)", I can only paste to the same blender version, e.g. copy in 2.90, can't paste in 2.92 but can paste to another instance of 2.90.
Deactivating all plugins (without restarting blender) in the earlier version did not help though.
Oct 30 2020
The permissions of the executables are identical and I did not change anything permission related. Also tested on a second Manjaro system and it's the same there, too.
Oct 25 2020
Thanks for the link! Also happens with --factory-startup btw.
Oct 22 2020
@Philipp Oeser (lichtwerk) your files crashed Blender if I clicked the Armature object in the Outliner prior to using make local. There is no problem using make local on the object data-block, the armature data-block is the one I can't make local (unless I use the workaround).
Confirmed in 2.90.1 and 2.91.0 Alpha, branch: master, commit date: 2020-10-21 09:38, hash: rB819b1a7f9da0
Only a local armature will retain NLA strips.
Oct 8 2020
Yes, it still looks the same after that.
Yes, it has improved slightly, but the artifacts are still there:
branch master, commit date 2020-10-07 17.31, hash rB833066088e4a
Oct 1 2020
Sep 30 2020
Sep 28 2020
Thanks for finding the source of the problem.
While it's not Blender's fault, shouldn't users be warned that this format is an exception and that the alpha channel will be lost if the video will be used in Blender?
I tried adding it here https://docs.blender.org/manual/en/dev/files/media/video_formats.html, but this page can't be edited by me (a warning in the UI would be more effective of course).