Jump to content

Nereid

Members
  • Posts

    1,043
  • Joined

  • Last visited

Everything posted by Nereid

  1. The vessel should not cause this. Tourist never get ribbons. If they are tourists when they got recovered, they are screwed.
  2. I'm using Scatterer and Kerbal Alarm Clock myself. So TAC-LS, TWP and EVE/SVE are candidates for any issues. If time allows I will test it in the next few days.
  3. New in 1.7.2-3277 Support for Kerbin-Side Airfields (9 new airfields for ILS approach) New gauges: ILS Airfield, ILS Runway Currently the Airfields are hardcoded and selectable even if Kerbin-Side is not installed. EDIT: It's not complete yet, but 9 airfields are included: Space Center (vanilla) Old Airfield (vanilla) Kerman Lake Black Krags Coala Crater Lake Dermal Green Coast South Point Kerbins Bottom The Shelf Valentina's Landing The first 4 are designated by SP, OA, KL, BK in the Nav gauge. The others are shown by their ID.
  4. New in 1.7.0 are three gauges. The first one is a Mini-DSKY gauge that looks smiliar to the DSKY used in Apollo. The indicator lamps on the left side do show the following: Remaining battery charge below 25% Communication established Terrain-Warning (Radar Altitude below 500m) Remaining Fuel below 5% (currently just Liquid Fuel and Oxydizer) Two other digital gauges are added: Digital versions of the apoapsis and periapsis gauges.
  5. There is an option in FF to enbable blizzys toolbar. But stock should be default. Did you try an unmodded copy of KSP with just FF installed?
  6. Did you extracted it into Gamedata/Nereid/FinalFrontier? If it's not it will not find its textures. If there is a problem with the toolbar, just remove it (temporary), start KSP, enable the stock toolbar in FF and reinstall the toolbar again.
  7. 1.3.6-3189 It's now possible to disable ribbons in the Ribbon-Browser. Currently you have to do it one by one. Closing the ribbon browser will save the configuration. EDIT: But be carefull. If you disable a ribbon, save your game, reload it and enable that ribbon again, it's gone. Disabling a ribbon will prevent it from being awarded to a kerbal. Already awarded ribbons are not affected [until you reload a save game].
  8. But this is completely fine and there is not much I can do about it. If you do EVA on a planet you have landed on that planet. This is true for all planets but not for Kerbin. So if you go on EVA on Kerbin you will automatically get the Landing ribbon. Kerbal logic. EDIT: And the EVA ribbon supersedes the Landing ribbon. Take a closer look to the ribbon graphics.
  9. The good news: If a ribbon is in the log, it's never gone. The not so good but still not bad news: It's WAD. Reason: if you drive a rover (beside from Kerbin), you will have to do an EVA first (*). Hence any EVA ribbons are superseded by the Rover ribbons. Thats why they have the two dots at the left side. If its an EVA in space, there is no icon at the right, EVA on ground gets a lander, and because a rover requires an EVA first, it gets a rover icon. Ok, if you start on Kerbin in a rover, than you are screwed. You will get the Rover ribbon first and on EVA you get the EVA ground ribbon, that is included in the Rover ribbon. (*) This is not quite true anymore, because technically you can start in a rover and drive it out of a complicated lander. So I tend do change this in the next release. EDIT: Changed. I will test it tomorrow. You will see your ribbon then, but the two dots in the ribbon are gone.
  10. LOL, I totally forgot that I have already implemented the addition of custom ribbons as a request from SmarterThanMe. So, its quite easy. Just create a file FinalFrontierCustomRibbons.cfg in your package. here is an Example from STMs ribbon packs # Final Frontier Ribbon Pack # # Syntax of file: # --------------- # NAME:<name of ribbon pack> # FOLDER:<folder containing ribbons> # BASE:<base for ribbon IDs (optional, default: 0)> # <ribbon ID>:<filename without suffix>:<name of ribbon>:<description>[:<prestige (defaults to ID)>] # <ribbon ID>:<filename without suffix>:<name of ribbon>:<description>[:<prestige (defaults to ID)>] # <ribbon ID>:<filename without suffix>:<name of ribbon>:<description>[:<prestige (defaults to ID)>] # [...] # # Do not use any <Ribbon ID> twice even its is used by another ribbon pack. # # If a base for this ribbon pack is set, all IDs are offsets from this base. If a ribbon gets ID 17 and the BASE is set to 7000, the used ID is 7017. # # Do not use IDs below 1001! # NAME:Medals FOLDER:Ribbons BASE:9000 1:heroku_01:Hero of the Koviet Union 1st Class:You know those Koviets... they love rows of medals. So you have 5 classes of those to give away and stuff the chest of your Kerbals with pride for the Motherland!:9999 2:heroku_02:Hero of the Koviet Union 2nd Class:You know those Koviets... they love rows of medals. So you have 5 classes of those to give away and stuff the chest of your Kerbals with pride for the Motherland!:9999 3:heroku_03:Hero of the Koviet Union 3rd Class:You know those Koviets... they love rows of medals. So you have 5 classes of those to give away and stuff the chest of your Kerbals with pride for the Motherland!:9999 4:heroku_03:Hero of the Koviet Union 4th Class:You know those Koviets... they love rows of medals. So you have 5 classes of those to give away and stuff the chest of your Kerbals with pride for the Motherland!:9999 5:heroku_03:Hero of the Koviet Union 5th Class:You know those Koviets... they love rows of medals. So you have 5 classes of those to give away and stuff the chest of your Kerbals with pride for the Motherland!:9999 A superseede option shouldn't be that hard to do either. Maybe this week.
  11. Well at the time I have started with FF we are were learning what is possible in KSP and what not. Maybe at those times this information was already at hand, but I didn't know about it a few years ago. SQUAD have added quite a bit since then. If I would start FF from scratch again I would do many things different and I would skip a few ideas and workarounds for bugs in KSP that may be solved now. But to change it at this time its beyond my time constraints. I'm still reluctant to remove some code that detect some missing events that may work now (like a closed orbit). And adding another source of carreer information other that recording it itself could bring up quite a few new problems and those KSP internal logs won't suffice. I would do it again, I would implement a module for "event-detectors" that just logs into another module (or directly into the SQUAD data, if possible) that just keeps track of those events and use FF just to visualize it. But this would not solve your problem at all.
  12. Feel free to do some graphics and I will integrate them.
  13. Yes. There is currently no way to add new ones.
  14. Not a guide, but you can replace a graphic files in GameData/Nereid/FinalFrontier/Ribbons as you like. At this point all ribbons are hardcoded in the source, but you can replace all CustomNN.png files.
  15. It's on Github: github.com/Nereid42/S.A.V.E It's a bug. Fixed in the current version.
  16. Sorry for my absence, but real life was calling. I have compiled FF against 1.3.1 and I will upload it today.
  17. Yes. Superseding is hardcoded (unfortunately). And because custom ribbons are generic...
  18. Tis is the expected behavior. Some ribbons are superseeding others. The reported behavior is an example: The ribbon for an EVA on ground is superseeded by the rover ribbon (because normaly you have to be on EVA before you enter a rover) In this special example there is the situation that you can drive a rover without EVA from a lander and it may be unexpected that you will never get the EVA on ground ribbon. Therefore the decision I made maybe was not optimal. Unfortunately FF doesn't have any gui to show what ribbon superseedes another and I do not have that much time at the moment.
  19. Hmmm.... then I will try to buffer the events before they are reported to the hall of fame. And maybe I should add pages to the log window...
  20. A buffer is not that easy to implement. The clas HallOfFame records all events in a logbook and entries for each kerbal. Recieving science is one of them. To filter all events for a specific kerbal a hall of fame entry has a list of logbook references. And now it gets complicated. The logbook entry is created at the moment the event occurs and its a method for all action like events (science, eva, recover,...). Buffering science is not possible without a massive change the code or writing very, very ugly code. Another solution would be to resolve all logbook antries after recovering and merge science events into a single one. Question is: Is it worth the effort? Are there really that many science events?
  21. Done. But merging a chunk of multiple science points into a single records is not that easy. A buffer could be one approach. The buffer has to be summed up at each save. Maybe I will give it a try.
  22. Fixed in 1.4.3-2822. I have seen this myself once, but I cannot reproduce this. EDIT: OK, this happens, when there arfe no backupsets (or games). I will fix this, too
  23. It will backup your ship-designs, too. Those are stored in subfolders of your savegame folder. Yes. It works on my system, but I got reports that it doesn't work for all. Compressed backups doesn't cost a lot. But it comes with a price: You cannot restore the backups without S.A.V.E that easy anymore. As far as I rememer. No. But I can add this as an option. I will take a look what may cause this bug. Maybe something is different in 1.3... Hmmm.... maybe the latest branch was a bit ahead of time. For FF and NG I copied all source back from the latest releases to preventg any unfinished development changes a few months ago. Minor bugs, therefore I will work on them next week. But thanks for reporting anyway...
  24. I didn't noticed this so far. Preventing entries of 0 should be easy. Its Kiel Week so my time is limited but I will give it a try next week.
×
×
  • Create New...