A.N.T. Landscape add-on cannot be enabled (2.79) #53537
Labels
No Label
Interest
Animation & Rigging
Interest
Blender Cloud
Interest
Collada
Interest
Core
Interest
Documentation
Interest
Eevee & Viewport
Interest
Geometry Nodes
Interest
Grease Pencil
Interest
Import and Export
Interest
Modeling
Interest
Modifiers
Interest
Nodes & Physics
Interest
Pipeline, Assets & IO
Interest
Platforms, Builds, Tests & Devices
Interest
Python API
Interest
Rendering & Cycles
Interest
Sculpt, Paint & Texture
Interest
Translations
Interest
User Interface
Interest
UV Editing
Interest
VFX & Video
Meta
Good First Issue
Meta
Papercut
Module
Add-ons (BF-Blender)
Module
Add-ons (Community)
Platform
Linux
Platform
macOS
Platform
Windows
Priority
High
Priority
Low
Priority
Normal
Priority
Unbreak Now!
Status
Archived
Status
Confirmed
Status
Duplicate
Status
Needs Info from Developers
Status
Needs Information from User
Status
Needs Triage
Status
Resolved
Type
Bug
Type
Design
Type
Known Issue
Type
Patch
Type
Report
Type
To Do
No Milestone
No project
No Assignees
4 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: blender/blender-addons#53537
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
System Information
Xubuntu (Ubuntu) 16.04, Nvidia GTX 720
Blender Version
2.79
Error:
Attempting to enable the A.N.T. Landscape add-on produces this error:
Reproduce it:
File > User Preferences (or CTRL + ALT + U) > Add-ons > Add Mesh > Enable Add Mesh: A.N.T.Landscape
Added subscriber: @GreenXenith-3
Closed as duplicate of #52786
Added subscriber: @VukGardasevic
Please check the solutions mentioned in the task (trying the official Linux build from Blender site).
If the add-on cannot be enabled try starting with --factory-startup.
If the add-on can be enabled, it points out to a corrupted saved preferences / start up files.
In cases like this, (when add-on can't be enabled) it is possible that the
startup.blend
anduserpref.blend
got corrupted, as it can happen depending when the Startup or User preferences files were saved. Usually the issue arises with developer builds or third party add-ons (add-ons not shipped with Blender).On Linux for instance, some of the packaging for different distros can use different versions of Blender (developer builds that had issues that since then were addressed). In doubt, it's better to download the official builds as those can eliminate possible issues and are the most current (as there is a daily new version).
As some kind of guidance, when using the developer builds or trying out add-ons not shipped with Blender it's better to save the startup file without the enabled add-ons and use the user_pref file (Save User Settings) for storing their enabled state. Then if some add-on is misbehaving it's easier to address the issue by redoing the userpref with enabling add-ons one by one.
Hope that helps. If there are some further issues please feel free to comment here so we can reopen the task.
Thanks.
Well there's a problem with that - this is the official version, and A.N.T. landscape is shipped with Blender. using
--factory-startup
produced the same bug.Added subscriber: @LazyDodo
You sure this is the official version? unless you placed it in /usr/share your self, it kinda feels like is the version your distribution offers?
Oh, huh. My bad, sorry.
Tested with one downloaded from the website, it works now :)
Changed status from 'Duplicate' to: 'Archived'
Added subscriber: @AjiibiStephenAyodele
mine still isn't working ..... please i really need help not just that though, my Mesh Tissue is {F3366886}also not working
you somehow corrupted your profile folder (possibly by installing some wonky addon).
close blender
rename C:\Users\yournamehere\AppData\Roaming\Blender Foundation\Blender\2.79 to
C:\Users\yournamehere\AppData\Roaming\Blender Foundation\Blender\2.79.bak
start blender, should be good as new now.