Jump to content

OrbitalManeuvers

Members
  • Posts

    1,563
  • Joined

  • Last visited

Everything posted by OrbitalManeuvers

  1. I finally took the time to document what's happening with my launch pads not retaining their color settings when using the JNSQ color preset (on JNSQ, needless to say). Maybe this is all already known? The steps to reproduce are: Edit the launchpad and select the JNSQ color preset Save the pad, Save All At this point, with the game still running, the pad looks correct, and the .cfg has been properly updated. Exit and Restart KSP The results of these steps are that the file has been properly updated, but the color is not loaded/not used on restart. Here's the (only) diff that occurs when selecting the JNSQ preset (changed version on the right) After restart the color is back to being wrong. Screenshot shows editing the previously-edited pad. You can see the grass color from the cfg is not used. Editing the grass color with the Grass Editor results in essentially the same thing - the changes are written to the file, but apparently not loaded on the next restart, since the color always reverts. The same thing happens on the NearGrassTexture setting, when changed from the UI. The file gets updated with the new value, but upon restart and editing of the pad, the new value has been lost. So in the end I don't think this is specific to the JNSQ preset. Any ideas?
  2. btw, since you have Gemstone, I thought I'd recommend these as well:
  3. cool, you found it. So tbh, I don't think debugging solar system basics should be done on a heavily modded install. My personal approach is to build the solar system first, before anything else. It's just a super basic component of the game, and I like to make sure it's solid. That said, in terms of working with your current install, I think your best bet would be to simplify your Kopernicus load considerably, and see if you can get a basic install of KSRSS working. Meaning, I would ditch the following mods, at least temporarily: Parallax, KSRSS-64k, KatnissCape, Kop Expansion, and anything/everything with "RSS" in the name. But I honestly think that a better use of your time would be to get CKAN to create a new, second instance for you, and install just KSRSS and its immediate dependencies, and try an empty install with only KSRSS. This will give you confidence that it works (which it does) and then you can add things on top of it, a few things at a time, and test along the way as it gets built up. That way if something goes wrong you know for 100% that it's in the last "batch" of things you added. All just one person's opinion
  4. You might make a mental note of where you found that. From what I've seen, there's only one mod author who prefers that file. The file you want is ksp.log, and it will be sitting next to the main ksp executable, ksp_x64.exe. It's in the folder that also contains the GameData folder. I think Steam takes you right to that folder if you ask it to browse local files.
  5. Make absolutely sure that you're on the latest release. This used to be an issue many moons ago, but isn't any more.
  6. Is this on purpose? Empty file added0 ModularLaunchPads/Compatibility_Patches/MLP_MAS_Fix.cfg Empty file.
  7. The best way to get help is to upload your ksp.log file to a file sharing service like google drive, and provide the link. Otherwise you're asking for people to guess among a trillion different reasons why a mod might not be installed correctly. For a catastrophic install issue like this, the log file should contain the answer with no guessing needed.
  8. GameData\KSRSS\Configuration.cfg has this option. It defaults to the scale you want, so nothing should be required.
  9. You have version 2.13.0 of B9PartSwitch, but the current version is 2.20.0. https://github.com/blowfishpro/B9PartSwitch/releases
  10. The file named ksp.log is located in your main KSP folder, along with ksp_x64.exe. You won't be able to copy/paste the whole thing into a forum message, so you need to use a file sharing service like google drive to upload the file, and the provide a link to it here. It's important to provide the entire file, and not just snippets.
  11. The OP has a spoilered section with KSPedia images - a couple of them are about snack production.
  12. ksp.log is in the main ksp folder, which is the folder just above GameData, along with ksp_x64.exe. Google drive is a good solution for file sharing large files like the log file, as they can't be pasted in a forum message.
  13. ooh weird. Were you using scatterer 0.772? And maybe your tufx profile needed tweaking? I remember I needed to desaturate a little overall to get the grass to not be neon green. There was also a while where a colorfix.cfg was needed with certain Kopernicus versions. Anyway, that's a bummer it didn't look good on your system. Luckily it looks great on mine, without me doing anything except eve/scatterer and a couple decent tufx profiles.
  14. https://github.com/Profiremu23/RescaleContinued/releases use this link, but look near the bottom of the page where it says "Source Code (zip)" and download that link instead. It has all the versions in it, so be careful what you install. But in good conscience, I gotta add that JNSQ is a far better choice than stock + 2.5 rescale, primarily because of better textures and more planets.
  15. For sure one thing you need to do is get rid of the extra module managers. In the root of the GameData folder, you should have only modulemanager.4.2.2.dll, none of the previous versions. It's possible that will fix your issue, but if not, please consider posting a link to your ksp.log file.
  16. Hey just mentioning, in case you're seeing what I did at first, too -- which is that nothing updates on existing parts - you need a completely new engine mount part dragged from the part tray. Ignore me if you've tried this
  17. Welcome to the club For me the thing that sealed the deal was Minmus. I distinctly remember thinking "this doesn't look like a toy any more!" and I was hooked. JNSQ was my gateway drug to 2.x scale. Impossible to go back now.
  18. I am not one of the mod maintainers. My install has clouds. I've just synchronized this morning and the only change compared to what I had before was the new normals file for Earth. So I know the latest changes didn't break anything with clouds (that would be weird anyway) If you're open to a suggestion ... I would try removing the 64k texture folder. That's one thing I don't have.
  19. congrats. I saw your message and wanted to answer but my answer would have been a guess since I don't use parallax in my KSRSS installs. Can I ask, did the solution have to do with deleting a stock textures folder? That would have been my guess How does it perform for you? For me it's too much for my wimpy card and I don't know which settings to change to reduce quality - so I only use it in my stock install.
  20. puzzling. if you can upload ksp.log somewhere we can at least rule out simple install issues
  21. It does indeed. Running Eve 1.11.7.1 btw. If you have any other Eve configs laying around (like boulderco, etc) I would not expect that to work.
×
×
  • Create New...