RocketRyleigh

Here's a question: KWP on a JNSQ Kerbin with Kerbal Konstructs launch sites, and KWP set to point weather data. Will KWP have an issue with the KSC location on JNSQ-Kerbin, and then would the point weather launch conditions get applied to other detected launch sites, like ones added by KK?

Question: As far as compatibility, specifically with Nertea's Near Future suite, do I have the right impression that not all of the Near Future mods require explicit support from Kerbalism? Namely the mods that only add engines etc. The only aspect I can think of that might would be reliability stuff being applied to mod engines, but then I wonder if maybe that gets dealt with through part modules so would be automatic. The TL;DR here is just wondering if things like Near Future Launch Vehicles/Propulsion/anything with mainly/only engines require explicit support, or if it's mainly the crewed/antenna/science/electricity-related parts that need it. Edit: The specific mod breakdown I'm thinking is something like: NF Solar, Spacecraft, Electrical = the ones with some explicit support NF Construction, Propulsion, Launch Vehicles = ones that might not need it NF Aeronautics, Exploration = ones that would need explicit support added which don't have it now Close? Or is it exclusively mods on the list after all?

Dunno why I didn't think of that lol, thank you! I'll just try the last release. Edit: Bingo, thanks! I'll keep my eyes open for both JNSQ and Scatterer's next updates, but Scatterer 0.0772 works fine. Thank you as well btw, I'll check that out! Edit: I am noticing it's not listed on Kerbalism's mod compatibility page, RealAntennas that is. As is I can probably get by - JX2 (which is recommended by JNSQ) is listed as supported by Kerblism.

Same result for me with Scatterer/JNSQ/provided configs. Eve doesn't look completely black now, but like it's barely lit and the colour isn't really apparent. Would I maybe be better off dropping Scatterer until I guess JNSQ updates that on it's end? https://github.com/Kerbalism/Kerbalism/wiki/Home-~-Mod-Support RemoteTech 1.9.5 Supported Note : not yet, support will be back in 4.0 Code integration with the science data system, reliability configs.

I'll give those a try, thank you very much! I'm gonna get to it likely before you'd reply anyways and I'll find out, but along with those configs and JNSQ, all I need installed is the Scatterer mod itself right? It's one of those mods I'm never 100% sure will need external configs, cause some mods seem to provide them (like JNSQ), or like, if I'll still need the stock planet configs or not. Sidenote:

Sorry, I tried to figure out the answer first, and I know CKAN would solve this specifically but no. Having the same JNSQ issue, atmospheres completely unlit/black for a number of bodies. The answer given to the other person asking was to update configs, but I'm not sure where I should be getting them separate from what's inside Scatterer and JNSQ already.

Thank you! I had looked in my save folder once, but I don't always think to check weird file extension types with Notepad++, I think from dealing with Minecraft and obfuscated data and stuff. FYI the setting is called "DSNModifier", so for future reference, you could even just skip messing with the slider, and just start up that save and ctrl+f for "DSN" in the persistence.sfs. I actually slightly misspoke. I was trying to find out how to set up RemoteTech to use with JNSQ such that it's as close to the same balance as the suggested CommNet+JNSQ settings (mainly the x4 DSN range modifier - how to replicate that with RT). But also I'm not using RemoteTech anymore until Kerbalism 4.0 adds compatibility, so I can kick the question down the road lol. Thanks anyways!

So I'd definitely still like to know about how to set up RemoteTech with JNSQ to give the intended balance, but it's not compatible with Kerbalism for now. So new question: How in the heck do I wrangle this DSN range modifier slider, or otherwise set the value, to actually get an exact number I want (like 4.00, for JNSQ)? I managed 4.02 with 120% UI scale lol, but it wasn't easy. IS there even a better way? Or should I be happy with .02 off the mark?

From the JNSQ changelog, it looks like the antenna range modifier was added for RemoteTech. So I'd think that, if for CommNet you're just increasing the DSN range modifier, that increasing RT's Mission Control range would be equivalent since both sets of antenna ranges are already adjusted by JNSQ. I think the important question then, from anyone who knows RemoteTech, is how RT's default Mission Control range compares to the default CommNet DSN range, so I know what multiplier to use. Also just tell me if I'm wrong about everything so far - I know they also model signals/connectivity differently.

Two-part question: Is RemoteTech usable with JNSQ? Assuming yes, if I wanted to get the intended balance etc, would the way to set it up be to disable CommNet and apply the 4x range increase instead to RemoteTech's Mission Control Range Multiplier?

That would've been my first guess at compatibility. BetterTimeWarp seemed inherently more overlapping, but then I was just thinking about any mods adding background anything in questioning PersistentRotation. Works for me though, thanks AGAIN @Gordon Dry. PR is the important one anyways, and I don't really want slow-mo either, it'd just've been for general improved timewarping, but I don't care really.

Quick question: Would/does Kerbalism have any issue with PersistentRotation? And for that matter, BetterTimeWarp? I only wondered about those two because of how much Kerbalism needs to handle in the background, and I don't really know where regimes of processing begin and end in KSP.

To get the thread back on track: Dovahkiin had a question earlier which got steamrolled by my stuff. @Dovahkiin2132Could you go into your Kerbal Space Program folder and find at least the "KSP.log" file? Share it through something like https://pastebin.com/ and give the link, or at least put it in a spoiler (the eye) if you paste it straight to the forum. Logs are usually the best first step. An earlier user was advised to make sure they have up-to-date versions of "ToolbarController" and "ClickThroughBlocker" installed properly when they had the same issue without Kronometer (which DOES work with FAR after all, for the record - just not old versions).

I should've reminded myself the username of the new maintainer, definite faux pas lol. @dkavolis definitely gets all the credit! I think I've just seen you on the forums and my brain saw a familiar name and just jumped to conclusions.

Thank you for the first part, about some KSP session still running - I have seen that before in task manager, just not sure when/why it happens and didn't know CKAN would trip out over it. And I definitely will be using a separated install of KSP, and also do my mods manually. I'm sure you guys get a lot of questions that'd be solved by using CKAN, but I know how to build a modpack, and in my case it's more reliable doing it manually than using the mod manager. Thank you for maintaining FAR as well - I'm just loading my full install for a FINAL test to confirm Kronometer and FAR work together after all. I'll let you know, even if I'm actually the last one learning this. Edit: FAR/Kronometer compatibility confirmed, BUT:

I'm going to stop monopolizing this thread now, but honestly... CKAN Error: Fresh Steam install, only selected JNSQ and FAR to install, accepted dependencies and rejected suggested mods. Rant: My manual install without the mysterious broken Kronometer I got from the first link I found works perfectly though, so I'm just going to play that install and hope CKAN works next time. I might try Gordon Dry's Kronometer link if it will work with FAR for my manual install, but CKAN has been far too temperamental with this specific set of mods since I've been trying to install them. I know CKAN is great, but if it's raining don't tell me it's sunny. It DOES have issues sometimes. Not always end-user error.

Looks like the JNSQ install is now working normally on CKAN, but I'll grab that for a manual secondary install, so thanks. Now I know I had the wrong Kronometer though, so it's all good. Nothing wrong with JNSQ Date on its own.

Thank you LGG, that information is very helpful for future reference. Although it seems that whatever was wrong on JNSQ's side in regards to CKAN was fixed at 5:42 last night, allowing it to show up for 1.12.2 as it should.

Literally the reason I'm here though, I'm not letting that get dismissed lol. Regardless of what you think I missed on CKAN, JNSQ was not appearing as compatible, no checkbox, didn't show up in the compatible filter, without me installing Kopernicus and Kronometer beforehand. Part of the wonderful convenience of CKAN is it handling dependencies etc, so why wouldn't it just let me click JNSQ, click accept, and bring me to the required dependency screen, like mods normally do? I love CKAN for that stuff, and I'm familiar with how it's meant to work from the user end, and it at least wasn't working with JNSQ in this way in the past few days. That's not on me lol - give me a checkbox and I'll click it, accept the dependencies, whatever. Allow me to use CKAN, and I will every time. Edit: I see JNSQ now - I also see the "release date" as 5:42 pm yesterday. Coincidence?

Which is good to know. I'll check out the one linked by Gordon Dry. I was genuinely trying to be helpful with what I thought was an actual issue. I apologize for whatever offense I've given for not knowing how to wrangle the convenient CKAN. Thank you for your work anyways.

I respect you immensely LGG. Part of my entire reason for bringing this up has been the issue I mentioned with installing JNSQ through CKAN, which I always prefer, and have only avoided in this case because of this specific dependency issue with Kronometer. Unless something changed in the last day, JNSQ will not appear as compatible on a 1.12.2 install on CKAN, despite being in fact compatible, and its metadata calls for a "virtual" dependency of Kronometer which is not listed on CKAN, nor actually required by JNSQ, hence why I searched out download of Kronometer on my own. This apparently broken version of Kronometer didn't bother CKAN, and installing it, along with Kopernicus, allows JNSQ to show up as compatible. This is how CKAN behaves with these mods on any 1.12.2 install I've used. I would very much like to install JNSQ through CKAN - how do I do that the correct way, since that way is not obvious? Edit: I missed the mention of Kronometer on CKAN. Thanks for updating it so I am able to use CKAN now, which I prefer... but "Frankly"... nevermind.

UPDATE TO PREVIOUS (IMPORTANT): Alright. It's not ToolbarController or any of that, which is kinda what I thought. The errors about ToolbarController from the other user were unrelated to this issue. I uninstalled Kronometer, made no other changes to the install I described above, and the issue is completely resolved - I can enter the editors no problem. I can add some insight too, that it may be a problem between Kronometer and FAR specifically. Something I noticed after the successful, no-Kronometer attempt - I believe there was no "Custom_FARAeroData.cfg" generated in the GameData folder while Kronometer was installed and the VAB/SPH issue was present, and it's now been generated since I removed Kronometer and the issue stopped. Here are the same logs as before but since the second, successful try without Kronometer: Edit: I just remembered Kronometer packages its own "Kopernicus.Parser.dll" which I didn't remove for my test. I'll do one more test WITH Kronometer with that .dll removed. Sidenote: I don't know CKAN backend, but could THAT be why JNSQ wants Kronometer if you CKAN install, but doesn't list it as a dependency on the JNSQ page? Edit 2: Final verdict(ish): Nope, same result, and once again "Custom_FARAeroData.cfg" failed to generate with Kronometer installed. So the "unable to enter VAB/SPH" issue is specifically caused by the presence of both FAR and Kronometer, with or without Kronometer's kinda superfluous "Kopernicus.Parser.dll". So I think until the conflict is figured out, FAR and Kronometer (and its dependents, like JNSQ_Date) seem to be incompatible. Final note for JNSQ users: Manual install seems the best way to go right now. If you're on 1.12.2, it won't show up on CKAN until you manually install Kronometer (which is not on CKAN for 1.12), and if Kronometer is messing up mods like FAR (or even just FAR), and isn't a JNSQ hard-dependency, leave Kronometer and JNSQ_Date out for now, and manually install JNSQ.

EDIT: Leaving this for context/reference, but my following post makes some of this one pointless in retrospect.

Isn't that a Minecraft mod? Now THAT'd be some impressive integration

Complete edit because I'm an idiot (read further down the mod compatibility page). The question I still have though, if I want KerbalAtomics/CryoTanks, must I manually install since they get bundled with Dynamic Battery Storage as a dependency through CKAN?