Jump to content


  • Posts

  • Joined

  • Last visited


1 Neutral
  1. EVS 2.2 is not working for me in KSP 1.12.1. 3142 windows player. It hangs during start-up, and never finishes loading. EVS is very helpful, I hope it can be made to work somehow. Last few log entries are: [LOG 13:37:01.447] CodeAssetLoader: Compiling all code assets [LOG 13:37:01.453] ExperienceSystemConfig: Added Effect 'DeployedSciencePowerSkill' to Trait '#autoLOC_500103' [LOG 13:37:01.453] ExperienceSystemConfig: Added Effect 'DeployedScienceExpSkill' to Trait '#autoLOC_500105' [EXC 13:37:01.479] NullReferenceException: Object reference not set to an instance of an object GameDatabase.CleanupLoaders () (at <a5c262f7fe724eb9918d4487db8b635e>:0) GameDatabase+<CreateDatabase>d__71.MoveNext () (at <a5c262f7fe724eb9918d4487db8b635e>:0) UnityEngine.SetupCoroutine.InvokeMoveNext (System.Collections.IEnumerator enumerator, System.IntPtr returnValueAddress) (at <12e76cd50cc64cf19e759e981cb725af>:0)
  2. Problems with EL 6.6.2 and KAS. And wish list. I am having difficulties with Extraplanetary LaunchPad 6.6.2, on KSP 1.7.3. With EL 6.1.0, it is my practise to build a part (typically on an orbital dock), then finalize it, but never release it. Instead I send out my engineer, to KAS the part where I want it. I am then able to re-use the orbital dock (EL Pad) to build another part. Under EL6.6.2, this does not work at all, in that while my engineer can KAS the part elsewhere, the EL GUI insists I must release the moved part (which then floats on nothing) before building another, then makes the first KAS-ed part disappear when the second is finalized. When I release things as EL 6.6.2 wants, they can float or slide off the dock before I can get my engineer out. I find this behavior unacceptable, and so have stuck with EL 6.1.0. This means I am behind on the other upgrades, but it really has to work with KAS better. Note: I said part above, when I really should said ship. This is because it is frequently my practise to build single parts and KAS them into my base. Which means I have a whole bunch of single part ships in the SPH and VAB inventory. Support for single part build would be nice. Also, in EL 6.6.2, unlike 6.1.0, the right-click menu on the orbital dock no longer has the "show UI" or "rename pad" options. The app button still works. But re-naming pads is important. Especially if one is as fond of building orbital docks with orbital docks as I am. In 6.6.2 and 6.1.0, when the EL survey station is present is appears as a fictitious 'pad' appears in the GUI. This without and survey sticks deployed or even present. Then a "might explode" warning appears, and the new finalized part appears in a random spot, with potential explosions. This appears to be two problems - a) a survey station is never a valid build pad, only a deployed survey stake and (b) the default naming of all ELpads as "pad-X" can be confusing, try naming them 'orbital dock' or 'launchpad' or 'survey stake' But a good point of EL 6.6.2 over 6.1.0 is that does not forcibly filter anything with ELworkshop or RocketParts into the EL Items category within the DLL. Module manager should be used for that. More cfg configurable options for EL in the settings would be helpful. (E.g. disable survey station and stakes; recycler recipe) In summary, these days I can not imagine building my base without EL and KAS. But I will stick with EL 6.1.0 until the new release works better with KAS removal instead of release. Thank you for the mod.
  3. Hello. Problem with fresh install of KSP on windows 10, no mods or expansions. When in full-screen mode, whenever in flight, the ASL/AGL altimeter main display is blank. See snapshot at https://drive.google.com/open?id=1ph1IguanScjLilryfzJZjJU-zAPNrJju Problem seems to disappear when not in full-screen mode. Changing UI scale to 110% also appears to fix it. KSP.log file here: https://drive.google.com/open?id=1Nff0AHqt2aSdgQIwYbwNt1mNQ0iI4V-F Graphics data from KSP.log: OS: Windows 10 (10.0.0) 64bit CPU: Intel(R) Core(TM) i5-3570 CPU @ 3.40GHz (4) RAM: 16270 GPU: Intel(R) HD Graphics (912MB) SM: 50 (Direct3D 11.0 [level 11.0]) RT Formats: ARGB32, Depth, ARGBHalf, Shadowmap, RGB565, ARGB4444, ARGB1555, Default, ARGB2101010, DefaultHDR, ARGB64, ARGBFloat, RGFloat, RGHalf, RFloat, RHalf, R8, ARGBInt, RGInt, RInt, BGRA32, RGB111110Float, RG32, RGBAUShort, RG16, BGRA10101010_XR, BGR101010_XR, R16
  4. KIS 1.7 is seriously breaking and crashing in KSP. 1.6.1, suggest no one use it. A) Module KISCollider added to ship.craft files breaks backwards compatibility. B) Possibly related , ships with parts like engines pre-attached (e.g. via KAS) directly to docking ports separate violently on switch to ship. C) Possibly related crashes disappear with down-grade to KIS 1.6 D) Suggest setting.cfg option to disable KISCollider use and inclusion in ship.craft files.
  • Create New...