- User Since
- Apr 11 2017, 11:26 PM (118 w, 5 d)
The archive unpacks and validates just fine with both Windows tools and 7-Zip. What software did you use to extract it?
Sat, Jul 20
Looks like several files that Blender requires went missing. Could it be that your antivirus has accidentally deleted/quarantined these files?
Works fine on my machine (also Windows 10 64 bit and Nvidia GeForce GTX 1080 Ti). I do get the following warnings on the console though I'm not sure if they are related to the crash you were experiencing.
The same issue applies to .mtl files with map_Kd and a texture filename in quotes.
Unfortunately your GPU has a CUDA compute capability of 2.1 which is no longer supported in Blender 2.8.
Looking at the code of import_obj.py from 2.79b it seems that this may not have been an intended feature.
Technically this isn't a bug, since Blender follows the spec. However it may still be useful to support this as it was in 2.79b. This issue was originally brought to my intention in this post on Blender StackExchange.
Fri, Jul 19
Thu, Jul 18
Please provide a blend file and exact steps to reproduce the problem. The currently provided information aren't enough for us to investigate the underlying issue. If the listed problems are independent of each other, please create separate bug reports in the future.
Blender does not save still renders to the hard drive by default. You need to save them manually from the image editor. When rendering as animation the naming scheme is applied correctly. Unless I'm missing something everything works as intended. A similar question has been asked on the Blender StackExchange, perhaps this may help you.
Wed, Jul 17
Can confirm. It does adjust properly when reducing the vertical height even further, but in between a large vertical height and a small vertical height the empty space occludes the panels.
Tue, Jul 16
You're graphics card doesn't meet the minimum requirements. It would need to be at least first generation of the GCN architecture, which the AMD® Radeon™ HD-6000 series isn't.
I've taken a look at the file and there don't seem to be any keyframes left, the dope sheet is empty. Only the timeline still shows a marker, but this seems to be a rendering error, the actual keyframe is removed. In Blender 2.8 this is working correctly, no marker is shown in the timeline.
You're currently using an older graphics driver. Please update to a more recent version and check if this resolves the issue.
@Ton Roosendaal (ton) Yes sir, will do. You're absolutely right.
Sun, Jul 14
@Adam Janz (Copperplate) While it may be more work, you still have full control over the result by color grading in the compositor.
Cycles: OpenCL on macOS has been disabled
There was a growing payload of bugs in Cycles related on OpenCL on macOS
platform, and those issues were caused by a compiler bug, which we have no
Surely, it is sometimes possible to work compiler bugs around from a
source, but we are facing some of the issues which are not solvable in this
way. Also, such solutions are usually short-living,. since adding more
features are often kicking compiler to provide buggy binary again.
In this case compiler will not get fixed since Apple decided to discontinue
OpenCL on its platform.
So the decision was made to drop support of OpenCL, keep official features
of Blender stable and predictable, and focus on things we have control over.
P.S. Older Blender releases are always available. Surely, this sounds like
using an ancient software without neat features. But we can't push Cycles
OpenCL on macOS measurably beyond that anyway.
Sat, Jul 13
@mohsen (mos) Could you run blender_debug_log.cmd which can be found in the install directory and try to cause a crash? It will log all errors into a file and makes it easier to identify issues. Once you have a log file of a crash please upload it here.
The given information are not enough for us to replicate the issue. Please describe what steps you have taken that resulted in the crash. The following link may help you improve the current bug report.
You missed to quotation marks. It should be help('modules'), which works as expected.
Now let's say we were to change from current behaviour (the default mode for new text) to e.g., the mode of the selected text. Now what if the selected chars have each a different style value (half bold, half italic) what do we show in the UI?
@Dalai Felinto (dfelinto) I agree this is not a bug, but imho bad UX. Seems like something minor that could be done for 2.81 and added to the paper cuts.
Please provide more information about the crash. The following links explains how to write a good bug report.
The way it currently works is awkward. You can set the properties *before* typing and it will appear as you'd expect. However the interface doesn't allow to change the format with these buttons once typed as far as I'm aware. This is not a regression though, the behavior was already like this in 2.79b. The underlying features are there, but the operator behind the buttons isn't context sensitive (e.g. change all letters when in object mode, change selected letters when in edit mode). You can change individual letter by setting them through bpy.data.objects["Text"].data.body_format.use_italic = False, where "Text" is the name of the object and the index in body_format is the character you want to change. See the API docs for more formatting options.
Can't reproduce. Please run blender_debug_log.cmd which can be found in the install directory (C:\Program Files\Blender Foundation\blender-2.80rc1-windows64\blender_debug_log.cmd) and repeat the steps that produce the crash. The log file may help to identify the problem.
Thu, Jul 11
Crashes for me. Seems to be a driver issue though, since the access violation occurs in the nvoglv64.dll.
Wed, Jul 10
Weird, can confirm SHIFT+ö enables it for me as well.
@Sebastian Parborg (zeddb) I was testing on Windows and it's a dead key by default.
Tue, Jul 9
Can confirm. It doesn't work on a German keyboard, because pressing shift is required to get the ` in the first place.
Sun, Jul 7
Ignore my previous comment. I'm not sure what's going on here either Affinity Photo and LuminanceHDR both have broken OpenEXR implementation or Blender creates file that don't follow the spec. Affinity Photo can open the files and reads both RGB layer and alpha, but fails to save the data on export resulting in a blank alpha. LuminanceHDR complains that it can't find RGB data and refuses to load the file altogether. This happens for both your supposedly broken file and .exr files that can be properly read in Blender.
I've got the same result in 2.79 and the current master build. Both show the broken result. Since loading your .exr file in an external image editing application and saving it as .hdr or .exr doesn't fix it, seems like the alpha hasn't been properly tagged in the file.
Jun 11 2019
macOS implementation of soft delete using the cocoa runtime.
Alright, no problem.
May 29 2019
Let me know if you'd like to see this implementation for macOS in Blender or what other approach should be used.
May 25 2019
May 21 2019
I've done some more research and it seems we could use the runtime with pure C on OSX. Certainly not the most elegant approach. @Brecht Van Lommel (brecht) do you want to take this from here?
May 20 2019
- Simplified Linux soft delete, now using fork and execvp
- Added keymap entries back
- macOS currently commented, because changes necessary to make Objective-C work
- removed duplicate include for <sys/stat.h>
Since 64acb70e7f0f removes the ability to delete files, is development on this patch still of interest?
May 15 2019
May 6 2019
May 5 2019
I'm currently quite busy, updates may take a while. Hopefully I can squeeze these in next weekend.
Apr 28 2019
It's likely just outside the clipping plane. Select the object in the outliner (top right window where the collections are), go to the object tab (the window below that, click on the square icon) and set the location on all coordinates to zero. You may have to adjust the scale as well, if it's very large.
Apr 27 2019
What you described sounds unrelated to Blender and more like your computer has been infected with malware.
Apr 26 2019
@T.L (T.L) Yes you're right, that's why I wrote that it seems to be a different cause.
Seems to be a different cause.
It's quite possible that this isn't a bug in blender, but another case of the strange way Windows handles encoding / code pages. Depending on your locale, it may be that è is not included in your code page, which results in Windows replacing the character with ? when passing the argument to the program. If that is the case, then there is nothing blender can do, because it's not getting the right string. You can check if that's the case by temporarily activating the UTF-8 beta feature described here. If that works properly, it's Windows' fault.
Apr 24 2019
@Campbell Barton (campbellbarton) I think this patch is done, if we want to limit the supported desktop environments as @Brecht Van Lommel (brecht) suggested. And if it works properly on macOS which I haven't been able to test.
Apr 23 2019
Correct error messages
Apr 22 2019
Replaced malloc with Blender's allocator.
Added missing include for macOS
Fixed wrong debug print function for Linux.
I can't test the macOS implementation, perhaps somebody can help with that . I'll test the Linux implementation later this day.
Removed unused argument from Windows delete_soft()
Several small fixes. Sorry for spamming the tracker.
Work in progress implementation of soft delete for Linux and macOS
Sure, no problem. I'll implement it today. Do you have any special security policies regarding system() for calling the CLI utilities?
@Brecht Van Lommel (brecht) just in case you change your mind: I have implemented the trash specification (currently without directory size cache).
Apr 18 2019
That would be an option, although I'd favor a general solution that works on all Linux distributions and desktop environments. @Campbell Barton (campbellbarton) @LazyDodo (LazyDodo) Do you agree with this approach?
Not sure how relevant this is to the bug report, but I can't reproduce this with my Wacom Intuos.
I think the complexity is manageable, but that is your decision. The problem that I see with the Electron approach is finding out what desktop environment we're on (which implies what CLI utility can be used). Does Blender already have an equivalent of libgtkui::GetDesktopName?
Apr 16 2019
I would like to implement support for $topdir, but in case (1) and (2) fail (see spec) refuse to trash. This means we can simply use rename since we don't move files over across devices. This makes the code simpler and doesn't require reimplementing mv.
Work in progress.
Apr 14 2019
Looks like this might be the same issue as T63582
Can you share a minimal .blend file where this error occurs?
builder is a nullptr.
As you've said yourself, you're running out of memory. Your project likely needs more memory than Windows allows you to swap to disk, resulting in a crash. If this is the case then there is nothing to fix, you simply don't have enough memory available to render the scene. If you suspect that the crash isn't caused by OOM, you can go to the installation directory and run blender_debug_log.cmd. This will give you a detailed output about what went wrong.
Apr 13 2019
Currently a bit busy, but this isn't forgotten. When I got some time I'll implement the Linux soft delete based on the approach that trash-cli uses.
Apr 12 2019
Does this happend with the most recent build? If yes, can you provide the .obj or .blend file?
This is likely because you use an old driver for your graphics card which doesn't support OpenGL 3.3 or newer. Install the latest driver and see if that resolves the problem.
It seems v_curr is pointing somewhere it shouldn't.
Apr 11 2019
col_tot is zero in the division which causes the crash.
> blender.exe!image_sample_rect_color_ubyte(const ImBuf * ibuf, const rcti * rect, unsigned char * r_col, float * r_col_linear) Zeile 3085 C blender.exe!image_sample_apply(bContext * C, wmOperator * op, const wmEvent * event) Zeile 3161 C blender.exe!image_sample_invoke(bContext * C, wmOperator * op, const wmEvent * event) Zeile 3279 C blender.exe!wm_operator_invoke(bContext * C, wmOperatorType * ot, wmEvent * event, PointerRNA * properties, ReportList * reports, const bool poll_only, bool use_last_properties) Zeile 1343 C blender.exe!wm_handler_operator_call(bContext * C, ListBase * handlers, wmEventHandler * handler_base, wmEvent * event, PointerRNA * properties) Zeile 2144 C blender.exe!wm_handlers_do_intern(bContext * C, wmEvent * event, ListBase * handlers) Zeile 2462 C blender.exe!wm_handlers_do(bContext * C, wmEvent * event, ListBase * handlers) Zeile 2720 C blender.exe!wm_event_do_handlers(bContext * C) Zeile 3141 C blender.exe!WM_main(bContext * C) Zeile 421 C blender.exe!main(int argc, const unsigned char * * UNUSED_argv_c) Zeile 505 C
Looks like this was already fixed in adaa7688ee77
This was reproducible in a previous version from today, but the current master doesn't crash. GPU_texture_width was dereferencing a nullptr.
I can't reproduce with the current master. Your blender version seems to be an older build, does that happen with the current 2.8 build as well?
Apr 8 2019
@Sergey Sharybin (sergey) It seems to me that object_for_eval is set to the result of DEG_get_evaluated_object which has the modifiers applied, is used incorrectly in:
The functions rna_Object_to_mesh(), rna_Main_meshes_new_from_object() and BKE_mesh_new_from_object() all get apply_modifiers set to false as it should be. Could it be that this is an error introduced in 46eb5a0b8a4f3a7826b5e5a1a11e114e09037dba @Sergey Sharybin (sergey) ?
Looks like EXPORT_APPLY_MODIFIERS is set to False when the option is unchecked but to_mesh() or another function applies the modifiers regardless.
Can't reproduce with the current master as well as previous releases. What exactly happens or doesn't happen? Are you sure that the search pattern doesn't apply to all files in the directory?
Apr 5 2019
Patch is D4655. Haven't use arcanist before, will look into it for future patches.