No entry 'bin\config.bin/CfgWeapons.Single'.

[R4IDER 10]

Does anyone know what causes this error message to appear? I have a feeling it might be caused by the CUP Weapons pack.

 

This error is currently preventing the first load through of a mission on our Linux server which is a bit of a pain but the second time through the mission loads but this error message is still being displayed.

[ineptaphid 6413]

It has been popping up for quite a while on Dev branch. While it does happen with CUP it seems to be caused by several weapon addons.It is due to some change made by BI to weapons recently. My only advice to you is to disable all mods and start adding them back one by one until you find the culprit.

[fourjays 27]

I'm interested in any information available on this (such as what needs changing in the config files). Seen it pop-up up a lot in our server logs while testing Apex, amongst many similar messages. It seems it is stopping missions from loading too. Although I've also seen some of these errors as a visible prompt on one of the vanilla MX's, which seems a bit odd.

 

Any information from those in the know would be much appreciated though, so I can start trying to fix our mods and applying fixes to the less regularly maintained mods we use. Thanks

[Megiddo 73]

​Have almost the same error since the update ( update + APEX DLC):

 

No entry 'bin\config.bin/CfgWeapons.ItemInfo'

 

shows up at the main menu screen and twice when opening any editor mission. As underlined, maybe this is caused by some weapon mods or CBA with joint rails?

 

Will test Ineptaphid method to try and spot the cause.

[Hagraven 1]

Apparently caused by ace3, which needs to be updated. WithSIX doesn't offfer the update yet though

 

https://github.com/acemod/ACE3/issues/4087

 

edit: the problem remains even with the updated version (361)

[HeroesandvillainsOS 1504]

It's not just ACE 3, I'm seeing it in my non-ACE missions too. I'm thinking Massi Weapons is shooting it but I'll have to isolate it when I have more time.

[road runner 4344]

It's pretty much all 3rd party weapons addons that were made using Bis default config.cpp's, seems BiS have changed something in their standard config file.

[Megiddo 73]

​

No entry 'bin\config.bin/CfgWeapons.ItemInfo'

 

 

When proceeding by elimination, so to say when deactivating all the content mods and then reactivating them one by one, it seems that this ItemInfo error is tied to Robert Hammer Pistol Pack. (only have RHS and RHPP active as weapon/gear mods these days)

 

Not 100% sure of course, as i'm not a specialist, but it seems that either the pistol box itself, the weapons, attachments, or ammos are causing this.

 

Something good in this : this will bring us an update for this excellent, essential mod :)

 

Will report this in the dedicated thread as well.

[Singh Aram 137]

No entry 'bin\config.bin/CfgWeapons.ItemInfo'

(Ace3 + RHS ) is also causing that error.

[mannulus 38]

Can confirm our server is having the issue as well. Currently working out a workaround in the mean time. If anyone else has an idea of how to fix it, please present it. :3

[evil_brownie 17]

Based on what what i was able to gather these past days trying to fix this on my end, class Single and class Burst seem to be "deprecated" by the game and throw an error upon loading the game. While I haven't seen it being directly called upon on weapon configs, it just being there in the cpp file makes the error pop up.

 

Furthermore, the ItemInfo error is a similar situation, it can't be mentioned out of anything that actively uses it. Say if you want to make a specialised MX rifle with modified ItemInfo information, inherit from whichever MX variant you want beforehand (same applies for anything that uses ItemInfo).

Example (classnames made-up for illustrative purposes):

class CfgWeapons
{
 class MX_base;
 class MX_rifle_1: MX_base
 {
  class ItemInfo;
 };
 class my_personal_MX: MX_rifle_1
 {
  class ItemInfo:Iteminfo
  {
   "insert whatever you wish to change"
  };
 };
};

[mannulus 38]

Been working on a workaround for this issue. As long as you make a cba folder in userconfig and put a empty settings.sqf file inside, it will solve one of the two issues. The next thing is to try to load the mission you want. It WILL kick you back to the lobby but all you got to do is try again to load it (DO NOT RESTART/STOP THE SERVER) and it will go through. I double checked this with my unit and we are now operational.

[Tuskegee_99th 43]

I get the same error message when using either RHSAFRF or RHSUSF even without CBA. And, as far as I know RHS does not require CBA so it's not just and issue with CBA and can't be fixed with just a CBA folder added to userconfig either.

[mannulus 38]

I get the same error message when using either RHSAFRF or RHSUSF even without CBA. And, as far as I know RHS does not require CBA so it's not just and issue with CBA and can't be fixed with just a CBA folder added to userconfig either.

As I said. Start the server, tried to load the map (It should kick you back). Reload the mission one more time without restarting the server. Should be able to join.

[militarypolice 10]

As I said. Start the server, tried to load the map (It should kick you back). Reload the mission one more time without restarting the server. Should be able to join.

 

I confirm this works as well. My unit has been doing this since Arma 3 came out and using mods. You get used to it after a while.