Katniss218

They should, but I'd try with RSS-Textures afterwards, if VaN's textures don't yield positive results. New 16k RSS-textures have a lot of textures ported directly from VaN though.

Make sure you're using the latest RSS (v18.1.2) AND latest RSS-Textures (18.2)

You can send me an .fbx or if that's not possible for some reason .obj will work too. Well, I just post my images to imgur. Works amazingly well and they don't get removed for inactivity/etc. The only way to have them deleted is if you manually press the delete button.

Sure! The LC39 texture is currently pretty lacking, I'd gladly accept a better one. PS: I'm aware of your 16k pack

Yes, this is intentional. Otherwise the ksc scene camera would appear god knows where.

KSP can be beautiful sometimes, day launch looks even better (RSS/RO, custom parts, custom plumes, customized RSSVE config, custom TUFX profile)

KK is in general poorly integrated with RP-1, which is a shame, bc it's the only mod that allows you to actually place custom pads. Ctrl+K menu is in-flight only AFAIK (you have to be in the flight scene, not in the VAB, etc.) and is used to place/move the objects. In the VAB you should have a button with pad selectors. Idk how well it plays with RP-1 sims, costs, toolings, etc. Probably not too well, but I can't really do anything about it.

Either an old version of KCC or your KerbalKonstructs is bugged. You use KK menu to switch to KK pads, not KCT.

It doesn't. But Omega's Stockalike Structures has some nice landing zone models for KK. (to be placed via Ctrl+K menu)

I promise, this is KSP.

Thanks! From what I can tell that overlay is purely related to Scatterer and RSS, not my cape.

KSCmap.cfg is obsolete and not used anymore. Mod uses PQSCity2 for the main mesh. Yes, it is okay, as it isn't used anywhere. The main post clearly states what you need to do to get the real VAB.

Yes and no. The camera behavior is very weeeird. I've seen reports of that in some peoples' installs, but in others it works fine (including me), the version of the mod doesn't seem to matter (and it shouldn't, as I didn't change anything that'd affect that). It's weird. It also was broken in my install for some time, but it fixed itself at some point, which is even weirder. And.. It IS mentioned in the big wall of disclaimers

Ah yes, the main post can actually contain useful info It's not like this wall of bullet points there for a reason or anything.

It's a custom part mod, I've been making for a video. There's a lot more in it than just saturn parts too. And no, it's not ready for public use, probably won't ever be, as I don't care about proper colliders, exact masses, volumes and all that fluff. It'd on the other hand slow down the preparations and possibly demotivate me enough to stop.

1. Black screen? Zoom out, it's a "bug" with KSP's camera (and I'm just lazy) 2. Anything else - Install RSS 18.1.2 and RSS-Textures 18.2, then overwrite the earth heightmap with the one provided with my mod.

There was an update that should've fixed the inability to launch from Pad 39A/B without using Making History DLC Should all work from the KK pad selector menu. https://github.com/Katniss218/KatnisssCapeCanaveral/releases/tag/1.2.2

Good idea, might do that in the future.

3. Yes, it is supposed to be there. Without it your camera position would be probably even more messed up than what it is currently. 4. Try the new kLC-39-instances.cfg from the repo (merged it like 15 mins ago).

(It also says it in the main post, but) you need either to download the release (compatible with RSS 18.1.2+ and RSS-Textures 18.2), in case you really want to use older RSS, there's an old 8k heightmap in the repo if you clone it, compatible with older RSS, before they started using 16bpp heightmaps.

Pics? Also, make sure you're using correct (compatible) RSS and KSP versions.

Bugfix v1.2.1 Changed the filename extension of the EarthHeight.dds to lowercase (was DDS previously). Should fix some bugs in some installs (Linux?) https://github.com/Katniss218/KatnisssCapeCanaveral/releases/tag/1.2.1

Good luck storing information about such deformations. I imagine you could use something akin to an octtree, with non-uniform information density, but it still has drawbacks. But would be cool of course.

I have another idea. Try attaching a launch clamp to the rocket, the launch base might not be a launch clamp and thus KSP tries to put it at the lowermost point on the pad regardless where it's positioned in the VAB. And yes, I added a custom position to the VAB, the rocket should spawn above the flame trench, not inside it, don't know why it spawns this way, it's something with KK I assume. Maybe it tries raycasting downwards to find the correct spot for spawning, but doesn't take rocket's dimensions into account. (but it's just me guessing how it might work, idk how it works in reality)