Not related to archipack's generated geometry
Cube.003
BKE_mesh_validate_arrays: Loop 5912 is unused.
BKE_mesh_validate_arrays: Edge 518: v1 index out of range, 4294901760
mesh_validate_customdata: CustomDataLayer type 16 has some invalid data

Ok validating geometry on another file this is what i get
Vertex 3: has zero normal

Hi there,
Stair entity was working since 2.79 without any known issue, so it's probably not a mesh generation issue on the addon side, would crash at creation / update time.

Os ? Blender version ? Any error in the console ?
Once render thumbs done, restart blender.

Duplicate of #T59119

Archipack 2.x is not an official addon, feel free to contact developper and report on github repo or using support form.
https://blender-archipack.org/contact/
https://github.com/s-leger/archipack/issues

As far as i can understand the pre-rotation concept, it is not as the rotation must apply before any other transform (around 0,0,0).

Either apply the "pre rotation" first - assuming bone is transform free when we apply, or cancel any transform before, "pre"-rotate and re-apply transform after.

Looks like at least math behind pre-rotation is wrong.
PreRotation should be something like this
parent_matrix @ rotation_matrix @ parent_matrix.inverted()

Short description of error
[Please fill out a short description of the error here]
Any error message in your console ?

Looks like archipack still is in "manipulate mode" try to right click or press esc before creating the column / deleting the snap helper - or keep the snap helper as it ...

Multiple dots in filename make it fails, try to rename your .zip into Modeling-clothing-28.zip

System Information
Operating system: Linux-4.15.0-50-generic-x86_64-with-debian-buster-sid 64 Bits
Graphics card: GeForce GTX 1070/PCIe/SSE2 NVIDIA Corporation 4.5.0 NVIDIA 410.104

Root of this issue still not known, but it occurs. It's clearly related to use of annotations.
So maybe keep open with a lower priority in order to gather more information from other users.

Archipack, is enabled,
but double checked material loading 29.03 and not it does check and when gp attr are found skip material and never apply it.
So i cant imagine it's related to this one.

Don't know how to repro, it suddenly appear on a file after loading.
Looks like it's probably related to Annotation.

Nope, select the object and take a look at material,
you should see typical grease pencil attributes on it, stroke and so on, and i definitely not expect those params on regular material.

This is no more required in 1.2.81 for blender 2.8,
setup action does copy factory presets in user profile folder, witch is a writable location for regular user.

Never mind !
Will find workaround on my side.

Step to repro:
Enable archipack addon, press render thumbs in addon prefs, wait 10-15 sec until done.
Draw / create a wall,
then try to draw a window/door (using button with the pencil) over the wall, ray_cast hit the hole, witch is hidden when ray cast occurs.

Hi,
could you preg replace across addons/ too when doing such breaking changes ?

Hi,
Any chance to get updated pdb for current python37 ?

From latest tests, adding a vertex colors layers on "hole" does fix issue on parent, the same goes for uvs (at least 1st layer, not checked further with 2nd one).

See T58472 as reference.

It also breaks uv channels > 0,
Add 2 uvs chanels, 2nd one is black with modifier enabled.

Will check twice the mesh generation code - to ensure there is no dups as i do join() meshes together before bisect().
But as far as i can tell, exact same code was (is) working without any trouble under 2.79c and 2.79 lastest buildbot

The bug_to_curve.blend file is a result of bisect done through same code as seen in video, but under 2.8

In edit mode if i recall correctly

# plane co: coord of one point in bisect plane
# plane no: vector of bisect plane normal
bpy.ops.mesh.bisect(
                        'INVOKE_DEFAULT',
                        plane_co=plane_co,
                        plane_no=plane_no,
                        use_fill=True,
                        clear_inner=True,
                        clear_outer=True)

see in action:
https://youtu.be/AmPDyhwBA8w?t=31

Same geometry is failing on both 2.79c and 2.8 (using crtl+c and paste to move between apps)

Not a bug here,
Archipack addon require additional steps to complete setup.
Enable archipack addon, setup a material library path and press "Render presets thumbs" in Preferences -> Add-ons > Add Mesh: Archipack -> setup actions.

Could you at least provide a description of your issue ?

Ok,
removing faces does fix the issue, but it's a regression from 2.79

Both samples does work in 2.79 but not in 2.8
Basically i do slice geometry using

Fixed by dbb224a606f2

Will try to find the right way to auto disable on scene switch.
In the meantime, Right click or press ESC to disable manipulators.

This is not a bug, but a restriction from BF to not include thumbnails into source.
A setup step is required to render thumbs,
user prefs -> add-ons -> archipack -> Setup actions -> render thumbs.

Not a bug here,
Archipack addon require additional steps to complete setup.
Enable archipack addon, setup a material library path and press "Render presets thumbs" in Preferences -> Add-ons > Add Mesh: Archipack -> setup actions.

Might be lack of vertex/edges/faces select state of solidify output ?
Following code was working under 2.79:
(input geometry is a plane in edit mode)

import bmesh

scene.ray_cast crash in addons running into 3d view too, (since ~1 week - at least 2018-11-14 was ok)
Since the addon is huge (archipack),
i do try into console to make report as simple as possible, so you probably spotted another issue ?

This is not a bug,
In order to generate thumbs, there are some additional steps to setup the addon under addon preferences -> archipack.

Any reason for lowercase units enumerator items in python ?

Was a 403, guess a miss-configuration in my ssh keys.
Solved now, thanks

Not directly related, but anyway .. ref [1]

Still having issues with custom properties and python api defined rounding values in ui while not editing, eg: 9.74303m -> 9.7m
could .precision property or .step property be used as rounding basis for display ?

Checked again with factory startup file.

Same issue with other manipulators.
Maybe a threshold for minimal change required before we actually update the real value could fix it.
At least it is a solution on python side but require a get_cb and set_cb to be handled properly.

Using a bar for shortcuts is definitely not way to go.

Ok, will proceed soon

Missing proper xml import
Never checked category stuff, i only made some cosmetic changes during 2.79 release process related to user defined library path and fixed temporary scripts path to writable folder.
Will probably require more in depth investigations of overall code, might take a look next week.

Not found path message is related to "user defined path" to library not set in addon preferences. It is only info and can't be the source of any error.

Update:
simplify math behind, bugfix for vertices lying on plane, pep8.
Note: unlike bissect tool this one is able to provide section as edges only, and dosen't cut the source mesh.

Another easy to repro failing case (2.79):

Hi,
+1 for .rst documentation.

Hi George,
Select your wall before autoboolean.
Also note that autoboolean is designed to work on closed wall mesh, and may produce unexpected result on open surfaces, as regular boolean do.

Commited fix rBA4bac8438df99 for critical issue T53706

commit fix into master