Jump to content

Biotronic

Members
  • Posts

    359
  • Joined

  • Last visited

Everything posted by Biotronic

  1. If the problem does not disappear (I honestly don't expect it to), I'd love to have a list of mods you're using. An output_log.txt would also be very nice, and for the grand bonus, I'd like a pony. I mean your persistent.sfs (from KSP\saves\savename\). With those, I might be able to reproduce the problem and see what I can do to pare it down.
  2. And 1.36 is released. New in this version is updated Real Fuels and Modular Fuel Tanks support, since they have apparently released new versions. Also, added KSPX config.
  3. Log: https://www.dropbox.com/s/sofskjftnydv040/larkvi_20140803_01.log In this log, with more mods, but the same problem, https://www.dropbox.com/s/cpgfdfu0szmw61o/larkvi_20140803_02.log, most of my original craft is missing, leaving this: http://i.imgur.com/FN5vQek.pngInterestingly, if I remove tweakscale, all the parts are there and attached, but they are no longer sized correctly, and the craft breaks apart. 0.24 Compatibility NoteTE is not broken in 0.24, and neither are a lot of other mods. That said, if you are using mods that change part functionality, especially if those mods use ModuleManager, you cannot use old or un-modded .craft files because KSP will break them. Squad introduced some new code to "fix" module order when loading persistence files, and it has introduced a raft of new issues to do when loading craft that were saved without mods into a game with mods. If you are having issues and are trying to load from a .craft file; please rebuild the craft by hand before reporting a bug. Thanks! It looks like it might be related.
  4. Landing legs were added in 1.35. I admit I'm not sure what you're talking about here. The sliders controlling resource amounts are exactly the same with TweakScale as without - the only difference is the maximum amount. Changing the maximum amount changes the size of each step, as the number of steps is simply the width of the slider in pixels. There was a report that TweakScale and TweakableEverything were not working nicely together. I have not been able to replicate the problem, and the information given was insufficient for me to start guessing at how to fix it, so I'm guessing it's not an actual problem (at least not anymore, as that post is two months old now)
  5. If it's your mod, I would suggest just adding the TweakScale module to the configs. It's not like superfluous MODULEs cause any problems, as far as I'm aware. That way, you don't need to prod me about updating TweakScale should your nose cones change, and users who download an updated version of your nose cones would not also need to update TweakScale, which might happen a few days after your update. That said, if it's what you want, I'll of course add the cfg.
  6. And now 1.35 is up. This fixes the problems with recovery cost, upgrades to KSPAPIExtensions 1.7.0, and adds support for many more stock parts, including wheels and probe bodies.
  7. When you download the TweakScale zip, many parts are made rescalable, but not all. If a part is not from the list of supported mods on , or a stock part, it is not rescalable, and must be added explicitly. You can do this by adding this in the part's .cfg: MODULE { name = TweakScale type = stack defaultScale = 1.25 } for a stack-mounted part with a diameter of 1.25m. For a different size, change 1.25 to some other number.
  8. I had a look-see at the pricing problems, and it appears that GetModuleCost is not called when recovering a ship. This is a bug in KSP, not something I can do much about. (except the workaround of adding a resource called 'money' and all the jazz that follows that) [edit]Scratch that, it's just being called at a weird time.[/edit]
  9. Weird. I know the Tweakscale cost handling has issues, and it's possibly the top priority to fix right now. Sadly, my gf insists on using my computer to play wow.
  10. Interesting. Is this 32 or 64 bit? Could you supply an output_log.txt when having both installed? Have you tried removing other mods to see if the problem disappears? (the latter is the reason I am loath to say Tweakscale supports KSP x64) I'm gonna have a look to see if there's any discernible reason for this incompatibility.
  11. I have not looked into how TweakScale interacts with wheels. It's very much possible that something is not scaled correctly, so thank you for prodding me to take a closer look.
  12. Sadly, KSP x64 is a fickle beast, and not fond of divulging information about why things don't work. I'll look into this, but given that, I am not sure I can solve the problem.
  13. This is, sadly, a known problem. It's to do only with KSPAPIExtensions, and can often be fixed by finding the newest KSPAPIExtensions.dll and replacing the others with that version.
  14. I'm not aware of any hard incompatibilities between TweakScale and any other mod except Goodspeed Aerospace, from which TweakScale is derived. There are some unfortunate interactions, especially in 64-bit KSP. TweakScale and Procedural Parts have a small disagreement where parts will be incorrectly placed, which I have yet to understand the reasons for. Some parts (Real Fuels engines come to mind) are not correctly updated in some cases, due to support not yet having been added. Apart from that, I am aware of no specific incompatibilities. (I am probably wrong) If you upload your output_log.txt and link it here, I could take a look and see if I can figure out what's wrong.
  15. There are no dependencies on MFT or Real Fuels. If you don't have them installed, you will get an error message like the above. Just ignore it, as it's expected and does nothing bad.
  16. Thanks, fixed in 1.34. Also added Karbonite parts for rescaling. I haven't been able to test that properly, so please report any issues.
  17. As can clearly () be seen in ScaleExponents.cfg: TWEAKSCALEEXPONENTS { breakingForce = 2 breakingTorque = 2 buoyancy = 3 crashTolerance = 1 explosionPotential = 3 maxTemp = 1 mass = 3 Resources { !amount = 3 maxAmount = 3 } attachNodes { breakingForce = 2 breakingTorque = 2 } } The Resources{} part tells TweakScale to resource anything that's contained part.Resources, so any and all resources are scaled. This should scale Karbonite stuff roughly correctly, I hope: TWEAKSCALEEXPONENTS { name = ORSModuleResourceExtraction extractionRateLandPerTon = 2 extractionRateOceanPerTon = 2 powerConsumptionLand = 2 powerConsumptionOcean = 2 } TWEAKSCALEEXPONENTS { name = USI_ResourceConverter inputList { rate = 3 } outputList { rate = 3 } inputResources { rate = 3 } } TWEAKSCALEEXPONENTS { name = KarboniteGenerator maxOutput = 3 } TWEAKSCALEEXPONENTS { name = ORSModuleAirScoop scoopAir = 2 } I'm gonna give it a spin and see what goes wrong.
  18. The problem isn't really with the configs, but that ModuleEngineConfigs supports multiple configurations. Whenever the configuration changes, TweakScale must be run anew on the ModuleEngineConfigs to update the values. It seems likely this can now be implemented, but there are some delays.
  19. MODULE { name = TweakScale type = KibbalScale MODULE { resources { name = Kibbal amount = 50, 160 maxAmount = 50,160 } } } Please tell me how this works. I expect there to be a bug that refills the tanks when loading.
  20. Do you have an output_log.txt for that? There are in fact three Scale.dll there. So do what Master Tao said, and then delete KSP\Gamedata\MagicSmokeIndustries\Plugins\Scale.dll. Crap, I'm sorry. The small gaps have always been there, at least for some parts (more parts may have gotten them now), and are probably artifacts of the placement of attach nodes. Is this 32-bit or 64 bit KSP? Without an output_log.txt or a craft file it's hard to figure out what's wrong, sadly. And on x64, it can be hard even then. I've been running lots of tests to see what makes KSP x64 crash when I have TweakScale installed alongside many other mods, and I have gotten everything from a semi-consistent crash in a different mod before TweakScale does anything (which goes away if I remove TweakScale), through consistent crashes with horribly inconsistent stack traces, to games that run without a hitch for hours. I've basically concluded that KSP x64 is not really ready for modding yet.
  21. Oh, and I forgot mentioning such things here: 1.32 is out, bringing along KSPAPIExtensions 1.6.3.
  22. I was gonna excuse my tardiness with slow intertubes, but I notice I'm downloading at twice the speed I'm paying for. I'll just shut up and wait.
  23. That sounds like it's a case of an outdated KSPAPIExtensions. Do you have an outdated version of one of these mods installed? Procedural Parts Real Fuels Modular Fuel Tanks Extraplanetary Launchpads Procedural Farings Infernal Robotics Glow Strips Screw that, you have an output_log.txt. Judging from this line: [CompatibilityChecker] Incompatible mods detected: aaa_Toolbar, CrossFeedEnabler, FerramAerospaceResearch, Firespitter, Kethane, KSPAPIExtensions, KSPAPIExtensions You have two outdated copies of KSPAPIExtensions. Furthermore, it's one of these four: MagicSmokeIndustries\Plugins\KSPAPIExtensions.dll NearFuturePropulsion\Plugins\KSPAPIExtensions.dll ProceduralFairings\KSPAPIExtensions.dll TweakScale\plugins\KSPAPIExtensions.dll If you're using TweakScale 1.31, it comes with KSPAPIExtensions 1.6.2.0, which is the newest version. You can try replacing the others with the one from TweakScale, but I'm not 100% sure that will work with no problems. Mind you, KSPAPIExtensions 1.6.2.0 is the newest as of just now, and will be replaced by the 0.24.2 compatible 1.6.3.0 (I think) within the next few hours, if not minutes.
×
×
  • Create New...