Observations on Arch Textures in FC 0.19:
First: Big Ups for latest FC version. seems much more stable than three weeks ago version...
Also I'm liking the ArchTexturesWB tools - easy to use.
However a few points on ArchTexture WB tools.
It seems you need to allocate
a new ArchMaterial
to each instance of ArchTexture
This is a bit different to the help (https://github.com/furti/FreeCAD-ArchTextures
), which suggests one material can be allocated to many textures (which makes sence).
However, doing this made my model crash.
This is perhaps because in m
y model there are a lot of separate (unconnected) walls
etc, whilst in the Help
it looks like the very few walls are based on a polyline - perhaps...?
This may be a bug
that just hasn't manifested in tests with a few simple continuous walls. I am interested in others experiences.
When you allocate material and Texture, a TextureConfig Object
appears at the bottom of the Tree.
So far so normal.
But the TextureObject is not referenced in the Properties of the structure which has had a Texture added (ie a wall),
and I cant Drag-and-drop it as a Child into the Structure in question (ie into the wall parent
). (i tried groups, parts etc - It just wont go)
I assume this is something to do with the preceding discussion threads (which I tried but failed to follow
However it means a lot of random Texture objects sitting in the lost objects graveyard at the end of the tree.
As a temp solution
would it not be possible to be able to drag it up and have it sit as a child of the relevant structure (wall, roof etc) - a bit like a CutVolume
That at least would be consistent with the usual heirarchy (even if it wasn't active).
I tried exporting the .IFC model (with Textures) into Blender
Unfortunately, neither application wants to acknowledge my beautiful brick and tile-work!!
which brings me to a general question: is this because IFC's don' t have texture info, or is it because the texture info needs to be allocated to a specific IFC-related property attribute location? The online discussion is uninformative on this point except for learning that there may be an ifc attribute called IFCSURFACESTYLEWITHTEXTURES.
(On this, I noticed that in Properties / IFC / IfcType; if I select BuildingStories for my Floor levels, then the exported .IFC when opened in BimVision will recognise my FreeCAD Levels and be able to separate them spatially - on demand.
Is it the same with textures? If you allocate them to the correct .IFC Attribute location will they display in an texture-enabled IFC reader?
OS: Windows 8.1 (6.3)
Word size of OS: 64-bit
Word size of FreeCAD: 64-bit
Version: 0.19.22960 (Git)
Build type: Release
Python version: 3.6.8
Qt version: 5.12.1
Coin version: 4.0.0a
OCC version: 7.3.0
Locale: English/United Kingdom (en_GB)