User Details
- User Since
- Sep 19 2013, 10:55 AM (490 w, 1 d)
Mar 11 2021
Sorry for the late response, I go back and forth between many jobs. My blender crash log was uploaded in the first message. I had to reinstall manjaro due to an issue with my grub not showing at boot after an update. It appears to no longer crash. Thank you.
Feb 17 2021
Jan 28 2021
PID: 7223 (blender)
UID: 1001
GID: 1001
Signal: 11 (SEGV)
Timestamp: Wed 2021-01-27 16:48:20 PST (13min ago)
Command Line: blender
Executable: /usr/bin/blender
Control Group: /user.slice/user-1001.slice/user@1001.service/app.slice/app-gnome-blender-7223.scope
Unit: user@1001.service
User Unit: app-gnome-blender-7223.scope
Slice: user-1001.slice
Owner UID: 1001
Boot ID: *
Machine ID: *
Hostname: *
Storage: /var/lib/systemd/coredump/core.blender.1001.4d910a0f3efd4ff69e80b8b0b91a9148.7223.1611794900000000.zst (inaccessible, truncated)
Message: Process 7223 (blender) of user 1001 dumped core.Jan 25 2021
Jan 23 2021
It's quite random and is on anything I sculpt. Creating a simple cube and sculpting with crease brush for a matter of minutes or sometimes 10, it can then crash. I've tried 2.92 beta and experience the same issue with all addons turned off.
Jan 22 2021
2.83 seems to work fine. Receive a similar error at start, but it does not appear to crash while sculpting.
Aug 28 2019
As a suggestion for operations in outline -> view layer; isn't it easier to just create a new Collection then add the relative object as a child of that collection when the user hits ctrl + g. If the name doesn't exist then create new collection, if the name exist just add to already created collection in the outliner -> view layer.
Aug 27 2019
Aug 24 2019
Oct 30 2018
https://github.com/stacksmith/Monoprice_22_linux_kernel_module
Install this then you need to add xorg.conf file to X11 directory to get blender to recognize your pen pressure. Follow these instructions.
https://github.com/aidyw/bosto-2g-linux-kernel-module/issues/13
Jun 16 2018
At this point I guess will be more of an xorg and driver issue. I'll have to join #xorg and figure out how to get both programs to work without rebooting.
Adding an xorg.conf with:
Jun 12 2018
wm_event_do_handlers: Handling event
wmEvent type:1 / LEFTMOUSE, val:1 / PRESS,
shift:0, ctrl:0, alt:0, oskey:0, keymodifier:0, mouse:(1023,529), ascii:'', utf8:'', keymap_idname:(null), pointer:0x7fea79160988
wm_handlers_do_intern: handled! 'SCULPT_OT_brush_stroke'
Jun 10 2018
Jul 20 2016
I went to test my Fiji(Fury X) and I was noticing the speeds I've had for a while are now totally different. My render time went down to .30sec on both cards in 2.76b. And now my Hawaii(Firepro w8100) renders at 1.75sec in 2.77a instead of 23sec for a cube. I haven't changed anything as to why I'm baffled. I tested this just yesterday and for a week before that.
Jul 18 2016
Feb 17 2016
http://blender.stackexchange.com/questions/32900/how-to-properly-render-smoke-on-a-transparent-background
Attempt 1 works very good as a workaround.
Nov 17 2015
Am using 2.76b and problem is fixed. When I save user preferences on my second monitor then exit and reopen I no longer crash with violation error. Instead the user preferences window pops up on my second monitor.
Sep 25 2015
Sep 22 2015
I realized after posting that techs might not be familiar with baking. So I attached a premade file that just requires you to hit bake within the render properties under bake tab.
Aug 14 2015
So I recently was talking to the good folk in IRC. I believe the problem is possibly fixated in my dual monitor setup. I noticed in my primary monitor when blender was stationed did not crash. However, when I switched blender to my secondary monitor and saved startup is when it began crashing. Accessing user preferences pops up on my primary monitor. So we ran a few test of Duplicating window across monitors, and play render animation which popped up on my primary monitor but did not crash at all.