Jump to content

icedown

Members
 View Profile  See their activity

  • Posts

    371

  • Joined

  • Last visited

 Content Type 

Everything posted by icedown

  1. icedown
    I need your output_log.txt please. My family member is back in the hospital so it's going to be a few days before I can get it fixed
  2. icedown
    You can do this through action groups or using vessel viewer. The parts list in vessel viewer is a pain to walk through with a big ship though.
  3. icedown
    You might try ship manifest if it is updated. It can do transfers but I'm not sure about while in iva. It might work if it's not the active kerbal
  4. icedown
    He was the first one I went to
  5. icedown
    There is not a DOE patch for this version. I removed it a build or two ago while I clean up some internal code and get stuff working better. After that is complete I'll start adding stuff like DOE back in. There is a patch and other Cacteye versions on CKAN but I have no control over those.
  6. icedown
    Release 1.2.0.9 Compiled against 1.2.0 Restructured GUI for better usability
  7. icedown
    Release 1.2.0.9 Compiled against 1.2.0 Restructured GUI for better usability
  8. icedown
    I am already in contact with them, they have just been busy with the release.
  9. icedown
    I have thought about this approach but it has some issues. Any time I put a kerbal in there it becomes a manned mission while in the IVA. This poses problems with both life support mods and progression checks. I'm waiting to hear back from the devs right now to see if they can suggest a way around this limitation.
  10. icedown
    The 1.2 release will be delayed. I have a family member in the hospital and will not be at home to finish the update for a couple days. I will finish the release as soon as I am able to complete it.
  11. icedown
    @cyberpunkdreams Ok, I've tracked that down the error with the asteroid processor and will have it fixed for the 1.2 release. https://github.com/icedown/CactEye-2/issues/5 For now, I would avoid the asteroid processor. It also causes a lot of lag on my system as well. That's already on the list of to fix along with the new gui for 1.2 The log spam of FileNotFoundException: Could not load file or assembly 'DistantObject, Version=1.7.1.12685, Culture=neutral, PublicKeyToken=null' or one of its dependencies. Is because you still have the DistantObjectHook.dll in your GamedData\CactEye\Plugins directory. You must completely remove any previous version of a mod before upgrading. This was removed in 1.1.3.8 because of compatibility issues.
  12. icedown
    Output Log please, KSPFolder/KSP_x64_Data/output_log.txt That one is missing critical information
  13. icedown
    @cyberpunkdreams I will need the full logs. I need to see where that happened at in the sequence
  14. icedown
    Sadly, at this point I'm not sure if it's possible. I'm trying to find a way but some part of the game is blocking input to the IVA since no kerbals are on board. Still trying to find a way around this. I'm going to keep trying until I find out for sure one way or another.
  15. icedown
    Need your output log please
  16. icedown
    I did not, I'll incorporate that once I get the interface working. It doesn't play well with the ALCOR mfds at the moment, apparently their rotation and scaling is off.
  17. icedown
    I'm working on getting ProbeControlRoom mod back going. I have the IVA showing up and RPM appears to be working fine. MOARdV thought it might be the update rate of RPM but there are monitors that are ticking along just fine showing vessel name and MET clock. I think it's a matter of it doesn't actually recognize that its a controllable IVA without a kerbal present. The main reason I think this is because the UI groups that should hide on entering an IVA don't. Also while in an IVA, if you right click, the mouse pointer disappears and allows mouse view control, in PCR you have to right click and hold to look around and the pointer just changes to a green color. I don't think it's actually triggering the IVA setup that allows mouse events to be passed to RPM. I might be able to make it work by sticking a kerbal in there but then it would no longer be an unmanned mission while in IVA. I'm not sure the sequence that a normal IVA goes through while being setup. I've been searching through the documentation and trying all kinds of functions for a while now. Does anyone have any suggestions about a direction I need to look or something I might be missing?
  18. icedown
    It does, sort of. None of the screens are responding to input yet. Something has changed with the IVA controls, still trying to figure that out. I think it doesn't like going IVA without kerbals on board any more since it's not triggering the collapse of UI groups that should collapse on IVA. I have messaged the current owner to see if he doesn't mind me taking it over if he does not wish to continue. If I get it up and running before I here back from him, I will probably start a continued version. If he wishes to continue, I'll simply submit it as pull requests.
  19. icedown
    Oh, nothing as nice as them. I don't think Jeb is quite that friendly with parts
  20. icedown
    A functioning copy is available at the github link if you want to look at it. Do you have any suggestions of how I might remedy this? I really liked this mod and would like to get it back working. https://github.com/icedown/KSP-ProbeControlRoom
  21. icedown
    Random events like staging, activating actions with increasing probability as stupidity factor of crew, as noted by the highest value, increases.
  22. icedown
    Grabbed the logfile of my other project, here is the correct one. output_log.txt I started up, went to the control room, tried to click things, then went to a nearby mk2 cockpit with the aset props and moved some stuff in it. EDIT: I see the error now, [Error]: RasterPropMonitorComputer: UpdateLocalCrew() - no internal model! What function should I create the internal model in to get ahead of that check?
  23. icedown
    Logs are attached but I couldn't find anything unusual in them. I figure its an api change but I've spent the last 2 days going through the docs and haven't found anything yet. Just looking for ideas of something I haven't look at. output_log.txt
  24. icedown
    I'm trying to get Probe Control Room updated and working. I've got the IVA showing up and all the MFDs have been converted to ALCOR ones. The only problem I'm having is none of the buttons are working. Lights and animations work fine. Besides the buttons not working, the only other odd thing I've noticed is that the nav ball and altitude tape are still there unlike in other IVAs. Do you have any idea what might have changed to cause this? I've been looking through the forums and documentation but this is a bit of a special case since it's an IVA without a kerbal. I think it looks like it's activating the IVA but the mode isn't changing correctly.
  25. icedown
    Might be working on a new project
×
×
  • Create New...