Sorry about that, I missed your email. And yes the problem has been resolved.
You can kind of see it when you get really, really close in wireframe mode, but it only becomes obvious while specifically panning or orbiting. Can't see it while zooming.
Awesome, thank you.
Is this bug a regression related to this issue ?
Seems like this hasn't been fixed completely. It still doesn't work when the curve doesn't have any volume/geometry (bevel or profile). In 2.79 this was working as expected.
a simple curve with mirror modifier
a curve with bevel profile
working as expected in 2.79
First contributor here. I managed to reproduce with the Linux build. I'll start looking into this.
If you have a special blend file where something fails, you can strip out everything that is irrelevant to the bug and attach the blend file here. In the meantime I will tag this as incomplete.
Oh, yeah, very sorry - totally works in default scene!
Apologies, will double check next time!
Must be my scene :l
The house in that scene is 700m by 450m by 280m. I imagine default settings aren't meant for such scales.
I have the same issue, the keymaps are not persisted.
Can confirm in that file indeed....
Hi Brecht, you're quite right, I've just checked the system log and it was gpu timeout.
Sure. I simplified the project a bit and just left the object I'm having issues with. Gave it another test and it's still coming up with the same problem.
Sorry for the late reply!
latest build tested: blender-2.80.0-git.1c7695b8483d-windows64
This build works (final rendered image output is there, not blank) with all the scenes except for koro and splash_278 (Blenderman) - GUI and CLI as well.
classroom - the scene is now seemingly has all the objects in it, some lighting differences are present between v2.79b and v2.80 beta
fishy_cat - v2.79b fur is a bit more fluffier
splash_v277 - some beams are missing from v2.80 beta
splash_v277 / pavillon_bcn - different random seed generator
barbershop_interior - specular highlight differences
I can't reproduce the issue.
As i was deleting things, i figured out that the grilles are parented to another object.
If i delete the parent, the grilles move to the position considered wrong.
But what seems to be happening is that if both collections are linked togheter, the parent works.
If the collections are imported separately, the parent doesnt't works because they were on different collections.
@Brecht Van Lommel (brecht) get_devices() worked for me, thanks. On a side note, I've noticed that after I used get_devices() once, the devices started to appear in the list. What's a bit strange is that I previously did run Blender 2.79b in the background in a Docker container (via nvidia-docker) where Blender was installed from scratch and never ran with UI, and I did not run into this problem—the GPU was definitely working.
Indeed appears to be solved.
I've got the feeling that commit 5e121c8eab23d3d42745277f9c92617cb0aeb066 by Stefan Werner has resolved this issue. So far I had no more crashes.
Ah oops, you are right; it felt right, but was not.
I'm unsure what you mean with "Blender keeps rendering the last image".
Can you prepare and upload a simple .blend file that shows the issue?
hmmm, can't confirm that. I get x <-> y switched and an upside down z axis. Seems to be the case in your captured clip too. Or maybe I am misunderstanding what you mean
Thanks! That helped. Here is an even simpler case:
the modifier on the plane is only there to give it some motion & can be deleted. the cube is parented to 3 verts of the plane, try to move it along any axis.
Probably related: T60577