- User Since
- Jul 10 2015, 5:49 AM (202 w, 2 d)
Thu, May 23
Removing volume scatter from the broken file seems to fix the smudging. Copying all objects into a new file (Blender Build 2019-05-23 14:37, hash: rBfd3f75a02cf9) with volume scatter also works fine.
Wed, May 22
Fri, May 17
Not sure if this matters, but camera properties changed from bpy.context.object.data.dof_gpu.fstop (I think)
bpy.context.object.data.dof.aperture_fstop = 5
bpy.context.object.data.dof.aperture_blades = 6
bpy.context.object.data.dof.focus_distance = 2
Mar 25 2019
Jan 17 2019
What is the best performing workaround for this? Linked duplicates instead of collections?
Dec 13 2018
Seems to be working fine in the past week's builds! Thank you. It was broken for about a week around the time of this bug report.
Nov 29 2018
Jun 20 2018
Found another detail to the problem. Remap relative works properly if I import an alembic. If I import 2 alembics, the 2nd imported does not remap relative, while the first imported does. (These alembics are coming from Maya)
Apr 20 2018
I found more detail on the problem:
Mar 29 2018
Antonio, I agree! Especially for repetitive tasks like color picking, it's a huge deal to have a popup happening under the cursor to reduce mouse travel.
https://youtu.be/QNixxQ6BVxQ Here is a materials popup I made for this purpose + a few convenience scripts. This also frees up a properties area for something else...before I found myself switching tabs there too often to get to materials.
Mar 16 2018
I guess this isn't the right place, but can I ask for a relative file paths option on Alembic import?
Mar 15 2018
Jul 10 2015
Just checking in to say I'm having the same experience with my MSI 980ti with 353.30 drivers.