DocNappers

Yeah, there are still a variety of glitches in CameraTools. I've been busy with adjustments to BDArmory lately for the latest Runway Project round. Hopefully, I'll have a bit more time to fix these issues now. I haven't tested it with time warp enabled since we've mostly been running fights in real-time in atmospheres. It ought to just be a matter of shifting the velocity calculations over to using KSP's `TimeWarp` class instead of Unity's `Time` class, I think. Using the wrong time-step in those calculations would definitely lead to a horribly shaky camera. Using a different camera mod together with CameraTools should be fine as long as only one of them is active at a time. The way that it works is that each mod (and the base KSP flight camera) assigns the flight camera to a game object and then moves that object around, so if it's active in one mod and then another one steals it, the first mod is going to continue applying transformations to it with the expectation that the camera is attached to its game object (which it isn't). Ideally, each camera mod would check that the flight camera parent transform is the one it's using before applying any transformations.

I've just updated CameraTools continued to v1.15.1, which should resolve the issues with the missing config file.

Looks like I missed one of the places where the version number is set. I'll update it. The problem with the icon not showing up in the GUI is due to it not finding the settings.cfg file when it tries to load the assembly (the settings.cfg file was removed at one point to avoid overwriting everyone's settings each time it got upgraded). I'll add a fix so that it uses the default values if it doesn't find it. In the meantime, you can generate a settings.cfg file with my current settings: CToolsSettings { referenceMode = Surface toolMode = DogfightCamera randomMode = False autoFlybyPosition = False autoFOV = True freeMoveSpeed = 10 keyZoomSpeed = 1 zoomExp = 1 enableKeypad = False maxRelV = 2500 manualOffset = False manualOffsetForward = 500 manualOffsetRight = 50 manualOffsetUp = 5 useOrbital = False targetCoM = False cameraKey = home revertKey = end useAudioEffects = True shakeMultiplier = 1 dogfightDistance = 50 dogfightOffsetX = 10 dogfightOffsetY = 4 autoZoomMargin = 25 useBDAutoTarget = True dogfightLerp = 0.1 dogfightTargetLerp = 0.25 autoEnableForBDA = True DEBUG = False dogfightRoll = 0.5 }

There should be a sonic boom in there from before, though it requires that a plane be travelling faster than 330m/s towards the camera. I'll need to do some testing to check that the playback volume is the right level to be audible.

This is a continuation of Camera Tools originally made by BahamutoD and previously maintained by jrodrigv. It is intended to be used with the version of BDArmory Plus that has been extensively built upon after gaining a surge in popularity from Scott Manley's use of it in Runway Project and is currently being used for Flying Circus, but probably works fine with other versions of BDArmory too or even without BDArmory. > Download from SpaceDock Source on GitHub License: GPLv3 New features in v1.36.0 New features in v1.35.0 New features in v1.34.0 New features in v1.33.0 New features in v1.32.0 New features in v1.31.0 New features in v1.30.1 New features in v1.30.0 New features in v1.29.2 New features in v1.29.1 New features in v1.29.0 New features in v1.28.0 New features in v1.27.0 New features in v1.26.0 New features in v1.25.0 New features in v1.24.0 New features in v1.23.0 New features in v1.22.0 New features in v1.21.0 New features in v1.20.0 New features in v1.19.2 New features in v1.19.1 New features in v1.19.0 New features in v1.18.2 New features in v1.18.1 New features in v1.18.0 New features in v1.17.0 New features in v1.16.4 New features in v1.16.3 New features in v1.16.2 New features in v1.16.1 New features in v1.16.0 New features in v1.15.4: New features in v1.15.3: New features in v1.15.2: New features in v1.15.1: New features in v1.15.0: