Do you use Arma on stable or on dev branch? What other mods do you use? Can you take a look into the RPT file and see if there might be an error message with JSRS? Do you use the Arma launcher? Where did you download this mod from, here or armaholic?

LordJarhead,

First of all thank you for taking the time to respond to my thread here. Secondly, thank you very much for your continued development in such a high-quality sound mod (one that I've been using for years).

Bear with me here (long post below) because I *think* I have figured out there were a couple issues going on, of which you may or may not care about (mostly regarding mod compatibility).

I use Arma on stable branch. I do not have access to any of the RPT files as I do not know where to access them. I DO use the Arma launcher, and I will describe where I d/l in the below post (in short, I d/l from both locations to troubleshoot).

In addition to the apex weapons not having any sounds, I was also having savegame loading issues (which I will describe below). I believe this is unrelated to the sound issues I was having but I think it is worth mentioning because it may or may not be an issue related to steam workshop downloads and compatibility between JSRS and CBA_A3 (just my theory, you'll see why I say this below).

First, the other mods I was using at the time of this posting was the RHS AFRF and RHS USAF, and Specialst Military Arms (SMA) packs, downloaded from steam. I was using their respective sound support packs as well (JSRS SOUND MODS: AFRF, USAF, SMA, all downloaded from steam). I was also using the community-base addon CBA_A3.

It is important to note that up to this point everything I was using at the time was downloaded from Steam, including CBA_A3. This will be important later on.

I ended up going through and removing pretty much everything except the base JSRS sound mod. After I did this, my Apex DLC weapon sounds starting working (using the JSRS sounds instead of just being simply silent). I believe the culprit here was either one of the mod pack sound support modules or one of the RHS weapons packs. That's fine, things seem to work without them.

In summary, up to this point, I was able to get all of the (base game and apex) weapon sounds working correctly with JSRS by having JSRS as the only mod loaded. So, on to the next issue I was having, regarding saved games.

Every time I started the game, including when JSRS was the SINGLE and ONLY mod that I had installed (from steam), I would get a pop-up error in the launcher when starting the game (during the "mod initialization" portion of the load bar) that would say:

"Addon 'JSRS_SOUNDMOD_AK12' requires addon 'JSRS_SOUNDMOD_GlobalFilters".

The game would boot properly and all sounds worked fine (including the Ak12). Saved games seemed to reload fine at this point (I made sure I was creating new games/saving games/loading games using the same mod config).

So, I decided to try adding SMA weapons pack and CBA. I was able to determine that any time I had the CBA loaded as a mod, installed from steam, with JSRS installed from steam and loaded as a mod, not only would I get the error mentioned above (jsrs_soundmod_globalfilters) but any time I tried loading a saved game with this mod configuration (CBA and JSRS both downloaded from steam) I would get the following error:

"You cannon play/edit this mission; it is dependent on downloadable content that has been deleted.jsrs_soundmod_globalfilters".

This error would return me to the scenario menu, effectively denying me from loading any saved games.

Again, I am making sure that when I start a new game (for example, on a map such as Jester's Altis Showcase) I start a new game with the current mod selection (in this case, CBA_A3 and JSRS both from steam) and try to load the game with the same mod selection. I would get this error written above every time, on any scenario i tried to start and then reload.

So then i went to Armaholic and downloaded JSRS manually and installed the mod manually by placing in my steam/arma folder, and then adding manually using the Arma launcher. I loaded the CBA_A3 mod (still installed from steam) and then loaded the JSRS mod (the only I downloaded from Armaholic). I unloaded SMA. I have had 0 issues, no errors, games seem to load fine using the method stated above. I then went and loaded SMA and have had 0 issues then using those three mods.

So in this way, at least with my very primitive troubleshooting here, it looks like there is some issue between the steam workshop versions of JSRS and the CBA? I think this is important because a lot of mods, as you are very well aware, use CBA. I just find it strange that after searching online I can't find anyone else having the same issues regarding problems with JSRS and CBA. I would figure a lot of people have those two mods loaded at the same time from steam.

This is a lot of writing and I have no doubt your eyes are bleeding, thank you for your patience and let me know your thoughts.

To me it seems that your steam version of JSRS got kinda mixed up. When it says "Addon 'JSRS_SOUNDMOD_AK12' requires addon 'JSRS_SOUNDMOD_GlobalFilters" it can only mean you have a really old version loading up. Because the Addons JSRS_SOUNDMOD_AK12 doesnt exist anymore, I mean for like half a year or so. So I think that Steam might have updated your JSRS version wrong.

And if there would be an issue between JSRS and CBA I would have noticed by now as my mod list is similiar to yours. CBA, RHS Full, NIArms, SMA, and a whole lot of more. And I use the same version of JSRS that get updated here so frequently. I mean I directly update the steam version out of my playing version, so there would be an error on my end as well, plus a couple of other people, I'm sure.

The only thing I can think of is that your Steam Workshop version of JSRS was wrong, as multiple things kinda indicate that. First it requires an addon that simply does not exist anymore (Had been replaced) and second as soon as you downloaded a fresh version and put it separatly it works somehow... but the armaholic version is the exact same as the steam one as FoxHound updates his version via steam as well. So there is no difference than the folder it got loaded from.

Check your Steam JSRS folder, check the Addons folder. There shouldn't be any more than exactly 30 files in it! So I would suggest deleting the whole folder. Unsub this mod, subscribe again, get a fresh version and check again.

On the other hand, the RPT will tell a little more if so. You can find your log files under C:\Users\USERNAME\AppData\Local\Arma 3. They are called like Arma3_x64_2018-08-01_19-10-33.rpt and can be opened with a simple text editor.

Hope I could help!

-LJ

LordJarhead-

Thank you for the prompt reply. After reading your post and doing a little further investigating, I seem to be having a bit of an odd problem when I download JSRS from steam.

When I download from armaholic, like you implied above, I have about 30 files in the 'addons' folder under the JSRS master folder.

I take the JSRS folder from armaholic and remove it from my mods list (and physically move it out of the arma folder in the steamapps/common directory). At that point, there is not a JSRS SOUNDMOD folder in the my arma3 base folder OR arma3 > !workshop folder. There is nothing for me to delete, to ensure there are no old files hanging about, like you mentioned.

When I go to download JSRS again, through steam, the folder doesn't show up until A) I have finished downloading, according to steam, B) I open the arma launcher and it automatically tells me on the mod menu that "mod JSRS SOUNDMOD was installed". Then the folder then magically appears in the !workshop directory.

When I access that folder that was just created, I notice a bunch of extra .pbo and .bisign files that are not present with the version I download from armaholic in the addons sub-folder.

Is there another place on my computer that, when steam downloads JSRS, it is placing it somewhere temporary, and thus is giving me a bunch of old files?

I just don't understand why these old files would be downloaded through steam, but I watch it physically happen, even after verifying that these files don't exist before I download the most recent steam release of JSRS.

Check your steamapps workshop folders. You can find them within your steam folder. Mine is located like this: C:\SteamLibrary\steamapps\workshop.

Now check the folders "content, downloads, temp". Within these folders you find the ArmA folder named "107410". These numbers are games, so Arma has the number 107410. Now in each of these three ArmA folder you need to look for the number "861133494". That is JSRS, at least on my end. You can simply check, in the folder 861133494 is a folder called ReadMe and the file is calles JSRS_ReadMe. So easy to locate.

Now check each of these, content, temp and downloads, check the 861133494 folder and look into the Addons folder and find out what you have in there. And if you have anything else than 30 files, or any files like the AK12 file you mentioned, unsubscribe, delete the whole mod content out of the folders "content, downloads and temp", and subscribe again and get a fresh copy.

Bascically, as your at it already, delete all 861133494-folders.

LordJarhead,

I went and found the 861133494 folder (it was only located the content > 107410 folder). It was empty but I went and deleted it anyway. The other folders (downloads, temp) had nothing related to JSRS.

Also, I went and manually deleted through windows explorer (instead of unsubbing/deleting through the launcher) the JSRS Soundmod folder in the Arma3 > !Workshop directory. That was the folder that had all of the extra files (dated almost entirely a year old). I'm starting to wonder if these files were somehow leftover from me unsubbing the previous times I tried to redownload the mod.

Either way, after deleting those two folders mentioned above and re-downloading the mod again through steam, I not longer have any compatibility issues or error messages (and no extra files in the jsrs addon folder). So, it is now working like normal.

Thank you for your time and help. Seems like in the end this was a fairly simple fix.

Also, once again, thanks for developing such a fine sound mod. Keep up the great work!