Jump to content


  • Posts

  • Joined

  • Last visited

Posts posted by RocketRyleigh

  1. 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?

  2. 29 minutes ago, RyanRising said:

    You could always just use an older version of scatterer, that works alright for the time being.

    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.

    12 hours ago, Spaceman.Spiff said:

    If you want more realistic antennas that work with Kerbalism, RealAntennas is the mod for you. 

    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.

  3. 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?

    12 hours ago, OhioBob said:

    What is not compatible with Kerbalism - RemoteTech or JNSQ?


    RemoteTech 1.9.5 Supported Note : not yet, support will be back in 4.0 Code integration with the science data system, reliability configs.
  4. 5 hours ago, Coldrifting said:

    I've made some configs for JNSQ that work with the latest version of scatterer if you're interested. They should be fairly similar to the default, but no promises.

    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.



    I'd use CKAN but... no more. Tried it just now hoping the outdated JNSQ scatterer config issue would be solved that way, and I don't know if this is just happening for me, but CKAN will not install JNSQ. It just gives me one error or another every time. So back to manual with your configs, thank you again!

    Latest error as I tabbed from this reply if interested:

    About to install:

     * JNSQ 0.10.2 (cached)
    The operation is not valid for the state of the transaction.
    Error during installation!
    If the above message indicates a download error, please try again. Otherwise, please open an issue for us to investigate.
    If you suspect a metadata problem: https://github.com/KSP-CKAN/NetKAN/issues/new/choose
    If you suspect a bug in the client: https://github.com/KSP-CKAN/CKAN/issues/new/choose

    There was a previous time I got an error, was advised of running KSP instance, and found one in task manager in the background, but I've triple-checked for that.


  5. 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.

  6. 1 hour ago, Fihnakis said:

    I always open the save file, search for 4.02 (or the closest number I can get) and make sure it's the DSN portion and set range and dsn to 1.0 and 4.0. 

    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.

    1 hour ago, Fihnakis said:

    I'm not sure about the disable comnet I always leave it enabled but honestly haven't made it far enough to know if it's working right. Just put my first satellite in orbit. 

    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!

  7. 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?

  8. 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.

  9. 2 hours ago, Gordon Dry said:

    Looking good on my side.

    Not sure, though I removed it for some suspicion. And besides that, I don't need slow-motion etc.

    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.

  10. 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.

  11. 4 hours ago, Dovahkiin2132 said:

    I don't have Kronometer but the game still refuses to let me enter Vab/Sph or any building except the Astronaut complex and when i enter i can't leave it. Any other mods that cause conflicts? (Running RO and RSS)

    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).

  12. 5 minutes ago, kcs123 said:

    Thanks, but I can't take credit for that. @dkavolisis current maintainerafter ferram stopped development. I'm just regular long time user, so I help others when possible and within my humble knowledge.

    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.

  13. 1 hour ago, kcs123 said:

    That kind of error suggest that you may not properly closed previous KSP session. You may want to check task manager if you encounter this kind of error next time. On the side note, you should avoid to install mods directly over steam folder. It can srew your game for multiple reasons when you least expected. You should rather keep steam install as stock only files and copy whole KSP elsewhere for moding purposes. It will take some additional HDD storage, but it pays of on the long run.

    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:


    Can confirm FAR and Kronometer RELEASE are compatible. In my defense, Google "ksp kronometer", and follow the first link, then follow the big blue "Latest Release at Github" link:

    Now, upon much closer inspection, I do see the decidedly TINY text saying "Kronometer support for the latest ksp patch is available here". 

    I don't feel quite as at fault anymore lol. And the main link that IS visible to the naked eye leads to the old Kronometer version on Github which I've confirmed does not work with current FAR. It seems slightly misleading to include, not being the latest release. Yes it has "" in the file name, but I assumed that was just mod version and trusted the link lol.


  14. I'm going to stop monopolizing this thread now, but honestly...

    CKAN Error:


    Unhandled exception:
    System.Transactions.TransactionException: Failed to roll back. ---> System.IO.IOException: The process cannot access the file 'C:\Program Files (x86)\Steam\steamapps\common\Kerbal Space Program\GameData\JNSQ\JNSQ_Textures\PluginData\Edna_heightmap.dds' because it is being used by another process.
       at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
       at System.IO.File.InternalDelete(String path, Boolean checkHost)
       at ChinhDo.Transactions.FileManager.Operations.SingleFileOperation.Rollback()
       at ChinhDo.Transactions.FileManager.TxEnlistment.Rollback(Enlistment enlistment)
       --- End of inner exception stack trace ---
       at ChinhDo.Transactions.FileManager.TxEnlistment.Rollback(Enlistment enlistment)
       at System.Transactions.VolatileEnlistmentAborting.EnterState(InternalEnlistment enlistment)
       at System.Transactions.TransactionStateAborted.EnterState(InternalTransaction tx)
       at System.Transactions.EnlistableStates.Timeout(InternalTransaction tx)
       at System.Transactions.Bucket.TimeoutTransactions()
       at System.Transactions.BucketSet.TimeoutTransactions()
       at System.Transactions.TransactionTable.ThreadTimer(Object state)
       at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
       at System.Threading.TimerQueueTimer.CallCallback()
       at System.Threading.TimerQueueTimer.Fire()
       at System.Threading.TimerQueue.FireNextTimers() 

    Fresh Steam install, only selected JNSQ and FAR to install, accepted dependencies and rejected suggested mods.



    Like I'm being told "oh everything's there, just use CKAN for christ's sake", when that's all I wanted, JNSQ's entry was not updated until literally last night - I can see the timestamp - which is the mod I'm saying wasn't appearing. Maybe I somehow missed Kronometer being listed as well, but if it was, I don't understand how me manually installing it would allow JNSQ to show up if it's apparently also already on CKAN.

    None of it adds up, and now I try to just do as I'm told and use CKAN now that people have evidently fixed things, select only JNSQ and FAR to install on a fresh Steam install, accept their dependencies, reject all suggestions, and it just gives me that error every time...

    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.

  15. 5 hours ago, Gordon Dry said:

    I always do.

    Not the version that  I got: https://github.com/linuxgurugamer/Kronometer/releases/tag/

    https://spacedock.info/mod/2755/JNSQ Real Date?ga=<Game+3102+'Kerbal+Space+Program'># works on my side without issues, I just edited GameData\JNSQRealDate\JNSQRealDate.cfg at each offsetYear entry and changed it to another year than 2001, I chose 1951.

    Looks like the JNSQ install is now working normally on CKAN, but I'll grab that for a manual secondary install, so thanks.


    The JNSQ Date thing, you kinda clipped that out of a sentence and post that was mainly about Kronometer, and in that sentence you half-quoted, I was basically saying Kronometer, and therefore JNSQ Date, since it depends on Kronometer, would not work right now. Thought it worth mentioning since ultimately the point was using FAR and JNSQ together, with which people might use JNSQ Date.

    Now I know I had the wrong Kronometer though, so it's all good. Nothing wrong with JNSQ Date on its own.

  16. 3 minutes ago, linuxgurugamer said:

    Due to the plethora of versions, CKAN has this ability to specify that versions of KSP other than the current version are compatible.  See the following screenshots for how to get to it:




    I maintain over 260 mods, and am unable to update each one for each version, most of which is unnecessary.  What you are seeing above is what I use for my career and development installs, and this makes everything needed available.  

    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.

  17. 3 hours ago, linuxgurugamer said:

    Again, use CKAN to install, it has the latest version

    No offense taken.  Just use CKAN :D 

    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?

  18. 47 minutes ago, linuxgurugamer said:

    Seems that most if not all of your problems came from having an incompatible version of Kronometer installed.  I don't use FAR, so I can't comment on that.  But not having the correct version (and, highly suggested, having the KSP Community Fixes installed) works.

    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.

  19. 50 minutes ago, linuxgurugamer said:

    Frankly, at this point, I'm at the point where, if someone does NOT install via CKAN, I consider their installation suspect.  More often than not, if someone manually installs and then complains about a problem, it's quite often an install issue.  CKAN has improved so much over the years that it is now one of the best mod manages I've seen.  I install over 220 mods into my games using CKAN, and except for one time 4 years ago, have never had a problem.  I realize that it did have problems years ago, but it's much improved since them, and the support/development team is active and helpful

    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.


    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.

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


    I'll keep this concise - RE: Unable to enter VAB/SPH with FAR installed, and also using Kronometer (which I think is still part of the issue, unless it's all FAR/its dependencies):

    Followed what I believe was the entire conversation between pages 28 & 29, and I:
    - Wiped KSP Steam directory/Still uninstalled through Steam afterwards JIC;
    - Redownloaded and copied KSP to a separate directory;
    - Manually installed latest ModuleManager, Kopernicus & the MFI bundled with it (not overwritten by FAR's copy), JNSQ, Kronometer, FAR, and the versions of ClickThroughBlocker/ToolbarController/Toolbar from the links provided in earlier answers, downloaded from their Github links:





    - Loaded KSP, still unable to enter VAB/SPH

    Here are what should be fresh logs of that single attempt (providing KSP.log and also what's in the "Logs" folder):

    If this is still user error installing ToolbarController correctly, I think we might need some kind of further direction on that, because I simply grabbed it from the link provided and installed it in my fresh, isolated KSP install (with ClickThroughBlocker). Isn't that the correct way to install it?

    Hope this is enough to help figure it out. I haven't tested with FAR and without Kronometer, but I'll try to get that feedback to you soon. The problem for CKAN users in that regard is JNSQ won't show as compatible with 1.12.2 unless Kronometer is installed (though it's not a hard dependency), and the JSNQ_Date mod actually requires Kronometer.


  22. 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?

  • Create New...