JPLRepo

TACLS has not been dropped... What is all this talk of someone else picking the mod etc. TaranisElsu is still around. See this post from him on the 14th September:- http://forum.kerbalspaceprogram.com/threads/40667-1-0-2-TAC-Life-Support-v0-11-1-20-5Apr?p=2193832&viewfull=1#post2193832 AVG has not been updated for 1.04, it is safe to ignore the AVG prompts. TAC LS works fine with 1.04.

My issue really is time. I don't really have the time. I already have about 15 installs of KSP at the moment.

The logs are very helpful thanks, probably don't need any more information for now. Just to confirm: It looks like this is happening to you with multiple vessels? not just the same vessel? Does it only happen when you switch from one vessel to another? or when loading a vessel from tracking station or all of the above? What DeepFreeze parts do these vessels have on them? I'll look into it and try to turn around a fix as quickly as I can. (next few days).

Things are looking good. Congrats to Dave (TriggerAU) as well.

Not really, that Free IVA mod is incompatible with RPM which I use extensively.

Ok, a fix to make Texture Replacer compatible with DeepFreeze is nearing completion. Expect an update to Texture Replacer in the near future (days?) - it has already been tested. I can then add Texture Replacer support into the next version of DeepFreeze. So any customised Kerbals will no longer lose their customised textures when they are frozen/thawed (as is currently occurring with current versions).

NP. How about extending this mod to animate IVA kerbals as well then?

FreeIVA is not compatible with RasterPropMonitor. It draws a cylinder which RPM makes visible. I already raised this on the FreeIVA forum thread.

There has been a delay in Nils277 releasing the DeepFreeze parts for Kerbal Planetary Base System as there were some compatibility issues that we had to sort out. But that is now all done and I expect he will be releasing it in the next couple of days.

I'll see what I can find and report back to you. EDIT: I have found a KerbalExpressionSystem class/object for both IVA/EVA. You can find it a number of ways: This class is an extension of MonoBehaviour so all instances can be found with: foreach (kerbalExpressionSystem kes in Resources.FindObjectsOfTypeAll<kerbalExpressionSystem>()) A single instance is instantiated per kerbal attached to their kerbal class. (kerbalref). So can be found with: foreach (kerbalExpressionSystem kes in kerbal.gameObject.GetComponentsInChildren<KerbalExpressionSystem>()) where kerbal is the Kerbal class/kerbalref attached to the protocrewmember, etc. So you could check if it's an EVA kerbal first, Get the crew protocrewmember.kerbalref from the vessel.GetVesselCrew() list, a number of ways you could do it. Within the class there a number of useful vars as well: Bool isIVAController is true if attached to IVA kerbal or false if attached to EVA kerbal. KerbalEVA kerbalEVA is null if on IVA kerbal or set to the kerbalEVA partmodule if on an EVA kerbal. Part evaPart contains the EVAPart when attached to a kerbal in EVA

So certainly I could make a less fatal consequences optional. So if the part overheats it uses more EC. What haaens if EC runs out? How about they automatically thaw - but in a comatose state for a period of time. They start using LS supplies again obviously and then they become active again.. I'm waiting for any other ideas to be put forward... If part overheats ___ happens. If EC runs out ____ happens. Fill in the blanks. No one wants or has any other ideas?

The expressions? on IVA kerbals appear to be embedded in the animations attached to the Unity Legacy Animator. If I turn off the Animator all movement stops including their faces, head, arms, legs. There are a couple of classes related to expressions AI, etc, but I thought they were only related to EVA kerbals. I will investigate further.

It would be because Unity/KSP is rendering an external model and internal model at the same time... doing this for just one part usually isn't an issue. But if you line up five of them like I was doing last week you notice a big difference. There is also this issue with Unity: Props should not contain flat mesh colliders -- such objects when seen with a world-space camera cause Unity to spam error messages and cause a sharp drop in performance. I would also guess the pizzaoverhead IVA mod you are referring to is actually for moving the IVA cameras around, not making them visible from external/flight view. Unless I have missed some new updates to that mod (highly likely).

I have made a discovery and found all the necessary pieces to the puzzle to also enable/replace IVA kerbal animations.

Through lots of digging I have dug up and found a) the IVA Kerbal bones (although others had already found this before) the Unity Animator attached to the IVA kerbal's and their Animation clips (of which there are 58 defined). c) How to replace the animation clips in IVA, which I have successfully done. All that is left now is to maybe incorporate into MrHappyFace's Animation Suite (rather than building another one) for IVA kerbal animations and we can create our own IVA animations for kerbals.

Sorry I don't think people are understanding this. no you can't just change stock parts to be transparent, or other mods parts to be transparent. It depends on how the model has been created. In order for RPM transparent pods to work (not sure about this mod) the windows must be separate pieces of the actual model. Then you can define transparent shaders to the windows. Let's take an example stock part: the copula. this model was created by squad with the windows and the body of the part all as one piece. Therefore you cannot make it transparent using RPM transparent pods. The model would have to be changed/re-created. Like I said, what you can do is contact the mod authors and ask them to look at making their parts transparent (where the part has an internal). But I doubt Squad will change the stock parts.

To detect if in iva mode: [COLOR=blue]public[/COLOR] [COLOR=blue]static[/COLOR] [COLOR=blue]bool[/COLOR] IsInIVA() { [COLOR=blue]return[/COLOR] [COLOR=#2b91af]CameraManager[/COLOR].Instance.currentCameraMode == [COLOR=#2b91af]CameraManager[/COLOR].[COLOR=#2b91af]CameraMode[/COLOR].IVA || [COLOR=#2b91af]CameraManager[/COLOR].Instance.currentCameraMode == [COLOR=#2b91af]CameraManager[/COLOR].[COLOR=#2b91af]CameraMode[/COLOR].Internal; } To switch to flight mode: [COLOR=#2B91AF]CameraManager[/COLOR].Instance.SetCameraFlight(); To switch to previous camera mode: [COLOR=#2B91AF]CameraManager[/COLOR].Instance.PreviousCameraMode(); Anyway, it's all in the CameraManager class.

No and Yes. The model maker has to create two sets of window shaders, one transparent and one opaque and then configure to use RPM in the part config file. You can of course just have ONE window shader (say the stock one) and then just change the config file, but then it looks like there is no window/glass at all, but it doesn't always work. A more realistic and working window needs a window shader to be generated with low opacity. Like I also said, having lots of internalmodels being rendered as well as external part models... does hit on performance. Which is probably why it is not stock. As per RPM it was noticed also that the more internal props you have configured the more performance hit there is as well.

RasterPRopMonitor mod already does transparent pods/parts and IVAs. And before RPM, a mod called sfr command pods did it, which was abandoned and Mihara rebuilt it in RPM. Beware it is heavy on performance which is probably why it's not stock. I just finished updating the RPM module so you will be able to turn transparent pods on and off per part in the editor or in flight. MOARdV should be putting out a new version of RPM this weekend with this feature.

The door opening on the CRY-300 is only active if you have RasterPropMonitor mod installed if that is what you mean. If you do not have RPM installed you cannot open the doors or see inside from the outside. As per the install instructions and optional mods list in the OP

With regards to bug reports, please follow the instructions in the OP. I require description of the problem, steps to reproduce the error, a full debug log (not the Ksp.log). I am not following what you mean by "i see a picture with open chambers but i cant open the chambers". You need to describe the problem and how to reproduce the problem. IE: "I see a picture" - what picture? "I cant open the chambers" - there is no function in DeepFreeze to "open the chambers"? What do other people think? If the kerbals don't die because of overheat or if EC runs out - what should happen? I'm looking for ideas and suggestions of what people would like to see happen.

I can certainly make it optional that they don't die... but what is supposed to happen to them if they don't die? What is "trown"?

Yes it works in the VAB/SPH and in flight. Description in the pull request. https://github.com/Mihara/RasterPropMonitor/pull/369 The WIKI page will need to be updated. It's important to note that a part using JSITransparentPod should specify transparentTransforms field in the MODULE config so that when toggling JSITransparentPod OFF any window/transforms specified will be changed to opaque. If this is not specified for the part the internal will be turned off, but the window will remain transparent and you will see inside an empty part.

Yes you have to instal the dds plugin for gimp

So I have been tinkering today and I coded up a simple part menu toggle button for TransparentPods functionality. It has three settings: ON, OFF, AUTO. It defaults to ON, which means any part that has TransParentPod module will be transparent. If you toggle it to off, then you guessed it, it turns off transparentpod functionality for that part. and Auto will be off unless you set that part to be the "control from here" part or you hover the mouse over the part whereby it will turn transparentpod functionality on for that part. In testing with 5 parts all with transparentpod module assigned to them I got: 35FPS with them all set to ON. 52FPS with them all set to AUTO and 93FPS with them all set to off. Does anyone feel this would actually be a useful feature for TransparentPods?