Sigma88

I've already stated this multiple times in the past but I'm going to repeat myself. If you have any kind of problems while using a planet pack + kopernicus you should report your issues to the developers of the planet pack. We can't be expected to fix all the problems that arise from the use of all existing planet packs. this topic should be used to discuss kopernicus and the problems of kopernicus itself, not those caused by third party planet packs over which we have no control. thank you everybody for your understanding if you want to read more about why this is the case or how you can produce a useful bug report here are some links:

depends on what you mean by "work" usual rescaling issues will apply, but KKtoSD should be able to solve the majority of those

I'll take a look later today Thanks for reporting it

it gets worse with kopernicus if you add planets outside the orbit of Jool you can find my official bug report here

ok, I've managed to write a plugin to add scatterer compatibility to SD I've opened a github issue and pinged you there, if you can take a look I would apreciate your opinion since I have literally zero knowledge about scatterer

The bug is still there You can easily check it out since it is a KSP bug that does not require kopernicus

@Galileo I was looking to your cfgs and I noticed that you had to add extra code to account for some SD shortcomings. I'd like to add some code to SD in order to enhance compatibility and reduce the fiddling required for a very basic rescale. specifically, I am referring to your code for EVE and scatterer and stock antennas is there something specific I should know about those mods when looking to add compatibility?

-

step 1 a new version of KSP comes out step 2 people with no patience pretend suff for free and, when they don't get it, hell ensues step 3 once things get out of hand, a moderator (usually @Snark) swoops in to save the day and deletes all messages step 4 repeat from step 1

this issue has been fixed on the latest kopernicus release (1.3.0-6)

in the ksp install directory you can find a "Logs" folder, inside there's a "Kopernicus" folder, inside there are logs from all bodies. the tidus log will most likely show what is going wrong.

Please report planet pack issues on the planet pack's thread, not here

as far as multiple light sources, I can confirm they work even using curves both on planets and ships

this is not a kopernicus issue, it's most likely caused by the planet packs you are using. it might be because you didn't install "RSS-Textures" but that's just a guess, you should ask for support to the developers of the planet packs you are using

if you click the nyan cat in my sig you will find a guide describing what wee need you to provide us in order to provvide support

@EricL intensity curves are a custom feature from kopernicus so the stock sun doesn't have one @OhioBob scaled space is actually 6000 smaller than what the numbers say (for some reason) so if you have to guess a scale in the future, 6000 should be your first guess (Btw, I had no idea as well until I tried a couple of days ago) EDIT: regarding the vessel question, I don't know if it's possible to have a craft illuminated by more stars, you can try removing the curves and use two stars with different colors, if the craft is illuminated by both stars it should be obvious then

Those curves will probably require more than 2 key defined If you want to see what your curve looks like I suggest trying this mod:

is this a custom system you designed or is it a planet pack developed by someone? if so please report this issue to them, they'll know what to do EDIT: I guess it's for your mod your problem is that with the new kopernicus planets can be illuminated by multiple stars. by default each star has an infinite range, so that's why your planet is illuminated by both you need to add inside the Light node of every star an intensity curve in this post thomas explained the syntax PS: for the distance, take the amount of kilometers you want and divide by 6

to reparent kerbin you can't change the referencebody for KSP reasons but you need to add this node inside kerbin's body node (just after the Orbit node is fine): PostSpawnOrbit { referenceBody = Cavran }

I don't think OR have ever worked in HAS

did you manage to reproduce this issue without the planet pack in question? if you are getting the bug on a stock install with only kopernicus, MFI and MM it would help a lot narrowing down the culprit In any case, I'll need you to find the minimum amount of mods that causes the bug, then click the nyan cat in my sig. you'll find a list of files that we need to debug issues. upload those and we'll take a look as soon as we have some time

the point is that an end user should report the issues to the planet packs developers who in turn will check if the issue is caused by their mods (example, weird soi boundary that makes orbits freak out) if the planet pack dev finds out that the problem is caused by kopernicus, then he will report the issue here. otherwise we end up with a bunch of reports that are caused by errors in planet packs, which makes us less likely to see the real Kopernicus issues and since we have a limited free-time, if we waste the majority of it to debug issues caused by planet packs, the progress on kopernicus will of course be slower

are you using any planet packs? if you are, you should report this issue to the devs of that planet pack if you are not, click the nyan cat in my sig and upload the rest of the files listed there