BahamutoD

I tried it with TrackIR and it works as intended - ICC doesn't interfere.

Chase mode is different in 1.0. It works in Free mode and Locked mode (Locked is the same as the old chase mode).

Hmm.. post your output log then so I can try to figure out what's wrong.

Post your output_log.txt from KSP/KSP_Data. It still works if you have Firespitter. Its just not included with bdanimationmodules alone. BDArmory doesn't use BDAnimationModules. I'm not entirely sure how CKAN works but I was told it updates BDAnimationModules as a separate mod. Double check that you have it, or install it manually. Yes it should

It could be any number of things. I need you to describe one specific situation where it happens consistently, in detail. What weapons, what guard settings, is the guard flying, is the target flying, what phys distance, what target distance, etc. The more accurately you can describe it, the better chance I have of reproducing the problem and working on a fix, or figuring out if its a user error and telling you how to solve it. You may need to increase the guard range and field of view. Yeah that looks much better. It should come along with the turret rewrite (not-so-soon). Okay, I've noted the infinite ammo issue and will fix it. I looked over the code that checks if the target is in turret range and it looks okay, but I know there are some issues with refreshing the target database if a recorded target has switched teams. Perhaps its not a guard or turret problem but a problem with the target database. In any case, as I said above, it would be much more helpful if you give me a very specific way to reproduce the issue. It might even be helpful to create the scenario in a stock+bda save and send me the save file. Again, please clearly describe what you're doing. For example: Attached aim-120 to craft, attached weapon manager to craft, assigned weapon manager's Fire command to action group 1, launched craft, selected AIM-120 from toolbar weapon list, pressed 1. Where you attach it to the craft and what the missiles drop settings are matter as well. The weapon manager checks to see if the missile has enough clearance to drop and won't fire it if something is obstructing the path. Did you try "rescaleFactor"? (not "scale")

It's on the todo list but it will take a bit of an overhaul on the turret code so I'm reserving it for later. It's planned but I decided to wait until I improve the AI a bit. If the other suggestions failed, just wait. I'm still making improvements to AI behavior with fixed guns. It won't be necessary to do anything different to the missiles if the planes are flying correctly. They shouldn't ever be pulling(pushing?) negative G's so they shouldn't pitch down into underslung missiles. I noticed in your video that your planes were over-damped so they couldn't roll into the correct orientation. Try turning steer damping down to about 5. It might help your proc.parts planes work better too. (ninja'd) Good! I forgot to mention that you should un-check Emit on the particle emitter so it doesn't emit until the turret script tells it to. My fireAnim is only for animating the reciprocating barrels. Units: all masses are in metric tons, velocity in m/s, distances in meters, pitch and yaw in degrees. Rotation speed is a bit arbitrary.. its degrees per physics frame. Accuracy is also a bit arbitrary.. higher is better. 0 would result in NaN! (dividing by zero) so don't do that. These arbitrary things will be fixed when I get around to re-doing the turrets. Rotation should be degrees/sec, and accuracy should be a range in degrees or a spread at a certain distance. I'm delaying re-doing the turret code because the way I want to do it would require reconfiguring every turret. Can you somehow give me a way to replicate the problem? Describe your crafts - what are they equipped with, what are the guard settings. How far are the targets? etc. Thanks. What were the guard's guard settings?

Can you explain the scenario where this is happening? A log would help too. Guards spit out some info on what they're doing in the debug log. Better yet, (additionally) some screenshots with the option "Draw Debug Labels" on. It shows a list of each team's targets and whether they have been engaged.

Thanks. Since part tools is running into a problem during export, the exported model is incomplete, so KSP can't load it. Make a new material for your particles - don't use the Default-Particle material, as it uses a shader that KSP doesn't have. When you make your material, use one of KSP's particle shaders. I'm considering your suggestion, as I do all suggestions. I don't want to say yes or no to any of them, but I do keep a list of them which I look at when I decide to work on an update. The weapon manager is a part that you have to attach to your ship. You should watch the tutorial video on the first page, it'll explain almost everything.

For the AI (also anyone who had questions about AI setup), try setting steer factor to 15 and damping to 5. I have been able to get all different kinds of planes to fly fine with AI in FAR. It sounds like you may have turned steer damping too high. What steer damping does is it applies input to counter angular velocity. You need it so that the plane will slow it's rotation as it gets close to the attitude it wants, otherwise it will keep overshooting and overadjusting. If it's too high, the plane will try to slow its rotation down as soon as it starts turning so it will never pull any Gs. 5 seems to be a good value for most planes. As for the missiles sticking - I'll see if I can get it to work more consistently (its a KSP issue with load ranges) but for now try increasing the phys range. If guards don't have a target, or don't have a weapon to match a target, it will disengage and select None until it finds a suitable weapon-target match. Post a screenshot of your turret's hierarchy with the muzzleTransform selected, and then run KSP with that setup and post your output log. I'll try to see what's wrong. RCS isn't necessary for the AI, and it won't really help much. Control surfaces apply way more force than any RCS can. EE only used them to help planes stay in formation with BurnTogether. No, there's no way BDArmory is adding animations to turrets. If it is working on your computer but not someone else's, it means they have different files than you. Make sure they have the latest BDArmory. Remember, the fix was in an update, and if they don't have that update, it wont be fixed... To anyone reporting a bug or issue: I need specific details of the problem, how to reproduce it, and an output log of when it happens. Screenshots and videos can help too. Otherwise there's no way I can help.

Make sure you installed BDAnimationModules.dll. I assume you installed only the AdjustableLandingGear folder and not the BahaSP folder. You need both.

Try this: Tweak the .50cal's yaw range to be 180 or less. The guard checks to see if the target is within the gimbal limits of the turret. This way, if the target is in front, the guard should pick the m230 instead of the .50cal.

I took that option out of the settings window because I want to focus on making 'smart guards' better without having to worry about backwards compatibility. You could help by explaining precisely what it's doing, and what you expect it to do, so I can try to improve it. Otherwise, you can turn it off in the settings.cfg file but I don't guarantee it works completely. I haven't checked to make sure that smart guard code never interferes if it's set to false.

But you can't fire any guns with just the action group. Weapon manager's fire is only for missiles, bombs and rockets.

Press Alt-B to bring up the settings. You can bind the fire key to your joystick.

Update v1.3: - 1.0+ Compatibility - Manual camera position now persists after resetting camera - Bind activate/reset key by recording instead of typing button name - Camera no longer resets when pausing I didn't get around to adding new features I wanted, but at least I fixed a couple things

BDAnimationModules can now toggle engine animations in the editor.

Update v1.1.1 - Fixed sound file path for small landing gear - Removed invisible box (FAR voxel is now correct) - Changed steering to wheelSteer instead of yaw - Converted textures to DDS format I was delaying so I could try to implement mass and cost scaling and heat shielding but decided I should release it with the fixes first. Delete your old AdjustableLandingGear folder first to get rid of the png textures before updating.

I use Blender and Photoshop, sometimes GIMP. Check the log (KSP/KSP_Data/output_log.txt) for errors, or host it somewhere and post a link here, and explain exactly what you do that causes the crash. One of my turrets or a "third-party" turret? Glad you got it working. If you haven't figured out muzzle flashes yet, just look at the muzzle transform in the sample turret. It has a KSPParticleEmitter that is disabled before exporting. The shiny scratches can be done by using a specular map. You do this by painting in the alpha channel of the diffuse map (texture). Black will be completely diffuse and white will be completely specular.

Yes AI uses AGM missiles when appropriate. Pretty much, haha. No, not yet. I'm delaying because I'm working on additions and improvements to the AI so I think I might as well wait so I don't have to re-explain stuff if I change something. Seems fine to me!

You're using the KSPParticleEmitter right? Not the standard Unity one? Also don't do any animations on the particle emitter. Yeah EnterElysium also asked that. Its on the todo list. Which missile against what kind of target? Anti-air missiles will almost always miss against grounded targets. Missing textures and ammoboxes is a result of installing it in the wrong place. Check the tutorial.

CrayzeeMonkey, do you have a fire animation? If not, make one, or set "hasFireAnimation" to false. PrototypeTheta, that's not a solution to anything because muzzleTransform is required if you want to have muzzle flash/smoke. You should try to find out the real reason behind why muzzleTransform is causing you problems.

No, I was going to do that (peace time option that you can switch off after setting things up) but I forgot. I'll put it back on the todo list.

It already kind of does that. If it scans and finds a target and picks a weapon, but the target is not lined up in a good position to fire the weapon, it cuts the scan interval by 85% until it can fire.

Thanks guys. I edited the title.

Bullet mass is calculated in metric tons. The Oerlikon bullet is actually supposed to be 35mm with a projectile mass of 550g. So yes you're right, its a typo and should be 5.5e-4. Thanks for noticing that!