JPLRepo

Yeah sorry. there was a fix in the OP for the hatches. I'd completely forgotten about. Doesn't matter now. V1.1 has been released. It includes the hatch fix... plus docking port fixes, lander/ranger stability fixes, few other things. See the ChangeLog in the OP for the full list.

I'll take a look at it. I am very familiar with the TACLS code.

yes

yes

This should probably go to whoever has that issue of Nils277 assigned to them. Not sure who? @Porkjet or @sal_vager or someone might be able to pass it on? My thoughts here are that given Internal space and external space (Scaled space) are orientated differently.. when you render the IVA camera the way it is now being done in 1.1+ I can't see how you would ever see the shadows of the external part model fall onto the internal model. Given they are in two different location/orientations. That is assuming the two cameras being used to render both the internal space and external space have the Sun (light source) orientated appropriately for each... Wouldn't the only way to get the external model / mesh shadow to fall on the internal one would be they are located in the same position and orientation? Or you copy them and put the copy in the right location / orientation? Or do as Nils277 has suggested and put a copy of the external into the internal model to cast the shadows (just another way of doing the copy or move in real time). Only this way would probably be cheaper.

I know it can be improved more... but I also know Squad have plans to change/improve resource/part processing... I think that's all going to be in 1.3 though.

NP. Sounds like I need to do another efficiency round on the code again.

I have worked out the cause of the bug and a work-around. If you really want to remove AY from your install. Just LEAVE the \GameData\REPOSoftTech\AmpYear\Resources\AmpYearResources.cfg file and remove everything else from the AmpYear folder. This will stop the crashing in the Tracking Station until you recover all vessels that were launched with AmpYear installed. The cause is a stock bug, but by leaving this file, it won't occur. A fix for the stock bug though won't be available probably under 1.2 now given 1.1.3 has entered code lockdown this week (as per the DevNotes).

@Deimos Rastthanks! I'll look into it.

NP. If you manage to break it again PM me the log. As for the TAC LS msgs. That msg used to get issued once when you thawed a kerbal in DF. Which was issued when TAC suddenly discovered them again. But it used to just re-add them to its own list and start tracking them and including them in its calcs again. If it's spamming I'm guessing the new maintainer has done something to the code that is causing it to have problems.

OK. So if you go back to your fully modded install and try does it bomb out? If so, send me the log and I'll take a look before you embark on the process of elimination.

That's ok... I'll see if I can get any errors myself first. That's because back in 1.0.5 it (JSI ATP) did things in an entirely different way to the way it works in the 1.1+ world. The flickering is because it is detecting something between the Internal and the camera... the thing is - in your video, there isn't anything... so I actually think that bug belongs over on the JSI ATP thread.

I think my plans for ResearchBodies and Tarsier Space Tech are pretty close to the first part of your vision... That feature is Currently in development.

On the first problem, that's actually JSI Advanced transparent pods I think. You can see the setting for that swapping from Obstructed to ON over and over. I'll take a look at it, but that is going to be a tough one to crack. As for the KAC alarms integration. I'll investigate. I've never had any issues before and testing has never shown any problems. and your final request, action groups for freeze/thaw - that's not really going to be possible. Simply because the freeze/thaw events are tied to actual kerbals frozen in the part. So you can't just have a generic freeze or thaw, as it needs to have a kerbal linked to the event. Maybe, just maybe, I could look at something using the existing emergency thaw processing code that I have already written that automatically thaws ALL frozen kerbals on-board. But I can't promise when I will get to that. Perhaps the focus should just be on what your KAC integration issue is for now.

Well that's got me flummoxed. I just tested it again, and yes it's working.. but that other screenshot proves I wasn't dreaming. I guess we leave it working then.

hmmm.. you are using V1? I had that in testing but thought it was fixed. Just started up KSP testbed and it's fine. So either I fixed it and it will be in the next version, or you have something else going on.

hmmm... ok... Thanks. I'll re-test it. It didn't show them for me.

@Gordon Dry Well I am not really following what the issue is here. As @Deimos Rast said it would appear RO or something is changing your NFE reactor. I went through your log and couldn't find anything evil with regard to AmpYear. But I did see lots of Remote Tech log spamming. All I can really do is test the NFE reactors with AmpYear ESP processing again to make sure this is no bug. ESP does not support the NFE reactors, so it should not be changing them at all. So I will check that. But given I see nothing else in your log AmpYear related not much else I can do.

Whilst the Roster screen seems fixed and not bugging out, frozen kerbals are not appearing. I'm helping Papa_Joe out to determine the issue there.

Still working on it. But it looks promising. Hope to have something this weekend, but no promises (tm)

Read back 3 or 4 pages would be my advice.

The docking ports are busted.. I have a fix, but I haven't released it yet.

Fail. I summon @Majorjim

So I have fixed the docking ports. Hopefully once and for all. And tested them in flight. I cannot find a fix for the ScienceLab Legs. I believe this is related to the physics issues in 1.1.2. It seems ok as long as you don't launch your vessel with the sciencelab legs deployed. I just need to do a bit more testing and a couple of extra bits I have been working on before I package an updated version. Hopefully tomorrow or the next day.

it's been moved into internal Dev queue. Same happened to one of mine.