FLIR Targeting Pod and Target Camera have a very limited viewing distance

[twoexem]

Describe the bug
When using either of the two targeting cameras, nearby structures appear like behind a thick fog wall (see Screenshots below). Upon larger distances, the terrain disappears altogether. When getting closer again, the strucures appear properly. It appears like the terrain clips upon larger distances to the targeting camera.

To Reproduce

1. Create a craft with either a FLIR targeting pod or the inline targeting pod
2. Launch the craft from a distance away from the KSC and target the KSC with the camera
3. The KSC isn't visible, nor is anything

Expected behaviour
I expected to see the KSC.

Logs
KSP.log

Screenshots
In order:

Additional context
Targeting via the targeting cameras used to work, but doesn't anymore. I use Linux and a list of other mods. Here is my complete modlist:

Modlist

ASET Consolidated Agency (ASETAgency v2.0.2)
ASET Consolidated Props Pack (ASETProps v2.0.7)
B9 Part Switch (B9PartSwitch v2.20.0)
BDArmory Extended (BDArmoryExtended 1:1.4)
BDArmory Plus (BDArmoryForRunwayProject 2:v1.8.0.1)
Breaking Ground (BreakingGround-DLC 1.7.1)
Chatterer (Chatterer 0.9.99)
Chatterer Extended (ChattererExtended 0.6.2)
ClickThrough Blocker (ClickThroughBlocker 1:2.1.10.22)
DE_IVAExtension (DE-IVAExtension v1.2.0)
Destruction Effects (DestructionEffects 2:v1.12.0)
Environmental Visual Enhancements Redux (EnvironmentalVisualEnhancements 3:1.11.7.2)
EVE - Stock Planet Configs (EnvironmentalVisualEnhancements-HR 2:EVE-1.2.2-1)
FreeIva (FreeIva 0.2.19.0)
Harmony 2 (Harmony2 2.2.1.0)
KSP Community Fixes (KSPCommunityFixes 1.36.1)
KSP Wheel (KSPWheel 1:0.16.14.33)
Making History (MakingHistory-DLC 1.12.1)
MechJeb 2 (MechJeb2 2.14.3.0)
Module Manager (ModuleManager 4.2.3)
Physics Range Extender (PhysicsRangeExtender 1.21.0)
RasterPropMonitor (RasterPropMonitor 1:v1.0.2)
RasterPropMonitor Core (RasterPropMonitor-Core 1:v1.0.2)
ReStock (ReStock 1.5.1)
ReStock+ (ReStockPlus 1.5.1)
Scatterer (Scatterer 3:v0.0878)
Scatterer Default Config (Scatterer-config 3:v0.0878)
Scatterer Sunflare (Scatterer-sunflare 3:v0.0878)
Stock Waterfall Effects (StockWaterfallEffects 0.8.0)
Tarsier Space Technology with Galaxies Continued... (TarsierSpaceTechnologyWithGalaxies 1:7.13)
Textures Unlimited (TexturesUnlimited 1.6.2.28)
Toolbar Controller (ToolbarController 1:0.1.9.11)
Vessel Viewer Continued (VesselView 2:0.8.9)
VesselView-UI-RasterPropMonitor (VesselView-UI-RasterPropMonitor 1:0.8.9)
Waterfall - Restock (WaterfallRestock 0.2.3)
Waterfall Core (Waterfall 0.10.3)

[twoexem]

I just noticed this issue also appears with the external camera part provided by RasterPropMonitor, so I don't think this is related to BDArmory. Closing.

[twoexem]

Reopening because I have no idea what's going on, and I think the issues in RPM are unrelated.

[BrettRyland]

This appears to be due to blackrack's Scatterer mod

Modlist

$ awk '/Mod DLLs found:/{f=1}f;f&&/^$/{exit}' KSP.log | { sed -u 1q; sort; }

Mod DLLs found:

0Harmony v2.2.1.0
0_MultipleModuleInPartAPI v1.0.0.0
BDArmory v1.8.0.1
Deferred v1.2.6.0
HarmonyInstallChecker v2.2.1.0
KSPCommunityFixes v1.36.1.0
ModuleManager v4.2.3.0
PhysicsRangeExtender v1.21.0.0
scatterer v0.878.0.0
Shabby v0.0.0.0 / v0.4.0 / v0.4.0.0
Stock assembly: Assembly-CSharp v0.0.0.0
Stock assembly: KSPSteamCtrlr v0.0.1.35

Without Scatterer:

With Scatterer:

BDArmory (and presumably RasterPropMonitor) takes a copy of KSP's near and far flight cameras when setting up the targeting camera, which Scatterer appears to have made changes to, specifically, the near flight camera in this case.
I may need help from blackrack to figure out how to fix this.