#Deltacad layers code

The name of the CSV file is the same as the Excel WorkSheet name. The offset table is exported to DeltaCad as a CSV file. No curvature checks are made, the design may not be developable (i.e.If an interpolated value appears wrong or wildly off then you will need to add “breaks” to the chine stations near the problem area.Stations within 5 mm of each other will have “breaks” automatically added.The stations are rounded to the nearest millimetre.

Chines can have a “break” or a sharp bend.Chines can be invisible (and ignored) if the colour is “0”.Chines have a colour for easy identification.The above offset table has three additional features over an offset table: The actual design is too small to be of practical use as a Kayak (refer to Anderson’s webpage). “Mini-Kayak” is an adaptation of work by Bruce C. Below is the Excel offset table for the “Mini-Kayak”. WorkflowĭeltaCad does not have a suitable table entry process which is why Excel is used. Note: DeltaCad can be purchased for US$40 from. The DeltaCad macro imports the CSV, draws the design and unfolds (develops) the hull. The Excel file and macro allow you to enter the offset table and then to export the design to a CSV file for DeltaCad. The process consists of two macros/files: The new DeltaCad macro version handles simple hulls easily and the more complex designs are slow but doable.

#Deltacad layers code

Why migrate from the spreadsheet version previously presented? After all it works! The reason is that even simple designs take forever to code and it is just too hard for more complex projects. Asking the macro to sort out lazy chine offsets was a dead end. The issue is that the underlying processes (wire-framing) is not unique/deterministic. All I can say it was a bit of a marathon getting the code working reliably.