Biotronic
Members-
Posts
359 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Everything posted by Biotronic
-
StripSymmetry, a mod I've adopted and cleaned up a bit, does things when you click on a part. One of the things it does, but is not supposed to do, is pick up the ship. I looked at SelectRoot's source to get inspiration, but it seems to sidestep the whole problem by saving the ship, modifying the save, then reloading again. So, is there a way to tell KSP not to pick up a part/ship?
-
Thanks to ZodiusInfuser's modeling efforts, I spent a few hours yesterday perfecting my Kethane rover (Warning: contains spoiders): And its little babies: Mod list (beeg spoider): Infernal Robotics and Rework for the legs. Habitat Pack for the pod opisthosoma (tail, abdomen, icky ball thing). KAS for attachment spinneret and crane on opisthosoma. Kethane for the main body tank and the drill 'fangs'. SCANsat for GPS and anomaly tagging. And small spoider: Infernal Robotics and Rework for the legs. KAS for attachment spinneret. B9 Aerospace for RCS thrusters. KW Rocketry for the head. Now to get the blasted things to move... Also, does anyone know of a spherical container where I could put a dozen or so of the babies and release them when needed?
-
Thanks to ZodiusInfuser's modeling efforts, I have spent a few hours today perfecting my Kethane rover (Warning: contains spoiders): Mod list: Infernal Robotics and Rework for the legs. Habitat Pack for the pod opisthosoma (tail, abdomen, icky ball thing). KAS for attachment spinneret and crane on opisthosoma Kethane for the main body tank and the drill 'fangs'. SCANsat for GPS and anomaly tagging.
-
This is the line that does the scaling: savedScale = part.transform.GetChild(0).localScale = Vector3.Scale(basePart.transform.GetChild(0).localScale, rescaleVector); basepart is the prefab. So yeah, if something else sets the scale at an inopportune time, we's ferked. Maybe it's possible to add another layer in the transform hierarchy, and do TweakScale scaling there? If not, I'm looking for ideas. Weird, they work great for me. What other mods are you guys using? Now there is. Example with which I tested the feature: @PART[solarPanels1] // SP-W 2x3 Photovoltaic Panels { MODULE { name = TweakScale type = surface MODULE { name = ModuleDeployableSolarPanel chargeRate = 1, 2, 3, 4, 5, 6, 7 flowRate = 1, 2, 3, 4, 5, 6, 7 panelMass = 1, 2, 3, 4, 5, 6, 7 } } }
-
Actually, I'm gonna ask for a bit of clarification - do you mean that a specific part (say, IR_Pivotron_Basic) should have a different factor for some module parameter (say, keyRotateSpeed should scale with the cube of the scale)? Or are you thinking of something else and I haven't quite understood what you meant?
-
I'm with marce on this - it works for me with all three installed, and three different KSPAPIExtensions. A question to to other mod makers out there - TweakScale currently changes part.transform.GetChild(0).localScale. That's the way GoodspeedTweakScale did it, so I saw no good reason to change that. Now I see that removing GetChild(0) from that fixes the scale problems with KW parts. I don't really know why, as I haven't looked too closely at the values there, but it seems this change does good things and nothing bad. Any reasons why I shouldn't do this? Scratch that, I just found plenty reasons not to do that.
-
1) Have you installed TweakScale 1.5.0.1? 2) Have you deleted KSPAPIExtensions.dll from Kerbal Space Program\Gamedata? 3) Does output_log.txt say anything whatsoever about TweakScale? 4) Not all parts have been made scalable. I belive everything under propulsion is, so try a few of those if you're unsure. I've traced the error messages in your log to a combination of MechJeb, SCANsat and RasterPropMonitor. If you lack one or more of these, you will get error messages. If you don't use RPM and don't want the messages, delete both SCANsatRPM and MechJeb2RPM from your GameData folder. Same goes for MechJeb and SCANsat for their respective folders.
-
It seems that IRescalable is not as fantastic as I first thought. Basically, it seems one'd need to put them in a separate dll from the main behavior. This is less than optimal, so I'm considering a different solution where one'd simply register a function. This is also less than optimal, but might be better.