Jump to content

linuxgurugamer

Bug Hunter
 View Profile  See their activity

  • Posts

    24,965

  • Joined

  • Last visited

 Content Type 

Everything posted by linuxgurugamer

  1. linuxgurugamer
    Sure, source would be nice
  2. linuxgurugamer
    Thank you !!!!! Have I told you how much I love this mod?
  3. linuxgurugamer
    @Angel-125 Any chance of getting a .version file in the next release? Would make it a bit easier to know when a new version is out.
  4. linuxgurugamer
    Are you aware that it apparently already does logging to the KSP log? Not sure if it's useful. I'm only looking at the source, not near my dev system right now
  5. linuxgurugamer
    How do you test this in US2?
  6. linuxgurugamer
    Definitely going to be e keeping an eye on this. But, you should definitely make explosions optional. I would do it so that an engineer has a decreasing chance of repairing something. But another engineer's attempt wouldnt/should not be affected by any previous attempts.
  7. linuxgurugamer
    Ok. So I'll look into adding that. I think I'll do it something like this: Config file to enable/disable each of the following optional items Each of the following items will be optional: Write all desired values to a file for instant monitoring. This file will get overwritten every time Append values to a log file for long-term review. This line will have a date/timestamp Write data to KSP log
  8. linuxgurugamer
    Thank you Your initial comment was about an ips to an external logging system. I stil think it would be overkill. The amount of IO at 4x a sec really isnt that much. This is a case of keeping it simple to implement. Log file (any, not just to the KSP/Unity log) is trivial. Im not familiat with Windows monitors, but I wrote a mod a while ago called KSPLogger, which writes certain values to a file multiple times a sec. This was for a streamer. It works well, and no noticible impact on stream
  9. linuxgurugamer
    Umm, the disk IO would be minimal compared to everything else. And it's a LOT simpler to add a bit of logging code than to implement IPC. In fact, why would it need to be in a separate file? Why not let Unity handle the io, and just let GC Monitor write to the standard Unity log file? That would then eliminate the need to match up different log files, and it's very easy to pull out specific things from a log file using a filter such as grep. I mean, I can easily add the logging and have it write to the log file, AND I can have that start immediately
  10. linuxgurugamer
    One thing that would make me very happy is a IPC call between GC Monitor and some external logging tool (something as kRPC). I'm pretty confident that cross-referencing KSP.log, Player.log and this log would help to diagnose some mysterious "Unplanned Instant Application Closures". Ksp.log and player log contain the same info, one just has more than the other. Would be very easy to have GC Monitor write to it's own log file, no need for any IPC calls
  11. linuxgurugamer
    I think I know what's going on with the rings Got the rings working. I need to reorganize the mod and will then release a beta.
  12. linuxgurugamer
    I think I know what's going on with the rings What is the Instantiator?
  13. linuxgurugamer
    That makes sense. I'm trying to get this working in the current version of Ksp. So far it is working but the rings are all black. Right now it's running on a long term test to see if it is stable.
  14. linuxgurugamer
    What DLLs? And, unless there is something not visible from the web page, you can certainly rebuild and redistribute. So I looked at the mod, and it doesn't have any code. So anyone can revive this for 1.4.3, as long as they stay within the license; ie: No Commercial etc.
  15. linuxgurugamer
    Adding functionality to a probe core won't help. People will still have the parts there. Modders don't make parts for nothing. Parts have a reason for being
  16. linuxgurugamer
    In my signature: Read this BEFORE asking for support: http://forum.kerbalspaceprogram.com/index.php?/topic/83212-how-to-get-support-read-first/
  17. linuxgurugamer
    Sorry, I read it too quickly. I didn't realize how old the previous post was You are correct, and @icedown did reply above.
  18. linuxgurugamer
    1.4.3 is , IMHO, much more stable than 1.3.0 Regarding the other question, it's been well proven that it is not spyware.
  19. linuxgurugamer
    Just an FYI, last night I did a stream where I compared all the science management mods. The tests were done on 1.4.3, and all the mods were installed using CKAN, and listed as 1.4.3 compatible. I found that two of them generated nullrefs and were not working: The offenders were: ForScience AutomatedScienceSampler
  20. linuxgurugamer
    Well, _something_ was keeping it open, but probably not related to the cause of the crash. I've seen that before (files being kept openh)
  21. linuxgurugamer
    Ummm, I'm currently maintaining 3 science management mods, and believe me, they are not forks from one origin
  22. linuxgurugamer
    then reboot
  23. linuxgurugamer
    UMmmm, really? Can't you read the post just before yours?
  24. linuxgurugamer
    That would indicate that it was still in memory, probably waiting for you to click an OK button
  25. linuxgurugamer
    Actually, the current version works in both 1.3.1 and 1.4.x
×
×
  • Create New...