- User Since
- Mar 9 2013, 6:17 PM (300 w, 1 d)
Sat, Dec 8
If it is indeed a driver issue, there is not much we can do.
Did you try the latest drivers available for your card?
Fri, Dec 7
Can you post the output if you run blender with --debug-gpu
Additionally, can you try if --debug-gpu-force-workarounds makes any difference?
Can you try running blender with --debug-gpu and provide the output here.
Additionally, run blender with --debug-gpu-force-workarounds and see if that fixes it.
Can you run blender with --debug-gpu and perhaps try if --debug-gpu-force-workarounds fixes this?
I can not reproduce this error. Can you try updating to the latest blender beta and additionally updating your GPU drivers to the latest version.
I can reproduce this on the old version you are using, however this is not the case with a build from today. So I'm marking this as resolved
That is not a graphics card. That is a motherboard...
Figure out what GPU you have and then get back to me.
I've noticed that this also happens in 2.79 for me. So I'm unsure if this is intended or not.
I'm guessing that the GPU driver are old and buggy. The must have not seen any updates for a very long time at least.
I don't know if there is much to do here.
I should note that I didn't need to move the subsurf modifier to get this result. It's enough add it first and add a skin mod on top.
This works as intended in 2.8 (just pressing c works)
Try updating to a later blender beta. The one you used is quite old by now.
@Brecht Van Lommel (brecht), I don't know who to assign this to.
Besides checking newer blender builds, I would suggest getting the latest drivers for your GPU: https://www.amd.com/en/support/graphics/radeon-500-series/radeon-rx-500-series/radeon-rx-540
Is this still a problem in newer blender betas?
If it still is, provide the output if you run blender with --debug-gpu and check also if --debug-gpu-force-workarounds solves anything
If updating drivers or moving to a newer blender beta does not work, try starting blender with --debug-gpu or --debug-gpu-force-workarounds and report your results here.
I'm guessing that this is a rendering issue on Mac OSX
The blender 2.8 version should include build data and hash.
You should also try the newest blender 2.8 beta version as a lot of graphics bugs and crashes has been resolved.
You could also try newer blender beta versions. The one you tried is quite old now.
I can not reproduce this. Please download the latest blender beta and see if the problem still remains.
I can reproduce this. The Z rotation speed of the cylinder stays the same when changing the generator settings.
This page is for feature requests and discussion: https://blender.community/c/rightclickselect
The drivers in the appended file does not work in 2.8
I've created one with drivers for 2.8
Can you add a blend file so I can try this out easily? There is a lot of bug reports flooding in so it would be great if I could check this quickly
@Brecht Van Lommel (brecht) unsure who to assign this to.
I can confirm that this happens for me too. This is the segfault backtrace:
Can you try the blender beta from today and see if the problem is still there.
I can not reproduce this in Linux. I get the reverse (and that is to be expected if it works correctly).
IIRC, this was a problem a long time ago as well. So it seems like the problem has come back from the dead to haunt us once more.
This seems to work well in the 2.79 master branch.
Before I assign this to the maintainer of the graphics system in blender, I would like us to try out a few things first.
I talked to Sergey about this a bit on IRC and it seems like there will be slow down if we are to support this.
So I can mark this as resolved?
I can reproduce this issue if I try your build commit. However as my initial test were from a newer build (where it didn't happen), I'll mark this as solved.
This seems to work for me.
blender2.8, commit date: 2018-12-07 08:10, hash: 32aefb6fba
I've created a file for easy testing:
The changes in cycles seems to indeed affect the eevee render.
I can not reproduce this on my AMD 290x running linux.
I'll mark this as resolved then
I can not reproduce this on my AMD 290x in Linux.
Do you have a minimal blend file that has this problem?
Do not create new tasks for every edit you do. Keep them in the one you created...
Can you provide a simple .blend file that makes it really easy to reproduce this issue?
Don't know if it is you or Dalai I should assign this to @Brecht Van Lommel (brecht).
This is just how clipping values work. If you have a low near clipping value and a high far value, there will be issues on objects far away from the camera. There is no getting away from that.
You need to follow the bug report template for us to be able to reproduce this and help you.
In this case, besides providing some the info requested in the template, you should attach a minimal .blend file that has this problem so we can easily reproduce the issue.
Thu, Dec 6
We do not close this now. We will close it when my patch has been accepted or if it is decided to keep it as it is now.
@Brecht Van Lommel (brecht) Yes, thank you! :)
I put in your card on the nvidia website (or so I hope) and got this link:
Your driver seems to be a bit older:
I've submitted a fix: D4042
My suggestion is that you find out what graphics card you have and then try to update to the latest graphics card drivers. This might be related to outdated drivers.
Have you tried updating to the latest nvidia drivers?
Can you provide a minimal .blend that has this issue? It's really hard to reproduce this with just your description.
Have you tried updating your GPU drivers? https://downloadcenter.intel.com/product/98909/Intel-HD-Graphics-630
I'm suspecting that this is a driver bug.
You can still get the old functionality if you choose pivot point to active element instead of median.
However as you pointed out, in 2.79 this wasn't needed as it automatically scaled the handles from the active element even if you were in median mode.