This is Silehard's flagship Sovereign of the Seas, alias "manowar1".
The rigging can be diplomatically described as "minimalist". So here's what I've been doing recently:
I'm particularly pleased with the ropes which are tied to the hull, such as backstays and mainbraces. Because they're not. Though I started by attaching them to "Manowar1.gm" and placing them with TOOL and GM Viewer, I then subtracted the co-ordinates of the "geometry/mast" locators from those of the new rope locators, then added the locators to the masts and removed them from the hull. Why? Because TOOL can read "Manowar1.gm" but it can't read any of the others - "Manowar2.gm", "Manowar_gub.gm", "SP_Manowar.gm". But it can read all their "mast" and "rey" locators. By putting all the locators onto the masts, I can then write them to text files, then import them onto the masts of the other types to give them all the same improved rigging.
There were a few complications, such as "Manowar2" having a spanker instead of a lateen, and "Manowar_gub" has a different bowsprit. There's also locator "ropee17". It's attached to a small projection on the port corner of the stern and it ties down the trailing corner of the lateen sail. It's in the same position on "Manowar2.gm", tying down the spanker's boom, but that model lacks the projections on the stern, leaving "ropee17" in midair. But I found a nifty trick. The system objects with "Bad rope" messages if one end of a rope is not defined but it doesn't object if the same rope is defined more than once. It simply uses the last version of the locator which it encounters. So, if the same locator is defined in both the hull and mast models, and if the mast is read after the hull (which it probably is, after the system has found the "geometry" locator on the hull to place the mast), then it will use the mast's version instead of the hull's version. Which means all I have to do is add a new "ropee17" to "mast4.gm" and the boom is then tied to the stern board, not to somewhere floating above the stern.
The rigging can be diplomatically described as "minimalist". So here's what I've been doing recently:
I'm particularly pleased with the ropes which are tied to the hull, such as backstays and mainbraces. Because they're not. Though I started by attaching them to "Manowar1.gm" and placing them with TOOL and GM Viewer, I then subtracted the co-ordinates of the "geometry/mast" locators from those of the new rope locators, then added the locators to the masts and removed them from the hull. Why? Because TOOL can read "Manowar1.gm" but it can't read any of the others - "Manowar2.gm", "Manowar_gub.gm", "SP_Manowar.gm". But it can read all their "mast" and "rey" locators. By putting all the locators onto the masts, I can then write them to text files, then import them onto the masts of the other types to give them all the same improved rigging.
There were a few complications, such as "Manowar2" having a spanker instead of a lateen, and "Manowar_gub" has a different bowsprit. There's also locator "ropee17". It's attached to a small projection on the port corner of the stern and it ties down the trailing corner of the lateen sail. It's in the same position on "Manowar2.gm", tying down the spanker's boom, but that model lacks the projections on the stern, leaving "ropee17" in midair. But I found a nifty trick. The system objects with "Bad rope" messages if one end of a rope is not defined but it doesn't object if the same rope is defined more than once. It simply uses the last version of the locator which it encounters. So, if the same locator is defined in both the hull and mast models, and if the mast is read after the hull (which it probably is, after the system has found the "geometry" locator on the hull to place the mast), then it will use the mast's version instead of the hull's version. Which means all I have to do is add a new "ropee17" to "mast4.gm" and the boom is then tied to the stern board, not to somewhere floating above the stern.
