OhioBob Posted May 2 Share Posted May 2 7 hours ago, GoldForest said: @R-T-B I have a bug with Kopernicus not loading, even though it's clearly installed. Did you also install the dependencies -- 000_Harmony, ModularFlightIntegrator, and ModuleManager? Quote Link to comment Share on other sites More sharing options...
GoldForest Posted May 2 Share Posted May 2 10 minutes ago, OhioBob said: Did you also install the dependencies -- 000_Harmony, ModularFlightIntegrator, and ModuleManager? Yes, I did. Quote Link to comment Share on other sites More sharing options...
CashnipLeaf Posted May 2 Share Posted May 2 (edited) 14 hours ago, GoldForest said: @R-T-B I have a bug with Kopernicus not loading, even though it's clearly installed. Here are my logs: https://www.dropbox.com/scl/fo/nr2qg8m6trcl8ihiyjpfq/h?rlkey=xoa5s9gnl8kkikmpl5cg2bjow&st=4oxvc1lh&dl=0 According to the logs, you do not have ModularFlightIntegrator installed, which in turn caused Kopernicus to fail to load. I'd suggest reinstalling Kopernicus and all of its dependencies. Edited May 2 by CashnipLeaf Quote Link to comment Share on other sites More sharing options...
GoldForest Posted May 3 Share Posted May 3 1 hour ago, CashnipLeaf said: According to the logs, you do not have ModularFlightIntegrator installed, which in turn caused Kopernicus to fail to load. I'd suggest reinstalling Kopernicus and all of its dependencies. Strange, because I do have it installed...., I'll double check tho. Quote Link to comment Share on other sites More sharing options...
JonnyOThan Posted May 3 Share Posted May 3 3 hours ago, GoldForest said: Strange, because I do have it installed...., I'll double check tho. You have the folder but it appears to be empty. Quote Link to comment Share on other sites More sharing options...
GoldForest Posted May 3 Share Posted May 3 (edited) 15 minutes ago, JonnyOThan said: You have the folder but it appears to be empty. Yeah, IDK how that happened... Thank you and @CashnipLeaf for pointing that out. Now if I can find out why Rescale isn't working... One problem down at least. Edited May 3 by GoldForest Quote Link to comment Share on other sites More sharing options...
R-T-B Posted May 3 Author Share Posted May 3 (edited) On 5/2/2024 at 1:50 AM, GoldForest said: @R-T-B I have a bug with Kopernicus not loading, even though it's clearly installed. Here are my logs: https://www.dropbox.com/scl/fo/nr2qg8m6trcl8ihiyjpfq/h?rlkey=xoa5s9gnl8kkikmpl5cg2bjow&st=4oxvc1lh&dl=0 I'll have a look in a few hours, thanks for the report. Just to be sure, you are on ksp 1.12.x of some type, correct? We dropped support for anything less some time ago. EDIT: disregard, RTB is slow... lol. Speaking of slow, next release is still incoming, but with work being busy, it may be as late as the end of May. We'll see. Edited May 3 by R-T-B Quote Link to comment Share on other sites More sharing options...
GoldForest Posted May 3 Share Posted May 3 27 minutes ago, R-T-B said: I'll have a look in a few hours, thanks for the report. Just to be sure, you are on ksp 1.12.x of some type, correct? We dropped support for anything less some time ago. EDIT: disregard, RTB is slow... lol. Speaking of slow, next release is still incoming, but with work being busy, it may be as late as the end of May. We'll see. I am on 1.12.5. I have another problem though. I think Kopernicus is stopping Rescale from working. I have Rescale and all the dependencies installed, but the planet is still stock size. I did notice that Kopernicus was throwing a LOT of Null refs. Logs: https://www.dropbox.com/scl/fo/nr2qg8m6trcl8ihiyjpfq/h?rlkey=xoa5s9gnl8kkikmpl5cg2bjow&st=tjxbkfri&dl=0 Quote Link to comment Share on other sites More sharing options...
GoldForest Posted May 4 Share Posted May 4 @R-T-B You can ignore my last message. I figured it out. It was KSP being KSP. I reinstalled KSP's core files and it fixed the error. Quote Link to comment Share on other sites More sharing options...
R-T-B Posted May 14 Author Share Posted May 14 (edited) New in this latest version release-199: 1.) Hotfix an incorrectly functioning sinking-on-distant-worlds workaround. 2.) Fix a spamming OnDestroy in ShadowMan subsystem. 3.) That's it for now. This is not the big Feature release yet, we are planning that by end of May. We just realized the sinking bugfix had a big bug and wanted to smash that sooner. See Known Bugs & Caveats for known bugs. Edited May 14 by R-T-B Quote Link to comment Share on other sites More sharing options...
R-T-B Posted May 23 Author Share Posted May 23 (edited) Big release time. The release notes here are rather large. But it has been in testing for some time, so we consider it suitable for stable usage in the utmost sense. New in this latest version release-200: 1.) The distant body sinking bugfix has been rewriteen by @gotmachine to be nearly zero-overhead vs the previous, soemwhat CPU-heavy version. 2.) Added a new landscatter parameter for scatters, lethalRadius, default 0. Values above 0 add a kill sphere to scatters that kills only kerbals, in meters. 3.) Added a parameter to the RingShader, radiusMultiplier, that effects the multiplier to planet radius for the shadow cast on the rings. 4.) Adds an offset to KittopiaTech's zeropoint for heightmap export. Planet authors may find this useful. 5.) Exposed Atmosphere value shockTemperatureMultiplier to KittopiaTech. 6.) Many many fixes for distant bodies and bugs related to them, especially in terms of scene switching. Again, credit to gotmachine for being invalueable here. Parameters ResetFloatingOriginOnKSCReturn and TrulyMassiveSystem are both deprecated, as they are no longer needed. 7.) Config file generation when one does not exist was moved to earlier, to fix some bugs. See Known Bugs & Caveats for known bugs. Edited May 23 by R-T-B Quote Link to comment Share on other sites More sharing options...
theJesuit Posted May 23 Share Posted May 23 3 hours ago, R-T-B said: Added a new landscatter parameter for scatters, lethalRadius, default 0. Values above 0 add a kill sphere to scatters that kills only kerbals, in meters. Being an avid user of Kerbalism (tagline: many kerbals died in making of this mod) and the many ways for kerbals to die, I approve of more ways to have Jeb KIA. Thanks for the update! Quote Link to comment Share on other sites More sharing options...
R-T-B Posted May 23 Author Share Posted May 23 (edited) 1 hour ago, theJesuit said: Being an avid user of Kerbalism (tagline: many kerbals died in making of this mod) and the many ways for kerbals to die, I approve of more ways to have Jeb KIA. Thanks for the update! Stop licking the radioactive rocks, Jeb! On that note, it's been suggested to add a text string explaining WHY your kerbal just died in a popup, lol. Probably will do that in a followup maintenance release at some point. For now, just know, this won't happen unless your planet pack author gets ideas. Edited May 23 by R-T-B Quote Link to comment Share on other sites More sharing options...
modus Posted May 23 Share Posted May 23 (edited) Well, release 100 (almost 2 years ago!) was a bit of an anticlimax (like I said back then) but congrats on number 200, señor @R-T-B! Edited May 23 by modus Quote Link to comment Share on other sites More sharing options...
R-T-B Posted May 23 Author Share Posted May 23 49 minutes ago, modus said: Well, release 100 (almost 2 years ago!) was a bit of an anticlimax (like I said back then) but congrats on number 200, señor @R-T-B! Indeed. We've slowed our release cadence a little since then, but isn't it nice when things are just working and we can focus on fun stuff? I'd like to think so. Quote Link to comment Share on other sites More sharing options...
R-T-B Posted Saturday at 05:52 PM Author Share Posted Saturday at 05:52 PM New in this latest version release-201: 1.) Fix a nullref spam that could occur if a body lacked a scaledspace version. 2.) A few more performance related optimizations from @gotmachine. See Known Bugs & Caveats for known bugs. Quote Link to comment Share on other sites More sharing options...
GuessingEveryDay Posted Saturday at 11:06 PM Share Posted Saturday at 11:06 PM Hey, we got bright terrain again for the biomes on 201. 200 is fine. Quote Link to comment Share on other sites More sharing options...
R-T-B Posted Sunday at 02:37 AM Author Share Posted Sunday at 02:37 AM (edited) 4 hours ago, GuessingEveryDay said: Hey, we got bright terrain again for the biomes on 201. 200 is fine. Can you post a before and after, or even just an after? I think I know what happened but want to confirm. Also, what planet pack, if not stock? EDIT: Cannot replicate, at least in stock. Is anyone else experiencing this? EDIT EDIT: Nevermind, JNSQ. Yep, I know what's going on. Hotfix incoming. Edited Sunday at 03:08 AM by R-T-B Quote Link to comment Share on other sites More sharing options...
R-T-B Posted Sunday at 03:24 AM Author Share Posted Sunday at 03:24 AM New in this latest version release-202: 1.) Fix a regression that caused leprochan valley JNSQ and bright colors in other planet packs (caused by createColors = false not being applied). 2.) Better error message if an orbit icon fails to be applied. See Known Bugs & Caveats for known bugs. Quote Link to comment Share on other sites More sharing options...
GuessingEveryDay Posted Sunday at 09:18 PM Share Posted Sunday at 09:18 PM 18 hours ago, R-T-B said: Also, what planet pack, if not stock? EDIT: Cannot replicate, at least in stock. Is anyone else experiencing this? EDIT EDIT: Nevermind, JNSQ. Yep, I know what's going on. Hotfix incoming. Whoops, forgot to say JNSQ, heh. I've been using it for so long, normal Kerbin looks weird now. Quote Link to comment Share on other sites More sharing options...
Oprissmian Posted 10 hours ago Share Posted 10 hours ago Hello, I seem to get the following error when opening KSP: This happened after installing the newest release, release-202. I don't have any idea why this is happening. Quote Link to comment Share on other sites More sharing options...
R-T-B Posted 8 hours ago Author Share Posted 8 hours ago (edited) 1 hour ago, Oprissmian said: Hello, I seem to get the following error when opening KSP: This happened after installing the newest release, release-202. I don't have any idea why this is happening. This has been cropping up a bit. An outdated version of VertexHeightOblateAdvanced can cause this in Kopernicus. The author has fixed that bug. You can download the update here: https://github.com/jamespglaze/VertexHeightOblateAdvanced/releases Ensure you completely remove the old version, as it breaks Kopernicus's ability to even load, and the directory names have changed. Edited 8 hours ago by R-T-B Quote Link to comment Share on other sites More sharing options...
Oprissmian Posted 46 minutes ago Share Posted 46 minutes ago 7 hours ago, R-T-B said: This has been cropping up a bit. An outdated version of VertexHeightOblateAdvanced can cause this in Kopernicus. The author has fixed that bug. You can download the update here: https://github.com/jamespglaze/VertexHeightOblateAdvanced/releases Ensure you completely remove the old version, as it breaks Kopernicus's ability to even load, and the directory names have changed. Thank you very much! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.