Jump to content

R-T-B

Members
  • Posts

    2,017
  • Joined

  • Last visited

Everything posted by R-T-B

  1. If it's any consolation, I have a much cleaner approach that does not involve actually running the kerbalism sim I will be working on today. We will still be borrowing some ideas but running the full sim was excessive, and unnecesary. You basically called it.
  2. I'm in agreement after a morning lookover. I am rolling back this release for issues with Kerbalism amongst other mods. If you installed it via CKAN, I would advise a revert. I do apologize, it is the bleeding edge I know but this doesn't even meet those limited standards. It just needs to work better with other mods than this. I have a better idea of how to approach this. Expect a release without the compatability bugs soon. Even if it seems to be working well with third party solar panels, the issues with Kerbalism are enough to justify a different approach. Thanks for testing.
  3. Performance issues or heating/EC generation not working as expected, mainly. I am already aware that this may not work well with some third party solar panels. The Kerbalism devs have been kind enough to provide some pointers there, so there should be a bugfix release for that soon. PS: Some old craft may show errors during the loading process about a missing module or similar in next, or maybe even present release. This can be safely ignored.
  4. The big solar heating fix milestone has finally dropped. This release fixes the heating bug in multistar as well as many solar panel issues, but it's interactions with other mods right now are unknown and untested. It also may have some bugs of it's own. But this is a MAJOR MILESTONE in that the solar panel heating code rewrite is feature complete. This release integrates a lot of solar code from Kerbalism, so interaction reports with that mod in particular are appreciated. You do not need Kerbalism installed to use it, but the contributions of Kerbalism devs work in making this release possible should not go unapreciated. Please test this so we can get it to stable as fast as possible and move on to comets and better things. Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 47 R-T-B released this 6 minutes ago This is R-T-B's "Bleeding Edge" branch of Kopernicus, intended to support the latest features, KSP editions, and also the latest bugs. Please keep in mind this branch may be more buggy than Prestja's mainline Kopernicus branch, but it also supports more KSP versions and has more features implemented for testing reasons. Many features that make it into mainline Kopernicus are born, tested, and trialed by fire here. This is release 47. It contains the following changes: 1.) This is the big release that fixes the heating bugs with multistar! It does this and also fixes the crazy-level buggy multi-star solar panel implementation, by importing code from Kerbalism. Effectively, we are running a stripped down version of Kerbialism internally now that only does the solar math stuff (this is possible since Kerbalism is Unlicense licensed, but I will respect the devs wishes if they object to this, of course). Obviously this needs testing, as I'm unsure how well it will work in it's first release! Give credit to the amazing Kerbalism devs for their contribution here! I don't think I could have done it without using their code as a base, frankly. It should not interfere with stock kerbalism. 2.) Rings were not visible from within atmospheres. An experimental fix for this has been deployed as well. Known Bugs: 1.) None known right now, but given the beta state of this release, don't be afraid to report any you find! There probably are a few! Please download the right output zip for your version. "191" zips are for 1.9.1, "1101" for 1.10.1, etc. Thanks and as always, report bugs! -RTB
  5. The stable branch of Kopernicus, supporting only 1.9.1 at the moment, does not require you to add anything. Some day that branch will support 1.10.1 and this question will be less important, but right now, we are still waiting on some features before declaring it "stable" for 1.10.1. That's odd. Can I get a KSP.log from you? We had a similar bug many moons ago but I thought it was completely squashed. Curious for sure.
  6. No, doing what is suggested reverts to stock single-star solar code, which is bugfree more or less and works with all part packs, but does not support more than one star.
  7. Thanks! This will be in next release (and credit you), which should be out in a few days... Unfortunately still not the final 1.10.1 release with the heating and comet fixes, but it's going to be a small bugfix release and your translation will fit in nicely with that. If you ever wonder where to make a pull request, just use github.com/R-T-B/Kopernicus, the latest version branch you can find (right now 1.10.1). That's normal procedure and bleeding edge always runs tests on things before we push to stable. Yep, JNSQ works pretty good with it actually (I play a game with it when I find time).
  8. I'll need a log file to help further (problem description would help too). You can find one in zip form in <Game Install Folder>/Logs/Kopernicus or in your game folder as KSP.log. Thanks.
  9. I have seen this reported once before, and I unfortunately have no idea what caused it in the end, but the user fixed it with a reinstall of the game. It seems to trip up on Moho and then the KopernicusStar.LateUpdate exception spams, is the common symptom. I wish I knew what caused it but as of now, all I can say is try uninstalling things one by one and then if that fails, reinstall KSP and try again. It worked for at least one user. If you can isolate a mod that causes it, please do report back. This is great news to hear someone finally figured this out! I'll see if I can't resolve the conflict in the next maintanence release (now overdue, but work is making everything slow. It will be out... soon, I think).
  10. Is it the bug where you can't click anything? If so, you can still use arrow keys on your keyboard to navigate. I've yet to figure out what causes this, and it does not happen to everyone, making it further confounding. If you have a log file, I'd appreciate it.
  11. Probably an OpenGL shader bug. I'll ping @blackrack, he's the author of the ringshader and I don't know how to fix that beyond yelling at him for help (sorry man... lol).
  12. Yeah, that sounds like a good idea. I'd reinstall and start from a clean slate since from your log, it seems like maybe the base Moho config is corrupt, which definitely should not be happening.
  13. No, stock does not ship clouds but the base textures are better than SVT/SVE. You can use something like Eve's baseline config, or maybe spectra to provide clouds (I'd advise Spectra as it's pretty and has decent performance). I'll look at what else is wrong in the morning, sorry for being so slow to respond to you I just have a lot vying for my attention.
  14. Thanks. SVE (StockVisualEnhancements) is the origin of your issues. It is not compatible with the latest releases... you aren't missing much though, as the new effects introduced in stock 1.9/1.10 are actually better than what it offered.
  15. Thanks for this. Bug seems to be with stock system then, but I am unable to replicate. Can I see your gamedata folder please? Screenshot will do. I'm going to readd the ability to use the stock asteroid generator next release as an optional setting. The Kopernicus one is customizable, but breaks sentinel contracts as you noted. It will be replaced longterm, but for now, options are better than just forcing people to use a somewhat broken system. The solar panel code is undergoing a complete rewrite right now, with your complaints amongst numerous other being the chief reasons (the other reason is it's really really buggy). When it is replaced, it will be far more friendly and less annoying than the current implementation. This will all be released sometime tomorrow as another "interim patch" before the big heat bug fix (the bug with multiple stars not applying heat properly).
  16. SVT is broken now due to something I haven't been able to track down, and little will to do so given it's obsolete anyways. Thank you for identifying it happened on the release of version 45 on bleeding edge though, that at least narrows it down. I'd still use the latest and uninstall SVT though, even stock textures at high+ settings are better now.
  17. Yep, I bolded that in the release notes but some people missed that... heh. Happens. That looks like it should work... maybe somethis is wrong with the modulemanager syntax. It has to work in some form or system replacement mods would fail to remove bodies. Try something like this, maybe: @Kopernicus:AFTER[Kopernicus] { !Body[Dres] {} } BTW, why u hate Dres? It's just a potato. Everyone knows it's not a planet. Thanks. It's bugging out on Moho. What planet pack are you using? In your logs/Kopernicus folder somewhere, there should be a Moho.log file with the specific cause of the error. Can I get that?
  18. Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 46 R-T-B released this 12 minutes ago This is R-T-B's "Bleeding Edge" branch of Kopernicus, intended to support the latest features, KSP editions, and also the latest bugs. Please keep in mind this branch may be more buggy than Prestja's mainline Kopernicus branch, but it also supports more KSP versions and has more features implemented for testing reasons. Many features that make it into mainline Kopernicus are born, tested, and trialed by fire here. This is release 46. It contains the following changes: 1.) Land scatter cull range has been reduced to approximately 7.25km. This offeres reasonable performance boost without losing much of anything noticeable. It is still configurable in Kopernicus_config.cfg as per usual. 2.) Packaging changes to MFI dependency so CKAN users have an easier time installing. You may need to uninstall your old Kopernicus and reinstall via CKAN, this is mostly to make new installs easier via CKAN. Known Bugs: 1.) Solar flux (heat) is not applied to the vessel if you are orbiting a non-center/root star. EC generation still works on solar panels, though. This is an old bug we are just now being made aware of and is mostly applicable to complex systems with multiple stars. We hope to fix it by next release. Please download the right output zip for your version. "191" zips are for 1.9.1, "1101" for 1.10.1, etc. Thanks and as always, report bugs! -RTB Please note the bold text above. CKAN users will most likely need to uninstall/reinstall the mod to proceed, but after that it should be much smoother to maintain.
  19. I'll need a KSP.log file (in install root) and/or a screenshot of your gamedata and Kopernicus folders to say what's going on.
  20. I've noticed the culler system sometimes spits out exceptions with scatters enabled. It's not harmful, but I will try to do away with the logspam at least with a try catch or similar in today's release on the bleeding edge (coming soon). EDIT: Oh wait, you said WITH scatters disabled same error? Then you are experiencing something different, and likely parallax related, sorry for the confusion.
  21. I actually made a rough JNSQ pack from the parralax stock textures for Parallax and I agree. I love parallax but using the stock textures as I did takes something away from JNSQ. Though flat, the original stock textures are pretty well thought out. Plus they perform well.
  22. He means the weird bundling system on Kopernicus BE where at least, until tomorrow when I plan to change it, included it's own ModulerFlightIntegrator and refused to install if you already had it installed. It was an old work around for when MFI wasn't listed as 1.10.1 ready, which has been fixed. Tomorrow I'll fix the install process as well. That should REALLY prevent confusion.
  23. My plan is to make an interim release with a few small bugfixes (mostly performance related, nothing major) and removal of that old remove-dependency thingy tomorrow, so I'll hold off on editing since it would be irrelevant in 24 hours. I'll do an edit with new instructions then. As for the "big release" that fixes the heating bug. Soon, but not tomorrow, sadly. Maybe. The code that handles asteroids/comets is... weird. It's been changed a lot lately on the bleeding edge and we finally just decided it needs a rewrite rather than trying to fix something that seems eternally broken. I can't really advise other than say it will be better soon.
  24. I can't say what CKAN is thinking exactly. I just know if you back out by uninstalling Kopernicus and ModularFlightIntegrator in their entirety in CKAN, and then attempt to install Kopernicus BE, it generally works even with the present workarounds. If you have it working though, I'd just go with it.
×
×
  • Create New...