- User Since
- Nov 8 2004, 6:54 PM (771 w, 2 d)
Wed, Aug 7
Tue, Aug 6
Use the tool in the blender help menu
Please provide complete information from your system including GPU and driver
Mon, Jul 29
Jul 19 2019
Please provide blend file
Jun 25 2019
Hi, this is still a problem and it's very annoying :)
Jun 10 2019
@francisco silva (kiko) Please simplify your file greatly before submitting a bug report.
Jun 4 2019
Jun 1 2019
Please simplify your file. A scene with hundreds of objects and so many groups that takes minutes to render is not a good test file.
May 29 2019
May 28 2019
Already did it, check initial description
Try and get it down to one object and one shader, no lights etc. I had a similar case a few days ago. It was a principled shader
There's a LOT of stuff you can still remove in that file, the culprit is probably a shader node or something like that, please do the legwork so that the developers don't have to.
May 20 2019
May 17 2019
May 13 2019
Yes according to a brief test
May 10 2019
May 9 2019
Already fixed. Please update your build
Apr 26 2019
Apr 25 2019
Apr 16 2019
Apr 12 2019
I see the problem, but arent auto keyframes never supposed to do that? Should blender allow for that mess to begin with when setting autohandles from BPY?
Apr 11 2019
Apr 8 2019
Apr 7 2019
Mar 21 2019
You need to create a very simple example file that crashes.
Mar 19 2019
It can happen with vertex selection mode but seems easier with edges
Mar 14 2019
Mar 7 2019
Oh no! I sweared noone could possibly have fixed that bug in the meantime, totally my bad :)
Mar 6 2019
Mar 2 2019
@Dalai Felinto (dfelinto) Thanks that helps for now :D
Mar 1 2019
And to be clear, what I expect is to hide originals and show only instances from BOTH viewport AND render
@Dalai Felinto (dfelinto) then what about this
Feb 28 2019
Feb 26 2019
I agree that the join and split situation is even more cumbersome in 2.8 than it already was in 2.79.
Feb 25 2019
Feb 22 2019
Feb 21 2019
Feb 18 2019
If you're not already subscribed to https://fund.blender.org/ go do it now! You can start as low as $6 a month :)
Feb 8 2019
Feb 7 2019
Jan 25 2019
Jan 24 2019
Oh boy.. we where using a blender build from about 2 weeks or so, that's all I can think of
Jan 23 2019
Jan 7 2019
@Mike Futcher (yogyog) let's just hope this get's fixed properly :)
Dec 28 2018
Guys what I had to do is rendering with the Render OGL way from the viewport, it lacks quality controls but it works with movies with my workaround. Hope that helps!
Dec 12 2018
OK I found a hack for the hack :) When rendering doesn't work, you can render a "Playblast" with View/Viewport Render Animation.
Dec 10 2018
I don't know what else to say :) The hack works for me. Did you actually execute the script? In my original screenshot I have the Register option enabled. This makes it so that the script is executed automatically on load. Also the Auto Run Python Scripts preference must be enabled..
I see this keeps popping up, and with good reasons. Is this going to be fixed soon?
Dec 8 2018
@Martin Harth (mhcall) I see you have 2 copies of the movie, the one your referencing in the script is Kati.mp4, the one in the image editor is Kati.mp4.001
@Martin Harth (mhcall) It does work with rendering animation for me
I just got the same bug, here is a super simple file that crashes consistently when you press 3 for left view on 6a5e8096973 win64
Dec 7 2018
@Martin Harth (mhcall) You have a typo in line 4.
Dec 6 2018
Well in case anyone else needs it urgently, for now I've hacked it with a frame change handler. It works in viewport and render but only if the image editor is present :p
Hi, any update or workaround on this issue? We're being hit by it :)
Dec 4 2018
@Brecht Van Lommel (brecht) I see, so this is a temporal solution while the UI for left click select is polished?
Dec 3 2018
Dec 1 2018
Not only render modes, EVERY hotkey is listed as O
Nov 28 2018
Can not reproduce on latest build
This has been fixed and reported already. Please update your build
Nov 27 2018
I think this is supposed to be fixed on 1d4ad6819857 while the latest build is only 26b1aa99436 so it might indeed be fixed already but have to wait for next autobuild to confirm
It's still crashing. If it doesn't crash at first try switching to a few tabs and then sculpt
Nov 26 2018
Have you guys thought about a getting into test driven development?