Resolved Broken weapon meshes and Weapon gap fix

[DanScallion]

Summary: Some weapons have broken meshes or meshes at incorrect position, causing gap. Lod 4 of aserai_noble_blade_4 is broken and only half the mesh or more like one triangle. While lod 1-4 of aserai_noble_blade_5 are at incorrect position, you need to substract -0.07 on all lod levels. Both issue can be easiliy seen and fixed in your official modkit, which I did.
For aserai_blade_19/Iron Scimitar Blade - X:-0.0037 m Z: -0.133 m for all lod levels

Also
<CraftingPiece id="aserai_noble_blade_4"
name="{=xYgJN0Ja}Decorated Scimitar Blade"
tier="5"
piece_type="Blade"
mesh="aserai_noble_blade_4"
culture="Culture.aserai"
length="87.4"
weight="1.0">
Length is longer than actual mesh which causes slight gap.

Also to get rid of weapon gap for crafted weapons remove line with a comment in Crafting.SwitchToPiece:
And all crafted weapons will have correct scale, with exceptions to the one with broken meshes.
public void SwitchToPiece(WeaponDesignElement piece)
{
this.SelectedPieces[(int)piece.CraftingPiece.PieceType].SetScale(100); //remove this line of code
CraftingPiece.PieceTypes pieceType = piece.CraftingPiece.PieceType;
WeaponDesignElement[] array = new WeaponDesignElement[4];
for (int i = 0; i < array.Length; i++)
{
if (pieceType == (CraftingPiece.PieceTypes)i)
{
array = piece.GetCopy();
}
else
{
array = this.CurrentWeaponDesign.UsedPieces.GetCopy();
if (array.IsValid)
{
array.SetScale(this.CurrentWeaponDesign.UsedPieces.ScalePercentage);
}
}
}
this.CurrentWeaponDesign = new WeaponDesign(this.CurrentWeaponDesign.Template, this.CurrentWeaponDesign.WeaponName, array);
this.ReIndex(false);
}

How to Reproduce: Craft aserai_noble_blade_5/Engraved Kaskara Blade and aserai_noble_blade_4/Decorated Scimitar Blade or any weapons they will have gap.
Have you used cheats and if so which:no
Scene Name (if related):
Media (Screenshots & Video):
Computer Specs:
OS:
GPU:
GPU Driver Version:
CPU:
RAM:
Motherboard:
Storage Device (HDD/SSD):

 

[MArdA TaleWorlds]

This issue is fixed with v1.1.0 version. Thank you for reporting.