The second will be fixed in the coming days (if not today), and the first I'm investigating...

Bugfixes/hotfixes will be frequent.

1.) The aiming of the CTR-68 seems to be wrong if no optic is installed. Seems its placed to fit for a iron sight similiar to the RM277.. As a result you have to aim at the feet of the enemy in the distance of around 30m to hit its body mass. With a optic installed its aimed properly.

2.) When selecting the CTR-68 in the arsenal there is a messagebox with the error "No entry 'bin/config.bin/CfgSoundCurves.defaultVolumeCurve'"

When aiming with the MCX Spear (in first person mode) without a optic installed, then you see directly into the weapon. With a optic installed on the weapon their is no such issue.

I'm getting the "sounds_f_exp" error for all the weapons from the mod.

Each of these has been noted, recreated, and will hopefully be fixed with the next update. Thanks guys!

MCX Spear model seems slightly too large - attachments sink into the picatinny rails.

I seem to be getting the first error here
let alone if i try to load a previous save be it on Extraction or any other SP campaign, this mod is the one causing errors and making the save file not available to be continued to be played on

MCX and CT-68 are mirrored, it isn't that they are in left handed-configuration, but they are actually reversed!

The model for the Spear has been re-sized and mirrored in the process of improving the textures, I will be mirroring the CT-68 as well. Thanks for the help!

The pop-up errors in the original discussion post have been fixed!

FYI, the error message "No entry 'bin/config.bin/CfgSoundCurves.defaultVolumeCurve'" still appears for me after yesterdays update when selecting one of the weapons in the arsenal. I have seen it for CT-68 but also for MCX Spear, its probably a issue with all weapons of the mod.

Yes I haven't narrowed that one down yet, it wasn't causing as big of issues so I put it on the backburner while I fixed textures. All goes well it should be fixed with the next update, hopefully alongside the texture issues with the CT-68.

I do believe you are right that it's each of the weapons however, it seems to be something I did wrong in the first config and then pasted to the remaining ones.

Mod is not correctly signed, so key verification will report that mod is not signed correctly.

This issue can be reproduced by activating "Check Signatures" option in the parameters of the Arma3 Launcher.

During Arma3 start it will then report "rm277lonestarrifle.pbo is wrong Error 0x22, Test Failed"

Its a pretty common problem i encountered with other mods too. Here is a thread in BI forums about that, which might to try different options. https://forums.bohemia.net/forums/topic/233762-solved-dsutils-not-signing-a-pbo-correctly/?tab=comments#comment-3432278

Cheers, that's quite odd the publisher said it was signed but I know how "reliable" BI tools are.