Jump to content

Deimos Rast

Members
  • Posts

    1,392
  • Joined

  • Last visited

Posts posted by Deimos Rast

  1. On 9/13/2018 at 8:04 PM, linuxgurugamer said:

    New release, 0.11.15

    • Added ANY_Engine, to deactivate all engines, or activate all engines in current stage

    Problemo: So I can shut down all engines, but the "activate all engines in current stage" doesn't seem to work. Activating/deactivating the engine normally works fine. 

    Craft is just a short hopper, only engine is a 909. No errors in log.

    Also, does this mod respect RemoteTech? I'm in a crewed capsule, but it doesn't have connection at the moment.

     

     

     

    Otherwise, I'm really liking the mod - its usage with the Science Container is great - I had previously be making action groups to Perform All, Collect All, and Reset All, which was a hassle.

    Ideas  - Parachutes? Decouplers? Not sure if they're the greatest ideas, but it could be useful for a lazy man's "Abort" but I'd understand it if it was a bit far afield. Maybe to be implemented like the engines "activate all x in current stage" - but then I suppose you could just stage them instead... :/

     

    EDIT

    Also - "Deactivate all SAS" = "Deactivate all RW" ...

  2. 5 hours ago, Puppy_The_Pup said:

    How do i make stuff happen more often? for all parts? is there any easy way?

    Also is this incompatible With Kerbal Launch Failure?

    check settings > MTBF multiplier (Mean Time Between Failure). Lower it.

    2nd question: seeing as LGG maintains both mods, they are probably compatible. But my understanding is they work on different levels.

    --------------------------

    @linuxgurugamer

    If you do go with TestFlight, you'll be entering the Realm of RO. Thar be dragons! Also, if you have Kerbal Launch Failures, DangIt and TestFlight, people will start calling you the "King of Failures.":D (I thought that was funny. No? Bah.)

    But why I'm here: Your blacklist is currently only for resources. Any chance it could be extended to parts and/or modules? I'm using the Surface Experiment Package mod, and it has parts with batteries and such, which DangIt currently targets. But the parts need to run (at least in the background) for months at a time, and I'm thinking that's a guaranteed failure waiting to happen. The mod has unique/proprietary modules (for most parts), so it'd be easy to except the parts by module if you go that route, but being able to do it by part specific means wouldn't be half bad either.

    Is it also possible to make a MM patch to add things to the blacklist?

    Cheers.

  3. 3 hours ago, StahnAileron said:

    I actually tried that. Didn't change anything. Still got flung out like a slingshot. I think when this mod got "updated" to 1.0.5, the models weren't thoroughly tested or something. If I recall, 1.0.5 mandated convex- or concave-only (forgot which) collision meshes or something. I recall the author of another mod recounting how that broke several of his parts. Fixing them made the models more complex. I don't recall problems with the KANDLE in 1.0.4, which I think was when I first found and used this mod.

    If so, much like the thermal jet, it's an inherent model issue. Someone would have to take a look at the models and fix them. It's not a config issue. (I love the KANDLE. This is partly because I like making small, compact satellites and probes that can be launched via 1.25m lifters or Mk2 profile SSTO Spaceplanes.)

    Bummer. Saves me from making a patch though. I know what you mean about the concave/convex collider issue - run into it a bit here and there with the older mods. Safest to delete the fairing then I guess.

    Is it the only engine that does that?

    I opened a github issue about the engine troubles we discussed though. Not much more I can do really.:(

    Thanks for mentioning it.

  4. 4 hours ago, StahnAileron said:

    I don't think the exhaust nozzle is supposed to look like that. If you go by the image in the OP, it should be a smooth, round nozzle like you'd see on a typical jet engine/fighter plane. There shouldn't be any "fins". Something is up with the model. I imagine something got lost/changed between 1.0.5's model handling and 1.2's.

    BTW, did anyone else suffer explosive ejection of the KANDLE's fairing? (The RTG NTR engine.) I know in 1.0.5 I always had to disable it's fairing. If I didn't, it'd get violently ejected when I staged/decoupled. It also apparently solid: I've had it knock solar panels off my satellites. (This is why I need to disable the fairings.)

    yeah, you're right, looks like it got turned inside out or something. Not the end of the world, but I don't know how to fix it. I could remove the animate with throttle effect though, but meh.

    Regarding the fairing, there are a few options: delete it or change the ejection force to zero (it'd still have mass/be solid probably, but wouldn't go flying). I can't say this is something I ran into though. I could also add something to the description to the effect of "do not aim at face when staging.":D

  5. 15 hours ago, Tau137 said:

    Nice, thank you!  I will test how this works (w/ Kerbal Atomics/NFE custom patch)...

    EDIT:  Everything seems to work fine in stock (thank you again!).... NFE/KerbalAtomics, although extremely cool and somewhat realistic, is still bugged beyond belief and not usable in career.. Damn, do I really have no other option but to move to the fantasy land of Karbonite+?

    P.S. Anyone capable of working on 3d model, please fix the NuclearTurboJet throttle animation.

     

    what's wrong with the turbo jet animation? It worked fine for me (the fins at the back dilate with throttle).

    Also, and I know this isn't the right thread for it, but what's wrong with NFE/Kerbal Atomics (as far as bugs go)?

    EDIT: this is what the throttle animation looks like for me.

  6. 49 minutes ago, LeLeon said:

    Yeah base configs! When i see my last module manager starts with 12000 patches, every mod without additional patches is welcome.

    I just know github from fork-side, but i don't wanna miss this. Comfortable as hell. So you need help in any way? I'm career player, so balance is important to me.

    you must love my updates then:D

    I used to always do base configs, but have switched to doing patches, and am sort of switching back to base configs. I actually discussed this with LGG before re-releasing RLA, and his advice (given his experience with KW) was to do base configs.

  7. Possible bug report:

    • Battery short circuited. Expected behavior.
    • Alarm sounded briefly, then stopped. Expected behavior.
    • Every time I switch to the map mode and back to the flight scene, the alarm plays again. Unexpected behavior.

    I suppose I could just disable the alarms completely (I can do that right?).

  8. On 11/16/2016 at 1:48 PM, ArkaelDren said:

    Holy crap I'm so happy to see this again.  WHERES ALL THE SUPPORT Community???  This is one of the legendary packs from days gone by.  Show some love and hope and maybe Raider will get this up to speed for 1.2.1.

    Thx Raider

    From Oregon, Dren

    you're part of this community too, fyi

  9. I just downloaded the latest and I'm unable to respawn Valentina;.;.

    Error:  in RosterListViewer.  Error:  Object reference not set to an instance of an object 
    
      at ShipManifest.SMVessel.FindPartByKerbal (.ProtoCrewMember pKerbal) [0x00000] in <filename unknown>:0 
      at ShipManifest.Windows.WindowRoster.DisplayRosterListViewer () [0x00000] in <filename unknown>:0 

    Full log here if curious (SM log).

     

  10. NullReferenceException: Object reference not set to an instance of an object
      at FlightPlan.FlightPlan.BuildFlightPlan (.Vessel vessel) [0x00000] in <filename unknown>:0 
      at FlightPlan.FlightPlan.Update () [0x00000] in <filename unknown>:0 
     
    (Filename:  Line: -1)

    Seeing this non-stop on vessel launch. Just started a new game. Maybe because I don't have the tracking station upgraded yet, no idea?

  11. On 11/13/2016 at 10:35 PM, Justicier said:

    That is how I had it set up before. No sounds worked at all. From what I have seen, MODULE,0 works for a single module file. Multi-module files work starting with MODULE,1 and so on. Setting the code to MODULE,0 still has no effect on the particle emitter, it still is at full emission regardless of engine state.

    that's because Module,0 references the Multi-Modal engine module in the RAPIER engine, whereas Module,1 is the first ModuleEnginesFX; 2 being the second engine.

  12. 8 hours ago, PocketBrotector said:

    Is anyone else experiencing the 2.5m separator go missing here? Doesn't appear in my VAB even in sandbox mode. A quick look at the config suggests that the mesh is being simply removed rather than replaced.

    config looks fine, the % acts as an "add if absent or override if present" function, so it's inserting the model node. A model loading error should show in the log.

     

    you planning on dusting off this mod? would be nice to see all of hoojiwana's stuff updated. This would require next to no work probably (all I saw was default action groups to be added).

    really wish this pack was bigger though:(

  13. 29 minutes ago, Starwaster said:

    I haven't found the centrifuge to be reliable in 1.2 at all, given that it causes me crashes. I have no idea why it works for you and not me. In fact, given that you reported no problems without the patch, I'm not sure what it would be good for?

    other people who do have issues with it might benefit, if they decide to use the part.

×
×
  • Create New...