ValiZockt

Heya! Yeah i’m (slowly) working on a refactor & adding docking corridors style visualization in flight and some other stuff. Will bump up the version in that pass. But thank you for letting me know!

I’ll probably look into a user friendlier difficulty setting for that, so everyone can choose for themselves.

That’s not really helpful. What doesn’t work? If you really want to help I’d need logs, reproduction steps etc.

@Apricot I'm not sure when or why this was added, but looking back this is probably right. If you want to (and if you’d be able to) can you create a PR for that on git?

@TomfooleryYT, the action groups are gone, as a new fins module was introduced. So that is expected. Nevertheless, It seems like KSP can't find the specified localisation strings. Which game version you're running? There may were some changes on SQUADs side between updates. If that is the case best is to dump localisation and just use english titles for the next update, if that's not the case try verifying your files via Steam.

To extend to this, keeping RO patches up to date is a hard task. That's why everyone from the RP-1/RO team mostly (as far as I know) discourage spreading of RO configs outside of the RO repo, it's much harder to keep them up to date (or even keep track of them).

To be honest, I'm just guessing at this point as DragCubes are a science on their own, but using multiple PartModules (that also include multiple drag cubes per module) always have been a bit problematic. Pre 1.10, it was not even possible do define multiple drag cubes like that. Since 1.10 they changed some part of that, see following (taken from the 1.10 modder notes): Which means that no matter what you do currently, the solar panel will always refer to procedural drag cube generation (As it includes four PartModules all implementing IMultipleDragCube). So I guess the only viable solution (to my knowledge, please if anyone knows more that me, I would be happy to be proven wrong) is to separate the functionality into it's own part, so that there aren't multiple PartModules that include IMultipleDragCube per part. If @benjee10 really has the time and motivation to even work on this (I guess he has a long enough list of things to work on), I'm happy to look into such PartModule, that can indepenently track to the sun (with respect to their child parts).

@TaintedLionBe sure to also have the quality setting not set to lowest. KSP (in that setting) reverts to a single bone weighting per vertex. Which can break complex skinned mesh animations with many bones deforms

I don't have permission to view the file currently. Although, I may have already identified the issue, would still be good to double check with your craft file.

@Tivec, thank you for the bug report, is there a chance to could send me the craft file you were working on when that happened, so I can replicate this easily? (and possibly - if it’s still there, the complete log?)

If it’s linked to this mod, would you be able to upload and post your KSP.log?

It’s fairly straight forward: 1) Choose an IDE of your choice. Personally I use Visual Studio 2019. 2) Open the Project in your IDE and add references (point to KSPs and Unity assemblies) 3) Depending on how old the mod is you’re trying to recompile, you have keep in mind that there were API changes throughout version, so you may have to adjust or change some parts of the code. 4) Hit the Build Button. For more detailed instructions read through this post:

The wearable props are locked behind 1.11. They require the updated inventory system that came out with 1.11. The EVA & IVA suits will work with 1.10. For everything below you need to use TextureReplacer and manually have to flip the textures vertically. (Out of some reason, stock flips the textures after being applied to the kerbal material, which TextureReplacer doesn’t do.)

This is truly incredible, as always this is exceptional work, looks damn beautiful! Congrats on release! <3

That looks absolutely stunning! Congrats on release!

It’s definitely possible, as a starting point you might wanna have a look at the. EditorPartList and PartCategorizer classes. Both seem to go into the direction of part sorting.

There are three ways major ways to create a UI. First being the legacy IMGUI system, which is a fully code approach for creating UIs. It’s pretty easy to get into, but the performance is really bad compared to other approaches. (As it’s redrawn every frame) Don’t use it for really large complex UIs with a lot of objects. Then there’s the uGUI system (unity prefabs). This means creating the UI in unity, exporting it as a AssetBundle and hooking it up via code. Has much better performance and is really customizable. Tho, It’s harder to get into. There’s also ways to do uGUIs but with full code approach, which is damn hard to get right and would require a lot of code. If I’m not mistaken sarbian and taniwha were working on a KSP library for this. Last but not least there’s the KSPs own PopupDialog class. It’s a full code approach, but mostly (as the name suggest) only meant for small popup windows.

Yes, this is a bug that has been around since KSP 1.0.2, sadly. https://bugs.kerbalspaceprogram.com/issues/13199

manNode.nodeRotation.eulerAngles is a rotation, not a direction. Use manNode.GetBurnVector(vessel.orbit); Vector3.Angle is an absolute value, but you can calculate the polarity by using the cross product of both vectors and invert the angle if y is negative Vector3 currentOrientation = FlightGlobals.ActiveVessel.ReferenceTransform.up; //up is foward Vector3 targetOrientation = manNode.GetBurnVector(vessel.orbit); float angle = Vector3.Angle(currentOrientation, targetOrientation); Vector3 polarity = Vector3.Cross(currentOrientation, targetOrientation); if (polarity.y < 0) angle = -angle;

Do you need them separated in pitch, yaw, roll? If not you can simply use Vector3.Angle: Vector3 currentOrientation = vessel.referenceTransform.up //up is foward Vector3 targetOrientation //your desired direction float angle = Vector3.Angle(currentOrientation, targetOrientation) If you want to know how much your translating (or rotating) in each direction you can use vessel.angularVelocity

You don't need any Unity version to programm KSP Mods. You just need an IDE where you can write your code and compile it. (I personally use Visual Studio 2019 Community Edition, but you can use any IDE that suits your needs). If you really need to do stuff in Unity (which is rare), use Unity 2019.2.2f1 See this thread for more information.

Those looks amazing! Congrats on the release!

All modders out here do this stuff for free, they don’t get paid and completely do this in their free time. Your statement above is just frustrating for the people behind it (or rather dunbaratu, he’s the only developer left). They put hours and days into project just to provide us with free updates. kOS is a huge mod/repository trying to maintain it alone is very hard to do, so please don’t post such comments. Instead we should all thank dunbaratu for all his work on kOS. Just yesterday he released a huge update. And then if you aren’t happy with a mod, provide and post comments that can help the developer(s) to improve their mod, your comment isn’t helping anyone.

@Mossconfig, Yes this is mainly balanced for 1.0x up to 2.7x (JNSQ). Everything above (6.4x or 10x) will be really hard and maybe even impossible. If you are using Real Solar System, there’s only Realism Overhaul. RO does a bit more (ie part scaling) but in its core it holds all the RealFuels configs.

Uuuh, correct me if I’m wrong, but wasn’t this already pickup shortly before this? I think you both missed each other by only 6 hours