I tried all of the versions actually, the only one that seemed to work correctly was the 2.8 branch. All other versions had the same errors.
With that same example .blend file, just turn the factor all the way down to zero. The shadow (or AO, more likely) remain:
'There can be missing image files and missing linked library .blend files, and those are quite different to Blender. Are you saying it's just the image texture that are missing, or are the materials and nodes missing (and so the image textures are also missing along with them)?'
The .blend file attached to this report seems to render correctly for me. If there's a different case that renders wrong, please do attach a .blend for that.
Did you download the Experimental Build Branch by VS 2015 build?
From the section marked as 2) here:
Is this supposed to be fixed in the latest builds? I'm still seeing artifacts in the nightly of 2.79 (more specifically, 2.78.5 1bd9531fda7).
Ok, I'm confused still.
The File: Bliblubli posted renders without error on Build: 57f937ad5a Blender 2.78.4 on an RX 480. Must be something that has changed after. Ill keep digging.
Thanks for the report, but the answer on stack exchange explains it. These do indeed work differently but that's not a bug.
Should be resolved by the previous commit.
A general rule of thumb is do not use drivers distributed by the computer manufacturer, always get them from the source, especially for gpu drivers. Try this and see if it fixes the issue.
Thank you for taking the time to look through the file, resetting the scale of the object fixed the issue.
Hi try the to substitute the files in the attached .rar:
- make a backup copy of the files ui.py and rig_lists.py you find in rigify main folder
- unzip the content in the same folder and overwrite
Reproduced on latest master, macOS, python3.6
I think from the internet that I read, it's an issue with your Intel HD 360 driver, which is why Blender works with NVidia GeForce.
I'll leave it to developer to confirm and close this bug report, but it seems that it's a Windows 10 issue.
Run blender.exe while explicitly choosing the dedicated graphics processor.
@Luciano Muñoz Sessarego (looch)
Could you please try the attached patch?
The problem was probably the Panel draw method calling a function that's importing modules at runtime
I think we should wait till after 2.79. This could change existing setups and it is too late in the release cycle to introduce changes like this.
Asserts OpenGL 4.4 support.
Screenshot of said "pop-up window"