DocNappers

The Player.log doesn't appear to show anything more than the KSP.log did. However, I have to reiterate that the last message is where a typical log switches to messages from other mods, so I very much suspect that BDA+ is not the cause of the issue here and you'll need to manually figure out which mod is causing the problem by removing mods until KSP can get past that point. The surface AI set to submarine type will try to adjust its altitude to an appropriate depth for combat (surfacing or returning to "Combat Alt." as needed). It does this by adjusting pitch, though, not by adjusting ballast.

This is the same log file that you posted above, to which I already gave an answer here.

If it's using up your fire bottles, then it's BDA+'s fires that are occuring, which is an option under the Battle Damage settings — you can disable battle damage, disable fires completely, or just disable "Fires Add Heat" to prevent auto-ignition of fuel/parts when they reach their ignition temperatures (493K for kerosene, 900K for ammo, 510K for wood, etc. (see GameData/BDArmory/BulletDefs/BD_Materials.cfg for the various material properties, a value of -1 means it won't auto-ignite)).

Ah ok, I can ask the others (I don't do the modelling side of things, only the coding). The guy that originally made the open cockpit is vary rarely around and I'm not sure what's involved in making a variant for a part from an existing model. The alignment indicator doesn't show for APS (Active Protection System) turrets, but I suspect that it's a bug that it's not showing for turrets that can act both as APS and regular turrets.

BDA+ isn't a parts mod. It only has a few parts designed to show off what functionality is supported. So, variations on the open cockpit would be more appropriate in other mods such as "Moderately Plane Related" or "BDArmory Extended" (though the latter is more focussed on weapons). The "weapon alignment indicator" (which I presume is what you're referring to) is toggled with F2 in the SPH. The other toggle BDA+ provides in the SPH is a CASE ammo explosion visualiser, which is toggled with F3.

I don't see anything in the log that would prevent KSP from starting. The errors in the log from BDArmory about using default values when it's parsing various bullet types aren't important (they should really only be warnings), they just indicate that those bullet types might not be working as originally intended due to incomplete or outdated configs. The log ends after parsing the various material types, which is generally where the log entries change to that of other mods (such as EVE for my installs, but may be different on yours). So, I suspect that it's a different mod that is preventing KSP from starting. You might be able to find more info in the Player.log file (see https://forum.kerbalspaceprogram.com/topic/83212-how-to-get-support-read-first/ for where that might be) and/or by setting "LOG_INSTANT_FLUSH = True" in KSP's main settings.cfg file.

Check for errors and exceptions in your KSP.log file. It's working correctly for me ™, so I would need more information to figure out why it's not working for you.

That should be possible. You should already be able to map the controller's buttons to the various keybindings, but it'll need some code changes to make use of the stick axes.

Config parameters for any given class are all the public fields that are tagged with [KSPField] in the code of that class and its base classes (so, MissileLauncher and MissileBase for standard missiles). Many of them aren't even documented in the code though, so you'd need to compare them with those in some of the existing missile configs or ask whomever added them in (@BillNyeTheIE has done quite a bit on lofting missiles, but I'm not sure who else has worked on missiles). gLimit looks to be only used as a parameter to getGLimit in MissileGuidance, which has a pseudocode explanation of what it's doing at the end that might be helpful.

v1.34.0 of CameraTools is now released. It has the following improvements / bugfixes: Chinese localisation thanks to user ThreeMACH. Pivot toggle: Add an option to toggle pivot points between the camera and the target (if valid) when rotating with the right mouse button. A hotkey can be assigned to this toggle, but is not assigned by default. When pivoting around the camera, the behaviour is unchanged. When pivoting around a target in pathing or stationary camera modes, the behaviour is similar to KSP's standard camera movement depending on whether the movement modifier is being held or not. While the movement modifier is not being held, rotation is aligned with the camera's axes. While the movement modifier is being held, rotation is aligned with the target vessel's axes. In pathing camera mode, the pivot point is the vessel's reference transform position. In stationary camera mode, the pivot point is either the targeted part or the vessel CoM if that option is selected. In dogfight camera mode, the pivot toggle affects the free-look mode and pivots around the closest point to the vessel along the camera's forward axis. Fix camera roll when transitioning between modified and non-modified movement modes in stationary camera mode. The free-move mode (position vs speed) and pivot mode are now preserved in the settings. Tweak the mouse sensitivity for input to rotations for more comfortable rotations.

Enable debugging for Weapons and AI in the settings and then check the log and on-screen telemetry when this happens to see if there's a problem with some of the craft.

I haven't heard of that happening before. You'll need to look in your KSP.log file to see what exceptions are being thrown, which will likely tell you which mod is the root of the problem.

Do you have "Keypad Control" enabled (near the bottom above "Edit Keybindings"), Zoom In/Out bound to keys and the "Zoom Speed" set to a reasonable value? v1.33.0 of CameraTools is now released. It has the following improvements / bugfixes: Add a slider for controlling how long after BDA's secondary dogfight target dies (for non-missiles) before selecting a new secondary non-missile target (to enable lingering on kills). Fix false positives of Krakensbane being active on vessel switches.

The infinite ammo option is for gun, laser and rocket type weapons (you may also need infinite EC for lasers, depending on the laser). The infinite ordinance option is for missiles/bombs, but it only works for reloadable missile launchers, such as the "Twin-mount Missile Rail", "Deployable Missile Pod (Reloading)", "C-VLS-12" and "C-VLS-24" MissilePods and "VLS Quad Cell" from BDArmory-Extended (basically anything with the ModuleMissileRearm module in the part config. So, for infinite bombs, you could add some twin rails or a reloadable deployable missile pod to your craft and add whichever bombs you want to use to them and have this option enabled.

Open the settings window with the cog icon on the weapon manager window, then expand the sections in the image. From the snippet of the log that you posted, it looks like Kopernicus is throwing an exception when handling the event of the ProtoVessel getting loaded (part of the spawning process), which might explain why an aircraft ends up partway into terrain if all the colliders aren't properly loaded (or take a long time to be loaded in the background), however, this is being caught and reported as an error (above the exception's stacktrace), so it doesn't interrupt the spawning process. Next, however, PersistentThrust is throwing an exception when the ProtoPartSnapshots are being saved (also a crucial part of the spawning process), but this isn't being handled, so it's causing the spawn process to break and BDArmory thus reports "[BDArmory.VesselSpawnerBase]: Failed to spawn craft Dove".