JPLRepo

V0.19.1.0 released. Expanded the NON-Fatal EC usage/overheat setting to comatose kerbals that are emergency thawed for a period of time. Fixed the new pop-up menus when EC runs out or overheat occurs. See the Changelog in the OP.

TextureReplacer mod allows you to assign different suits by profession (as well as lots of other options). PortraitStats mod adds icons for experience stars and profession in the portrait cameras during flight.

I recently ran into this fixing a bug and found isactivevessel not always accurate depending on where you are checking. I.e.:onstart. I found checking this.vessel.id == flightglobals.activevessel.id worked much better and always accurate

More information is required here.. You say you docked two ships with CRY-1300's with 6 kerbals on-board each? I think you mean 3 kerbals on-board each? And were all 6 frozen? And after you docked you attempted to thaw and got what error? The error you have reported above is not directly after doing this, I can tell because in the error it says: at System.Collections.Generic.List`1[internalSeat].get_Item (Int32 index) [0x00000] in <filename unknown>:0 at DF.DeepFreezer.resetFrozenKerbals () [0x00000] in <filename unknown>:0 at DF.DeepFreezer.onceoffSetup () [0x00000] in <filename unknown>:0 at DF.DeepFreezer.OnUpdate () [0x00000] in <filename unknown>:0 This particular part of the code does not run when two vessels dock and you attempt to thaw. This error is on initial load of the part, say when you switch to it from space center. Anyway, I just conducted an exact same test: Two CRY-1300's with 6 kerbals on board. All of them frozen.. whilst the two vessels were separated. I docked the two vessels and was able to successfully thaw them all. This is all using V0.19.0.0 which fixed this problem. So I cannot reproduce your error. I'm guessing you may have docked them before upgrading to V0.19.0.0?? If anyone experiences similar errors you need to save your log file and submit it with steps to reproduce etc. As per the support instructions here. I would very much like to see your persistent.sfs file to try and determine what is going on if you are willing to share it. As to how to now recover, here are the steps, but if you get it wrong, well, should have backed it up. 1) Edit your persistent.sfs file and Find SCENARIO where Name is DeepFreeze as per this : SCENARIO { name = DeepFreeze scene = 5, 6, 7, 8 DFGameSettings { Enabled = True KerbalInfo { lastUpdate = 315357.079318465 status = Dead type = Unowned vesselID = 6715860e-036c-4353-8e63-ef8872e83e99 VesselName = cry1300testDocking partID = 4107896637 seatIdx = 0 seatName = Seat1 experienceTraitName = Engineer kerbalName = Frolie Kerman } KerbalInfo { lastUpdate = 315364.739318472 status = Dead type = Unowned vesselID = 6715860e-036c-4353-8e63-ef8872e83e99 VesselName = cry1300testDocking partID = 4107896637 seatIdx = 1 seatName = Seat2 experienceTraitName = Engineer kerbalName = Hallock Kerman } KerbalInfo { lastUpdate = 315378.239318484 status = Dead type = Unowned vesselID = 6715860e-036c-4353-8e63-ef8872e83e99 VesselName = cry1300testDocking partID = 4107896637 seatIdx = 2 seatName = Seat3 experienceTraitName = Pilot kerbalName = Shermund Kerman } KerbalInfo { lastUpdate = 315386.119318492 status = Dead type = Unowned vesselID = 3326f7fb-266f-4dbb-b471-cb7eddcfbf2c VesselName = cry1300testDocking Ship partID = 941884159 seatIdx = 0 seatName = Seat1 experienceTraitName = Engineer kerbalName = Milke Kerman } KerbalInfo { lastUpdate = 315392.879318498 status = Dead type = Unowned vesselID = 3326f7fb-266f-4dbb-b471-cb7eddcfbf2c VesselName = cry1300testDocking Ship partID = 941884159 seatIdx = 1 seatName = Seat2 experienceTraitName = Scientist kerbalName = Rodgar Kerman } KerbalInfo { lastUpdate = 315399.619318504 status = Dead type = Unowned vesselID = 3326f7fb-266f-4dbb-b471-cb7eddcfbf2c VesselName = cry1300testDocking Ship partID = 941884159 seatIdx = 2 seatName = Seat3 experienceTraitName = Engineer kerbalName = Wilelle Kerman } VesselInfo { vesselName = KPBS-CRY5000 vesselType = Base numSeats = 6 numCrew = 3 numOccupiedParts = 2 numFrznCrew = 0 hibernating = True hasextDoor = False lastUpdate = 315330.45931844 storedEC = 4284.62676003316 predictedECOut = 25707.7605601989 Guid = 424e3973-3fff-4889-9189-348c9666ae29 } VesselInfo { vesselName = cry1300testDocking vesselType = Ship numSeats = 6 numCrew = 1 numOccupiedParts = 2 numFrznCrew = 3 hibernating = False hasextDoor = False lastUpdate = 315406.19931851 storedEC = 8149.99906847407 predictedECOut = 0 Guid = 6715860e-036c-4353-8e63-ef8872e83e99 } VesselInfo { vesselName = cry1300testDocking Ship vesselType = Ship numSeats = 3 numCrew = 0 numOccupiedParts = 1 numFrznCrew = 3 hibernating = False hasextDoor = False lastUpdate = 315406.19931851 storedEC = 8030 predictedECOut = 0 Guid = 3326f7fb-266f-4dbb-b471-cb7eddcfbf2c } PartInfo { vesselID = 424e3973-3fff-4889-9189-348c9666ae29 PartName = CRY-5000Freezer numSeats = 4 numCrew = 2 crewMembers = Newke Kerman,Jebfred Kerman crewMemberTraits = Scientist,Scientist numFrznCrew = 0 hibernating = False hasextDoor = False timeLastElectricity = 315330.46875 frznChargeRequired = 10 timeLastTempCheck = 312922.09375 deathCounter = 315406.19931851 tmpdeathCounter = 0 outofEC = True TmpStatus = OK cabinTemp = 306.1939 ECWarning = True TempWarning = False lastUpdate = 171189.6218575 flightID = 853394433 } PartInfo { vesselID = 6715860e-036c-4353-8e63-ef8872e83e99 PartName = CRY-1300Freezer numSeats = 3 numCrew = 0 crewMembers = crewMemberTraits = numFrznCrew = 3 hibernating = False hasextDoor = False timeLastElectricity = 315406.1875 frznChargeRequired = 10 timeLastTempCheck = 315399.625 deathCounter = 0 tmpdeathCounter = 0 outofEC = False TmpStatus = OK cabinTemp = 287.5132 ECWarning = False TempWarning = False lastUpdate = 315302.299318414 flightID = 4107896637 } PartInfo { vesselID = 3326f7fb-266f-4dbb-b471-cb7eddcfbf2c PartName = CRY-1300Freezer numSeats = 3 numCrew = 0 crewMembers = crewMemberTraits = numFrznCrew = 3 hibernating = False hasextDoor = False timeLastElectricity = 315406.1875 frznChargeRequired = 10 timeLastTempCheck = 315378.9375 deathCounter = 0 tmpdeathCounter = 0 outofEC = False TmpStatus = OK cabinTemp = 287.5406 ECWarning = False TempWarning = False lastUpdate = 315302.299318414 flightID = 941884159 } } } Each KerbalInfo Entry is a frozen kerbal, each VesselInfo Entry is a vessel that has a DeepFreeze part attached, each PartInfo Entry is for each DeepFreeze freezer part that are part of active vessels. When the vessel is one vessel (docked) the VesselID in each KerbalInfo entry and PartInfo entry should match the Guid entry in the VesselInfo Entry (for their vessel). The partID for each KerbalInfo should match the flightID entry in their respective PartInfo Part's that they are in. And no two kerbals in the same part should have the same seatIdx or SeatName. From the error you have supplied it looks like a frozen Kerbal (KerbalInfo entry) is pointing to a part/seat that is already taken by either another frozen kerbal, or a thawed one. 2) To 'hack' your save file, you can remove the KerbalInfo for all the frozen kerbals, you then need to Remove the entries for each PartInfo (DeepFreeze will re-add them on next startup). 3) You then would have to put your kerbals back in the part, to do that you have to find the "VESSEL" entry for the vessel they are meant to be in, then the "PART" entry and add the crew= parms with the crew members names back in like this: VESSEL { pid = 6715860e036c43538e63ef8872e83e99 name = cry1300testDocking type = Ship...... .... PART { name = CRY-1300Freezer cid = 4294321408 uid = 4107896637 mid = 2531086846 launchID = 87 parent = 0 position = 0,-1.466139793396,0 rotation = 0,0,0,1 mirror = 1,1,1 symMethod = Radial istg = 0 dstg = 0 sqor = -1 sepI = 0 sidx = -1 attm = 0 srfN = , -1 attN = top, 0 attN = bottom, 2 mass = 2.5 temp = 287.513214111328 tempExt = 283.089101509767 expt = 0.5 state = 0 connected = True attached = True flag = Squad/Flags/default rTrf = CRY-1300Freezer modCost = 0 crew = Jebediah Kerman 4) Then you have to go down to the "ROSTER" and find the "KERBAL" entry for each frozen kerbal you changed and change type to Crew "type=Crew" and state to assigned "state = Assigned". ROSTER { KERBAL { name = Jebediah Kerman gender = Male type = Crew brave = 0.5 dumb = 0.5 badS = True tour = False state = Assigned ToD = 310267.603309575 idx = 0 If that is all overwhelming and you want to save your savegame, post it on dropbox or suchlike and send me the link via PM message. I will fix it for you.

V1.0.4.0 Released. Lots of fixes, and removed the on-going need to update this mod whenever a supported mod is updated. See the changelog in the OP for details.

that was it. Ad-blocker under windoze. Thanks!

Wouldn't work for me using chrome or IE on my Windoze partition. But it worked fine using Safari under OS-X.

Yep thanks, working now. Must have been down earlier.

The Download Icon (big gray button) in your OP points to: http://www.kerbaltopia.com/ModEASY/DLcount.php Right click open in new tab etc still tries to open this link which fails...???

Went to re-download (accidentally deleted it). The download link in the OP seems to just point to a download counter rather than the zip file? The source download works, but I don't have a Delphi compiler any more (been about 15 years since I used Delphi).

Was going to give this a go today. but your bitbucket links for source and download are dead?

This mod is not dead. Papa_Joe just has 'real life' concerns at the moment that are taking up a lot of his time. Please be patient.

I Believe Nils already said this was a bug and how to fix it until he puts out his next release. http://forum.kerbalspaceprogram.com/threads/127413-WIP-1-0-4-Kerbal-Planetary-Base-Systems-v0-2-6-Update-8-10-2015?p=2241249&viewfull=1#post2241249

Glad it's working for you.

I already answered this question: http://forum.kerbalspaceprogram.com/threads/117471-1-0-4-RasterPropMonitor-still-putting-the-A-in-IVA-%28v0-23-0-28-September-2015%29?p=2236323&viewfull=1#post2236323 http://forum.kerbalspaceprogram.com/threads/117471-1-0-4-RasterPropMonitor-still-putting-the-A-in-IVA-%28v0-23-0-28-September-2015%29?p=2236343&viewfull=1#post2236343

Probably it is more like no one has noticed them yet. I suddenly realised what you were saying because when I did the DeepFreeze parts I noticed some numbers on some of the parts (but only when I was looking very very closely at the textures). Now we know they are there - the challenge is there now for who can find them?

I have looked at this, the stock models do not contain the necessary transforms for the windows, etc. Most of them are one object/transform or a few. So you can't just find the window transforms and add JSITransparentPod unfortunately. Basically you would have to get someone to re-model all the stock parts to have separate window transforms on both the external model and any internal models - then you could do it.

Yes there are a few. Search for easter eggs or part number easter eggs. Spoilers (by no means the only links), there are lots. http://forum.kerbalspaceprogram.com/threads/60551-Spoiler-Easter-Egg-Stocktake-1-0-4 http://wiki.kerbalspaceprogram.com/wiki/List_of_easter_eggs Or do you mean you have added your own specific ones to your parts?

What I was saying is performance hit will occur when you have lots of parts both internal and external all being rendered at the same time... but if you download the latest RPM you can turn the setting on and off per part and customise your experience to how you like it between seeing all the internals through the windows or some or none the trade-off being performance the more you have visible at the same time. I would recommend at least giving it a go.

If you download the latest version of RPM the latest version of RPM allows you to change the transparency setting via the part right click menu per part. So you can switch them on or off, or set them to Auto (when in auto mode the windows become transparent when you mouse over the part). The performance hit is to be expected when you have multiple parts all loaded (in range) with the transparency on, as this causes the Internal model to be loaded and rendered as well as the external models. Rendering costs GPU/CPU. But the new toggle option in RPM allows you to switch them on and off to handle the performance issue. Remembering that RPM JSITransparentPod was actually built to make transparent command pods. Mods like this one which have lots of parts all connected and in range of each other using transparency will cause a performance hit. The best thing to do is to set them all to Auto in the Editor (or in flight) and mouse over them if you want to see inside...

This is already being discussed here. http://forum.kerbalspaceprogram.com/threads/134877-Undesired-Third-Party-Mod-Hosting

V0.19.0.0 Released. Lots of fixes and enhancements. Refer to the changelog in the OP. Should not break save games (as far as I tested), but as always back up your save files before upgrading.

Nils277 has released a new version of his KPBS mod that includes DeepFreeze Continued... parts, namely the CRY-5000 and a Glykerol storage tank. Go check it out over on his mod thread. These parts require DeepFreeze continued installed to function and are distributed as part of the KPBS mod. Which is an awesome base building mod BTW (which is why we decided to create these parts for his mod). - - - Updated - - - Excellent. Thanks for testing it out. I'm going to put IFI into the supported list. - - - Updated - - - Working on this fix and a lot more.. V 0.18.3.0 is nearing completion.

Yes they are thawed and restored back at the KSC (they won't re-appear on any ship). I will work on a fix this week. In the meantime I recommend for anyone that you don't dock/un-dock or use KIS on any vessel that has frozen kerbals on-board until I release a fix. Issue raised and being tracked here.

Thank you for the extensive bug report info. Yes, DeepFreeze stores frozen kerbals against the SCENARIO rather than in the PartModule. This is so it can be accessed from anywhere in the game, such as another vessel (when the part is unloaded), etc and given there are Electrical Charge and Heat usage and monitoring that occurs all the time in game, this is required. I am unfamiliar with how KIS operates and was not aware it can remove parts from vessels. It would be safe to say at this stage that DeepFreeze is NOT compatible with KIS. I will have to investigate how KIS removes parts, renames vessels, etc to see if it is using standard KSP GameEvents or not. I will check the GameEvents that DeepFreeze uses and check that standard docking, un-docking and renaming still works. Rather than your game save hack, DeepFreeze does allow you to Thaw Frozen Kerbals from the Space Center (they will re-appear in the Astronaut Center back at KSC) if they are no longer associated with a valid vesselID. So you could try that.