phas

P.s. since this is an annoying, persistent, non fixable bug, wouldn't be a good idea to make a standing thread about this?

So, now tell me something that i don't know: how can i mitigate this / workaround this / live with this?

I'm sorry: i'm sure that this issue has already be reported a lot of times, but i can't never find a thread or some other exhaustive informations on this. The problem is that orbits are "unstable". Ap and pe and other values keeps changing. This is limited and less problematic in kerbin SOI and a very big issue on interplanetary orbits. Let see an example: This is a recurring issue, i have got more than 400 hours on this game and i always got this problem on every versions. I play modded and this is my current modlist, but the problem is everlasting with every modset i play. The only constant is probably MechJeb. AFAIK this problem should be related to floating point math errors calculating positions and orbits in a big space and it's not easily fixable, ok. But isn't there any workaround? Any way to mitigate this? It's really hard to plot an accurate interplanetary transfer this way.

You have it installed twice

Use tweakscale

fffs my cruiser has a JATO drone armed with hellfire missiles

The tzar bomb actually crashes the game. I'm not sure if this is a bug or a feature.

This is what i would do: The radar detects the targets in his range and build a list-like object (maybe a binary search tree ordered on distance or even a quad tree). The guard will inspect this list-like object and his own weapons and settings to search for a suitable target. When found it will ask the radar for a lock on the target. The radar will track the target as locked and give back the guard some Lock object filled with informations on tracking status and stuff. The guard and missiles or whatever will use this Lock object to fire at the target/guide missiles/whatever. The radar will maintained a list of Lock objects and update them with current locking status. e.g. if lock it's lost it'll update the status and the guard/missile will act accordingly Considering the current tracking capability of modern radars and the limitations of pratical ksp/bdarmory i wouldn't worry on limiting the maximum number of trackable targets. Even if you have a lot of targettable objects, it's unlikely you have that many guards, so the system would not be OP. On the other hand in the future you may implement multiple target engagement in the guards and then set a different maximum number of trackable targets in different models of radars and that will add a lot of variety to the radar system.

Hey BahamutoD, please consider this small feature request: could you make an "auto mode" for the radar data receiver where if the "auto mode" is activated and the receiver is not connected to any radar, it will connect to the first available allied radar? (optional, preferring tracking radars) This is needed for making systems of turrets using one radard in contracts configurator (since you have no way of specifying a radar to connect to in either contract or .craft AFAIK) Also will be useful to create a more robust turrets defence system that can survive the death of a single radar. It should be quite easy, i would do that myself but, ehm, i've not visual studio installed at the moment and i think that it will require more time to setup the development enviroment than actually doing the changes in the code. Thx

Same here

I was playing with contracts and I ran in a peculiar bug. I made a contract that spawns an aircraft at 1000m, with pilot, guard and engines activated, so when the battle starts, it starts to fly just nice. What happens tough is that it's bot invisible on radar from my plane and fails to launch missiles at me (but it fires with gun). My bet is that somehow the enemy craft didn't "take off" and therefore still count as "landed".

moar aerial combat pls

Ah, that's interesting. Ok thx. I'll wait for my new video card to arrive then

Some of the enemies spawn underground ... Hey, i might be wrong on that, but it seems a bug of Contract Configurator more than a bug of 5dim. It happens e.g. in "no more KSCs" mission

It's just a matter of removing orbit info and setting the pitch in the configuration file. It's a one-hour job. I started to do that but it's so hot here that my desktop pc crashes for the temperature