DeliriumTrigger

Cheers, I will build with this and see if it helps. You have, as always, my eternal gratitude Edit: No joy. Thanks for looking into it anyway. Seems this problem is a hydra, cut one head off and another one pops up.

Alright, well, you told me to delete scatterer and stop posting, but I'm stubborn and I really want these flares without lens dirt. So after much tutorial reading and handholding by JonnyOThan in the /r/ksp discord, I managed to attach the debugger and feed him enough information to (I think? Hope?) nail down the issue. Don't shoot the messenger, I'm just gonna pass along what I gathered, do with it what you will. so... "hey there's more of these" https://github.com/LGhassen/Scatterer/blob/3124f0cbaa051d77bdfb548bcc2ee054f8b36411/scatterer/Effects/SunFlare/SunflareCameraHook.cs#L27 https://github.com/LGhassen/Scatterer/commit/3124f0cbaa051d77bdfb548bcc2ee054f8b36411 also I guess I'm supposed to ping @linuxgurugamer since he's the one that was working on it? idk, my head hurts, i need an aspirin. IDK how you guys do it, but after all this I can understand why you're so grumpy about it when someone throws a problem in your lap. edit: and of course, if you need any more info from me, i'll provide it, just ask.

I understand you're probably busy and constantly inundated with support requests and i'm sympathetic to that, and i'm sorry if my frustration has annoyed you, but if you didn't want to help you could have just said that 3 days ago instead of wasting both of our time. I tried removing sunflares with the in game editor. the sunflares don't go away, the nres still happen, and the game still runs like crap. believe me, if i could figure this out on my own instead of asking you for help, i would be doing that. I've been doing that for days before I came here with hat in hand. the error isn't something that i understand, it's referencing a line number in code, i don't know a thing about programming and as far as i have gathered the only way i'll get close to understanding it on my own is attaching a debugger, which according to the help i've gotten outside of this thread may not even work since "scatterer has issues with debug mode".

My best bet is to give up and just deal with the lens dirt in the unity flare, because if the person who made the mod doesn't know why it's throwing errors or what they mean then my chances of figuring it out are basically zero. I can already tell from the log that the flare it's getting tripped up on is the transparent barycenter, I don't need to mess around with an in game configuration editor to figure that out. The sunflares look correct in game, you said my configs look correct, so the only real problem is the constant log spam of an error that is dragging my performance into the gutter. Why even have the error or the repetitive log spam about it? It isn't giving you any useful information if you can't tell me what it means, and it sure as hell isn't giving me any useful information, it's just wasting my disk space and making the game run like crap. Seems rather pointless. Is there a way I can tell scatterer to just be quiet so my game stops running like crap?

I don't see how this will help me with the NREs but okay i guess

That discord message was a bit premature, I did find and fix the texture path issue that was causing the sunflare to not work at all. And then a missing texture issue which was causing some NRE spam, as I said above. And then I got stumped by mystery NRE spam which is ongoing and doesn't have an obvious (to me) source that's outlined in player.log like the other two problems I solved on my own. Also, I've tried to use the in-game editor but pressing the key combination just brings up the same menu that pops up when I click the menu icon at the KSC. The only thing I can change under "sunflare" in that menu is a single toggle.

Hi there! I've been trying to convert BallisticFox's Beyond Home repo to use the old Scatterer sunflares so that I could edit the Ghost1 on Destiny to get rid of the baked in lens dirt of the included Unity3D sunflare. I've gotten like... 99% of the way there I think. When loading in game, everything looks right, lens dirt gone, Destiny Fate and Kerbol all have their sunflare, and the barycenter is transparent as it should be. However I'm getting unrelenting NRE spam. I managed to diagnose some of it, it was complaining about a bad path, and then a missing ghost3 texture for the transparent barycenter (or Sun). After sorting those it's still complaining about something and I'm completely stumped. Here's an excerpt from player.log Cobbling together configs to try and make this work is already pushing the extent of my capabilities, trying to diagnose what's leading to this NRE spam has me entirely lost. It's pretty frustrating because visually I've accomplished my goal but clearly I've broken something. Any help that anyone can provide would be greatly appreciated. Here's a link to a google drive folder with the sunflare.cfg, as well as my KSP.log and player.log If you need me to provide anything else just ask. Thanks in advance for any help!

I know this is kind of old now and I don't want to prompt you to go and do a whole new round of testing, but for me the difference is extremely noticeable when I'm in low orbit of a planet/moon in a decently sized space station with all the associated part count that goes along with that. I suspect it has something to do with whatever planetshine is doing to add the glow to each part, in combination with whatever Parallax is doing. I don't notice a huge difference on things with smaller part counts, but I suspect it's somewhere in the range of 10fps+ difference if I remove Planetshine when I have Parallax installed with the orbital station situation.

Just going off a conversation I saw in the /r/ksp discord about this same issue, check and make sure that you have your texture res set to full.

Hey, sorry it took me a few days to get back to you, life gets in the way sometimes. The save this is happening in is science mode. I don't think that's relevant to why it's happening though. I just tried a career save with the same install and it's happening in there as well. I tried a different JNSQ install with KEI in the modlist, which is also a science save, and the window doesn't pop up like this in that modlist. So I guess that's good news since it's likely some interaction between mods or something broken in my install and not something that really needs your attention. However, since you asked, here is a link to the player.log. Not sure how helpful it will be, I did a quick ctrl-f for KEI and don't see anything that stands out to me as an error, but maybe something will jump out at you if for some reason you're really interested in hunting down whatever weird interaction is causing this bug. I'm not asking you to do that though, diagnosing a minor annoyance that is likely the result of some unique combination of mods and doesn't affect the actual functionality of the mod or the overall install in some game breaking way is completely unnecessary. I appreciate that you were willing to look into it but that sounds like a wild goose chase to me and I'm sure you have enough on your plate.

Attached screenshots of my settings window, and the window that is popping up when I open R&D/Astronaut complex (??) within the spoiler. Like I said, the pop-up of this window upon entering R&D only started happening some time in the last few updates, previously it would only open if I clicked on the toolbar button. If this is unexpected behavior that you're not seeing in your own testing and a ksp or player log would be helpful here I'm happy to provide, though I see no errors in the console that would indicate a problem. I assumed this was an intended change and was just seeking a way to make the pop-ups stop.

Is there a setting I can change somewhere for this mod to have it not pop up every time I open R&D? (and curiously enough, the astronaut center? ) And if not, could you possibly add one in the next update? The mod used to not do this, and somewhere in the past couple of versions it started to and I would prefer if it didn't, since having to close the pop-up every single time I go into R&D is becoming a bit of an annoyance as most pop-ups tend to do.

I have mine in /GameData/KopernicusExpansion/StockFootprints/Configs, but I don't see any reason why it wouldn't work if you just saved it as a cfg file anywhere in Gamedata.

Man you've been killin it with these releases lately.

Its not much, but here's an EVA Footprints config for OPM if anyone needs it. @Vabien feel free to include it with the mod if you like. https://pastebin.com/pLVaxF3p

This is going to be the crappiest bug report ever, and I apologize in advance for that, but after screwing around with getting things stable for over an hour I just can't be bothered to make another KSP install with just this mod to give you a full ksp.log and all of that. While trying to find the right combo of KSP version and mods to get Beyond Home working in a version without Parallax, I tried 1.9.1 and BH 1.4.2 (actually working well). Anyway, I installed KSP Community Fixes, mostly for the ROC fix since it seemed to squash some exceptions when I tried other KSP/BH versions. In 1.9.1 KSP Community Fixes completely breaks fairings. On loading any fairing part, the following exception is thrown. [ERR 12:22:49.868] Module ModuleProceduralFairing threw during OnLoad: System.MissingFieldException: Field 'ModuleProceduralFairing.isFadeLocked' not found. I decided to just ignore the error and see what happens. Going into the vab and trying to attach a fairing causes an exception to be thrown, and upon attaching it immediately disconnects and the top node of the fairing disappears. I'm sure it's KSP Community Fixes that's causing it because the issue only appeared after I installed it, and disappeared when I uninstalled it (I had a hunch). As I said, sorry I can't really provide more info. Should be easy enough to replicate if you fire up a 1.9.1 instance and install KSP Community Fixes, the problem affects stock parts. I'm sure it's not high priority but given that the mod is listed as compatible with 1.8-1.12 I figured I should let you know regardless. Edit: I should mention that removing KSP Community Fixes does bring the ROC exception back. Is there anything obvious that jumps out at you (even everything BUT the ROC fix) that I can disable in settings.cfg to stop the fairing breaking behavior? Edit2: Disabling the fairing thing in settings.cfg fixed it.

I know this is super late, but if you haven't found one yet, a solution I have found for this problem is to use this Lossless Scaling app from Steam, run the game in 1440p and upscale it with AMD FSR. Looks near native resolution, all mod windows are scaled better and the text is clear. I'm sure if you search around you could probably find a free solution that does the same thing, but this is what I use. The only downsides are that it forces the game to act like it's in fullscreen mode instead of a fullscreen borderless window, and on scene changes, the game will go from fullscreen to a window and you will have to hit the keybind to scale the window back up to 4k. If I'm streaming or using my second monitor a lot while playing I generally just run in 1080p to avoid the fullscreen mode thing since it can get kind of annoying.

wrong mod. sorry.

what nevermind the freaking error is back, will report back when i figure out what the hell im dealing with here

Just a heads up, clicked on the links to the previous threads to try and find some more pictures of these parts and they appear to lead to an unrelated mod (Pteron Micro Shuttle)

Hey @Manwith Nonamedo you have a repo or would you be willing to share a few example PSD files that I could use to try and figure out the workflow for extending this functionality to other mods? I was looking at the DDS files on the stock recolor in photoshop and I think I got pretty close when I tried to replicate the specular map on a stock fuel tank by messing with curves and contrast, but seeing some examples of what exactly you've done would be most helpful. Don't want to get too ambitious and start announcing grand plans, but there's a few parts in mods that I like that don't have the maps/configs that I'd like to try to create them for. Of course I would be willing to do so as a contributor to this mod if it develops into something resembling configs/maps for an entire mod or more.

Before I go and break my install doing something I don't fully understand, am I correct in thinking that if I remove the SSPXr-StockPartReplacements.cfg from the patches directory that it would restore all the stock parts back to stock? I like the updated models and color variants this mod provides but I like the ability to recolor the stock parts with Textures Unlimited more, and there's some kind of conflict between what this mod is doing and what Textures Unlimited Recolor Depot wants to do.

I really want to like this mod but it's like... there's no happy medium here. I want the chance of a part failure on launch. I don't want 3 SRBs to fail on each and every launch until I do a half dozen launches and then maybe one or two will work as they're supposed to. I get that the point of installing a mod that introduces part failure is that parts will fail, but I'm struggling to find settings that introduce 'fun' part failure because it seems like it's either everything fails all the time until I run out of money, or I turn all chances of part failure on activation off and then I guess in a few kerbal months i'll see solar panels on satellites fail or something. If there's some way to configure this mod that gives the opportunity for a failure on activation every once in a while without making me feel like Bill Murray in Groundhogs Day recovering the same rocket and launching it over, and over, and over and over again just to do a suborbital hop, I'm all ears.

Absolutely loving this mod. So great for making compact and nice to look at satellite bus assemblies. One very minor issue I've had with it is that on the basic and advanced satellite parts, disabling/enabling decoupler staging doesn't actually do anything. Regardless of how it is set, the decoupler remains staged. Not a huge deal as I can just drag their decouplers to the very top of the staging order so they don't get staged automatically, but perhaps something to look into when you have time.

Ah sweet, thanks for the quick update!