Jump to content

Uwain

Members
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral
  1. Apologies if I gave you the impression that I could troubleshoot this for you... I only meant that I would be happy to share my files or checksums so that you could see if anything jumped out at you. I can't fix this I'm afraid It really looked like the problem was the shaderloader thing but I have tried copying the shader file from my working install and that doesnt help. I also copied the squad folder from my working install and no help. I don't get that error in my working install: [LOG 13:56:30.719] [AddonLoader]: Instantiating addon 'AtmosphereFixer' from assembly 'Kopernicus' [LOG 13:56:30.720] [AddonLoader]: Instantiating addon 'Injector' from assembly 'Kopernicus' [LOG 13:56:30.723] [Kopernicus] Running Kopernicus 1.3.1-7 on KSP 1.3.1 [LOG 13:56:30.759] [Kopernicus] ShaderLoader: Loading asset bundle at path Y:/games/ksp131rp1/KSP_x64_Data/../GameData/Kopernicus/Shaders\kopernicusshaders-windows.unity3d [LOG 13:56:30.776] [Kopernicus] ShaderLoader: adding Kopernicus/Rings [LOG 13:56:31.098] [Kopernicus] CalculateArrayLengthOffset using offset of -8 [LOG 13:56:31.100] [Kopernicus] LoadWholeFile reallocating buffer to 1048576 [LOG 13:56:31.155] [Kopernicus] LoadRestOfReader reallocating buffer to 4194304 I tried looking through the Kopernicus source code - but I learned to program back in the procedural days... I struggle to read all these objects/events. I did consider getting a dev environment setup so that I could step through the code, but fortunately for me the thing worked on my final attempt! You could look into that... but its a bit of messing about. The only thing I have noticed is you said you chose RP-0 in ckan... I actually chose RP-1 (it was added recently)... but it didn't fix my broken installs. I'm only using a 750ti but my video drivers are up-to-date. It's a bit of a puzzler for sure... sorry I couldn't be of any real help. Thanks for those tips... the failed engine starts are pretty annoying - but I wanted a challenge! I've nearly finished my first year and just managed to push a 10kg payload out to 300km... crashing back to Earth. I feel like such a noob! Sub-Orbit-return next!!
  2. tl;dr Kopernicus in CKAN RP-1 build works for me?? Just FYI... I've been fiddling with this ever since first posting... today I did another clean install of KSP 1.3.1 (in another new sandboxie sandbox), started a new game then exited KSP. Using CKAN I checked RP-1 and installed only what was necessary. Fired up KSP and it worked! No Kopernicus error!! The only thing I can think is that my previous clean 1.3.1 installs were being corrupted somehow before I even tried RO/RP/RSS - I can't figure out how though because I'm usually very careful about such things? I did see in the logs that when it wasn't working I was getting the shaderloader error that you reported on discord - so maybe you have a similar problem? Anyways, if there is anything (files, versions, screen shots, logs whatever) I can do to help you spot differences just let me know. All I have to do now is figure out RP-1 :p
  3. Thanks, at least I'm not the only one. Thing is, I wanted to try RSS/RO/RP-0 (or 1) and I thought that was possible with 1.3.1? I seem to remember that 1.3 brought some pretty good changes (brought me back to KSP after a break) that I would miss if I dropped to 1.2.2. Looks like I might have to wait until the mods are all up to 1.5.1 (some of the mods seem to be skipping 1.4.5) I thought this was the place to get my log files analysed and a solution... is there somewhere else I should be posting? Or is Kopernicus 1.3.1 just never gonna work for me? I probably need a bit more patience... I forget other people have lives!!
  4. Lets try this again a bit more formally... KSP: 1.3.1 x64 (tried all DX9, DX11, OGL) Problem: Kopernicus breaks my clean KSP 1.3.1 Mods installed: Kopernicus 1.3.1-15 backport (but same for every 1.3.1 version I've tried) Module Manager 3.0.4 (packed with Kopernicus) ModuleFlightIntegrator (packed with Kopernicus) Reproduction steps: Fresh install of KSP. Run once for initialisation? Start New Game. Close KSP. Add Kopernicus (manually or CKAN) and dependencies to GameData. Start KSP. Start New Game. Black screen with "Loading..." image. Logs: Output_log.txt ModuleManager.ConfigCache GameData.jpg Kopernicus.log Kopernicus.Runtime.log (Only 2 Kopernicus log files so I listed them) KSP.log All these files and the Kopernicus logs folder are in a shared drive (KSP logs) along with a zip with all of the files. Let me know if you need more info or if you have ideas about what I can do.
  5. logs zip (hope this works... bit of a noob at sharing!) Hi I think I am ready for RO/RSS/RP-0 but I do not even seem able to install Kopernicus (is this a sign!?). I can happily add Kopernicus to a clean/new KSP 1.5.1 install - no troubles at all, it creates the log files for the stock planets and everything! Whenever I try to add Kopernicus to a clean/new 1.3.1 I get the "... not able to load custom planetary system...". I think I have tried every version of Kopernicus for 1.3.1 - the logs are from the latest 1.3.1-15 backport. To my untrained eye every version seems to give the same errors. FWIW if I add Kopernicus to 1.3.1 then whenever I try to load or start a new game I get a black screen with planet icons rotating next to the Loading message in the bottom right corner. Also I noticed that I am not able to get to the Settings menu (when I click Settings I get the black screen with planet icons rotating next to the Loading message in the bottom right corner). I would really appreciate help getting this working - would also appreciate pointers for how to troubleshoot this sort of thing for myself - I've read through this thread, reddit posts, github issues but so far I'm stumped... it feels as though there is something missing but I can't quite identify what!! FYI I run my games offline in a Sandboxie sandbox. This does not seem to interfere with 1.5.1 + Kopernicus so I'm guessing it doesn't interfere with 1.3.1 either? I have even tried running 1.3.1 in my 1.5.1 sandbox just in case there was something screwy going on but still no good
×
×
  • Create New...