ill fix the materials code so you can view objects clear.
What do I have to do in the file to make the bug appear?
I can reproduce this on Linux (using a AMD 290x).
Ah I see what you mean! I didn't change the steps in the viewport yet.
Even after changing the viewport steps to 9 you don't see it happening on the viewport?
Thank you for testing it out Wo.
I have other files that give me the same issue, so I will definitely test it out as you suggested by reducing children/steps and write a report to let you guys know how that went.
@Clément Foucault (fclem) There's no a build since 4th dec for Mac OSX.
I can confirm and I have a gtx 1060 6gb as well (blender-2.80.0-git.e79bb957fc3-windows64)
Just typing this for a friend who tested my scenes but didn't create an account here yet: she has the same issues with a GTX 1080ti on Windows 10. Not sure why the hair renders normaly with F12 for you Jose, but clearly this is something that causes troubles on a lot of other systems.
Seems like it crashes now when i try to move anything else to the nodes for it.
Kinda sucks but i guess this is a crash report too.
It seems to not work with any other projects i use it on either. So must be more of a bug then a simple problem. (Tried fireflys fix but no luck).
NO! sorry it worked about my scene files,, but downloaded file still cause crush when select material.
With recent build version: 2.80 (sub 35), branch: blender2.8, commit date: 2018-12-08 17:06, hash: e79bb957fc3, type:
build date: 2018/12/09, 17:21
@Stephen Swaney (stiv) do you know anyone that know about mac and who can help me
for easy copy paste:
Sat, Dec 8
Adding: I have played with the reflection plane probe settings extensively, and tried repositioning the probe closer/further from the plane geo to see if that changes the result. Nothing seems to make an improvement, as far as I've been able to find.
cycles is ok anyway
I'm lost then. Because with both GPUs and OS on desktop and laptop (updated drivers and latest build) I get the same result: no hair in final render. I wonder if there's something in the settings that I need to tweak?
I have gtx 660, windows 10 64bit, lated daily 2.8 build. And this both scenes works ok for me.
Yes, you're right. I reloaded the orgingal 'Kati.mp4'.. however, it won't seem to work in the render view.
This is my current blender Version
@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
Fri, Dec 7
Not the physical graphics card itself, but the software driver that Blender (and everything else) uses to talk to the card and make colored dots on the screen.
and.. which built is in use at your site?
Repaired… nevertheless… no Ctrl+F12 result… stucks at one Frame.
Scrolling timeline, the Image Editor refreshes well, though.
@Stephen Hodnicki (stephen) Swaney (stiv) when you say video driver you mean my NVIDIA Geforce GTX 660M 512MB right ? and I dont know if this will help to figure out me problem with EEVEE but my cycles render is work fine
@Martin Harth (mhcall) You have a typo in line 4.
I think it is more than the specular behaving oddly, when I disable the the specular for the light we still see a bit of the bleeding, although not as obvious (and of course without specular enabled it won't look as nice). I wonder if there is a temporary workaround, since this bug (?) may take a bit of time to address.
Working here on linux. Maybe a video driver issue?
you guys are rock stars, hehe
I can not reproduce this. Please download the latest blender beta and see if the problem still remains.
The changes in cycles seems to indeed affect the eevee render.