Arma can't find local mod models or icons - but the config seems fine.

[TomOZ 3]

Hi All - Hope everyone is doing well,

 

I've got a little problem here that i didn't have 1 month ago. I recently after 4 weeks starting to work on my custom backpack mod again, and for some reason it seems that Arma now cannot find the icons or models for the packs. The config is correct (at least i think it is - it was working and the items DO appear in the Virtual Arsenal list, just no .paa files and .p3d models.) I don't really understand what has changed, but obviously something has happened. 

 

I will post the config below - but again, it is working because the mod and the mod contents appear in game, just no models or icons. It almost like the config model and picture paths to the objects is hidden or prohibited when loaded in game?

 

I will add imgur images to show the file directories and example files.

The mod is called A3MOD (for testing purposes i haven't changed it) then it has Addons, then the A3MOD PBO, then the contents (objects, icons, textures - textures aren't implemented yet though)

 

Icons:

 

 

 

 

 

Objects:

 

CONFIG.CPP:

 

class CfgPatches
{
           class A3MOD
           {
                        units[]={};
                        weapons[]={};
                        requiredVersion = 0.1;
                        requiredAddons[]={};
                        author = "Tommy";
            };
};

class CfgVehicles
{
            class Land;
            class Man: Land
            {
            class ViewPilot;
            };
            class CAManBase;
        class B_AssaultPack_cbr;

////////////////////////////BAGS/////////////////////////////////

 class BF_Pack_Iteration1_OB: B_AssaultPack_cbr
 {
  displayName = "BF - Assault Pack";
  author="Tommy";
  model = "\@A3MOD\Addons\A3MOD\objects\BF\BF_Pack_Iteration1_OB.p3d";
  picture = "\@A3MOD\Addons\A3MOD\icons\bf.paa";
  icon = "\@A3MOD\Addons\A3MOD\icons\bf.paa";
  descriptionShort = "Small and lightweight assault pack perfect for small operations";
  transportMaxMagazines = 8;
  transportMaxWeapons = 1;
 };

 

};

 

 

Any help would be GREATLY appreciated - perhaps its something right in front of me that i cannot see, or maybe i'm just blind.

Cheers guys.

EDIT: This is what appears in-game

 

https://imgur.com/a/FMxed1W

 

 

[Jackal326 1182]

1 hour ago, TomOZ said:

EDIT: This is what appears in-game

https://imgur.com/a/FMxed1W

 

That is because your config is using longer paths than it needs. You don't need to reference the mod folder at all and simply need to start at the PBO folder.

class CfgPatches
{
           class A3MOD
           {
                        units[]={};
                        weapons[]={};
                        requiredVersion = 0.1;
                        requiredAddons[]={};
                        author = "Tommy";
            };
};


class CfgVehicles
{
	class Land;
	class Man: Land
 	{
		class ViewPilot;
	};
	class CAManBase;
	class B_AssaultPack_cbr;

////////////////////////////BAGS/////////////////////////////////

	class BF_Pack_Iteration1_OB: B_AssaultPack_cbr
	{
		displayName = "BF - Assault Pack";
		author="Tommy";
		model = "\A3MOD\objects\BF\BF_Pack_Iteration1_OB.p3d";
		picture = "\A3MOD\icons\bf.paa";
		icon = "\A3MOD\icons\bf.paa";
		descriptionShort = "Small and lightweight assault pack perfect for small operations";
		transportMaxMagazines = 8;
		transportMaxWeapons = 1;
	};
  
// INSERT OTHER CLASSES HERE
  
};

 

[TomOZ 3]

1 hour ago, Jackal326 said:

 

That is because your config is using longer paths than it needs. You don't need to reference the mod folder at all and simply need to start at the PBO folder.

class CfgPatches
{
           class A3MOD
           {
                        units[]={};
                        weapons[]={};
                        requiredVersion = 0.1;
                        requiredAddons[]={};
                        author = "Tommy";
            };
};


class CfgVehicles
{
	class Land;
	class Man: Land
 	{
		class ViewPilot;
	};
	class CAManBase;
	class B_AssaultPack_cbr;

////////////////////////////BAGS/////////////////////////////////

	class BF_Pack_Iteration1_OB: B_AssaultPack_cbr
	{
		displayName = "BF - Assault Pack";
		author="Tommy";
		model = "\A3MOD\objects\BF\BF_Pack_Iteration1_OB.p3d";
		picture = "\A3MOD\icons\bf.paa";
		icon = "\A3MOD\icons\bf.paa";
		descriptionShort = "Small and lightweight assault pack perfect for small operations";
		transportMaxMagazines = 8;
		transportMaxWeapons = 1;
	};
  
// INSERT OTHER CLASSES HERE
  
};

 

 

Hey Jackal,

 

Cheers for the response, but sadly the change you recommended doesn't work either, it acts exactly the same as before - exact same problems. Very strange. Any other ideas?

 

Cheers for the help though, always appreciated!

 

EDIT: 

I've fixed the issue now, it was a slight syntax error in the file path.

 

This was wrong --- model = "\A3MOD\objects\BF\BF_Pack_Iteration1_OB.p3d";

This one works --- model = "A3MOD\objects\BF\BF_Pack_Iteration1_OB.p3d";

 

Glad I got it sorted, i knew it had to be something related to the file directory line structure - what an annoying little thing. 

Thanks for the help Jackal, you've helped me before so i appreciate it a lot!

Cheers, Tom.

Edited September 5, 2020 by TomOZ
Fixed.

[Jackal326 1182]

9 hours ago, TomOZ said:

I've fixed the issue now, it was a slight syntax error in the file path.

 

This was wrong --- model = "\A3MOD\objects\BF\BF_Pack_Iteration1_OB.p3d";

This one works --- model = "A3MOD\objects\BF\BF_Pack_Iteration1_OB.p3d";

 

Glad I got it sorted, i knew it had to be something related to the file directory line structure - what an annoying little thing. 

Thanks for the help Jackal, you've helped me before so i appreciate it a lot!

Cheers, Tom.

 

Damn it! I didn't think it looked right when I posted my reply but hadn't had chance to reference any of my own configs to check it -sorry about that.

Glad you got it working anyway.

 

Just a quick heads up, if you plan to release I'd suggest naming the PBO as something different as well as giving your cfgPatches entry a unique name to prevent potential conflicts.