OK, Other than sitting for hours filling in "Forms," is there a way to copy Material Property data into a form useable by the system? Also, why is "Electrical Resistance" tied merely to area? It is a value based on area & length. ??? -- Lew
and again, believe it or not: Take a look into the help file:OK, Other than sitting for hours filling in "Forms," is there a way to copy Material Property data into a form useable by the system?
Hi Stefan -- And why is such a Utility not included? I am quite out of date on DIN material identities, but nothing in the supplied dataset complies with (what passes as) American Standards Designations (say: "ASTM A36" or the like). Low Carbon Steel (any steel with less than a 0.28% Carbon content) does not meet a generally acceptable designation! -- LewForgotten to say... It is possible to write a AlibreScript to "convert" a spreadsheet into a xml-file...
as i said, it is a xml-file and of course you can add information. Adding a new material to the file might be not so easy as each material in there has a unique number...The default Alibre Library of materials is not editable.
The currently active unicode material definition does, but not if you have other collections of material definitions in the unicode format that have been downloaded over the years from shared resources and are copied over as those materials are required. To achieve that, you have to merge them into the working first then let Alibre automatically import them. It's not a rant for rant sake, but the real practicality of how some users are currently use the 'old' framework! and how that doesn't directly fit into the new framework. Your assuming that people have a single 'master' definition file!Simon - v22 does AUTOMATICALLY import the users unicode custom material definition data into a new MTL folder that is shown in the Material Library and is editable. This is done at installation/first launch.
Sometimes it seems as if the first response here is to rant, rather than check.
As in testing, unless you use the features for a real use case, you won't find the short comings. I personally only tested features and workflow at the beta stage that was within the scope of simple throw away projects based around my workflow plus checking the new features (as there was no guarantee those projects would be useful post release and there is only so much or your time you can invest in testing someone else's product for them!)I don't believe it was raised at the beta.
As I now know the limitations, its not an issue for me as I can uninstall, remove the v22 specific directories as outlined in the v22 beta to release post, merge my material files into a single unicode, then reinstall and ensure everything gets imported in one hit.Simon - is this something that is actually a problem for you? I'm not clear whether you have multiple unicode material files, or if you are considering potential issues that others might have.