It helps a lot to pinpoint the cause if you ended up with a broken configuration.
#DOWNLOAD BRICSCAD V21 LICENSE#
Among others, it mentions whether Communicator was found and whether a license was found. In BricsCAD, COMMUNICATORINFO reports in detail whether or not Communicator is setup properly. app bundle, permission had to be given for every individual binary. app bundle structure is required to be able to accept the entire bundle - without the. Not so difficult, but not trivial to discover alright. After that BricsCAD can use the bundle for import/export. In the process, the permission should be granted. macOS does launch the app, but lacking arguments it exits immediately. After that, it should be possible to choose "Open anyway" in the macOS security settings. Normally on first run of BricsCAD after installing communicator a message box pops up. An app bundle is indeed a directory, with an agreed upon structure/contents.Īnother hurdle is getting macOS to accept the communicator as a trusted app bundle. BricsCAD runtime treats this path as a directory and directly addresses the binaries inside it, rather than addressing the app bundle as a whole. I think the pending slash in CommunicatorPath is required. If you use a custom installation path, or CommunicatorPath was edited, it can be tricky to set up CommunicatorPath correctly. If the app bundle is in that location, the default value should do. "/Library/Application Support/BricsCAD Communicator V21.app/" This is the default value of CommunicatorPath: There is no Communicator(Mac) installer yet, but the default CommunicatorPath and the instructions in Install.txt are kept as simple as possible.
With beta access you could try the V21.1.05 BETA version and future beta versions. If you want beta access, please enter a support request to request it. normally all upcoming BricsCAD V21 versions will be notarized before publishing. It is something that must be repeated for every version - quite tedious, but so it goes. We upgraded the fbxsdk library and BricsCAD V21.1.05 BETA was notarized successfully. This problem no longer exists in BricsCAD V21.
#DOWNLOAD BRICSCAD V21 UPGRADE#
(notarize, meaning: upload to Apple's notarization server for automatic checking and registration) As it happens, the fbxsdk library that comes with BricsCAD V20 was too old to be accepted for notarization, and we could not upgrade this library in time.Īs a result, on installation and on first run of BricsCAD V20, it is required to give explicit permission, as described here: