bas_repairh is defined in the addon bas_repair.bpo that came with the 1.0 release of the BAS Blackhawks.abomb1508 wrote:at start of level two it says:
cannot load/ misng addon bas_repairh
now i know the pmc fury is supposed to be without addons but in the meantime can you tell me where i can get it? (i know from the bas site but which addon does it come with?)
The reason, in short
You are getting that error message because you have the bas_repair.pbo somewhere in your addons folders. I'd guess its in the Res/Addons folder.
The problem
This addon, like many others have what can be called an addon dependency problem. In this case, inside the bas_repair addon there's a new variant of the Apache, based on the standard AH64, one that gets shot at by infantry to a greater degree than the default one. There are other "new" helos defined in there too, but the "Apache AH-64(A)" stands out as the only one that is based on an addon. The other helos are based on the core BIS helos (The Cobra, Hind and Hip).
The symptoms of this problem are as follows:
- Any mission containing an Apache will give you that error message
- There's a chance that if you have the addon active and place an Apache in a mission, the saved mission file will list "bas_repair" as a needed addon even though its not actually needed. It will "mysteriously" get added to the Addons[] or addonsAuto[] part of the mission.sqm. How's that for odd?
To be correct, the bas_repair addon should therefore declare the dependency on the BIS Apache. This is done by adding a requiredAddons[]=... statement in the CfgPatches part of the addon's config. This is how that part looks:
Code: Select all
class CfgPatches
{
class BAS_repairH
{
units[] = {bas_repairH};
weapons[] = {};
requiredVersion = 1.90;
};
};Code: Select all
class CfgPatches
{
class BAS_repairH
{
units[] = {bas_repairH};
weapons[] = {};
requiredVersion = 1.90;
requiredAddons[] = {ah64};
};
};Get a fixed one.
Here you go: Fixed bas_repair.pbo (3.9 KiB)Now replace (overwrite) the old one with this one and you'll get rid of that message. Of course, then you'll probably get some other "missing addon..." message due to another of the huge amount of broken addons that are out there...
I write this in hopes of that more players and addon makers are made aware of the reason (and the *sole* reason) for such error messages - addons that don't declare their dependencies properly.
Now, good luck with PMC Fury!
PS. In case its not obvious: no, Snake cannot "fix" the campaign for this problem since its not a problem of the campaign.
