Can you try to launch blender *from* cmd commandline window? That way, console will remain open after the crash and you'll get full error report.
Thanks for the report, but unfortunately supporting advanced scripts like those is currently not a high priority on our list, since it would require a rather huge effort to integrate relevant tools/libraries in Blender... A patch would always be welcome of course. ;)
As a workaround, typing in a real text editor and then copy-pasting into Blender should give valid results (i.e. keep the result of the complex matching operations).
I can reproduce on: MacBook Air 10.13.4, GeForce 320M, Blender 2.79b official
Please follow our submission template and guidelines and make a complete, valid bug report, with required info, precise description of the issue, precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Sat, Apr 21
Is there any work on this at the moment? It seems to be dead somehow.
$ sudo lshw -C video [sudo] password for john: *-display description: VGA compatible controller product: RS480 [Radeon Xpress 200 Series] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 5 bus info: pci@0000:01:05.0 version: 00 width: 32 bits clock: 66MHz capabilities: pm vga_controller bus_master cap_list rom configuration: driver=radeon latency=64 mingnt=8 resources: irq:17 memory:d8000000-dfffffff ioport:ee00(size=256) memory:fddf0000-fddfffff memory:fdd00000-fdd1ffff
Rather stay open source with the driver tbh.
- You have to know what you want to do... If you can do the audio editing in Blender, do it there, if not use some other program.
Fri, Apr 20
So this is what I'm getting from all this:
- The 32 channels of the blender vse are called channels but they aren't the same as audio channels (aka mono being 1, stereo 2 channel).
What not to report here
- Feature requests, see the developer contact page.
- Items that are already on our To Do list.
- Compile or build issues, ask on #blendercoders or mail bf-committers.
Thank you for taking the time. This is what I get with --debug-events from a single Ctrl+ operation (select more in edit mode):
I found more detail on the problem:
Also important to mention, that:
Hi Julien :)
Confirming on first sight, but need to have a closer look later
Thanks for the fast answer.
Sorry, I understand your point of view and I need to be more precise: the important part for the issue in object of the video I'm referring to in the main post is just the first part (3.30 minutes more or less). Following the video is very clear what is the problem I think every artist faces with blender snap weird behavior.
For the blender attached file: after watching the video I'm pretty sure that there is no need of it because the video in object per se is far more clear than a generic blend file with some entities in it.
Thanks again for comprehension.
"I'm not going to attach a .blend cause i think it's common, also here's a 30+ minute video for you to watch" is not a great way to report a bug.
@Philipp Oeser (lichtwerk), this is something what we should support indeed. Mind looking into this? Shouldn't be hard to add support :)
This is a limitation to the current Particle Instance modifier (not a bug though).
Sorry, was absent for quite some time, will take care [soonish]
Since last information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.
Since last asking for information it has been 7 or more days, due to the policy of our bug tracker we will have to archive the report until the requested information is given.
@Christian Hoffman (Dramock) : is this still relevant? Has above link solved this?
Most likely a driver bug then, what GPU is this? Have you tried upgrading the driver (or tried different versions)?