"Vessel is missing part RTShortAntenna1"

[EoD]

I tried to move from RemoteTech to Kerbnet, but I am encountering above error.

I thought it would be enough to use RemoteTech-Antennas (combined with CommNet Visualisation for the looks) to get a similar look&feel, but apparently RTShortAntenna1 is missing and hence kills about every single vessel I am flying.

It seems that 184b0fc removed the respective antenna, hence making an upgrade impossible. Would it be possible to change these antennas to the stock antennas by e.g. a module manager module?

Or are there other workarounds?

[KSP-TaxiService]

Hi, my apologies for not noticing your issue in this repository soon. I removed the antenna DP-10 as it looked same as stock stick antenna and didn't offer any advantage over the stock one.

However, you can use this workaround to resolve the missing-part error by copying the RemoteTech/GameData/RemoteTech/Parts/ShortAntenna1 folder into RemoteTech-Antennas/Parts to restore back the missing part.

[EoD]

I assume this means you are going to add a ModuleManager script which replaces the RemoteTech DP-10 with the stock counterpart?

[KSP-TaxiService]

For this antenna repository or your side with the missing-part error?

If former one, DP-10 is redundant and I can't see the point of re-adding back as the stock stick antenna is already there.

Otherwise, ShortAntenna1 (DP-10) folder I mentioned has MM cfg. Just copying over to your folder will fix the error.

[EoD]

I am not sure if you understood what I meant. It needs to be added for this (and also for the old RT) repository, otherwise you will break backwards compatibility with older saves. So you need to have some backwards upgrade mechanism in place.

Maybe there are more ways to do this, but a MM script sounds to be the easiest way for me. So once this script is in place and people load old savegames, the old DP-10 is automatically upgraded to the 16-S. And the next time they load the script, the MM script will just do nothing.

[KSP-TaxiService]

Ok I see your point. I could revert the deprecation of the antenna and change one attribute to be unavailable to player but accessible to the game.

But this antenna package is intended as a clean start state of RemoteTech 2, not upgradable from RemoteTech1. There is too many major changes planned in RemoteTech2 to be upgradable from RemoteTech1.

[EoD]

I was hoping that you can run a script which replaces (literally replaces) the RT antenna with its stock counterpart in order to allow loading oder save games. If this is not possible, disabling it from being used is probably the next best way to go.

Isn't this repo here the actually only piece which needs to stay backwards compatible between RT1 and RT2 (or even vanilla) to allow loading old save games?

[KSP-TaxiService]

Unfortunately, this repo is meant to be clean break from RT1. The planned RT2 codebase (realistic comm model) is so different from RT1 codebase (simple range model). This means any RT1 save is incompatible with this repo. I never realized this risk when I open this repo to the public consumption.

This repo serves as a starting point for RT2's comm model based on our reality (eg add new Omni, AESA, Parabolic antenna parts and remodel existing parts).