Change for 2.8

Sun color not adjustable , sun size difficult to adjust,(allways to big). Seems to be the same addon as for 2.79 without any changes to 2.8,

Oki, thx for getting back, closing then

Thank you very much for the idea of interface problems.
I turned off the interface addons one by one and checked to see if the Node Wrangler was enabled.
It turned out that PieMenu Editor causes this error.

Not able to reproduce.
Please note that NODE_PT_backdrop is part of the 2.80/scripts/startup/bl_ui/space_node.py.
not being in bpy.types means that error occured during register of the ui, or that somehow the ui is registered after the add-ons are registered, what seems strange.

Just pulled and rebuilt-- the properties are getting through!

please accept my apology, I thought this was a bug.. I totally overlooked the simplify.

I came to the same conclusion as @Marcin Twarowski (Tvaroog) and @Alex (SpectreFirst) .

You have "simplified" turned on in render settings. Render is set to "3", viewport is set to "0" subdivisions.

I have looked into provided file and found out that your rendering settings have Simplify enabled and Max Subdivisions is set to 0. Therefore, your model is not subdivided in viewport but when you render the final image, model gets subdivided twice by Subdivision Surface modifier and receives artifacts. When I disable Simplify and set Render and viewport subdivisions to 2, model receives the same artifacts in viewport as well. Disabling Subdivision Surface modifier seems to solve the problem in both viewport and final render.

(Also note that although the normals are wrong blender can import both while Rhino actually only supports the old one :) Good job guys)

@Brecht Van Lommel (brecht) you may also have an idea about why that conversion was needed back then too? And whether we can just use FBX value directly nowadays?

That conversion factor in import goes back to 2013 (rBA53f601943472b, initial commit adding some import support to generate Cycles materials from FBX - we did not have any way to export those at the time).

I'm happy with the maturity that this addon has attained, and so I've added the Collection Manager to the addons contrib repo, per @Brendon Murphy (meta-androcto)'s suggestion, and created a blenderartists page for additional feedback from the community https://blenderartists.org/t/contrib-addon-wip-collection-manager-feedback/1186198. This doesn't mean I've forgotten about the feedback and suggestions here and I still intend to continue development as usual. For now here's a new picture in case anyone's interested, but hasn't downloaded it yet. The current plan is to start experimenting with the "restore on quit" feature next.

I can confirm the creation of $HOME/blenderkit_data.

Yep, that was awesome)
Is it planned something for materials/textures support?

@Brendon Murphy (meta-androcto) We are both signed up and will send the email as soon as we have prepared it thoughtfully.

@Bastien Montagne (mont29) Sorry my update overwrote your changes.

I have maybe solved the problem. I started an old file with drag&drop on the exe-file, and all came back. I saved the file as startup file, open again a new file, deleted all, and saved the file as startup-file. The file are not working and still have the same problem. See last comment, where the file was uploaded

@Rune Morling (ermo) @Alan Odom (Clockmender) hi, the following is a template about access to the blender addons project. I think it's a good time now to start the review process.

hi @Rune Morling (ermo) the best option at this time is to create a wiki on your github. I'm still working on the Add-ons Manual, we have already accepted docs from github wiki or/and linked into github wiki via the addon. Later down the track I can look at the Blender Manual page and either transfer your work or link to your git.

See below

We would like to prepare a manual for PDT. Should we be using the official Blender wiki or ...?

This is in the Redo HUD now