[1.8.x-1.12.x]R-T-B's Kopernicus Unified "Bleeding Edge" Branch[REACTIVATED]

[Kwebib]

Wow, that's incredible! Great work.

[ffx]

look the same

[R-T-B]

1 hour ago, ffx said:

look the same

FPS is in the upper left corner.  It's not a visual difference, it's the same scene with better performance.

Edited January 19, 2021 by R-T-B

[R-T-B]

Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 62

R-T-B released this now

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 62. It contains the following changes:

1.) An additional fix for a regression in which scatters may under some circumstances levitate has been applied.  No more floaties.

Known Bugs:

1.) Distant bodies (farther out than Eeloo) sometimes exhibit issues with sinking landing gear. We are tracking this but don't have a fix just yet.

2.) At interstellar ranges, heat can sometimes behave strangely. It is best to turn off part heating when traveling far far away.

3.) The ring shader is broken in OpenGL environments. This is a hopefully temporary setback.

Please download the right output zip for your version. "1.9.1" zips are for 1.9.1, "1.10.1" for 1.10.1, "1.11.0" for 1.11.0, etc.

Thanks and as always, report bugs!

-RTB

Edited January 19, 2021 by R-T-B

[Dark_Noone]

Hello!

Could you guys help me please? I've just installed Beyond home mod, and I'm having am issue with gournd turning black around me on Rhode. I've tried using fix (jnsq stuff) that you guys told a guy like me earlier in this thread, but now I'm stuck in loading screen while launching the game. The  glitch looked like big black squares apearing everywhere I go.

 

[Murdabenne]

Just so I am straight on this, I got lost in the threads: Does the current released stand-alone version of MFI work with the latest 1.11.0 that you posted?  If not, do I need to use your patched version?  And if the latter, is it included with the latest BE 62 or is there a patched stand-alone version of MFI from you?  I'm hoping the MFI stand-alone is the proper one, makes things a bit less complex since I can easily use CKAN for that.

[RyanRising]

30 minutes ago, Dark_Noone said:

Hello!

Could you guys help me please? I've just installed Beyond home mod, and I'm having am issue with gournd turning black around me on Rhode. I've tried using fix (jnsq stuff) that you guys told a guy like me earlier in this thread, but now I'm stuck in loading screen while launching the game. The  glitch looked like big black squares apearing everywhere I go.

 

You should check out this thread. It'll tell you how to troubleshoot your issue, and if it persists, what information the modder will need to understand your issue.

[ss8913]

why does CKAN claim that this mod conflicts with ModularFlightIntegrator?  they *should* work together, yes?

5 minutes ago, ss8913 said:

why does CKAN claim that this mod conflicts with ModularFlightIntegrator?  they *should* work together, yes?

also, (yes I installed the 'bleeding edge' kopernicus), it says "not compatible with this version of ksp" running 1.11; is this intentional?  does bleeding edge mean 1.10 and not 1.11 ?  Will uninstall for now.

[linuxgurugamer]

Not sure if this is a JNSQ or a Kopernicus bug:

With RTB Kopernicus, JNSQ & KSP 1.10.1, the calendar rolls over at the end of the first year, to Y2 D00 instead of Y2 D01.

This is messing up my DatedQuickSaves because the date is wrong in the game.  See this picture for what I'm referring to (look at the date in the upper left):

[Astronomer81]

Hey RTB, Could you find out a way for this to be compatible with every version of ksp and as Mark Thrimm once said "I checked if my craft was causing the drop in frame rate but after some research I found out that kopernicus was causing the drop of frame rate. I hope the developers see to this in the Future", and this was said in a very old video so I also hope ya'll (the developers) see to this (if you can see my comment).

Thanks.

[R-T-B]

22 hours ago, Murdabenne said:

Just so I am straight on this, I got lost in the threads: Does the current released stand-alone version of MFI work with the latest 1.11.0 that you posted?  If not, do I need to use your patched version?  And if the latter, is it included with the latest BE 62 or is there a patched stand-alone version of MFI from you?  I'm hoping the MFI stand-alone is the proper one, makes things a bit less complex since I can easily use CKAN for that.

We are using the current MFI available publically from Sarbian, and the one we advise using is always in the release zip.

Edited January 20, 2021 by R-T-B

[Murdabenne]

14 hours ago, Astronomer81 said:

could you find out a way for this to be compatible with every version of ksp 

Welcome to the wonderful world of KSP+Mods!

I'll save R-T-B at least a part of this answer:

I hate to break it to you, but that's simply not possible. Sometime Unity (the underlying software engine) changes, and the base KSP program or APIs change, and those changes do things that frequently break or interfere with addons, or induce unexpected behavior (bugs), especially for addons that do such fundamental changes to the game at the lowest levels, like this one.   Software in general does not function that way, its simply how things are done in modern software architectures, software engineering, and the software development process.
 

 

Edited January 20, 2021 by Murdabenne
typos

[R-T-B]

16 hours ago, ss8913 said:

why does CKAN claim that this mod conflicts with ModularFlightIntegrator?  they *should* work together, yes?

also, (yes I installed the 'bleeding edge' kopernicus), it says "not compatible with this version of ksp" running 1.11; is this intentional?  does bleeding edge mean 1.10 and not 1.11 ?  Will uninstall for now.

because MFI isn't marked compatible with 1.11, we ship it with the MFI and because of that, you have to uninstall MFI before installing Kopernicus.  Sorry for that, we are working with Sarbian to fix it.

5 minutes ago, Murdabenne said:

I'll save R-T-B at least a part of this answer:

I hate to break it to you, but that's simply not possible. Sometime Unity (the underlying software engine) changes, and the base KSP program or APIs change, and those changes do thing that frequently break or interfere with addons, or induce unexpected behavior (bugs), especially for addons that do such fundamental changes to the game at the lowest levels, like this one.   Software in general does not function that way, its simply how things are done in modern software architectures, software engineering, and the software development process.

 

Yes.  Kopernicus further more really is dependent on the version it was built against, moreso than most mods.  My universal build system makes updates easy, but we still need to "target" a version and sadly, version lock.

13 hours ago, linuxgurugamer said:

Not sure if this is a JNSQ or a Kopernicus bug:

With RTB Kopernicus, JNSQ & KSP 1.10.1, the calendar rolls over at the end of the first year, to Y2 D00 instead of Y2 D01.

This is messing up my DatedQuickSaves because the date is wrong in the game.  See this picture for what I'm referring to (look at the date in the upper left):

This would be a Kronometer config bug, not a Kopernicus one (maybe leapyear related?).  Check your Kronometer config in your JNSQ folder somewhere.

Edited January 20, 2021 by R-T-B

[R-T-B]

I'm looking at whether or not the multistar solar code needs a serious optimization attempt ala what I did with the scatter culler.

How you can help:  I already have some stats, but if you are willing, you can do a "before and after" test by moving solarpanels.cfg out of your Kopernicus folder (thus reverting to stock code) and then moving it back in (using the new multistar code).  Compare FPS and report.  I would appreciate it from anyone willing.  Working on comets now.

[hemeac]

Awesome work on the scatters.  Just had a look at the updated SolarPanels.cfg and see that you are now using a new module rather than replacing the existing ones.  However the patch doesn't catch Near Future Solar's "ModuleCurvedSolarPanel".  The curved solar panels are working in a multi-sun game on Kerbin (ie. charging), but wanted to give a heads up as not sure if they will be working as intended in the scenarios that you were trying to fix.

[R-T-B]

3 hours ago, hemeac said:

Awesome work on the scatters.  Just had a look at the updated SolarPanels.cfg and see that you are now using a new module rather than replacing the existing ones.  However the patch doesn't catch Near Future Solar's "ModuleCurvedSolarPanel".  The curved solar panels are working in a multi-sun game on Kerbin (ie. charging), but wanted to give a heads up as not sure if they will be working as intended in the scenarios that you were trying to fix.

Good catch.  I will patch that next release.  My suspicion is they would freak out if you approached a different star.

[ss8913]

On 1/20/2021 at 10:04 AM, R-T-B said:

because MFI isn't marked compatible with 1.11, we ship it with the MFI and because of that, you have to uninstall MFI before installing Kopernicus.  Sorry for that, we are working with Sarbian to fix it.

Yes.  Kopernicus further more really is dependent on the version it was built against, moreso than most mods.  My universal build system makes updates easy, but we still need to "target" a version and sadly, version lock.

This would be a Kronometer config bug, not a Kopernicus one (maybe leapyear related?).  Check your Kronometer config in your JNSQ folder somewhere.

thanks for the reply - but either way, if I load the bleeding-edge kopernicus in 1.11 at all, I get the poptart cat rainbow thing and the message saying "this will corrupt your saves, not compatible with this version of KSP" - regardless of what I'm doing with MFI.

[hemeac]

Will keep an eye out and can do a test of them in your next release. 

[R-T-B]

5 hours ago, ss8913 said:

thanks for the reply - but either way, if I load the bleeding-edge kopernicus in 1.11 at all, I get the poptart cat rainbow thing and the message saying "this will corrupt your saves, not compatible with this version of KSP" - regardless of what I'm doing with MFI.

Are you downloading the correct version?  There are several builds for each version.  Here, I will link the latest for 1.11.0:

https://github.com/R-T-B/Kopernicus/releases/download/UBE-release-62/KopernicusBE_1.11.0_Release62.zip

3 hours ago, hemeac said:

Will keep an eye out and can do a test of them in your next release. 

Should be sometime soon, this weekend worst case.

[Messeno]

hi currently i play in 1.9.1, on ckan while i install the mod i get this conflict:  , does anyone know how to fix?

starting the game only with the kopernicus and that's it, I get this error

 

 

Edited January 23, 2021 by Messeno

[R-T-B]

You seem to have 1.10.1 version Kopernicus installed.  Uninstall Kopernicus completely, and try again to install it.

[Messeno]

27 minutes ago, R-T-B said:

You seem to have 1.10.1 version Kopernicus installed.  Uninstall Kopernicus completely, and try again to install it.

ok I installed the mod successfully, but now I only see the stock planets is this normal?

[modus]

Depends on which planet pack (and probably which version) you have installed? Kopernicus itself doesn't add anything. What extra planets were you expecting?

[Messeno]

17 minutes ago, modus said:

Depends on which planet pack (and probably which version) you have installed? Kopernicus itself doesn't add anything. What extra planets were you expecting?

ah ok, i don't have any planet pack installed can you recommend any?

[R-T-B]

1 hour ago, Messeno said:

ah ok, i don't have any planet pack installed can you recommend any?

A simple one that changes the stock planets only slightly and is very popular would be outer planets mod. (OPT)

Link.

New release drop as well.  Will be on CKAN shortly:

Kopernicus R-T-B Unified "Bleeding Edge" Edition Release 63

R-T-B released this 1 minute 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 63. It contains the following changes:

1.) A bug in which Solar Rotation Periods were being handled incorrectly has been patched, as well as some other misc bugs. For details, see PR #51 and PR #52 (Thanks @Sigma88)

2.) SolarPanel.cfg fixes to better cover ModuleCurvedSolarPanel, used by NearFutureSolar.

Known Bugs:

1.) Distant bodies (farther out than Eeloo) sometimes exhibit issues with sinking landing gear and deadly terrain to Kerbals. We are tracking this but don't have a fix just yet.

2.) At interstellar ranges, heat can sometimes behave strangely. It is best to turn off part heating when traveling far far away.

3.) The ring shader is broken in OpenGL environments. This is a hopefully temporary setback.

Please download the right output zip for your version. "1.9.1" zips are for 1.9.1, "1.10.1" for 1.10.1, "1.11.0" for 1.11.0, etc.

Thanks and as always, report bugs!

-RTB

Edited January 24, 2021 by R-T-B