Sovetskysoyuz

Members
  • Content Count

    13
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Sovetskysoyuz

  • Rank
    Bottle Rocketeer
  1. I'm having trouble getting the "send the first probe to another planet" contract to be offered. All of the requirements say "Met", but it stays grayed out in the menu. Any idea what could be preventing it from coming up? I haven't visited any other planets in this career, but I have already accepted an "Explore Duna" contract. Could this be the cause?
  2. Update: I also found that the SVT textures actually do show up when I fly to e.g. the Mun, but they still don't show up in the Map view., and they fade back to the stock texture if I zoom out really far. My ksp.log has lots of this repeating in it: [LOG 11:15:04.931] [OD] <--- ScaledSpaceDemand.UnloadTextures destroying NewMunSurfaceMap00 and NewMunSurfaceMap01 [LOG 11:15:05.796] [OD] --> ScaledSpaceDemand.LoadTextures loading NewMunSurfaceMap00 and NewMunSurfaceMap01 Is this possibly related to the Kopernicus load-on-demand settings, or some sort of memory management?
  3. I'm having compatibility trouble with OPM: with OPM installed, the SVT textures don't show up for any stock bodies. KSP.log with no OPM installed KSP.log with OPM installed (I used a regex to remove the [LOG], [WRN], and similar timestamps to facilitate comparing the two logs) I did notice that, when going into the Tracking Centre, there's a difference in how the stock bodies' textures are referenced: without OPM, it's [OD] --> ScaledSpaceDemand.LoadTextures loading SVT/textures/PluginData/NewMunSurfaceMapDiffuse.dds and NewMunSurfaceMapNormals [OD] --> ScaledSpaceDemand.LoadTextures loading SVT/textures/PluginData/KerbinScaledSpace300.dds and KerbinScaledSpace401 With OPM, it becomes [OD] --> ScaledSpaceDemand.LoadTextures loading NewMunSurfaceMapDiffuse and NewMunSurfaceMapNormals [OD] --> ScaledSpaceDemand.LoadTextures loading KerbinScaledSpace300 and KerbinScaledSpace401 I also found that installing Scatterer fixes the problem; unfortunately, it also makes the game lag too much on my computer, so I can't keep it. OPMVO doesn't seem to help.
  4. Installing this update on my (modded) KSP setup caused it to fail to load any parts other than struts and fuel lines; KSP.log is full of errors like this: [LOG 21:43:53.497] PartLoader: Compiling Part 'ASET/ALCOR_LanderCapsule/Part/ALCOR/ALCOR_LanderCapsule' [ERR 21:43:53.502] PartCompiler: Cannot find Part of type 'PartTapIn' [ERR 21:43:53.502] PartCompiler: Error parsing config [ERR 21:43:53.502] PartCompiler: Cannot compile part This repeats for every part in my GameData. Reverting to 0.1.6.3 cures the issue. I haven't yet tried to diagnose whether it's a mod incompatibility issue.
  5. I believe I've fixed the issue. I was causing it. The chain of events was: Due to my unfamiliarity with Unity, I was editing the IVA cfg file in SquadExpansion/Spaces, rather than a dummy file that I could copy into a ModuleManager cfg When I then created a new cfg file to act as the ModuleManager patch and add the RasterPropModuleComputer module, I didn't realize that Windows was appending a .txt extension after the .cfg that I had typed. This prevented ModuleManager from loading the file. Because the cfg wasn't getting loaded, the game was just loading the stock cfg file that I'd been editing. The RasterPropModuleComputer module wasn't being called out, so any prop function tied to JSIInternalRPMButtons wouldn't work properly. The stock button functions were unaffected because they were already there. After I fixed the file extension, everything seems to be working correctly. Now to figure out how to replace the mediocre texture on the stock control panel...
  6. I'm trying to make an IVA for the new KV-1 pod. So far, I'm able to get ASET props to show up in the game, but I'm running into an issue with all of the SAS push-buttons: clicking on them plays the button-press sound, but the selected SAS mode doesn't actually change. I've compared the .cfg file I've made to the .cfgs for the Near Future pods, which have the same buttons working correctly, but can't find any differences. This is my first time using the Unity editor and PartTools, so I assume that I'm missing some necessary step after spawning the props and positioning them where I want them. Update: I checked my ksp.log and found a bunch of errors of the forms "Cannot find an InternalModule of typename 'JSIInternalRPMButtons'" and "[InternalProp]: Failed finding module JSIInternalRPMButtons for method ButtonSASModeStabilityAssist". More investigation is required.
  7. When I tried it, everything looked OK except for the labels for the Mission Elapsed Time and Mission Name screens at the top of the wall, which were upside-down. Everything on the actual control screens was fined. This was with the ASET props, not the default RPM screens.
  8. I ran some tests on the Launchpad with newly-build rovers, and the normal-sized docking ports wouldn't work, but the Junior-sized ones do. DPAI didn't think the normal-sized ports were pointed at each other, when they were clearly aligned. It seemed like they were 90 degrees off in one axis. Perhaps the new docking port model has a coordinate swapped somewhere?
  9. The bug is specific to DirectX, and doesn't seem to be affecting OpenGL, so RPM works fine on Mac and Linux, as well as on Windows if running in OpenGL.
  10. Make sure you do the mission while remaining inside a box the rough size of the capsule.
  11. What about using the EVA suit lights?
  12. You're doing better than me… I can't get ScanSat to work with RPM either, even using the dev build. Is there an RPM-specific patch for ScanSat that I'm missing?
  13. Apple keyboards have both keys labelled as Delete, thanks to thirty-plus years of Being Different.
  14. 1st: Mun Rovers: Dangerous at any speed.