![](https://forum.kerbalspaceprogram.com/uploads/set_resources_17/84c1e40ea0e759e3f1505eb1788ddf3c_pattern.png)
![](https://forum.kerbalspaceprogram.com/uploads/set_resources_17/84c1e40ea0e759e3f1505eb1788ddf3c_default_photo.png)
Biotronic
Members-
Posts
359 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Everything posted by Biotronic
-
Not to be unreasonable, but I'm not gonna install all those mods to figure out which one gives you problems. As others have pointed out above, there are incompatibilities between Procedural Parts, Procedural Fairings and TweakScale. The sad fact is, they use incompatible versions of the KSPAPIExtensions library. I tried recompiling all three with the newest version of KSPAPIExtension, and that works. But that's hardly a burden you can place on the average user. I'm not sure what rights I have to distribute it, but here are updated DLLs for all three. They seem to work for me. [EDIT]swamp_ig has told me how things are supposed to work, and I find his logic impeccable. Please download and install TweakScale 1.5.0.1, where these problems seem to be fixed.[/EDIT]
-
[1.0.2][May17] SelectRoot2: Fixing stock awkwardness
Biotronic replied to FW Industries's topic in KSP1 Mod Releases
I took the liberty of turning this thing into a proper project. -
Have you ever wanted to remove one of four symmetrically placed boosters? Now you can, with brand StripSymmetry! Just alt-shiftclick the offending symmetric set, and start removing! More seriously, StripSymmetry lets you turn a set of symmetric parts into separate parts with the same locations. This project is based on code written by futrtrubl. Download here! Alternative download on Dropbox Curse page KerbalStuff Source on GitHub Current Version: v1.6 (2015-04-28 20:20 UTC) This project is made available under the Double-yoo Tee Eff public licence. How to use Hold left alt, left shift and left click on the offending part. A message will state that symmetry has been removed, after which you can move and remove parts to your heart's content. Oh, and don't forget to revel in your new-found powers. Version History v1.6 (2015-04-28 20:20 UTC) Updated for 1.0! v1.5 (2014-12-16 23:23 UTC) Updated for .90! Version 1.4 (2014-08-25 00:26 UTC) Fixed a bug in config handling. Version 1.3 (2014-07-18 19:16 UTC) Updated for 0.24 Version 1.2 (2014-06-04 23:06 UTC) Fixed a bug where child parts were not stripped of symmetry. Version 1.1 (2014-05-22 13:33 UTC): Moved config.xml to a folder where it does something sensible. You can now change the hotkey! Version 1.0 (2014-05-20 20:16 UTC): First version! Thanks, futrtrubl!
-
After a short test, it seems to me that removing Procedural Parts's copy of KSPAPIExtensions.dll fixes the problem. I strongly disagree with their placement of the dll, as it's a dll that is used by other projects and should therefore reside in a common directory, and I've thus informed the mod creator. [EDIT]A short talk with swamp_ig later, I've found his reasons to be sound. Please delete KSPAPIExtensions.dll in the Gamedata directory, and install TweakScale 1.5.0.1.[/EDIT]
-
Great project! One thing - a user told me that using Procedural Parts with TweakScale! Rescale Everything! is fraught with danger. It turns out this is caused by different versions of KSPAPIExtensions.dll. In order to minimize such problems in the future, it would be beneficial to place this dll in a common folder - I'd prefer Gamedata/. This way, if two or more mods include the same dll, we will not end up with conflicting copies. Thank you.
-
[0.23.5] Goodspeed Aerospace Parts v2014.4.1B
Biotronic replied to Gaius's topic in KSP1 Mod Releases
Worry not! The new version of TweakScale is compatible with GoodspeedTweakScale again. -
The way to do this at the moment is to create your own TweakScaleUpdater and register it with... crud, that function I seem to have removed. Well anyways, a new TweakScaleUpdater for IR, which sets some field on the MuMechToggle(?) to indicate the new size or simply changes the extension length. I'm currently in the process of testing NathanKell's idea of using reflection. If that works out (I doubt it'll work for every single possibility), you can just define something like this: TWEAKSCALEEXPONENTS { name = MuMechToggle extensionLength = 1 } and it'll magically look up extensionLength on your PartModule, multiply the default value by the scale, and store it back in.
-
@ZodiusInfuser: Currently, IR_TweakScale.cfg file is in the TweakScale folder. This is problematic if people want to update only TweakScale and delete the TweakScale folder and replace it with the new version from the TweakScale package. I suggest it be moved to the MagicSmokeIndustries folder. (for ease of transition, place an empty IR_TweakScale.cfg in the TweakScale folder, then people won't have to go around looking for files to delete)
-
New version out and available in the first post or here. For the record, I hate Curse's review system. Yeah, it's probably not that hard, so let's say it's not my #1 priority at the moment. There's also quite a few things I'd need to read up on before embarking on such a project. Mostly, I'm saying it will happen when I'm ready, so don't expect anything. Uhm... I have no excuse. I'm... sloppy? Fixed in the new release, at least. Not sure what you mean here - when you resize a fuel tank, its new volume is displayed. Do you want it to display the volume of non-fueltank parts? Done! It's much better now. Thanks a lot! Fixed. The new version comes with KSPAPIExtensions 1.4.3.6.
-
Here's my take. I haven't looked much into this, so I'm not sure this would be possible, but here goes: MODULE { name = TweakScale type = free // Or whatever. SEGMENT { mesh = myCap role = endcap_1 rotation = 0.0, 0.0, 0.0, 0.0 // Axis/angle, quaternion, whatever. offset = 0.0, 0.0, 0.0 node_stack_bottom = 0.0, 0.3, 0.0, 0.0, 1.0, 0.0, 1 } SEGMENT { mesh = myCap role = endcap_2 rotation = 0.0, 0.0, 0.0, 0.0 // Axis/angle, quaternion, whatever. offset = 0.0, 0.0, 0.0 node_stack_top = 0.0, 0.3, 0.0, 0.0, 1.0, 0.0, 1 } SEGMENT { mesh = myTruss role = section // rotation, offset, nodes cumulativeRotation = 0.0, 0.0, 0.0, 0.0 } SEGMENT { mesh = myMidCap role = midcap // rotation, offset, nodes cumulativeRotation = 0.0, 0.0, 0.0, 0.0 } sectionLength = 0.625 } This would be ZodiusInfuser's truss. The roles describe what rule to use to place each segment, and can thus be extended in the future should one want e.g. a 2D grid of M-1x1 Structural Panel. As you can see, type is still available, so a part could be rescaled in addition to being tiled along an axis. cumulativeRotation lets the next segment be rotated 90 degrees (or of course any other number), as ZodiusInfusers mentioned his trusses were. However, this is an advanced feature that I will not promise to implement.