Addon activate error Poliigon #105356

New Issue

Stan long · 2024-06-14T22:58:39+02:00

Stan long commented

2024-06-14 22:58:39 +02:00

System Information
Operating system: Windows 10 x64
Graphics card: 2x Geforce 1080Ti

Blender Version
Broken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)
Worked: (newest version of Blender that worked as expected)

Short description of error
Error activating (checking the box) for Poliigon add-on in Blender v4.1.1 portable (.zip) version

Exact steps for others to reproduce the error
Move the extracted add-on to user folder. Launch Blender and go to Edit==>Preferences==?Add-ons and check the Poliigon add-on. The error message in in attachment "Poliigon Activate Error". I've tried this with v4/1/1 and v4.0 I use the portable version on Windows 10 x64.

I contacted Poliigon support and they feel it's an internal Blender issue. They gave me a command to enter into the python scripting console. I did that and it returned the same error message. See "BPY Error" attachment.

I've included the actual Poliigon add-on for your testing. I understand this is a Blender Inc vs 3rd party issue. I'm just looking for direction.

Stan Long

**System Information** Operating system: Windows 10 x64 Graphics card: 2x Geforce 1080Ti **Blender Version** Broken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen) Worked: (newest version of Blender that worked as expected) **Short description of error** Error activating (checking the box) for Poliigon add-on in Blender v4.1.1 portable (.zip) version **Exact steps for others to reproduce the error** Move the extracted add-on to user folder. Launch Blender and go to Edit==>Preferences==?Add-ons and check the Poliigon add-on. The error message in in attachment "Poliigon Activate Error". I've tried this with v4/1/1 and v4.0 I use the portable version on Windows 10 x64. I contacted Poliigon support and they feel it's an internal Blender issue. They gave me a command to enter into the python scripting console. I did that and it returned the same error message. See "BPY Error" attachment. I've included the actual Poliigon add-on for your testing. I understand this is a Blender Inc vs 3rd party issue. I'm just looking for direction. Stan Long

Poliigon Activate Error.txt

1.6 KiB

BPY Error.txt

343 B

poliigon-addon-blender.zip

1.0 MiB

Stan long added the

labels 2024-06-14 22:58:39 +02:00

Cedric Steiert commented

2024-06-16 23:32:43 +02:00

Can't replicate the issue unfortunately. I can install and activate the attached addon just fine in portable and local blender version.

Here are some common troubleshooting tips:

Make sure you are using the latest addon version.
Do you have other external addons installed for that version?
Have you tried removing all poliigon addon related files and install the addon directly with the .zip file via Edit > Preferences > Addon-ons > Install?
Does this issue only occur on a portable version or also on a local install of blender? Where did you download it? Are you sure it is the official download from https://www.blender.org/download/?
Is a previous version working like expected, e.g. blender 3.6 or an upcoming (4.2)?
Are you able to test it on other PCs as well?
Try running blender as admin.
Try resetting blender to factory settings (it is possible that the startup.blend and userpref.blend got corrupted somehow somewhere). Start blender with --factory-startup. After resetting try again.
for further debugging: attach more system and environment info as well as logs etc

I did some googling and a somewhat recent similar issue from BlenderKit addon comes up for only a few users: https://github.com/BlenderKit/BlenderKit/issues/1038

Could you try installing that addon? Does the issue also happen?
If the issue happens, could you follow the steps listed by the dev: https://github.com/BlenderKit/BlenderKit/issues/1038#issuecomment-2076956799

From my current understanding of the error trace it all boils down to from bpy.app.handlers import persistent not working on your system and thus throwing an attribute error. Why though i don't understand as i'm not a blender dev and don't know the architecture too well. My best bet would be a) corrupt script files or b) uncomplete bootstrapping whilst loading an addon which tries to load it (thus the frozen state).

Can't replicate the issue unfortunately. I can install and activate the attached addon just fine in portable and local blender version. Here are some common troubleshooting tips: - Make sure you are using the latest addon version. - Do you have other external addons installed for that version? - Have you tried removing all poliigon addon related files and install the addon directly with the .zip file via Edit > Preferences > Addon-ons > Install? - Does this issue only occur on a portable version or also on a local install of blender? Where did you download it? Are you sure it is the official download from https://www.blender.org/download/? - Is a previous version working like expected, e.g. blender 3.6 or an upcoming (4.2)? - Are you able to test it on other PCs as well? - Try running blender as admin. - Try resetting blender to factory settings (it is possible that the `startup.blend` and `userpref.blend` got corrupted somehow somewhere). Start blender with --factory-startup. After resetting try again. - for further debugging: attach more system and environment info as well as logs etc I did some googling and a somewhat recent similar issue from BlenderKit addon comes up for only a few users: https://github.com/BlenderKit/BlenderKit/issues/1038 - Could you try installing that addon? Does the issue also happen? - If the issue happens, could you follow the steps listed by the dev: https://github.com/BlenderKit/BlenderKit/issues/1038#issuecomment-2076956799 From my current understanding of the error trace it all boils down to `from bpy.app.handlers import persistent` not working on your system and thus throwing an attribute error. Why though i don't understand as i'm not a blender dev and don't know the architecture too well. My best bet would be a) corrupt script files or b) uncomplete bootstrapping whilst loading an addon which tries to load it (thus the frozen state).

Damien Picard commented

2024-06-17 11:29:46 +02:00

Looks related to #105049. Have you installed any other third-party add-on? Maybe things related to StarFab?
Could you tell us what is inside %USERPROFILE%\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\modules?

Looks related to #105049. Have you installed any other third-party add-on? Maybe things related to StarFab? Could you tell us what is inside `%USERPROFILE%\AppData\Roaming\Blender Foundation\Blender\4.1\scripts\modules`?

Pratik Borhade added

Status

Needs Information from User

and removed

Status

Needs Triage

labels 2024-06-19 11:11:12 +02:00

Stan long commented

2024-06-20 04:49:35 +02:00

All
I've spent the last 10+ hours tring to diagonse this issue. In my production folder I have 31 other addons installed and none are displaying any issues. There are no error in the Edit==>Preferences==>Add-ons. The other addon work as needed including the Flip Fluid add-on. I reverted to previou versions to see when things stopped working. Here are my finding:

v3.6LTS
I downloaded the 3.6LTS portable (.zip) from the Blendor.org website into a clean folder. By clean, I men on a drive not linked to my original installation of Blender and shares nothing with my 'Production' install. I installed the Poliigon addon with the Install option as well as the static addon folder. Both worked perfectly. I was able to use the addon as described.

v4.0.0
I downloaded the 4.0.0 portable (.zip) from the Blendor.org website into a clean folder. I attempted to install the Poliigon addon using the Install option as well as the static addon folder. Both methods failed with the same traceback.

Something has changed between 3.6LTS and 4.0.0. I tried to follow the traceback calls and followed it down to a call in the Poliigon Toolbox module to:

from bpy.app.handlers import persistent

Which then goes into code that I could not find in Blender. I'm at my end of debugging.

File "shibokensupport/signature/loader.py", line 61, in feature_imported
File "shibokensupport/feature.py", line 135, in feature_imported

I've included System_info.txt, a listing of all my Set commands

All I've spent the last 10+ hours tring to diagonse this issue. In my production folder I have 31 other addons installed and none are displaying any issues. There are no error in the Edit==>Preferences==>Add-ons. The other addon work as needed including the Flip Fluid add-on. I reverted to previou versions to see when things stopped working. Here are my finding: v3.6LTS I downloaded the 3.6LTS portable (.zip) from the Blendor.org website into a clean folder. By clean, I men on a drive not linked to my original installation of Blender and shares nothing with my 'Production' install. I installed the Poliigon addon with the Install option as well as the static addon folder. Both worked perfectly. I was able to use the addon as described. v4.0.0 I downloaded the 4.0.0 portable (.zip) from the Blendor.org website into a clean folder. I attempted to install the Poliigon addon using the Install option as well as the static addon folder. Both methods failed with the same traceback. Something has changed between 3.6LTS and 4.0.0. I tried to follow the traceback calls and followed it down to a call in the Poliigon Toolbox module to: from bpy.app.handlers import persistent Which then goes into code that I could not find in Blender. I'm at my end of debugging. File "shibokensupport/signature/loader.py", line 61, in feature_imported File "shibokensupport/feature.py", line 135, in feature_imported I've included System_info.txt, a listing of all my Set commands

system-info.txt

27 KiB

Set.txt

2.5 KiB

Stan long closed this issue

2024-06-20 04:49:36 +02:00

Blender Bot added

Status

Archived

and removed

Status

Needs Information from User

labels 2024-06-20 04:49:38 +02:00

Stan long commented

2024-06-20 04:50:44 +02:00

I'm looking for support. Something changed from v3.6LTS and v4.0.0

Cedric Steiert commented

2024-06-20 05:32:10 +02:00

I don't know if the close of this issue was intentional @StanLong ?

However have you already tried removing the conductor addon, it's the only odd 3rd party addon from your system-info output: conductor (version: (0, 2, 2, 0), path: C:\Users\Stan\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\conductor.py).

Haven't looked at the rest of the output as it's too much to read right now.

Also i'd like to clarify that a protable blender version is using the preferences from the AppData folder if already set by a previous install. So your clean approach isn't very clean at all.
If you truly want a clean system either download a version you've previously never used (e.g. blender 4.2) or backup and remove the app data folder for the blender version you wish to debug. After a backup you can load factory settings. A backup would be needed so that you can revert back to your old settings any time.

Could you report back when done testing?

I don't know if the close of this issue was intentional @StanLong ? However have you already tried removing the conductor addon, it's the only odd 3rd party addon from your system-info output: `conductor (version: (0, 2, 2, 0), path: C:\Users\Stan\AppData\Roaming\Blender Foundation\Blender\4.0\scripts\addons\conductor.py)`. Haven't looked at the rest of the output as it's too much to read right now. Also i'd like to clarify that a protable blender version is using the preferences from the AppData folder if already set by a previous install. So your clean approach isn't very clean at all. If you truly want a clean system either download a version you've previously never used (e.g. blender 4.2) or backup and remove the app data folder for the blender version you wish to debug. After a backup you can load factory settings. A backup would be needed so that you can revert back to your old settings any time. Could you report back when done testing?

Cedric Steiert referenced this issue

2024-06-22 18:04:52 +02:00

Freestyle SVG Exporter Add-on Error #105300

Sign in to join this conversation.