MisterBennock

Members
  • Content Count

    40
  • Joined

  • Last visited

Community Reputation

15 Good

About MisterBennock

  • Rank
    Rocketeer

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. On imgur? I already got a comment there. And here I pasted the album code into the form. Anyways, here's the link: https://imgur.com/a/R02qP9s
  2. I just want to post an imgur album. I used the album post function, but it doesn't seem to work.
  3. Good day. Since there is an official VTOL thread, but no dedicated STOL thread (or at least not a more recent one, or me not looking hard enough), I thought it would be nice to discuss small, cute planes that can take off and land at low speeds. Mainly because in the last days, I tinkered a bit with these kind of planes. Some of you might know the Fieseler "Storch", a plane used by the Luftwaffe in WW2 as recon machine and by many other organizations since then because it can take off at around 50 km/h (which is like 16-17 m/s) and land at zero with wind blowing against it. I tried building a similar small and light plane and got this "glider" from it. It takes off by itself at almost exactly 30 m/s, has a range of around 270 km (triple that with drop tanks), a top speed of around 135 m/s if you go all out at a height of around 7 km (didn't try going higher) and has very calm and forgiving flight characteristics. It is basically 100% "stock", I just used the struts from Ven's Stock Part Revamp to lower part count (I once made a similar ultralight SSTO with around 40 of the cubic struts). Also, I realized how ugly the stock wings are and how lacking they are in every regard. The second one is basically just a turbine with canards. It can take off at around 12 m/s, but flying it requires a steady hand. https://imgur.com/a/R02qP9s Feel free to post and discuss your creations.
  4. Okay, well, love me, I found the mistake. Check the comment in the faulty patch $PART[dockingPort1] { %name = stageshield %node_stack_top = 0.0, 0.2828832, 0.0, 0.0, 1.0, 0.0, 1 %title = SSDP %description = Invented after a peaceful protest against the lack of spacecraft attachment systems turned violent, the Clamp-O-Tron Docking Port allows for the firm attachment of two separate vessels. After docking, vessels can be just as easily undocked. The Shielded version has deployable fins to protect the port during ascent. This one is also stageable. %attachRules = 1,1,1,1,0 %MODULE[ModuleDockingNode] { %referenceAttachNode = top !staged = False { //WHY IS THIS OPEN?!?!??! } Yeah, so it was just an open bracket instead of a closed one. With a closed one it works as it should. I really hate programming of any kind. Anyways, for the other problem, I was thinking of maybe having the shielded docking port open by default. Don't how how I will do this now, though.
  5. Hi genericeventhandler, yes, I just edited the attachment nodes. Thanks for your help, I now made this patch: @PART[dockingPort1] { node_stack_top = 0.0, 0.2828832, 0.0, 0.0, 1.0, 0.0, 1 @description = Invented after a peaceful protest against the lack of spacecraft attachment systems turned violent, the Clamp-O-Tron Docking Port allows for the firm attachment of two separate vessels. After docking, vessels can be just as easily undocked. The Shielded version has deployable fins to protect the port during ascent. This one is also stageable. @attachRules = 1,1,1,1,0 @MODULE[ModuleDockingNode] { referenceAttachNode = top !staged = False { } It should simply change the docking port nodes like it did with the "full" part. However, it doesn't and I have no idea why.
  6. Hello people, I present you an attempt of mine to make the Clamp-O-Tron docking port stageable by giving it the ability to have something attached to the port. Currently, though, I have two problems: 1. I have changed the complete part cfg, but I think it should be possible by just applying a MM patch to it. 2. It is possible to attach to the closed shield. Of course that's stupid and immersion breaking - does anybody know whether it is possible to only attach it to the closed shield? Or is that outside of the editor capabilities? This is the code, I basically just copied some parts from the regular docking port to the shielded one's: PART { name = dockingPortX module = Part author = MBennock mesh = model.mu rescaleFactor = 1 node_stack_top = 0.0, 0.2828832, 0.0, 0.0, 1.0, 0.0, 1 node_stack_bottom = 0.0, -0.005308203, 0.0, 0.0, -1.0, 0.0, 1 node_attach = 0.0, -0.005308203, 0.0, 0.0, -1.0, 0.0, 1 TechRequired = advMetalworks entryCost = 8400 cost = 400 category = Utility subcategory = 0 title = Shielded Docking Port description = This one can be used opened. Yeah, you heard right. OPENED! attachRules = 1,1,1,1,0 mass = 0.1 dragModelType = default maximum_drag = 0.25 minimum_drag = 0.25 angularDrag = 0.5 crashTolerance = 10 maxTemp = 2600 // = 3400 thermalMassModifier = 6.0 // like a nose cone emissiveConstant = 0.8 bulkheadProfiles = size1 tags = berth capture connect couple dock fasten join moor shield socket stagingIcon = DECOUPLER_VERT MODULE { name = ModuleDockingNode deployAnimationController = 1 referenceAttachNode = top nodeType = size1 stagingEnabled = False } MODULE { name = ModuleAnimateGeneric animationName = dockingring actionGUIName = Toggle Shield startEventGUIName = Open Shield endEventGUIName = Close Shield allowAnimationWhileShielded = False } }
  7. Hey man, very nice mod! I like it, finally something with an inclination that is still stock. Just a question: Do you have any data on the atmospheres? Or are they the same size as stock?
  8. Wow Dlucks, that thing looks wicked! This is my recent (.90) space station concept. The "Limes" type station, for usage as outpost/"welcome station" on the border of a body's SoI. It is put into space in one long piece and either sent to its destination and assembled or assembled and sent to its destination. Unfortunately, due to several technical difficulties I couldn't execute the whole thing as I wanted to - the pictures are merely from a test assembly in LKO. Let's hope it works better when I recreate it in 1.0.2. Basically it consists of three mainly identical parts that have different functions assigned to them. There is a command module, a comms module and an energy module. It has no fuel of its own besides some RCS for orbital housekeeping. It has, however, several docking ports so if needed it can be expanded with additional tanks etc. The most difficult task was to dock the modules properly, so I decided to make life easier by putting IR parts on the tubes to be able to rotate the modules against each other when needed (which didn't work out quite as expected, technical difficulties....). I think if I can get this thing to work as intended, it will be awesome!
  9. No, he meant the windows user account. But it's not that, either. I have the same problem, running an admin account, full permissions, saving the .cfg, re-opening it to see whether changes have been saved (they did), starting the game, setting reset. Every time, since the 1.0.2 update, full vanilla. Win7 x64.
  10. Been there, done that. Running KSP.exe as administator, have all permissions. Still resets.
  11. Yes, I have this issue too - since today. At first I though it might have to do with some updates and newly installed mods, but even after uninstalling from Steam and reinstalling, it keeps happening - with a 100% vanilla install. Edit: System is Win7 x64. No issues of that kind since 0.18.
  12. Yes, I am pretty sure - I mean, stock sensors work, seismic scan on sensor package works, just not the other behind/below. Here is the cfg of the B9 sensor package: MODULE { name = ModuleEnviroSensor sensorType = ACC } MODULE { name = ModuleScienceExperiment experimentID = seismicScan experimentActionName = Log Seismic Data resetActionName = Delete Data useStaging = False useActionGroups = True hideUIwhenUnavailable = False xmitDataScalar = 0.45 dataIsCollectable = True collectActionName = Take Data interactionRange = 1.2 rerunnable = True } MODULE { name = ModuleEnviroSensor sensorType = PRES } MODULE { name = ModuleScienceExperiment experimentID = barometerScan experimentActionName = Log Pressure Data resetActionName = Delete Data useStaging = False useActionGroups = True hideUIwhenUnavailable = False xmitDataScalar = 0.5 dataIsCollectable = True collectActionName = Take Data interactionRange = 1.2 rerunnable = True } MODULE { name = ModuleEnviroSensor sensorType = GRAV } MODULE { name = ModuleScienceExperiment experimentID = gravityScan experimentActionName = Log Gravity Data resetActionName = Delete Data useStaging = False useActionGroups = True hideUIwhenUnavailable = False xmitDataScalar = 0.4 dataIsCollectable = True collectActionName = Take Data interactionRange = 1.2 rerunnable = True } MODULE { name = ModuleEnviroSensor sensorType = TEMP } MODULE { name = ModuleScienceExperiment experimentID = temperatureScan experimentActionName = Log Temperature resetActionName = Delete Data useStaging = False useActionGroups = True hideUIwhenUnavailable = False xmitDataScalar = 0.5 dataIsCollectable = True collectActionName = Take Data interactionRange = 1.2 rerunnable = True } Now compare to the stock sensor: MODULE { name = ModuleEnviroSensor sensorType = ACC } MODULE { name = ModuleScienceExperiment experimentID = seismicScan experimentActionName = Log Seismic Data resetActionName = Delete Data useStaging = False useActionGroups = True hideUIwhenUnavailable = False xmitDataScalar = 0.45 dataIsCollectable = True collectActionName = Take Data interactionRange = 1.2 rerunnable = True } As you see, they are identical. And since every stock sensor works for itself and since in the package only the first sensor works, I really assume it has something to do with how often the "xmitDataScalar" line is changed, in that case apparently only once. Edit: I just found out that you can find keys and nodes. Now my cfg looks like this: @PART [*]:HAS[@MODULE[ModuleEnviroSensor],@MODULE[ModuleScienceExperiment]]:Final { @MODULE[ModuleScienceExperiment],* { @xmitDataScalar,* = 1 } } As you can see, I am finding all "ModuleScienceExperiment" in the file and then edit all the "xmitDataScalar". Probably wouldn't even be needed, but hey, it's just two characters AND IT WORKS! YEAAAHAW! :D:D
  13. No, I meant the "xmitDataScalar" parameter is contained in the ScienceExperiment module, not the EnviroSensor module, which is why I apparently need to address the Experiment. The ModuleEnviroSensor is just for filtering for sensors. Also, I just tried it and it still didn't work. Also, I just tried the changerd version, but it still doesn't work out completely... I get 100% transmission on the seismic data ONLY somehow - even though all is contained in one sensor package. Strange, strange things. Edit: Perhaps it could be because it only applies the patch once? Since the seismic scan is also the first in the part's cfg - what if it stops there?
  14. @*Aqua* - thanks for the insight, that was useful. Changed things accordingly I had to use the ModuleScienceExperiment since the "xmitDataScalar" part is contained in it, so in order to apply it I have to include it. I think I even tried it first with ModuleEnviroSensor only, but it didn't work.