linuxgurugamer

Sounds like something is wrong when no controller is selected, could you try again in a new, clean install and report back? Log file when it is happening is needed.

Then stop recording using that and test. Probably not related, but need to find out first

No idea what you just said, other than you have some sort of problem, please clarify, ans post a complete output_log.txt

Start by providing the full output_log.txt, not just a snippit

That change was reverted, but if the mod was installed after I updated, but before the last revert, then that option will be set to that option being enabled.

Read the OP. This does nothing by itself, it is there for OTHER mod to use

I may do a recompile, but it will be unsupported and unofficial for now. It needs more love than I can give it right now

@Nertea Found the following typo in the mk4cargotail-1.cfg: MODULE { name = ModuleAnimateGeneric animationName = RampOpen sstartEventGUIName = #autoLOC_502051 //#autoLOC_502051 = Close endEventGUIName = #autoLOC_502069 //#autoLOC_502069 = Open actionGUIName = #autoLOC_502078 //#autoLOC_502078 = Toggle Ramp allowDeployLimit = true revClampDirection = false revClampSpeed = true revClampPercent = true } The startEventGUIName has two s's Also, I found something very odd when trying to fix All Y'All for the cargo bays in the mark IV system. The Mk4 Service Bay when created in the editor is closed, and the setting closedPosition = 0 The Mk4 Tail Cargo Bay when created in the editor is open, and the setting closedPosition = 0 All the other Mk4 cargo bays when created in the editor are open, and the settings closedPosition =1 The following data was obtained using debug statements after adding all the modules to a vessel, launching it: part: CRG-120 Mk4 Cargo Bay, animTime: 0, closedPosition: 1 part: CRG-240 Mk4 Cargo Bay, animTime: 0, closedPosition: 1 part: CRG-240 Mk4 Cargo Bay, animTime: 0, closedPosition: 1 part: CRG-60 Mk4 Cargo Bay, animTime: 0, closedPosition: 1 part: DRP-120 Mk4 Ventral Cargo Bay, animTime: 0, closedPosition: 1 part: DRP-240 Mk4 Ventral Cargo Bay, animTime: 0, closedPosition: 1 part: DRP-240 Mk4 Ventral Cargo Bay, animTime: 0, closedPosition: 1 part: DRP-60 Mk4 Ventral Cargo Bay, animTime: 0, closedPosition: 1 part: Mk4 Service Bay, animTime: 0, closedPosition: 0 part: Mk4 Tail Cargo Bay, animTime: 0, closedPosition: 0 It seems very odd about the Mk4 Tail Cargo Bay, wondering if that's a bug When I changed the closedPosition in the Mk4 Tail Cargo Bay to 1, things started working as I expected.

New release, 0.1.9.11 Reverted change to line 317 in MuMechModuleHullCamera, caused issues with cameras Fixed cameras for the inline docking ports to match the navball when the docking port is the active control point New feature, holding down the modifier key (Alt on Windows) when hitting + or - will change the control point to the docking port with the camera, only works on docking ports and the original controlling part

I'm not, was just confirming that you hadn't done the same thing.

The other inline docking port had the same problem. I've fixed it locally, want to test before releasing

That is most likely the old behaviour

Actually, no. I sent a message to the FSF about this, because I wanted to release his v2. The problem is that he released compiled code, but didn't release the source code, therefore the source was not necessarily under the license. I'll paste it here:

Just an fyi, Meiru had released v2 as code, and its trivial to recompiled it.

I think I know what's going on, other than the Mk2 issue. Would you be willing to test a beta dll? Here is a beta zip: https://www.dropbox.com/s/661tahqqlevbqvq/HullCameraVDS-0.1.9.11.zip?dl=0 Try it out and let me know, no change done for the Mk2 yet

ok, now I understand what you are talking about this may be something else, but I'll check it out I saw this once. I will look into this in the next few days

Umm, Meirmu released two versions, one which was in a PR to the original KJR, and his v2, which he never released the code for. I inquired with the FSF, and since he never released the code for v2, that can't be used, but the first one is ok to use. So, which version of his code did you use?

Which version of Meiru's code did you do the remerge from?

I'm not myself, but I've asked for some help from @DoktorKrogg

Some information about your system, KSP's requirements have increased

It must not have updated the .version file, but if the file name is 1.9.0.2, you can be sure that is the correct version. I'm actually not sure if it is the right version in the file :-( However, I will get this fixed and out later this evening, will be 1.9.0.3 New release, 1.9.0.3 Fixed .version file

I got the first one last night, will get the CLS one later today Thanks

Are you referring to the Mk2 Clamp-O-Tron? If so, then there isn't any up/down to it. I also tested the Inline Clamp-O-Tron, the cameras for both of these are set the same way. See these pictures: And here are the camera views:

New release, 3.2.2.13 These minor tweaks from forum user @Gordon Dry 2 small RemoteTech fixes add KopernicusSolarPanel to subcategory Solar Panels add Coatl Aerospace add values to 000_FilterExtensions_Configs\SubCategories_ISRU.cfg add values to 000_FilterExtensions_Configs\SubCategories_ISRU.cfg for Kerbalism