BDArmory's Weapon Manager not working

[kspguy77]

Hi! If this is the wrong place to ask about this, then, mods, please move this thread to somewhere else. So, i have a problem with bdarmory. The weapon manager doesn't work even though it's attached to the craft (rover in this case with a Patriot missile launcher and batteries for POWAAH). When i click the bdarmory menu button (?) in "flight" on the upper right corner,  there should appear a some kind of a list of weapons you can use and stuff. Doesn't happen for me. It just says "no weapon manager found" even though the thing is attached to the craft. Any ideas on what's happening? Also when i try to make a link between a radar vehicle and a missile launcher, i have to drive them really close to each other (150 meters) for both of them to appear on the vessel switcher or whatever. I can always see the vehicle i'm operating at the moment on the vessel switcher but no other team A craft until 150 meters of distance or team B vehicles (it's the same for them too). Then, when i've managed to get all these things, for example the missile turret with 8 mid range SAM missiles (can't remember what it's called), and a fighter jet with the AI pilot thing attached, to at least 150 meters of distance when i switch to the "enemy" fighter, i set one of my units as the target, go back to the missile turret, press P on the vessel switcher to activate enemy's autopilot, the plane starts its takeoff roll but stops 350.7 meters from me (autopilot switches off). Then when drive closer than the distance previously said, the plane starts to take off once again. So if i'd like to shoot airborne stuff down, i would need to constantly drive after them to maintain no more than 350 meters of separation which is impossible. Thanks in advance for your answers.

Edited June 25, 2018 by kspguy77
Added a couple more issues

[SpannerMonkey(smce)]

Hi  you seem to have firstly installed BDA incorrectly and not installed Physics range extender, which a requirement for BDA, there should be on screen warning for some of this , but if BDA itself is incorrectly installed then the warnings do not show.  The correct filepath should be  KSP/GameData/BDArmory     not  KSP/GameData/GameData/BDArmory and not KSP/GameData/BDArmory.1.2.1.4_06102018.   A zipped and downloadable copy of your KSP.Log will enable us to check the installation, without it the above is my best guess.

BDA Help desk

Edited June 25, 2018 by SpannerMonkey(smce)

[adsii1970]

16 minutes ago, SpannerMonkey(smce) said:

installed Physics range extender, which a requirement for BDA

Is this a requirement for all BDA?

[SpannerMonkey(smce)]

1 hour ago, adsii1970 said:

s this a requirement for all BDA? 

Hi, Yes,  since KSP 1.3 it's been an essential part of BDA's functions

[kspguy77]

When i downloaded BDArmory, on the site there read that the file includes Physics Range Extender. The filepath you said (KSP/Gamedata/BDArmory), it's the same one i have. Where do i put my downloadable copy KSP log as you said? I'm not really good on computing stuff so.. Dumb question:won't it reveal something personal (the log)?