JonnyOThan

Sorry for the thread necro, but someone just linked to this post. Rather than changing CKAN's compatibility settings, you should click on the mod you want and then click on the versions tab on the right. You can check the box to install it there without blanket-allowing all older mods (which is sure to cause issues). Some recent updates to scatterer broke some older sunflare mods. They're not really incompatible, just the structure of the cfg files changed a bit. If an older version works, it's probably fine to use.

MM has no concept of what mod something came from. If all the parts in that mod have something in common (model path, author, naming pattern, etc) then you can use that to filter. Use something like @PART:HAS[!MODEL:HAS[#model[ModFolder/*]]] If there’s no common thing you can use, then one way to do this would be to add a custom key/value to all the parts you don’t want to affect and then apply your patch to things that don’t have that key.

If it's mainly centrifuge parts, this is a known issue with FreeIva and JSI Advanced Transparent pods. I'd suggest removing the latter.

It's on my list, but man it's a long list... https://github.com/FirstPersonKSP/KSA-IVA-Upgrade/issues/12

And of course, it’s never that simple: https://github.com/JonnyOThan/TweakScale/issues/53#issuecomment-2264325643 The good news is that this will fix a whole class of problems, but it’s not trivial.

Good question, let's see... KopernicusSolarPanel derives from ModuleDeployableSolarPanel, so that should already be covered. ModuleCurvedSolarPanel does not, but there is an existing set of exponents for it (targeting TotalEnergyRate) KopernicusSolarPanelCurved also does not, and is missing a set of exponents (looks like TotalEnergyRate should also work)

Wow good catch. I removed this patch without realizing that it’s the only thing that actually changed the output. https://github.com/JonnyOThan/TweakScale/commit/7e54309580caa27dc4ae0bf311496d02d25bdde6

Well, in any case I confirmed that TURD was using the same code that was in the dev branch, and got that merged and released: https://github.com/KSPModStewards/TexturesUnlimited/releases

Heya, I'm working on adopting and getting TU updated for deferred rendering support, and it occurred to me to look into possibly getting TURD onto CKAN as well. I wasn't aware there was a difference in the bundled version here, I'll check that out.. Would you mind if I set up CKAN metadata for TURD? Thanks!

Have you tried playing with just PCR and RT and seeing if you're experiencing the same problems?

Don’t install KSP in onedrive . It also looks like you might have renamed the executable to ksp_x64_opm. Don’t do that either.

They correspond to FAR controls

Please post your KSP.log and modulemanager.configcache

Got a fire extinguisher nearby? or hit alt-g to toggle gravity temporarily.

I'll make a note to take a look at it, but in general RSE patches ALL engines according to certain heuristics. There's probably something else going on and you might want to also ask the owner of that mod and possibly also any mods that configure the waterfall effects.

Woops, yes. thanks.

I’m not quite sure I understand the drawing. But Planetside, sspx, habtech2, pathfinder, buffalo2, and kerbal planetary base systems all have great base parts. There’s probably something you can use in those. I’ll add it to the list! Does it have a new iva too?

I can't really see the banding on the first image from BLUAV8R, but the second one is one place where I've noticed it. Also in KS_Positive_Z: If you use the eyedropper tool, the adjacent color RGB values change in increments of ~3 instead of using the full 32 bit depth.

Not currently...I'll have to think about the best way to do that. The screen selections should persist per vessel though.

TUFX 1.1.0 is now available! https://github.com/KSPModStewards/TUFX/releases Note the change in github repo. But you're using CKAN anyway, right? Right? New Dependencies ClickThroughBlocker ToolbarController Changes Remove patch that disables scatterer's temporal antialiasing Better default profile settings (mostly removing the neutral tonemapper which tended to result in a desaturated image) Added toolbarcontrol integration (you can use this to hide the toolbar button) Added clickthroughblocker support and other code to prevent mouse interactions from affecting other things when interacting with the config window Fixed icons appearing blurry when game is not at full texture resolution TUFX window is now hidden when you press F2 (this is useful in photo mode - press escape then F2) Disable stock antialiasing when HDR and bloom are enabled to prevent strobing artifacts Configuration window now loads and saves directly to cfg files Redesigned profile editor UI Postprocessing effects now only apply to the final camera so that they don't get doubled up when in IVA or other situations. Added a secondary camera antialiasing setting. The old setting will be applied only to the main camera (local space in flight). The secondary antialiasing method will be applied to other cameras (scaled space, internal camera, editor cameras). This prevents smearing when using temporal antialiasing because the cameras do not share motion information. Fixed a bug where the bloom diffusion parameter would not get loaded from the profile Fixed a NullReferenceException when saving a texture param with nothing selected Added properties to customize antialiasing settings Added support for changing the mainmenu profile in-game Added a separate default profile for IVA mode Properly set HDR on the GalaxyCamera

then you need to post new logs.

One that moderators don't want discussed on the forum.

Hi @theJesuit, I had some questions about the CKAN metadata here: https://github.com/KSP-CKAN/NetKAN/pull/10068#issuecomment-2243663614

That's really cool. Nice work MiraZaWitch! @MYKori_Rosales: out of curiosity, did you use CKAN to install it? Just want to verify that everything's working OK. Mistakes often get made when first adding mods to CKAN, but they're easy to fix if people report them.

Hey @linuxgurugamer I've heard that the reason this isn't on CKAN is because it does stuff outside the GameData directory. I think CKAN can now support that to a limited extent. I don't know the details, but if we can figure it out would you like us to get it added to CKAN?