Yes sorry for missing file. Ive tried adding the minimal parts need to reproduce this. Prior this would work when only the Class header had _MT_ in it. I think since release candidate 1 or 2 it stopped. Until yesterday i didn't looked at it. but had to since i wanted to update an addon. I noticed that now the bl_idname also needs _MT_ in it properly. Yet operators still work using say qs.quick_switch.

Please provide a Python script to reproduce the problem.

hi Phillipp solved by delete blender Foundation folder under C:\Users\myusername\AppData\Roaming and then relunch blender and reconfigure everything include addons except easy HDRI then save startup file and reopen blender many times and it's working fine thanks for help

oh easy HDRI addon always there i try to uninstall it then load default then save startup to get ride of it but it always there

even when i reset hdri addon still have the issue no idea why

oh easy HDRI addon always there i try to uninstall it then load default then save startup to get ride of it but it always there

hi every time i restart the pc and open blender undo not working i have to load default then it will work but the issue of load default i have to reconfigure everything
addons is booltools and edgeflow nothing else
even without addons it still not working
i tried to uninstall redownload and install blender and remove all files in roaming but still the issue i go to system setting and make bigger undo size and still no luck

Is this happening on every restart?

All the same, I left this setting. Now face-loops affect when creating Surface.

System Information
Operating system: Windows-10-10.0.17763 64 Bits
Graphics card: GeForce GTX 745/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 353.62

Steps to recreate the issue:
Step 1: create a plane in a new instance of blender.
Step 2: go to edit mode and in the N panel > "View" > "MeasureIt Tools" click "AREA" and "Segments" button while selecting the face of the plane also click "Show"
Step 3 : set the units to imperial mode in the Units panel in the scene context.
Step 4 : set the Units in the N panel plane to feet. This step should result in area=43.06ft^2 and segments=6.56ft on all sides
Step 5: in the plane panel of measure it check the "SCALE" check box and set it to 1:6 This step results in area=258.33ft^2 and segments=39.37ft the area according to my math should be 1,549ft^2
I guess this is only an issue if I use that scale check box which I did to quickly adjust the scale to match a satellite image I was looking at. Moving forward I just won't use scale. Is that how it is supposed to work?

The add-ons are not made by me.

Just a note while you're at it, can you make the scattering process interactive, ie. users should be able to change parameters on the fly to see the changes before commit. I know we can undo and redo but that would make the add-on SUPER to use.

a system that announces when an addon can be updated would be fantastic :)

I am looking at the file when i open a new blender I don't seem to have this same issue. So I guess I am not sure how to recreate this. But this is the file I am looking at{F7680284}

Well, the error message is pretty self-explanatory: Tangent space can only be computed for tris/quads, aborting …

cannot reproduce, dont have issues installing zipped Addons in 2.80 or 2.81 master.

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.

Task T68943 was related to this too.

Hey again,

Well that’s bizarre, the latest Linux nightly build works for me, and the other builds are shipped with the same version of the add-on as well. Have you installed the add-on manually from the preferences, or copied the script in your addons directory? Could there be a conflict? If so, you should delete it so that Blender uses the one from the downloaded version.

I can confirm the issue. My first guess is that this is a bug in Blender and not in the addon, because the addon just declares the property as any other. Will have a look.

Hello Damien!

CC @Jacques Lucke (JacquesLucke)

In D3162#126725, @Piotr Nikov (piotrnikov) wrote:

Hello!
This doesn't seem to work on curve points. Unless I'm mistaken of course!
. Add Circle (or any sort of curves), go in Edit Mode.
. Choose point, Insert Key.
. Change frame, move point, Insert Key: The point snaps back to where it was, resulting in no animation...
Am I the only one?
Piotr

This is basically an empty report (google translate helps a bit "Cannot run Blender Kit").

we need more information here:

There have been changes to the default keymap (Cut Links is now Ctrl + RMB, see rB1e8b007d50f7) and NodeWrangler was changed to compensate (see rBAe08d6983c05f).
This should work in 2.80 and current builds, please try these (not sure which exact version you are using -- wasnt mentioned in the report...).

The 2.8 porting and api refactor was done by @Alexander Gavrilov (angavrilov) so should probably better let him have a look at it.

Hello!
This doesn't seem to work on curve points. Unless I'm mistaken of course!
. Add Circle (or any sort of curves), go in Edit Mode.
. Choose point, Insert Key.
. Change frame, move point, Insert Key: The point snaps back to where it was, resulting in no animation...
Am I the only one?

I also just noticed when I hover over brush options , the words Internal Error appear in bright red.

I have downloaded it and am still experiencing the same issue. The Keymap preference area is empty and I cannot click on anything except menu tabs and no hotkeys work.