Jump to content

JPLRepo

KSP2 Alumni
 View Profile  See their activity

  • Posts

    3,142

  • Joined

  • Last visited

 Content Type 

Everything posted by JPLRepo

  1. JPLRepo
    Sorry are you saying changes to the AmpYear settings in the Space Center are not saved when you click save and exit?
  2. JPLRepo
    I will do a quick fix then. Can't say if it will be today or tomorrow or the next. Pretty busy with real life work this week. But before the weekend for sure.
  3. JPLRepo
    I have a fix already... as a work-around... I wanted to completely re-do the code.. but if this is causing people enough issues I'll look to do a quick patch fix release in the next day or two. Thanks for the ideas, pretty similar to what I was thinking.. Except Step 3 is further expanded depending on how far away the body is with further scanning and picture taking contracts that gradually reveal the details of the body (progressive textures) I'm thinking of introducing these and using the telescope in this mod along with TST telescopes, DMOS scanners, SCANsat, etc to gradually reveal more details of the body. This could all be driven by a contracts system.. I'm looking for any more ideas from others? Now's your chance to offer suggestions.
  4. JPLRepo
    Thanks for doing that... Ironic I was working my way through the code just 2 days ago? marking it all up with comments so I figure out what is going on in the code. Then I plan to re-write and standardize as much of it as possible. Already found a number of areas for improvement. Of course, this doesn't help getting a quick fix out for issues like this. This issue is being caused by ResearchBodies scanning the Offered Contracts list looking for Contracts offerred for CelestialBodies that are yet to be discovered and Declining them. Two things with this:- 1) In programming terms it is iterating a list that could change whilst it is doing so.... Which is what causes your error above... The Contracts List changed whilst it was working through the list. So this should be fixed. 2) It actually declines any contracts it finds - which as I understand it means you take a reputation hit depending on your game settings. It would be better if they were withdrawn, or even better yet, never got generated in the first place. So I am exploring both of these in my code re-vamp. As I don't know how long it's going to take me to work through the code (probably a couple of weeks given how time poor I am at the moment with real life work) if you get this error a restart of KSP should resolve it... Upon restart check the contracts offerred, or if Mission Control is still bugged out bring up the Debug window ALT-F12 and go through the contracts, re-generate, delete contracts until it starts working again.
  5. JPLRepo
    Sounds like it should stay the way it is. It also needs electrical air RCS thrusters... Not sure how they work, I assume only in atmosphere. And it sounds like it needs four DeepFreeze Cryopods.
  6. JPLRepo
    Post a pic of you colliders and model from unity editor
  7. JPLRepo
    @rasta013 as @nightingale said if you can raise issue two on my ResearchBodies thread please. I just took over this mod a few weeks ago and I was just looking at the code yesterday on this particular item thinking this was a time bomb waiting to go off. I'll have to fix it up and put out a new release.
  8. JPLRepo
    When you click an entry a Save button should appear at the bottom of the page? Yeah annoying it's at the bottom and the undo is under the field. @tomf - can this button be moved? and any progress on the XML extract?
  9. JPLRepo
    have you looked at kerbalEVA.fsm.CurrentState and CurrentStateName to get the FSM state machine state?
  10. JPLRepo
    I don't think that was the question. The question was why does the Ranger only have liquid fuel whilst the lander and endurance use liquid fuel and oxidizer. (and they all use EC as well) The Ranger's build in VTOL engine uses Liquid Fuel and Oxidizer. The "cooper" engine that goes on the back of the Ranger however does not. In Air mode it is configured to use LiquidFuel IntakeAir and ElectricCharge. In Closed mode it is configured to use LiquidFuel and ElectricCharge. Why is this? I have no idea, an oversight by the original author? or that's the way he wanted it. So the question is do people think the "Cooper" should use LiquidFuel, Oxidizer and ElectricCharge in Closed mode? I can make the necessary changes.
  11. JPLRepo
    Thanks for confirming why I think this mod isn't a huge hit/success, and why I have plans to reinvigerate it. What I meant was what game play mechanics do people want to see with regard to first discovering the bodies and then researching them? Certainly I can make it all contract based. But I was looking for ideas and inputs from the users of this mod.
  12. JPLRepo
    Very well, then I guess we release what we have and see what people think on the performance-side. I could make it non-click-through. I actually need to convert it all over to the Unity 5 GUI system, but that is a lot of work. But I'll see if I can do a quick fix for this version. the ION RCS is, as far as EC read-outs... do you mean not supported by the Emergency Shutdown Processing system? - That's just because I didn't get around to doing those parts. I'll see if I can before the next release. EDIT: Making some more performance improvements before release. Just in case. Click-through fixed for next release. ION RCS ESP processing support added for next release.
  13. JPLRepo
    To elaborate a bit more, for others who might stumble onto this and I was on my phone before. Yes you can offset the Internal as follows: INTERNAL { name = landerCabinInternal offset = x,y,z } where the Offset is from the pivot point of the External Part model that it is attached to.
  14. JPLRepo
    You can just add an Offset=X,y,z to the internal definition you have above
  15. JPLRepo
    Is anyone able to confirm whether the DEV version I posted a few days ago has improved performance on large part vessels?
  16. JPLRepo
    What do people think about development of the discovery and research functions of this mod? Specifically. I have my own ideas, such as timing factors / like scanning to progressively discover and research a body (instead of just clicking a button over and over as you do now) tied in with contracts..
  17. JPLRepo
    Now how did I miss that. @xEvilReeperx thanks for that pick-up. I'll work to develop what I need from that. Thanks again.
  18. JPLRepo
    Thanks... I will fix in next version. I missed this as ARP is still not available in KSP 1.1+ so actually missing this means nothing without that mod.
  19. JPLRepo
    Sorry I misunderstood. My idea is to use ResearchBodies to progressively discover and reveal the details of each Celestial Body. To do this you would use TST telescopes, DMagic OS scanners and ScanSAT scanners to reveal the details of each Body. @DMagic mentioned here potentially some starting point /codebase for it. I'm waiting for him to respond to a PM.
  20. JPLRepo
    No there isn't currently. You have to set it for each vessel. - and it does not save this setting currently in the release version (1.3) but it does in the latest dev version (1.3.1.1). Raise a request/issue on GitHub and it will get into the queue.
  21. JPLRepo
    Hoping for some help again from the expert... @xEvilReeperx Seems in 1.1+ this doesn't work any more. Investigations I have conducted so far appears the FakeCallback is not being called... and the subtree.science.OnDeploy() is... The AwardCompletion() is being called before GameEvent.OnScienceReceived is fired as it always has. A debug run sees the OnStow removes the callback for ProgressTracker from the GameEvents list and the FakeCallback and OnDeply re-adding. but something isn't right. I'll keep trying to figure it out. On the surface has the GameEvents order changed?
  22. JPLRepo
    Yeah sorry... you have to change the part names as well. as per above.
  23. JPLRepo
    Yeah sorry.... If I had the time to figure out the new KSP 1.1+ upgrade API I could have written one to upgrade your saves for you... But time is my enemy. If you want to upgrade craft or save files that had the parts when they were part of AmpYear you have to go manually edit the .craft and persistent.sfs files manually:- Change ModuleAmpYearPPTRCS to ModulePPTPoweredRCS Change ModuleAmpYearPoweredRCS to ModuleIONPoweredRCS Capatilisation is critical. but if you just do a change all the vessle/craft / parts will function as before.
  24. JPLRepo
    That's the plan. Waiting for @DMagic to get back to me.
  25. JPLRepo
    I don't see how this is related to AmpYear at all.... Your error is with a failure in NFT NearFuturePropulsion.VariableISPEngine.OnUpdate () That is not an AmpYear module. And I don't see how AmpYear would be causing this as AmpYear does NOT change the values of ANY variables on any Mods. All it does is READ those values. Tell me, if you remove AmpYear does the null reference error in your log go away? I would be surprised if it does. If it does I will look into it further because that would be incredible. I noticed in your report AmpYear incorrectly reporting the EC usage of that engine. But that does not surprise me at all, given AmpYear does not support it. AmpYear currently only supports (IE: READS values) from the NFT Electrical and NFT solar packs and I believe this engine is part of the NFT Propulsion pack? Yes? I am not sure on that because I've never actually played or used these packs myself. Any update on whether version 1.3.1.1 improves things?
×
×
  • Create New...