System Information
Operating system:
Graphics card:
Blender Version
Broken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)
Worked: 2.79*
Short description of error
Please see my screencast
| Philipp Oeser (lichtwerk) |
| brothermechanic (brothermechanic) | |
| May 31 2019, 7:29 PM |
| Brecht Van Lommel (brecht) |
| brothermechanic (brothermechanic) |
| Philipp Oeser (lichtwerk) |
| stephen leger (stephen_leger) |
System Information
Operating system:
Graphics card:
Blender Version
Broken: (example: 2.80, edbf15d3c044, master, 2018-11-28, as found on the splash screen)
Worked: 2.79*
Short description of error
Please see my screencast
Checked this, and it is not the . in the zipfile name, offending is the . in the foldername inside that zipfile...
2.79 also didnt allow for this (not sure why the report suggests this was working there?)
As the folder will be the python package: pretty sure python doesnt allow for top level packages to contain a .?
For sure bpy.path.module_names() doesnt allow this [which is why this addon then wont be loaded]
What we could do here though is to check inside the .zip if we would find offending package names prior to copying this to the addons folder and tell the user that the installation failed.