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.
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)?
I'll put that on my desk for the time being.
Cannot reproduce (unless I am misunderstanding something here).
reg. the dopesheet performance and animated materials: Is this still with the Material Preview (or any other rendering view) open? [that would be expected behaviour then].
Thu, Apr 19
from the bug submission page.
Confirming the issue on first sight.
Also: could you confirm such a key-combination is working properly in any other software?
(cant think of a good example, but e.g. in a text editor like atom.io... I think you get what I mean?)
Dont have such hardware at hand.
So these combinations of numpad + modifierkey dont show up when you launch with --debug-events?
You mean the Poly Build Tool? I think this is (like many things in 2.8) still subject to change.
Anyways, this tracker is for reporting bugs and not for asking (support) questions or requesting features.
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.
A guideline for making a good bug report can be found here: https://wiki.blender.org/index.php/Dev:Doc/Process/Bug_Reports
Also there seem to be multiple unrelated issues at hand here.
Vuk, thank you for the answer!
@Philipp Oeser (lichtwerk) @Jeroen Bakker (jbakker) Thanks for investigating this more. I also remember at some point when I was accessing the pixels directly through "Viewer Node" image block and stored them on disk. What I realized however was the pixels were sort of rotated. I remember the depth map rendering that I got was shown 90 degrees rotated. So I have a request from you: I would appreciate if you can provide a nice Python API that allows people to easily access the rendering results without having to store the renderings on disk. Maybe bpy.ops.render.render() could take an argument like keepInMemory=True. Then people can access the rendering results through something like renderings = np.array(bpy.ops.render.results). The should also account for having a couple of output nodes. For instance, if in the node editor I have 5 Viewer nodes, renderings should be a 5 x 4 x resolution x resolution tensor.
Actually, I include the latest .blend file to help you, the loaded UI should have both windows opened to let you see the effects, all you need to do is to drop the 'blender.mo' file and change the language to 'Vietnamese' (Tiếng Việt) :
I include the .blend file to save someone the process of rigging and setting up to see the mocap 'Fixes'
Confirmed on first sight, will have a look shortly.
Note: I checked by exporting with the settings the report suggest, resulting in
It no longer crashes, however a relatively small amount of key frames on the dope sheet starts to chug considerably if materials are animated. However, upon choosing animated objects without animated materials, the same number of key frames will run much smoother.
blender-softwaregl runs blender !!
While it might not be the perfect default speed in every situation (which is hard to predict depending on your model scaling etc), you can:
Cant get it to crash, one thing you didnt mention: Have you tried 2.79b? Or the latest build from https://builder.blender.org/download?
also added to TODO here: https://wiki.blender.org/index.php/Dev:Source/Development/Todo/Scripting
Will have look again if time permits
@John Luke Gibson (eaterjolly), can you compile in debug mode and run blender from gdb to get more meaningful backtrace?
Hey Philipp, sorry for the long reply- Finals are approaching. I didn't get an error running from the command line with -d, it just didn't boot as usual. I've disabled Kapersky entirely. I tried booting from factory settings to no avail. I also have tried running through OpenGL with no luck, it is the same outcome. I do know that it worked prior to installing my 1070 ti on my integrated graphics- of course it ran terribly. I disabled my graphics card and made sure my integrated graphics drivers were up to date. Any other ideas?
Wed, Apr 18
This is a different issue regarding transformation order, but alas.
Building blender as module is not very official feature, and i'm not sure why logging will be attempted to be initialized twice. This is more a question to @Campbell Barton (campbellbarton).
Confirming it's caused by above mentioned commit. @Campbell Barton (campbellbarton): feel free to assign to me and I'll try my luck :)
@Sergey Sharybin (sergey) mind taking a peek here?
Still dont think this is a bug (as this is working as designed), but I feel your pain and leave this open so it doesnt get lost..., assigning @Julian Eisel (Severin) here to have a final word.
not sure it's the best place, but also added to TODO here
Thank you for your time anyway.
I agree that this is not a bug but a known limitation.
Dont have issues in your provided .blend
Think there are two issues to solve here:
Not only this issue is already reported, system behaves according to its current design.
Afaik, blenders alembic exporter does not support particle dupli objects and only exports points. (see the manual)
For mesh objects you can use a particle instance modifier [that will export OK], but unfortunately this is not available for metaballs.
Interestingly: attempted building bpy from source.
$ python3 Python 3.5.2 (default, Nov 23 2017, 16:37:01) [GCC 5.4.0 20160609] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import bpy Color management: using fallback mode for management bpy: couldnt find 'scripts/modules', blender probably wont start. Freestyle: couldn't find 'scripts/freestyle/modules', Freestyle won't work properly. ImportError: No module named 'bpy_types' ImportError: No module named 'bpy_types' pyrna_srna_ExternalType: failed to find 'bpy_types' module ImportError: No module named 'bpy_types' ImportError: No module named 'bpy_types' pyrna_srna_ExternalType: failed to find 'bpy_types' module ImportError: No module named 'bpy_types' pyrna_srna_ExternalType: failed to find 'bpy_types' module F0418 03:39:48.776191 31765 utilities.cc:322] Check failed: !IsGoogleLoggingInitialized() You called InitGoogleLogging() twice! *** Check failure stack trace: *** @ 0x7f2b0472cb5d google::LogMessage::Fail() @ 0x7f2b0472e973 google::LogMessage::SendToLog() @ 0x7f2b0472c6ed google::LogMessage::Flush() @ 0x7f2b0472f35e google::LogMessageFatal::~LogMessageFatal() @ 0x7f2b04734b62 google::glog_internal_namespace_::InitGoogleLoggingUtilities() @ 0x7f2b0467f32d libmv_initLogging @ 0x7f2b02fc270c main_python_enter @ 0x7f2b033bf77d bpy_module_delay_init @ 0x7f2b033bf7dd dealloc_obj_dealloc @ 0x5a0189 PyDict_SetItem @ 0x5a114c PyDict_SetItemString @ 0x51ffb6 PyModule_AddObject @ 0x6100db _PyImport_LoadDynamicModuleWithSpec @ 0x610538 (unknown) @ 0x4e9c36 PyCFunction_Call @ 0x53dbbb PyEval_EvalFrameEx @ 0x540199 (unknown) @ 0x53c1d0 PyEval_EvalFrameEx @ 0x53b7e4 PyEval_EvalFrameEx @ 0x53b7e4 PyEval_EvalFrameEx @ 0x53b7e4 PyEval_EvalFrameEx @ 0x53b7e4 PyEval_EvalFrameEx @ 0x540f9b PyEval_EvalCodeEx @ 0x4ebd23 (unknown) @ 0x5c1797 PyObject_Call @ 0x5c257a _PyObject_CallMethodIdObjArgs @ 0x5260c8 PyImport_ImportModuleLevelObject @ 0x61025d PyImport_ImportModuleLevel @ 0x7f2b033d03c2 bpy_import_test @ 0x7f2b033d079a BPy_init_modules @ 0x7f2b033bfd19 BPY_python_start @ 0x7f2b02fcffc5 WM_init Aborted (core dumped)