Blender 2.83 – OSL bug and fix

Software:
Blender 2.83

I recently found that some of my OSL shaders don’t work in Blender 2.83.
More specifically, shaders compiled with Blender 2.83 had their microfacet bsdf not recognized by the renderer and return 0.
* Shaders that were compiled by previous versions did work.
Looking into the problem I found that the OSL source files that ship with Blender 2.83 are significantly different than the files shipped with previous versions.

Simple fix:
Copy the stdosl.h and oslutil.h from Blender 2.82 to 2.83.
On Windows these files are found in this folder:
C:\Program Files\Blender Foundation\Blender 2.83\2.83\scripts\addons\cycles\shader

* I’m not suggesting to download the files strait from ImageWorks GitHub because I’m not sure the ones that ship with Blender & Cycles are not modified.

I have reported the bug here.

Related:
Using OSL Shaders in Blender & Cycles

GitHub Desktop – Not launching UI – Problem & Fix

Software:
GitHub Desktop 2.4.3 | Windows 10

About 1 or 2 weeks ago GitHub Desktop stopped opening it’s window when lunched.
It would run in the background, you could see it in the Windows Task Manager, but its window would not open.
Looking into this on various web discussions, I found that deleting the folder named app-2.4.3 in its application data solves the problem:
Annotation 2020-05-09 200238
This is the path to GitHub Desktop‘s data:
C:\Users\<YOUR USER>\AppData\Local\GitHubDesktop
After deleting the folder and re-launching GitHub Desktop, I found it generated a new folder with the same name, so I guess settings for the latest update got corrupted, and the software generated new settings..

 

Related:
UE4 GitHub Setup

 

Setting Windows 10 Ransomware protection not to block Adobe Photoshop

Software:
Adobe Photoshop 2020 | Microsoft Windows 10

If you encountered this error message when launching Adobe Photoshop:
“There was a problem with Generator. If the problem persits….”
Annotation 2020-04-18 221206

Chances are it has to do with Windows 10 Ransomware protection blocking it and one of it’s components, and if you continue to working with Photoshop with this problem you’ll find export modules (and maybe other features) not working.

In-order to fix the problem, we have to set Windows Ransomware protection not to block these components:

  1. In the Windows Virus & threat protection settings,
    Click Manage ransomware protection:
    Annotation 2020-04-18 221251
  2. In the Windows Ransomware protection settings,
    Click Allow an app through Controlled folder access:
    Annotation 2020-04-18 221352
  3. In the Allow an app through Controlled folder access settings,
    Click Add an allowed app:
    Annotation 2020-04-18 221420
  4. To avoid having to locate the specific executable files choose Recently blocked apps:
    Annotation 2020-04-18 221444
  5. In the Recently blocked apps select both AdobeGCClient.exe and Photoshop.exe:
    * Click the plus button to add them:
    Annotation 2020-04-18 221639

 

General note:
You may need to to the same with many other apps.
Every time you get a Windows notification about a process being blocked,
Visit the ransomware protection setting, check what was the last app being blocked and see if it needs to be allowed to operate

That’s it. hope you’ll find this helpful! 🙂