Were you continuing to play from a saved game? If so, try from mission start and see if it's ok.

Every time I tried with a fresh start, now I understand that there is something wrong in my settings, I will try to delete all the mission saves, mission and 3CB mod and then ''reinstall'' them. I'll sort out somehow, because I love 3CB mod. Thank you once again for help.

I have updated the mod on the server and in the launcher. I have also uninstalled and reinstalled the mod from my PC and from the server and continue to get the error. Everything worked flawlessly until the 1.86 update. I saw that they were updating the signatures for security, not sure if this could be where the issue lies.

I have updated the mod on the server and in the launcher. I have also uninstalled and reinstalled the mod from my PC and from the server and continue to get the error. Everything worked flawlessly until the 1.86 update. I saw that they were updating the signatures for security, not sure if this could be where the issue lies.

From what I've read what mentioned is the issue. And its not just with this mod.

Share this post

Link to post

Share on other sites

From what I've read what mentioned is the issue. And its not just with this mod.

I haven't had any other issues so far other than this mod. But I fully believe that if they did truely update the signatures past v2 to a v3 signature that it would throw many mods out of wack. Especially with how little information I have been able to find about the signature update.

Share this post

Link to post

Share on other sites

I was wondering if I would be able/allowed to utilize the static weapons from this mod?

I'm looking at pulling the static pbo out (changing nothing in the credits so it all references the parent mod still) so that our community can utilize the vastly superior crew served systems in this mod.

Share this post

Link to post

Share on other sites

I was wondering if I would be able/allowed to utilize the static weapons from this mod?

I'm looking at pulling the static pbo out (changing nothing in the credits so it all references the parent mod still) so that our community can utilize the vastly superior crew served systems in this mod.

Looking forward to hearing back!

I don't know why you don't just load the 3CB weapons mod and not the others, that's all we do when we're not using the full pack.
Means you also get the best Javelin in the game to play with

Share this post

Link to post

Share on other sites

@constance68w: You are already free to download the weapon pack and use the .pbo's as required, however we don't permit separate uploads to Steam, so if you are making it for a clan or group, the upload would need to be for a private repo - say through Arma3Sync. As JD Wang states, we've already separated our mods into four separate packs to make it easier for groups that don't want to use all aspects of our releases. You only need the weapons, and not equipment, units, or vehicles. It's as user friendly as we can make it.

@The_Elkin: Not sure if there is any time scale on this. Most of the time, BAF use the gpmg without a scope. There are no rails on it. The only time it regularly is equipped with optics is when it is used as a static position. For longer range engagements where it needs to be used as a support weapon, you can already simulate that in the game by carrying a 3CB gpmg tripod on your back (or by an assistant) in the launcher slot and combining the hand held gpmg to create the tripod version. It can then be disassembled back into the gun and tripod and moved to a new fighting position.

But as you say there's practically no use for it, so hardly any of the HK guns even have one.

The optics that might be used with the gun while in the light role are night sights like Kite, Vipir, or FTS/Dragon. But they're heavy, and can make the feed cover more difficult to lift when operating the gun.

Both use the RKSLA3.bikey but they're different versions. Not sure who's is the outdated version but I've done a work round in our server keys folder by renaming the Watchkeeper key to RKSLA3_Watchkeeper.bikey so we can use both. Not a big deal but would appreciate if you use the RKSLA3.bikey, you both have the same version.

Both use the RKSLA3.bikey but they're different versions. Not sure who's is the outdated version but I've done a work round in our server keys folder by renaming the Watchkeeper key to RKSLA3_Watchkeeper.bikey so we can use both. Not a big deal but would appreciate if you use the RKSLA3.bikey, you both have the same version.

As ever, loving your work.

This is fascinating to discover that 3CB are uploading RKSL content to Steam without consent. I'm looking forward to an explanation for that. This is one of many reasons why you shouldn't re-upload other peoples content without permission.

@MitchJC The new versions of RKSL content use a completely new key. It's an issue caused by Da12thmonkey signing the Attachments pack with a different private key to the one I previously used. Once the updates are out in a few days this will not be an issue anymore.

2

Share this post

Link to post

Share on other sites

This is fascinating to discover that 3CB are uploading RKSL content to Steam without consent. I'm looking forward to an explanation for that. This is one of many reasons why you shouldn't re-upload other peoples content without permission.

They asked me way back

I said it was alright by me (for 3CB alone) to include my stuff (again, my stuff alone) until such a time you or I put them on the workshop, or it caused issues. But I haven't updated it in forever, so never uploaded it to WS and I didn't anticipate BIS redoing the signatures again

Share this post

Link to post

Share on other sites

I said it was alright by me (for 3CB alone) to include my stuff (again, my stuff alone) until such a time you or I put them on the workshop, or it caused issues. But I haven't updated it in forever, so never uploaded it to WS and I didn't anticipate BIS redoing the signatures again

Would have been nice to know.

I've been fielding these key issues for a while now, I've only just discovered its due to the 3CB upload. Reporters have denied having any other RKSL addons installed. This explains so much.

Share this post

Link to post

Share on other sites

We'll look to assist in any way we can with this issue. We really appreciated Da12thmonkey giving us permissions to include the scopes in our pack some four years ago when we first released the weapon pack - and now by so quickly explaining the situation. The scopes are still in their original .pbos and we haven't opened or modified any source material in anyway, simply included them in the BAF Weapon pack so that we didn't require a further dependency.

Share this post

Link to post

Share on other sites

This is fascinating to discover that 3CB are uploading RKSL content to Steam without consent. I'm looking forward to an explanation for that. This is one of many reasons why you shouldn't re-upload other peoples content without permission.

@MitchJC The new versions of RKSL content use a completely new key. It's an issue caused by Da12thmonkey signing the Attachments pack with a different private key to the one I previously used. Once the updates are out in a few days this will not be an issue anymore.

As I'm sure they'll be looking forward to an apology for suggesting they have done anything without the requisite permission...

Share this post

Link to post

Share on other sites

I'm sure you've been asked this before but do you know if its a bug or am I doing something wrong in terms of the weapons tripod and L16 mortar parts as when I remove them from my launcher slot to drop them on the ground they stay in the bag form therefore not allowing me to build said mortar or mounted GPMG. This only happens on our dedicated server so can you think of anything that is stopping the bag swapping over into its dropped form after a second? I've tried these both out in a hosted mp mission from my pc and they switch perfectly fine so it doesn't seem to be a mod conflict maybe a setting somewhere on the sever side?

Share this post

Link to post

Share on other sites

I don't think this issue has been reported. We've used the L16 mortar recently on our MP servers on private Ops without any issues. Does your server have anything else running perhaps that the hosted one doesn't?

Share this post

Link to post

Share on other sites

But another thing have you guys changed the NLAW so it can no longer lock onto vics with T? The diamond no longer appears all I can do with it is make it curve when holding TAB before firing or was this broken by an ace update?