Jump to content

Nereid

Members
  • Posts

    1,043
  • Joined

  • Last visited

Everything posted by Nereid

  1. Fixed. Unfortunately the scaling of the gauge seems to be broken and the new 200% scale isn't working, too. Maybe I can fix this at the weekend; if not it will take a week. The gauge scaling is fixed in 1.1.11-2274
  2. Well, its a very low priority issue. The hotkey was added for those who had problems with blizzys toolbar a long time ago. There was no stock toolbar and so FF was not acessable for them. ALT-F had fixed this as a workaround.
  3. I know this happens so some. But I never had any chance to reproduce this. It should be a chord. Dunno why it wont work for some. It must be some kind of timing problem I still do not understand.
  4. Thank you, but I already have solved this. Fixing it was a little complicated (but not that much at the end) and I have not tested all gauges yet. But I will test them today and release it tomorrow, if I won't find any new bugs.
  5. Thisa may be a bug. You can turn it off by holding down the hotkey (RIGHT-CTRL) and clicking the red X. But you cannot turn it on again then if the buttonb in the config is missing. I will check this. Confirmed. Fixed in the next release (hopefully tomorrow). This should not be very difficult in general. But a generic approch is not that easy. I can test RF myself and see how many in there. If there are to many, I need a list of the important ones.
  6. It doesn't support RSS directly but it can be made to (if RSS has unique names for celestial bodies). Just take a look in the planet packs and create your own or ask the author of RSS if tehre is a planet pack for FF available.
  7. I can now reproduce the reported issue and I know what is causing this. The good news: 99% of all vessels should not be affected by this. But if you design vessels in a specifc way KSP 1.1.x seems to be crazy about it, if NG is installed... EDIT: I'm still not able to create such vessels provided by CobaltMongoose myself. If I design a vessel, it works every time even with NG installed. I have tried it but even if I just change the vessel from CobalMongoose a bit, it works... Anyway... I will try to find a way around it.
  8. The description is stored in the persistence file. You may just lose it, if I decide to remove that ribbon (or if you revert to a save before you changed the desciption). This had happened only once (as a request of SmarterThanMe).
  9. If it stay in the save and you delete Final Frontier it remains in the save but get completely ignored. You can edit your save and remove it, but there should be not much of an issue if you do not. Maybe loading the game takes a second (or a few) longer, because of the remaining data. Because of the way KSP handles save/load now, the data has to be stored in the persistence file.
  10. I'm investigating the reported issue. It seems some of my changes for 1.1.0/1.1.2 caused this. NG scans the active vessel if it get changed (by staging or a collision) and in this case the scan takes up to 1200 ms. In my tests (with smaller vessels but looping the scan) it takes way less than 1 ms. EDIT: Not caused by the vessel scans (caused by the vessel scans but in an unexpected way) Two options: I will make the scans (and some gauges) optional and/or optimize the scan. This will take one day or two. Until then: don't use NG with larger vessels (which a lot of parts). (no need for this at all) Still not clear what is causing this... And the really bad news: It won't happen on my system at all. Even with vessels containing nearly 700 parts.
  11. I need a save to solve this. I will send you a mail address.
  12. A minor update: 1.0.4-2216 New First-Kerbal-In-Space and First-EVA-In-Space ribbons graphics by SmarfterThanMe Configurable hotkey 1.0.5-2223 correct URL download for KSP-AVC (thanks to Jacke for reporting)
  13. Now I understand your problem. But there is a simple solution to it: Just hide all gauges by the keyboard shortcut: Numlock; or RCTRL-TAB or RCTRL-DEL (which conflicts with a default key unfortunately). Pressing the key again will unhide all gauges of course.
  14. Well.... I was just about to release an updated version compiled against KSP 1.1.1 and now KSP 1.1.2 is available....
  15. My favorite game is still EU4; but I will give HoI4 a try, too.
  16. Updated to 1.1.1-2151 Updated to 1.1.3-2163 Updated to 1.1.4-2168 (Altimeter fixed)
  17. You can change all positions by dragging the gauges. If you leave KSP via the main menu or by saving the positions in the config menu of NG, they will appear in the new positions next time you start KSP. The "Click-Trough" is somewhat of an accident. I have this "problem" with all of my windows in KSP. If somebody can enlighten me how to avoid this...
  18. Nice story. J Most of the time I’m not that patient and do a reload if a mission went completely wrong. And they often do because of minor mistakes myself. And the second problem: It’s like another mod author was telling. If you are maintaining a plugin, you are not playing KSP anymore. You play your own mod and your will find some issues in play after a while. Even a very minor glitch will make you stop your game and start the development environment to analyze this. Maybe I spent about two hours in a game since the release of 1.1 and about 10 to 20 hours in testing and coding. So most of my careers are short lived. And then, when the coding is done and all seems to work… another game grabs for my attention. Stellaris will be released in a few days; HoI4 a few weeks later; No Men’s Sky is upcoming, too. Currently NanoGauges gets most of my attention. I was just about to release an update yesterday until I found some strange warnings in the log, I do not understand and so I have to check it today again. Well, and regarding your story: we really need an ironman career mod in KSP…
  19. Mac or Linux? If not: Install 7zip (http://www.7-zip.org/); it's a must have anyway. But I would prefer zips, too.
  20. Some minor issues found in 1.1.0-2113: Ablator gauge not working (working, but a heat shield is of course required) Air temperatur gauge missing (missing texture; fixed) External temperature gauge readings of 2000 degrees outside the atmosphere (gone for no reason) "Exception in window Nereid.NanoGauges.TooltipWindow, id 19281" (fixed) a few gauges permanently disabled in the code by accident (fixed) some minor warnings (fixed)
  21. And this is one of the concepts of CKAN I do not like... NP. Anyway: I'm 99,9% sure that FF does not add reputation to a kerbal.
  22. Well... until today someone else has done this for me. Anybody who like may do it; I personally do not like the concept of CKAN very much (its a mix of a personal taste and other reasons). Its works well for players but not so well for modders.
  23. It should appear under blizzys toolbar or the stock menu. It's your choice. But you will just get it in flight (not in the space center, VAB, SPH,...)
  24. Really? Curse tells me its for KSP 1.1. Well... I have done the same mistake with Chatterer this time. For some strange reason it went under JSI - and of course it won't work. PS: I have found some minor issues: If a FF window is open when quitting to main menu it stays open. The Download link vor KSP-AVC still links to kerbalstuff and some of obsolete class files are shipped in the zip; They are gone long ago but the release folder that contains all files was not wiped out.
×
×
  • Create New...