[BUG - Starfield + Singularity] Stars & Kartographer are horizontally flipped and have inverted vertical panning. ADDED: Issues with Singularity cubemap generation

[lifelesstoro]

Star & kartographer rendering works as intended in the Tracking Station, but in the game they have inverted vertical panning and, the kartographer at least, I assume both, are flipped horizontally, resulting in backwards text.

Tracking Station: https://youtu.be/-fqEolU1i_E
In-Game: https://youtu.be/keemqv3HcOI
CKAN modlist: modlist.txt
(Two manually installed mods not on the txt: Volumetric Clouds V5 and OPM-Volumetrics)
KSP.log: KSP - Copy.log

The only things I noticed while looking in KSP.log were that Kopernicus threw errors related to the Star Catalog (line 22174-22178)
[LOG 10:01:49.606] [Kopernicus] Could not load 'C:/Program Files (x86)/Steam/steamapps/common/Kerbal Space Program/KSP_x64_Data/../GameData/CinematicShaders\PluginData\StarCatalogs\hyg_v42.bin' [LOG 10:01:49.611] [Kopernicus] Could not load 'C:/Program Files (x86)/Steam/steamapps/common/Kerbal Space Program/KSP_x64_Data/../GameData/CinematicShaders\PluginData\StarCatalogs\hyg_v42_20k.bin' [LOG 10:01:49.616] [Kopernicus] Could not load 'C:/Program Files (x86)/Steam/steamapps/common/Kerbal Space Program/KSP_x64_Data/../GameData/CinematicShaders\PluginData\StarCatalogs\hyg_v42_50k.bin' [LOG 10:01:49.621] [Kopernicus] Could not load 'C:/Program Files (x86)/Steam/steamapps/common/Kerbal Space Program/KSP_x64_Data/../GameData/CinematicShaders\PluginData\StarCatalogs\hyg_v42_80k.bin' [LOG 10:01:49.624] [Kopernicus] Could not load 'C:/Program Files (x86)/Steam/steamapps/common/Kerbal Space Program/KSP_x64_Data/../GameData/CinematicShaders\PluginData\StarCatalogs\MyStarfield.bin'

I'm planning on reinstalling KSP later today and putting my modlist back together one-by-one because I really really think this is a beautiful mod and would love its stars to work, but I have classes for the next few hours until then. Thanks for the incredible work!

[DGerry83]

I think this sounds like the same bug someone else reported on the forums. I'll look into this and see what's happening, I suspect something is flipping some signs somewhere that my mod isn't anticipating - if that's the case it shouldn't be too hard to fix but I don't want to get ahead of myself. Thanks for reporting and including all that info!

[lifelesstoro]

I went through and reinstalled everything; it looks like its an incompatibility with Singularity, which does black hole shading. I wont pretend to know the specifics but it looks like Singularity is generating its own galaxy cubemaps after CinematicShaders in the logs.

lines 47339-45
[LOG 10:03:29.454] [StarfieldCubemapRenderer] Starting native cubemap render... [LOG 10:03:29.499] [StarfieldCubemapRenderer] Native render complete: 44ms [LOG 10:03:29.499] [KSPCubemapInjector] Injecting from RenderTextures... [LOG 10:03:29.499] [KSPCubemapInjector] Original skybox textures backed up [LOG 10:03:29.508] [KSPCubemapInjector] Found Parallax SkyboxControl.alreadyGenerated field [LOG 10:03:29.508] [KSPCubemapInjector] Reset Parallax SkyboxControl.alreadyGenerated = false [LOG 10:03:29.508] [KSPCubemapInjector] Parallax will re-extract on next scene change [LOG 10:03:29.508] [StarfieldCubemapRenderer] Cubemap injected into KSP skybox [LOG 10:03:29.508] [CubemapGenerationScheduler] Cubemap generation complete

lines 47377 & 78
[LOG 10:03:29.658] [Singularity][Info] Config loaded, resolutions: galaxyCubemapResolution=2048, objectCubemapResolution=2048 [LOG 10:03:29.789] [Singularity][Info] GalaxyCubemap initialized

EDIT: I got ahead of myself, those two loaded just together with no other mods works fine. I'll keep looking.

[DGerry83]

I know there's a separate bug related to Singularity and the cubemap I'm building - but I think I know how to fix that, and it shouldn't cause any coordinate flipping. When the starfield shader is running we're actually not using that cubemap, the cubemap we generate is for compatibility with other mods that expect the sky to be a cubemap(usually for reflections, but in Singularity's case it's for the shader that distorts the sky behind the singularity). I appreciate you looking! The key is if you can find a mod that you uninstall and then the camera works properly IE the stars don't move the wrong way, that's the mod I need to focus on. Don't beat yourself up trying to narrow it down, I'm going to take a look at it in the next few days - but if you do figure out exactly which mod is causing it that would be a huge help to tracking down and fixing the incompatibility.

[lifelesstoro]

Alright this time I think I actually got it lol. Singularity is half the problem. Its some sort of interaction between CinematicShaders, Singularity, and Scatterer. Having one or the other with CinematicShaders is fine, but having both causes the issue. At least singularity is only used for end-game content like promised worlds and kcalbeloh, hopefully it turns out to be an easy fix!

Idk how much theyll help in actually diagnosing why it happens but heres my logs from an install with just those 3 mods + CinematicShaders dependencies installed.

KSP.log
CinematicShaders_Native.log

[DGerry83]

Thank you so much that helps narrow things down a lot! I'll check out all your logs, and see about reproducing the issue locally and then see what might be causing it and hopefully be able to nail down a fix.

[DGerry83]

I just installed Singularity and even though I also have scatterer, I can't reproduce this bug. I also wasn't able to find anything in the code of either one that would indicate why this would be happening.

Edit: I'll have to set aside some time to replicate your exact install via your modlist on my machine and see if I can replicate the behavior. I can't really test a fix without being able to replicate the bug. A potential temporary solution is I could add a debug "camera matrix flip" toggle to the UI that you(and other users with this problem) could use....but I don't like that long-term.

[DGerry83]

After replicating your modlist, I found an unexpected solution that I hope is temporary but I need to investigate further now that I've been able to reproduce locally and fix locally via installing one additional mod. I noticed you didn't have TUFX and I do, and installing TUFX does seem to solve this problem. You do not have to use any of its post-processing at all(and temporal anti-aliasing will cause problems), at least as far as I could tell - I didn't install any profiles for it or change any settings, simply adding it to your modlist on my ckan instance fixed the issue. To double-check I uninstalled tufx from my dev install and the issue appeared. So for now, as a temporary workaround, you can try installing tufx and let me know if that solves it. I'll keep looking at this to see if I can get to a solution that doesn't require the installation of an additional mod.

[DGerry83]

Changed the title of this issue and I'm going to close the separate cubemap issue because they're fairly closely related. Essentially, Singularity makes some assumptions about the game environemnt that are completely reasonable that my mod makes invalid. This results in the generated cubemaps being incorrect, a harsh and obvious transition at the edge of the lensing sphere, and in some cases no cubemaps generated at all leading to a white sphere around the black hole. I was able to knock up a solution that solves the camera basis issues, but it's not generally applicable so I need to figure out how switch between that path and the standard one at runtime based on Singularity and Scatterer being present(and then potentially NOT if TUFX is present...). This solution did not fix the cubemap issue though, and that's something I'm not completely sure on how to fix - I know Singularity could just use the cubemap my mod generates, but I don't know that this would fix the issue with the lensing effect. This may be an ongoing issue for some time, and I apologize to Singularity users for that.