Jump to content

Professor K

Members
  • Posts

    30
  • Joined

  • Last visited

Reputation

11 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Is anyone else having an issue with the "self destruct" option on a staged section taking out the parent vessel as well, even though they have been decoupled and are several kilometers away? KSP: 1.12.5 TAC SD: 1.7.0.3 -K
  2. Ah, ok, that actually makes sense. The planet pack has issues with it's height maps (landing is tricky when the altimeter gets to zero, then resets to several hundred meters while the Kerbal Engineer altimeter starts counting into negative numbers). Thanks! -K
  3. What, exactly, does SCANsat base it's map data on? I ask because while it works normally for me on the stock planets/moon, it's not working on some extra moons done with Kopernicus (not made by me, I jut seem to one of the early downloaders of the mod pack). The scanners seem to be working and are showing "Ideal" Orbits in the sensor info, there's jut no map data showing up (Except fora single flag on one) . The mod has some texture issues and I'm trying to help the author troubleshoot but we're not sure what SCANsat is looking at to do so. Mod Pack in question: https://spacedock.info/mod/3273/ExtraKerbin Moons -K
  4. Ran a few quick tests on the update: This seems to be working. I'm not seeing any issues with this now, it seems to be visible right up until it's obscured by the dot that the system puts over all bodies at long zooms. These are not working. Ringer has an SOI of 30km now. It's own ring is outside it's SOI I think I see the issue though. It looks like the SOI is measured from the center of the planet, so Ringer with a radius parameter of 70000 and a sphereOfInfluence parameter of 100000 = a functional SOI of 30000. I believe the sphereOfInfluence setting would need to 170000 to give a functional SOI of 100000. I'll alter the cfg file and test next time I restart the game. EDIT: Yup, that did the trick. You need to add the Radius to whatever you want the functional SOI to be. to get the number for the sphereOfInfluence parameter. I think something went wrong with this. Ringer is visible in the map view (although very bright) but in flight view it's completely black. In the screenshots below, the first is in orbit, the black area behind the craft with the faint white edge is Ringer, from the daylight side. The second shot is landed, again on the daylight side, you can see a slice of ring in the background but none of the surface. Another strange thing I've noticed is some odd behavior with altitude when landing. I'm seeing this on Niermun and Ringer, the screenshots below are from Niermun. When landing the altitude will be deceasing seemingly normally but will reach 0 (ASL or Terrain) while still several hundred meters above the surface, then will suddenly jump up several hundred meters (the gauge, not the craft itself) while the altimeter in Kerbal Flight Engineer will start counting down into the negative numbers. This makes landing somewhat tricky (and gives the MechJeb lander module absolute fits). This was occurring before the update. I was hoping the new Normals would fix it, but no such luck. I'm not certain what the game engine bases the altitude on though.
  5. Greetings! Love this little mod, It's my first time using Kopernicus in a playthrough and something that didn't alter the stock system is exactly what I wanted. I tracked down this thread to report a few issues I had noticed, but @JcoolTheShipbuilderappears to have covered almost all of them already! The one thing Jcool didn't cover... I'm not sure if it's possible/practical to do anything about this. I'm also using Scansat for the first time in this playthrough and the low altitude scanners state an optimal orbit of Niermun for scanning as >34km , however Niermun's SOI appears to be somewhere between 33 and 34km. Is it possible to alter the SOI or is it computed by the game engine based on the body's stats? -K
  6. The new companion checker, while a nice idea, seems to be rather over enthusiastic, if not downright aggressive. To the best of my understanding, not having a companion for a mod simply means no Tweakscale on those parts (PKMC). That's not a "show stopper", save game breaking issue in my book. I didn't have Tweakscale on those parts before and I still won't have it. That shouldn't break anything. And insisting on a companion listed as still in Beta (Multipass) is not a good idea in my opinion either. The really, REALLY annoying part was when it shut KSP down when I clicked OK though. I'd missed the line about doing so shutting KSP down and "OK" means "keep going" to me. There should be an "are you sure?" check on this. KSP take too long to load to not have a check. If this will be the way the companion checker works, can we get an option to disable it? Or at least a "Don't warn me about these mods again" option? -K
  7. Before I open a bug report, has anyone else noticed MechJeb being added to the MicroSat twice? This is the only command group part that this seems to be happening with and if I disable the MechJeb patch that comes with this mod then new instances of the part only have one MechJeb. A check of the craft files shows two "MechJebCore" modules on the ones created before disabling the patch. The patches that come with MechJeb appear to be covering adding itself to the MicroSat, it looks to me like the separate patch is not needed. -K
  8. Very excited for the interstellar travel (when it gets added, that is!) -K
  9. Unless you're planning on adding a lot more parts, I'd keep it as one. -K
  10. Anyone else have the Soil Sample experiment nearly throw a 100 ton base off of Minimus when it extended and hit the ground? I've been looking for a setting for the animation module to stop when hitting something, but haven't found one yet. -K
  11. I know this was an older post, but I don't see any responses and I'm having the exact same issues with the wheels. They seem to have next to no power, no slope climbing ability and a set of 4 of them burn through the 500 unit battery in less than a minute, even with no load on the platform. -K
  12. My download of v2.1.10 seems to be missing a texture file. I'm getting the following error: [LOG 22:38:25.798] Load MU model: StationPartsExpansionRedux/Parts/Rigid/station-5/sspx-dome-cupola-5-1 [ERR 22:38:25.844] Texture 'StationPartsExpansionRedux/Parts/Rigid/station-5/sspx-internal-5-6' not found! The file is not present and I doubled checked the .MU file, it is referencing that texture. I also took a look at the github repository and I don't see the file there either. Can anyone point me to a copy of the missing texture? -K
  13. That's pretty much how I name all of my ships. -K
×
×
  • Create New...