AmanitaVerna

Would it be difficult to turn warp dragging into a tractor beam projected by an emitter that you could lock onto specific targets?

This wouldn't work if you're playing science mode, of course, since there are no contracts.

Kerbal Flying Saucers can do this, in theory. When you do a particular experiment near a crashed UFO and return the results to KSC, there's supposed to be a chance to discover a UFO technology if you don't have it, or some other technology if you do. I don't actually know if it works because the chance of success is so low, and because I'm using Kerbalism and it might interfere because of how it changes science and the experiment modules.

First zip it up and see how much smaller it becomes, then upload it to some cloud service like OneDrive or Google drive and share it. Anyone who wants to look at it can download and extract it. If it's that big, in all likelihood it contains a lot of repeated exceptions and stuff, and will compress really well as a result.

It would be easier to copy the mm patches in the mods that depend on CTT and modify them to depend on Skyhawk instead and put the various parts into whatever part of the tech tree you want them in.

Yes

I'm also using Kerbalism and RR, and I was never able to figure out how to get GC to work, and ended up switching to EL.

When I last tried OPT Spaceplane, all of the normal parts in the spaceplanes I was building had antimatter storage, for some reason (I hadn't unlocked any antimatter storage or use for it), and while I didn't load them with any antimatter, they still demanded huge amounts of power to contain the zero antimatter. Iirc bad things happened when it ran out of power, but it's been years and I didn't make any notes about it. I do remember a red message of doom when they ran out of power. Anyways, I'm wondering if you happen to have noticed and fixed anything like this in the new version. Or taken antimatter storage away from all of the normal parts and relegated it to antimatter-specific containers? (I was assuming this wasn't the fault of some other mod mainly because opt spaceplane parts are the only parts I've ever seen this with)

I noticed this as well.

There's an outstanding pull request from two years ago to fix a different cfg error, so I don't think Nertea is maintaining this anymore.

It does it on my perfectly ordinary 1080p display also. The most common issue for me is when the part overheating gauge appears, it covers the waypoint text. Which, since I use SystemHeat, is often, because the radiators get hot. I love this mod, by the way. I use it to mark biomes to target for landing, and (with the icons and colors) to keep track of which ones I've sent science probes to, and which ones I've sent kerbals to, etc.

It sounds like this would make it possible to produce LFO or methalox anywhere? I have no clue how to interpret the numbers to know if this would be a fast process or not but I assume the intention is for making fuel from rock to be slower than making it from directly mined resources that don't have to be sifted from rock first?

After updating this mod from 1.3.3.0 to 1.4.0, I started getting a bunch of B9PartSwitch errors on the mass driver parts from the Netherdyne mass driver mod, and I don't understand why. This is the only thing I've updated since the last time I ran KSP, nothing else has changed. I've zipped up my KSP.log, player.log, ModuleManager.log, MMPatch.log, and ModuleManager.ConfigCache into a .7z file with 7zip and uploaded it here: https://1drv.ms/u/s!AlnEemcsDL9Xlc1s6oqU77pOkbfMrg?e=h9WKvD The first B9PS error in the KSP.log starts with this and is on line 91244: [WRN 00:13:10.060] Warning on PartSubtype MissionControl_ASET on module ModuleB9PartSwitch (moduleID='IVASwitch') on part massdriver1: Cannot match a module node without a name! [EXC 00:13:10.061] ArgumentException: Cannot match a module node without a name! B9PartSwitch.ModuleMatcher.NodeMatchesModule (PartModule module, ConfigNode node) (at <a3c2951fc74e4639820ef37d2d29f386>:0) B9PartSwitch.ModuleMatcher.FindPrefabNode (PartModule module) (at <a3c2951fc74e4639820ef37d2d29f386>:0) (I've never figured out how to use these mass driver parts, so I might just remove the mod they're in, but there's no guarantee this is the only thing that's broken with the new version of PCR) (Edit: I decided to roll back to PCR 1.3.3.0 instead.)

Nope, unfortunately, that won't help. The Kerbalism wiki says that additional antennas don't increase the bandwidth, it can only counteract losses due to distance (which shouldn't be a factor for the SENTINEL since you can only do the experiment near Kerbin): https://github.com/Kerbalism/Kerbalism/wiki/PlayGuide-~-Signal

The experiment says it needs 1.26 MB/s to transmit the data as quickly as it is generated, and in total it generates 289 TB of data over 25 years, so that is far too low unless you were planning to try to store the data and return it to Kerbin every time you run out of data storage. Personally, I waited until I had researched an antenna which could transmit at over 1 MB/s before launching any SENTINEL probes. Of course, that cost 1000 science, so I only researched the topic when I wanted the antennas to send probes further into the solar system, since there wouldn't be much point spending 1000 to eventually get 660 and for no other reason. It's not electricity with the SENTINEL telescope - The experiment only needs 1.91 EC/s.

@space_otter what antenna do you have on it? It needs a *lot* of bandwidth.

I will admit that when I first started using CKAN, I was surprised that Steam stopped counting how many hours I had in KSP. But, I also didn't care enough to launch through Steam instead. And it is convenient to be able to have multiple KSP installs in different locations. Some people definitely do care to know how many hours they've played, but presumably they can just launch it through Steam? Assuming that still works properly. I was going to say that it couldn't hurt to have a one-time popup to inform that hours wouldn't be tracked if launched through CKAN, but it occurs to me that it actually could hurt, since it could lead some people to conclude that they can't use CKAN at all if they want their hours tracked, which to my understanding is not the case.

I ran into a sort of similar problem back before 2.0 (I haven't checked to see if it was fixed with 2.0, since I kind of forgot I was running a custom patch to fix it until I was reminded just now) with drills not showing the option to mine uraninite when both NearFutureElectrical (which adds uraninite mining to the two stock drills) and RationalResourcesKerbalism (which then deletes the modules and replaces them with B9 ones without including uraninite) were installed.

What's FuelCell_Lib.ks? ChuteDescent is trying to run it, and it seems to be missing.

I am unfortunately still getting B9PS errors with RR 2.0.1, but less of them this time. The ones on RRConverterCryomatS2 are only for moduleID=RRGasSwitch1 this time instead of RRGasSwitch1 through RRGasSwitch5. I'm also still getting errors on the atmosphere scoops, with moduleID='RamFilter'. That appears to be all of the B9PS errors in my KSP.log. Log files, MM cache, etc: https://1drv.ms/u/s!AlnEemcsDL9Xlc0jsZ0T9N7uM3a08A?e=ctG64s

I am also getting tons of B9PS errors after updating to RR 2.0, on several different RR parts - the first ones in my KSP.log are for RRConverterCryomatS2, and start at line 79902. In my case, however, the problem did not go away when I tried reinstalling B9PS through CKAN (along with the 40 or so other mods CKAN insisted on reinstalling at the same time). I tried having CKAN delete the cached download of B9PS prior to reinstall, to force it to redownload it, but that made no difference either. I've compressed my KSP.log, MMPatch.log, ModuleManager.log, ModuleManager.ConfigCache, and Player.log into a .7z file and uploaded them to OneDrive here: https://1drv.ms/u/s!AlnEemcsDL9Xlc0ism1_OYqRGepjwQ?e=gTUfSS

Oh! I had no idea you could do that in stock!

I am also confused. I tried setting it to physics warp in space, but still could not go faster than 1x under acceleration. It seems like selecting physics warp in the gui only allows changing the multipliers, not turning it on. Am I missing something or does this mod not do what the description says it does?

Something in KSPCF 1.32.0 breaks the popup menus in the CraftManager GUI in KSP 1.12.5. The popup menu opens and then immediately disappears, and options in it can't be clicked on. This happens whether right clicking on a craft in the list of crafts in the VAB/SPH, or clicking a button that opens a popup menu in the CraftManager GUI. Further, the next time it is attempted, nothing happens at all. The time after that, the popup menu opens and then disappears again. Presumably the menu isn't being closed, KSP is just forgetting to perceive it. The regular KSP popups seem to work fine still. This works fine in 1.31.1, and I confirmed that KSPCF 1.32.0 was the culprit by rolling it back to 1.31.1. (It also broke right after updating KSPCF, so it was kind of obvious) (CKAN lists the maximum KSP version of CraftManager as 1.9.9, but after some work I had got it working perfectly in 1.12.*, and the main obstacle, iirc, was actually CKAN, rather than KSP itself.) Edit: The problem appears to be the IMGUIOptimization option. Setting it to false makes the problem go away.

Kerbalism does this as well, and KSP1 with Kerbalism runs on my GTX 750 Ti, so I don't think that's the problem, really. Also, surely, that would be something that would be run on the CPU, not the GPU, and by all accounts I've seen so far, KSP2 is GPU-bound even on high end GPUs?