nukeboyt

Would someone please take a look at these crash files and see what the cause is? Much appreciated. Dropbox Link

Turns out that I'm in way over my head. So I'll defer that question to someone who has more knowledge than me; (Which isn't too hard to find) Alas, I have to un-recommend the coding changes I posted above. By changing the .cfg for the monitor, It introduces some weird artifacting, if you have the SVE mod installed. I had seen this before, but forgotten about it. The pan-tilt changes work ok. It's the multiple pages, one for each camera where the the artifacts show up.

I have not found an MFD config file that works that way. If it is possible, it certainly would be a more elegant solution.

I cleaned up the Page 07 code a bit and also included the method by which you would individually name each of the 8 cameras. Essentially you have to create a page for each camera. The downside is that when you do this, you have to cycle all the way through #8 to get back to #1. // --------------------Page 07 ----------------------------------------- PAGE { name = extcamA button = buttonR7 text = Your Name for Camera #1 BACKGROUNDHANDLER { name = JSISteerableCamera method = RenderCamera showNoSignal = true buttonClickMethod = ClickProcessor buttonReleaseMethod = ReleaseProcessor pageActiveMethod = PageActive cameraInfoVarName = MFDEXTCAM skipMissingCameras = true cameraTransform = ExtCam1 fovLimits = 20,5 zoomRate = 5 showTargetIcon = true iconPixelSize = 32 targetIconColor = 255,0,255,128 homeCrosshairColor = 255,0,0,255 pitchLimits = -45,35 pitchRate = 15 yawLimits = -45,45 yawRate = 15 // Buttons: zoomIn = 2 zoomOut = 3 nextCamera = 7 prevCamera = 8 yawLeft = 6 yawRight = 5 pitchUp = 0 pitchDown = 1 seekHome = 4 } } PAGE { name = extcamB button = buttonR7 text = Your Name for Camera #2 BACKGROUNDHANDLER { name = JSISteerableCamera method = RenderCamera showNoSignal = true buttonClickMethod = ClickProcessor buttonReleaseMethod = ReleaseProcessor pageActiveMethod = PageActive cameraInfoVarName = MFDEXTCAM skipMissingCameras = true cameraTransform = ExtCam2 fovLimits = 20,5 zoomRate = 5 showTargetIcon = true iconPixelSize = 32 targetIconColor = 255,0,255,128 homeCrosshairColor = 255,0,0,255 pitchLimits = -45,35 pitchRate = 15 yawLimits = -45,45 yawRate = 15 // Buttons: zoomIn = 2 zoomOut = 3 nextCamera = 7 prevCamera = 8 yawLeft = 6 yawRight = 5 pitchUp = 0 pitchDown = 1 seekHome = 4 } } PAGE { name = extcamC button = buttonR7 text = Your Name for Camera #3 BACKGROUNDHANDLER { name = JSISteerableCamera method = RenderCamera showNoSignal = true buttonClickMethod = ClickProcessor buttonReleaseMethod = ReleaseProcessor pageActiveMethod = PageActive cameraInfoVarName = MFDEXTCAM skipMissingCameras = true cameraTransform = ExtCam3 fovLimits = 20,5 zoomRate = 5 showTargetIcon = true iconPixelSize = 32 targetIconColor = 255,0,255,128 homeCrosshairColor = 255,0,0,255 pitchLimits = -45,35 pitchRate = 15 yawLimits = -45,45 yawRate = 15 // Buttons: zoomIn = 2 zoomOut = 3 nextCamera = 7 prevCamera = 8 yawLeft = 6 yawRight = 5 pitchUp = 0 pitchDown = 1 seekHome = 4 } } PAGE { name = extcamD button = buttonR7 text = Your Name for Camera #4 BACKGROUNDHANDLER { name = JSISteerableCamera method = RenderCamera showNoSignal = true buttonClickMethod = ClickProcessor buttonReleaseMethod = ReleaseProcessor pageActiveMethod = PageActive cameraInfoVarName = MFDEXTCAM skipMissingCameras = true cameraTransform = ExtCam4 fovLimits = 20,5 zoomRate = 5 showTargetIcon = true iconPixelSize = 32 targetIconColor = 255,0,255,128 homeCrosshairColor = 255,0,0,255 pitchLimits = -45,35 pitchRate = 15 yawLimits = -45,45 yawRate = 15 // Buttons: zoomIn = 2 zoomOut = 3 nextCamera = 7 prevCamera = 8 yawLeft = 6 yawRight = 5 pitchUp = 0 pitchDown = 1 seekHome = 4 } } PAGE { name = extcamE button = buttonR7 text = Your Name for Camera #5 BACKGROUNDHANDLER { name = JSISteerableCamera method = RenderCamera showNoSignal = true buttonClickMethod = ClickProcessor buttonReleaseMethod = ReleaseProcessor pageActiveMethod = PageActive cameraInfoVarName = MFDEXTCAM skipMissingCameras = true cameraTransform = ExtCam5 fovLimits = 20,5 zoomRate = 5 showTargetIcon = true iconPixelSize = 32 targetIconColor = 255,0,255,128 homeCrosshairColor = 255,0,0,255 pitchLimits = -45,35 pitchRate = 15 yawLimits = -45,45 yawRate = 15 // Buttons: zoomIn = 2 zoomOut = 3 nextCamera = 7 prevCamera = 8 yawLeft = 6 yawRight = 5 pitchUp = 0 pitchDown = 1 seekHome = 4 } } PAGE { name = extcamF button = buttonR7 text = Your Name for Camera #6 BACKGROUNDHANDLER { name = JSISteerableCamera method = RenderCamera showNoSignal = true buttonClickMethod = ClickProcessor buttonReleaseMethod = ReleaseProcessor pageActiveMethod = PageActive cameraInfoVarName = MFDEXTCAM skipMissingCameras = true cameraTransform = ExtCam6 fovLimits = 20,5 zoomRate = 5 showTargetIcon = true iconPixelSize = 32 targetIconColor = 255,0,255,128 homeCrosshairColor = 255,0,0,255 pitchLimits = -45,35 pitchRate = 15 yawLimits = -45,45 yawRate = 15 // Buttons: zoomIn = 2 zoomOut = 3 nextCamera = 7 prevCamera = 8 yawLeft = 6 yawRight = 5 pitchUp = 0 pitchDown = 1 seekHome = 4 } } PAGE { name = extcamG button = buttonR7 text = Your Name for Camera #7 BACKGROUNDHANDLER { name = JSISteerableCamera method = RenderCamera showNoSignal = true buttonClickMethod = ClickProcessor buttonReleaseMethod = ReleaseProcessor pageActiveMethod = PageActive cameraInfoVarName = MFDEXTCAM skipMissingCameras = true cameraTransform = ExtCam7 fovLimits = 20,5 zoomRate = 5 showTargetIcon = true iconPixelSize = 32 targetIconColor = 255,0,255,128 homeCrosshairColor = 255,0,0,255 pitchLimits = -45,35 pitchRate = 15 yawLimits = -45,45 yawRate = 15 // Buttons: zoomIn = 2 zoomOut = 3 nextCamera = 7 prevCamera = 8 yawLeft = 6 yawRight = 5 pitchUp = 0 pitchDown = 1 seekHome = 4 } } PAGE { name = extcamH button = buttonR7 text = Your Name for Camera #8 BACKGROUNDHANDLER { name = JSISteerableCamera method = RenderCamera showNoSignal = true buttonClickMethod = ClickProcessor buttonReleaseMethod = ReleaseProcessor pageActiveMethod = PageActive cameraInfoVarName = MFDEXTCAM skipMissingCameras = true cameraTransform = ExtCam8 fovLimits = 20,5 zoomRate = 5 showTargetIcon = true iconPixelSize = 32 targetIconColor = 255,0,255,128 homeCrosshairColor = 255,0,0,255 pitchLimits = -45,35 pitchRate = 15 yawLimits = -45,45 yawRate = 15 // Buttons: zoomIn = 2 zoomOut = 3 nextCamera = 7 prevCamera = 8 yawLeft = 6 yawRight = 5 pitchUp = 0 pitchDown = 1 seekHome = 4 } }

I'm fooling around with the configuration file for the External Cameras of MFD40x20 (page 07). I've been successful adding pan & tilt functions that others might find useful. So I put some code below. But I would like to display a unique name for each camera, instead of the screen always showing "Viewing ExtCam", ike "Port", "Starboard", "Fore" "Aft, etc. Can anyone recommend a way to modify the file so that each of the eight external cameras can have a unique name displayed? // --------------------Page 07 ----------------------------------------- PAGE { name = extcamAll button = buttonR7 text = Viewing ExtCam showNoSignal = true BACKGROUNDHANDLER { name = JSISteerableCamera method = RenderCamera buttonClickMethod = ClickProcessor buttonReleaseMethod = ReleaseProcessor pageActiveMethod = PageActive cameraInfoVarName = MFDEXTCAM skipMissingCameras = true cameraTransform = ExtCam1|ExtCam2|ExtCam3|ExtCam4|ExtCam5|ExtCam6|ExtCam7|ExtCam8 fovLimits = 20,5|20,5|20,5|20,5|20,5|20,5|20,5|20,5 zoomRate = 5|5|5|5|5|5|5|5 showTargetIcon = true iconPixelSize = 32 targetIconColor = 255,0,255,128 homeCrosshairColor = 255,0,0,255 // Buttons: zoomIn = 2 zoomOut = 3 yawLimits = -45,45|-45,45|-45,45|-45,45|-45,45|-45,45|-45,45|-45,45 yawRate = 15|15|15|15|15|15|15|15 nextCamera = 7 prevCamera = 8 yawLeft = 6 yawRight = 5 pitchLimits = -45,35|-45,35|-45,35|-45,35|-45,35|-45,35|-45,35|-45,35 pitchRate = 15|15|15|15|15|15|15|15 pitchUp = 0 pitchDown = 1 seekHome = 4 } } Please never mind the question. I took a look at how Alexustas does it and am going to give it a try.

Is it possible via game play, tweak or mod, to use SAS to stabilize pitch and yaw only, but allow free-roll? For example, I'd like a vessel in orbit to hold radial-out, and when I introduce a clockwise roll, have it keep rolling (not be stabilised by SAS

@alexustas If you zoom way in on the picture, you will see that there are very faint, white letters, identifying the indicators on the MFD's. The two shown are "DN" and "Pe". Can you or @MOARdV think of how these could be changed to black letters to increase readability? I have looked at every picture file in the game and came up empty.

I tried a couple of them and they worked ok.

Forgive my artistic ignorance, but what's the difference between those with overlay and those without?

@MOARdV. I know you have a feature freeze on RPM while you develop for MAS, but I have a question about the possible consideration for inclusion in MAS. Regarding integration with SCANsat; would it be possible to choose to view a map from a different celestial body (instead of just the one that who's SOI you're in)? The "Big Map" in SCANsat has the ability to do this.

He requested testers for ERS. I volunteered but haven't heard any response. I have no reason to believe that he is working on Konquest or any of the other mods, but I hope he considers it. I'm still having a blast with all the recently updated mods. I really wish I knew more about Navigational systems, (VOR, DME, ILS) and all that stuff. It is very complicated (in my opinion). Update: He has confirmed that he is working on ERS. It's not quite ready for testing yet (JSIUtil plugin not fixed yet) but progress is being made.

I think that @Kottabos should take a look at the ASET mods and do one of his very entertaining videos. What do you think?

@alexustas Granted, this is a 17t vehicle with only 3 legs, but you might want to increase the impact tolerance a bit.

@alexustas, @MOARdV Do you know of a method of having two distinct groups of action group descriptions. For example: In an apollo-style ship, One group of actions for the CM and a different group for the LM? I wonder if this is even possible.

No. This was from a mod called Konquest. It was never released or put into beta. The thread is now closed and I doubt that Alexustas is working on this any more.

A trip to a station on Mun, near the equatorial arch. Uses the Mk 1-2 Command Pod as the CM and the ALCOR capsule as the LM. The goal was to land within 500m of the station.

A trip to a station on Mun, near the equatorial arch. Uses the Mk 1-2 Command Pod as the CM and the ALCOR capsule as the LM. The goal was to land within 500m of the station.

Let us know if and how you fix the problem. It will help others. You have an incomplete or improper installation. I suggest you delete the ASET folder and try again. When all of Alex's (recently released) mods are installed, the ASET folder should look like this. I took this screen capture before the official release of the Mk1 cockpit, so "ASETDemoMK1Cockpit" above should read: "Mk1_Cockpit_IVA_Replacement_by_ASET ". Sorry for any confusion

@alexustas WOW! I never would have thought this level of avionics fidelity would be possible in KSP! You, sir are an absolute genius. Are you a pilot IRL?

Similar problems like this occur when ModuleManager is missing. Double check that it is present. Otherwise, check the installation location. GameData-->ASET-->Folders from different ASET mods

This prevents you from accidentally staging your vessel when you press the space bar in another application. I believe that this is a feature of Stock KSP, but you only notice it in ALCOR because of the audible "click" when the switch changes position.

I'm happy to share this new video, featuring this fine new command pod. It's an ALL-IVA tutorial that makes use of the new instruments.

I, too am trying to learn the basics of IVA modification. So when you spawn an IVA (like this) are the textures for the props supposed to show in Unity?

And also, if you have RPM installed, DPAI is integrated, and you can dock from IVA handily.

Good job, sir. I would like to seek the automatic direction buttons within reach of the two pilots. They need to be accessible to the Kerbals who also have the MFDs.