OK Final demo post.. I promise..
Heres the plank pattern after trimming the solids to the deck blank, and unstitching the lower faces.
Attachment:
demo 13.jpg [ 61.68 KiB | Viewed 2545 times ]
Once again I have thickened the sheets into solids using a 'Both directions" option
Attachment:
demo 14.jpg [ 62.76 KiB | Viewed 2545 times ]
And Finally, using Boolean add I attach them onto the deck.
Attachment:
demo 15.jpg [ 74.88 KiB | Viewed 2545 times ]
Now, as for the file size issue: The only advice I have for you is to stop just before the boolean step. I don't know about rhino, but we have a "subassembly" function. Certain Items can be exported as a sub assembly, and while still technically part of the file (a phantom bound box will be shown in their place) the assembley are stored separately, and the full detail (thus CPU hogging complexity) won't be loaded into active memory, unless you choose to deliberately view them, or actively edit them. I would suggest doing this with scribes/planks solids. Out of sight, out of CPU, until necessary. Then continue working with other items integral to the hull part (lower superstructures etc.). Wait until just before you intend to export the .stl file before attaching everything together. Then, yes you may have a huge file, but you only have to work with it for that one step. Once completed, save it separately, so If you decide to go back and rework something , you can do so with the original smaller and separate files.
Also, In our system, a huge CPU eater is doing booleans on complex, and compound surfaces such as hulls. In the case of a 1/700 battleship, for example, the transverse chamber would barely show up in the finished product. It may better not to introduce any transverse chamber at all. Any areas where the sheer is near flat, (like those in the big five) leave the deck planar altogether. This way the scribe edges data can be saved as linear (data size wise they get described as two connected points). Once you start doing this to a compound surface, each plank edge gets stored as a spline, which has MANY points..
HTH
Unfortunately if you're dealing with subs, this can REALLY cause a file to blow up like the relief planking, and limber holes on this one, simply beacause on a sub, EVERYTHING is a compound surface

. Any edits to the hull part at this stage, and my quadcore 2 starts smoking..
Attachment:
myst.jpg [ 43.59 KiB | Viewed 2545 times ]