CAD Monkey Lite introduces “File Trees”; a new way to save different file structures to better serve the diverse types of projects you work on. If you’re an architect who does small test fits, square footage calcs, stacking diagrams, interior renovations and new base building construction you’ll be able to save up to 5 different File Tree saving you time no matter how big or small the job is.
As of July 2018, we support:
Currently, CAD Monkey works with 2017, 2018 and 2019. However, if you're using 2017 then your XREFs may connect as Full Path and not Relative Path. We're working on this.
AutoDesk attempts to migrate a user's profile when you move from older to newer versions of AutoCAD. However we've noticed that not all pieces of information come over. We recommend running the MONKEYCONFIG & MONKEYPAPER command to inspect your file trees and reconnect any paths as needed.
Specifically, the following fields must be reviewed (at least):
On AutoCAD versions 2018 and higher, attached Xrefs use relative paths. This is so you can copy & paste the project folder with easy to any location and preserve the links.
On AutoCAD 2017, relative Xref paths are not supported by CAD Monkey. Your Xrefs will generate as absolute (full) path, and you'll need to manually edit them in the drawing to convert them to relative paths. We're working on this.
Let's double-check some common causes.
1. Suffix shared across two files
Open your File Tree in MONKEYCONFIG. Do any rows have the same text in the Suffix field? Are any two blank? If so, change the Suffix to be unique for each file. The Suffix is included in the file name, so if they aren't unique we can't create individual files for each config row.
2. Paper space file name shared across two files
Open MONKEYPAPER. Do any rows have the same File Name? If so change them to be unique. Leaving a File Name blank means the file will not be created.
3. No access to destination folder
Are you saving the files to a location that your computer has access to?
MONKEYCONFIG user interface creating a File Tree with model space file structure