Principled BSDF stuck on "updating shaders" #53117

New Issue

Vilgot Larsson · 2017-10-20T21:33:11+02:00

Vilgot Larsson commented

2017-10-20 21:33:11 +02:00

System Information
Windows 10 Pro Creators fall update 1709
GTX 1080Ti with latest 387.92 Drivers
Ryzen R5 1600 OC 3.9GHz
Asus X370-PRO latest BIOS 902

Blender Version
Broken: 2.79 - cb957fd
Broken: 2.79 - 5bd8ac9
Worked: None

Short description of error
Each time I enter rendered view (cycles) the screen goes black and it says "updating shaders" and take everything between 30 seconds to over a minute before thre rendered view appears. This happens every time both with AMD and NVIDIA GPU.
Rendered view does however load instantly when the model doesn't use Principled BSDF. So we have narroweed the issue down to having something to do with it. I'm on a fresh installation of windows10. This also doesn't happen on two of my friend's PC's.

Exact steps for others to reproduce the error
Basically load up a model without the Principled BSDF and rendered view loads instantly like it should. Load in another model with Principled BSDF and it takes 30-90 seconds before it appears. Note that the exact same thing happened on both NVIDIA and AMD graphics cards with latest drivers installed.

**System Information** Windows 10 Pro Creators fall update 1709 GTX 1080Ti with latest 387.92 Drivers Ryzen R5 1600 OC 3.9GHz Asus X370-PRO latest BIOS 902 **Blender Version** Broken: 2.79 - cb957fd Broken: 2.79 - 5bd8ac9 Worked: None **Short description of error** Each time I enter rendered view (cycles) the screen goes black and it says "updating shaders" and take everything between 30 seconds to over a minute before thre rendered view appears. This happens every time both with AMD and NVIDIA GPU. Rendered view does however load instantly when the model doesn't use Principled BSDF. So we have narroweed the issue down to having something to do with it. I'm on a fresh installation of windows10. This also doesn't happen on two of my friend's PC's. **Exact steps for others to reproduce the error** Basically load up a model without the Principled BSDF and rendered view loads instantly like it should. Load in another model with Principled BSDF and it takes 30-90 seconds before it appears. Note that the exact same thing happened on both NVIDIA and AMD graphics cards with latest drivers installed.

Vilgot Larsson commented

2017-10-20 21:33:11 +02:00

Changed status to: 'Open'

Vilgot Larsson commented

2017-10-20 21:33:12 +02:00

Added subscriber: @Wiloh95

Brecht Van Lommel commented

2017-10-20 22:03:18 +02:00

Added subscriber: @brecht

Brecht Van Lommel commented

2017-10-20 22:03:18 +02:00

Does it happen with CPU rendering, or only GPU rendering? Does it happens with a final (F12) render? Did it always happen, or only after e.g. an operating system or driver update?

Please:

Attach a .blend to reproduce the issue.
Try to redo the problem with File > Load Factory Settings.

I've done hundreds of renders with the principled BSDF and didn't notice this, so there must be something specific about your setup that reveals this bug, the question is what that is.

Does it happen with CPU rendering, or only GPU rendering? Does it happens with a final (F12) render? Did it always happen, or only after e.g. an operating system or driver update? Please: * Attach a .blend to reproduce the issue. * Try to redo the problem with File > Load Factory Settings. I've done hundreds of renders with the principled BSDF and didn't notice this, so there must be something specific about your setup that reveals this bug, the question is what that is.

Vilgot Larsson commented

2017-10-20 22:33:49 +02:00

Thanks for the fast reply Brecht Van Lommel (brecht). I've made some progress in figuring out what's wrong.

First things first, the issue happens both with CPU render and with F12. But now I have a reason to believe it is perhaps not a Principled BSDF issue.

The Blend file I've been using has two linked models, and switching to rendered view takes 30-90 seconds. If I hide one of the models, suddenly it only takes 4-10 seconds to enter rendered view. I've tried hiding each individual model with identical results. If I then unhide the model while in rendered view it pops in immideately.
So now I think it might be some issue with linking models, I would love to attach the blend files but they're NSFW and I'm unsure of that's allowed to be posted here.

Thanks again for the help :)

Thanks for the fast reply Brecht Van Lommel (brecht). I've made some progress in figuring out what's wrong. First things first, the issue happens both with CPU render and with F12. But now I have a reason to believe it is perhaps not a Principled BSDF issue. The Blend file I've been using has two linked models, and switching to rendered view takes 30-90 seconds. If I hide one of the models, suddenly it only takes 4-10 seconds to enter rendered view. I've tried hiding each individual model with identical results. If I then unhide the model while in rendered view it pops in immideately. So now I think it might be some issue with linking models, I would love to attach the blend files but they're NSFW and I'm unsure of that's allowed to be posted here. Thanks again for the help :)

Brecht Van Lommel commented

2017-10-20 22:45:54 +02:00

I'm not concerned about NSFW content. If you want you can usually e.g. remove objects, randomize mesh vertices, replace images, .. so that the bug remains but the file is unrecognisable.

mathieu menuet commented

2017-10-21 08:06:25 +02:00

Added subscriber: @bliblubli

mathieu menuet commented

2017-10-21 08:06:25 +02:00

I had the same problem with 1080Ti and win7. It was on classroom scene, so it had nothing to do with principled shader. Killing the process, restarting Blender and relaunching the render was enough. No idea what happened as I was using the release UI without any debug info and I couldn't reproduce it since then. It happened just after opening the scene and hitting F12.

Vilgot Larsson commented

2017-10-22 13:54:48 +02:00

Hi, sorry for the late reply, I now have a blender file that you can try downloading. The error hasn't changed in any way so far, so it feels like this might be some weird hardware error for me.

https://www.dropbox.com/s/6udm704e88dk0mi/Ticket-#53117.blend?dl=0

EDIT: just a reminder that the file is very NSFW

Hi, sorry for the late reply, I now have a blender file that you can try downloading. The error hasn't changed in any way so far, so it feels like this might be some weird hardware error for me. https://www.dropbox.com/s/6udm704e88dk0mi/Ticket-#53117.blend?dl=0 EDIT: just a reminder that the file is very NSFW

Brecht Van Lommel commented

2017-10-26 01:21:01 +02:00

Haha, that's not for the faint of heart.

Here updating shaders takes about 10s, and what it's doing is loading packed image textures. Some images seem to be missing from this .blend, and combined with possibly a slower hard drive or CPU than I tested on, I can see this taking 30s-60s.

Did you originally have image textures packed into the .blend, or did you only pack them for uploading the .blend here? I can see that our packed image loading code is single threaded, and ends up under "updating shaders" in the progress. If the images are not packed then it should be multi-threaded and show separately, although we do also peek at the image file header during when updating shaders.

Haha, that's not for the faint of heart. Here updating shaders takes about 10s, and what it's doing is loading packed image textures. Some images seem to be missing from this .blend, and combined with possibly a slower hard drive or CPU than I tested on, I can see this taking 30s-60s. Did you originally have image textures packed into the .blend, or did you only pack them for uploading the .blend here? I can see that our packed image loading code is single threaded, and ends up under "updating shaders" in the progress. If the images are not packed then it should be multi-threaded and show separately, although we do also peek at the image file header during when updating shaders.

Vilgot Larsson commented

2017-10-26 14:34:48 +02:00

Good news, the problem has been solved. Turns out it was exactly what you suggested, unpacking all the files of the models makes everything load just as fast as it should.
I had a very hard time finding any help about this issue on google so maybe post it in a faq somewhere so other people can easily find the fix to this issue. :)

PS. I ran into another issue that made my blender crash everytime I tried to render, turns out the overlay Geforce experience has and parhaps the windows one (for games live) as well will make the software crash, after turnings these off/uninstalling I could render again without any issues :)

Thanks again Brecht Van Lommel for great and fast help, much appreciated!

Good news, the problem has been solved. Turns out it was exactly what you suggested, unpacking all the files of the models makes everything load just as fast as it should. I had a very hard time finding any help about this issue on google so maybe post it in a faq somewhere so other people can easily find the fix to this issue. :) PS. I ran into another issue that made my blender crash everytime I tried to render, turns out the overlay Geforce experience has and parhaps the windows one (for games live) as well will make the software crash, after turnings these off/uninstalling I could render again without any issues :) Thanks again Brecht Van Lommel for great and fast help, much appreciated!

Brecht Van Lommel commented

2017-10-30 03:15:23 +01:00

Changed status from 'Open' to: 'Archived'

Brecht Van Lommel closed this issue

2017-10-30 03:15:23 +01:00

Brecht Van Lommel self-assigned this 2017-10-30 03:15:23 +01:00

Brecht Van Lommel commented

2017-10-30 03:15:23 +01:00

Ok, will close the report then. Certainly we can optimize some things with packed images, but will not consider those bugs for now.

We've reported the In-Game Overlay issue to NVidia, other users have found the same issue.

Ok, will close the report then. Certainly we can optimize some things with packed images, but will not consider those bugs for now. We've reported the In-Game Overlay issue to NVidia, other users have found the same issue.

Sign in to join this conversation.

No Label

Download

What's New

Blender Studio

Manual

Developers Blog

Documentation

Benchmark

Blender Conference

Development Fund

One-time Donations

Principled BSDF stuck on "updating shaders" #53117