gotmachine

    [AttributeUsage(AttributeTargets.Field)]
    public class PartModuleSerializeAttribute : Attribute { }

    public class SerializablePartModule : PartModule, ISerializationCallbackReceiver
    {
        private static readonly Dictionary<Type, SerializablePartModuleInfo> accessCache = new Dictionary<Type, SerializablePartModuleInfo>();
        private static readonly BinaryFormatter bf = new BinaryFormatter();

        [SerializeField] private byte[] serializedData;
        [SerializeField] private int[] offsets;

gotmachine

using System.Collections;
using UnityEngine;
using Vectrosity;
using Camera = UnityEngine.Camera;

namespace VectrosityCameraHandler
{
    [KSPAddon(KSPAddon.Startup.AllGameScenes, false)]
    [DefaultExecutionOrder(9000)]
    public class VectrosityCameraHandler : MonoBehaviour

gotmachine

using System;
using System.Collections;
using UnityEngine;
using UnityEngine.UI;

namespace Utils
{
    public static class PAWUtils
    {
        /////////////////////////////////////////////////////////////////////////////////////////////////////////////

gotmachine

using System;
using System.Collections.Generic;
using System.IO;
using System.Reflection;
using System.Reflection.Emit;
using HarmonyLib;
using Mono.Cecil;
using Mono.Cecil.Cil;
using Mono.Cecil.Rocks;
using MonoMod.Utils;

gotmachine

using System;
using System.Linq.Expressions;
using System.Reflection;
using System.Runtime.CompilerServices;

#pragma warning disable IDE0041 // Use 'is null' check

namespace UnityObjectNullExtensions
{
    public static class UnityObjectNullExtensionsSafe

gotmachine

using System;
using System.IO;
using System.Reflection;
using System.Linq;
using UnityEngine;

namespace KSPCommunityFixes
{
  [KSPAddon(KSPAddon.Startup.Instantly, true)]
    public class MyAssemblyLoader : MonoBehaviour

gotmachine

This guide applies only to KSP 1.8 and latter. It covers modifying a KSP installation to allow :

• In IDE debugging of KSP plugins by using breakpoints, inspecting runtime variables, doing step-by-step execution, etc. Both Visual Studio (including VS for Mac) and JetBrains Rider support debugging Unity games, and by extension KSP plugins.
• Using the Unity editor profiling tools, which include great tools to measure and analyze CPU/GPU usage and memory allocations.

This guide is extensively tested for a Windows / Visual Studio scenario. However, it is theoretically possible to make all that work under MacOS or Linux, either with the Rider IDE or Visual Studio for Mac. This guide has limited details about those scenarios. I encourage you to leave a comment if you have additional information / experience.

Modifying KSP for profiling/debugging

Downloading the Unity editor

gotmachine

using System;
using System.Collections;
using System.Collections.Generic;
using Unity.Burst;
using Unity.Collections;
using Unity.Jobs;
using UnityEngine;
using UnityEngine.Profiling;
using UnityEngine.Rendering;

gotmachine

using System;
using System.Collections.Generic;
using System.Reflection;
using UnityEngine;

namespace UINumericFloatEdit
{
    [KSPAddon(KSPAddon.Startup.FlightAndEditor, false)]
    public class CustomPartActionControlSpawner : MonoBehaviour
    {

gotmachine

    [HarmonyPatch(typeof(UIPartActionInventorySlot))]
    [HarmonyPatch("OnPointerClick")]
    class UIPartActionInventorySlot_OnPointerClick
    {
        static bool Prefix(UIPartActionInventorySlot __instance, PointerEventData eventData, ModuleInventoryPart ___moduleInventoryPart, InventoryPartListTooltipController ___tooltipController)
        {
            if (!(___moduleInventoryPart is ModuleActiveInventoryPart activeInventory))
            {
                return true;
            }