12/7/2023 0 Comments Blender motion blur![]() Go to first frame (if rendering still image). Sometimes it takes a couple of frames to render before crashing, but it's basically as simple as hitting the render button. Just to be sure that you're all rendering the right scene (it should be the one that's open when the project is opened), I've stripped out all of the other scenes in this file: ![]() ![]() So, it does seem to be something to do with a conflict between viewport and render threads, as Sergey suggested. It's just finished rendering another scene on both GPUs for 2 days solid without a crash.Īs far as nVidia drivers, CUDA etc, they're both on the latest version (but seeing as the crash is happening on both CPU and GPU I'm guessing this isn't too relevant now).Īs far as scaling from 0, I just tried deleting the objects that are scaling from 0, but it still crashes. I would just notch this down to being a bug related to the machine being a Hackintosh (if the iMac wasn't crashing too), but up until this scene, Blender has been rock solid on it. It doesn't have a GPU, so couldn't test that, but it did crash with CPU rendering. Just to make sure that it wasn't down to it being a Hackintosh, I tried rendering on an iMac that we have in the office. Yes, the machine that I created the project on and first noticed the bug is a Hackintosh (Mostly for Blender really, not a fan of Windows, need to use Adobe software so can't use Ubuntu but also need nVidia GPU rendering for Blender, which rules out most macs). Making a viewport fullscreen (shift-space) and rendering fixes the bug on both CPU and GPU (for both animation and still image). Yes, it crashes when rendering a still image on both CPU and GPU It crashes using both CPU and GPU, just checked again on the latest build from today (bbeb8c5). Sorry about the light details originally, pushing up against a deadline, ended up rendering without motion blur for the first draft. **Exact steps for others to reproduce the error** Also tried the latest build from (63f62cd) and that crashes also. Just tried it with the stable 2.74 (000dfx0) release from and it still crashes. Open the project that I've made and hit render. If you need any specific information from me, please get in touch, would be good to squash this bug.Įxact steps for others to reproduce the error I've attached all the information that I can, I'm going to frantically try to find a workaround for this problem now (probably while crying) as this is due tomorrow. If you need the project file, is there a way I can get it to you without publicly posting it here? It's client work. Also tried the latest build from ( 63f62cd) and that crashes also. I'm using armatures with bone envelopes to give text motion blur. The terminal shows the error "Segmentation fault: 11" When motion blur is turned on and I hit render for a specific project that I've been working on the past week, Blender crashes.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |