kmb1611

Thanks all. I ended up re-installing KSP after clearing everything per @Phineas Freak's instructions above (and retaining my saves per @Program Kerbal Space), and that seems to have resolved the issue - scatterer + eve working beautifully now. Really appreciate everybody's assistance, what an awesome community

Hmm, sorry - maybe a copy/paste error, I can open it on my phone and laptop... try this: https://www.dropbox.com/s/9h1ryfnlxtey6z5/Player.log?dl=0

Thanks - so I did the replace, downloading the copy you linked to, triple checked I was adding to the right GameData, etc. and I'm still seeing the exact same behavior. FWIW, my original install did include the entire scatterer subdirectory tree as well, not just the .dll. I do know the install was successful, as the option to integrate with eve clouds in the scatterer config menu at launch was now available, whereas it had not been previously. I'd welcome any other thoughts if you have any - Here's the new player.log (I replaced the old one), if that's helpful at all. - TIA

Thanks @Speadge! FYI for anybody who comes across this, on a Mac its: <user>/Library/Logs/Unity/Player.log

@Galileo Per the thread from the scatterer post here's the output.log as requested - TIA

Happy to, and will reconvene there. Confession: Sorry, not sure how to get to the output log versus the one I linked to above... is there a config option for it?

Realizing its probably EVE related, though tied to the clouds maybe? Anyway, that's the message I get repeatedly in the console... Starting at line 2602 of the log, bolding is mine: [LOG 17:34:27.454] EVEManager: Issue loading CloudsManager! Error: UnityEngine.UnityException: Unable to apply node! ---> System.MissingFieldException: Field '.MapView.MapIsEnabled' not found. at Atmosphere.CloudsPQS.Apply (System.String body, Atmosphere.CloudsMaterial cloudsMaterial, Atmosphere.Clouds2D layer2D, Atmosphere.CloudsVolume layerVolume, Single altitude, Vector3d speed, Vector3d detailSpeed, Vector3 offset, Matrix4x4 rotationAxis, Boolean killBodyRotation) [0x00000] in <filename unknown>:0 at Atmosphere.CloudsObject.Apply () [0x00000] in <filename unknown>:0 at Atmosphere.CloudsManager.ApplyConfigNode (.ConfigNode node) [0x00000] in <filename unknown>:0 at EVEManager.EVEManagerBase.Apply () [0x00000] in <filename unknown>:0 --- End of inner exception stack trace --- at EVEManager.EVEManagerBase.Apply () [0x00000] in <filename unknown>:0 at EVEManager.EVEManagerBase.LoadConfig () [0x00000] in <filename unknown>:0 at EVEManager.GenericEVEManager`1[T].Setup () [0x00000] in <filename unknown>:0 at EVEManager.GlobalEVEManager.Setup (Boolean late) [0x00000] in <filename unknown>:0 Better to just post in the EVE 1.2 thread? (sorry) Oddly, don't think it was happening until scatterer was installed, but alas, the proof is in the pudding...

Happy to post a log file as required, but thought I'd ask first about the symptom and see if it resonates with anybody. Using the latest scatterer (including the new dll posted a couple of pages back) and the most up-to-date EVE, including the new textures. Those are my only two mods installed. In my console I'm continually getting the message "Exception: MissingFieldException: Field '.MapView.MapIsEnabled' not found" in the console (so much so I can't actually see anything else in the console but this). When playing, toggling between the map view and the regular view in-game more than once will eventually strip away the scatterer effects. I didn't see that issue posted in either EVE or scatterer's known issues, and my apologies if its already been reported and resolved somewhere. Any thoughts people might have are welcome, otherwise happy to follow-up with any info needed to help troubleshoot. -TIA

Yeah, that's the revelation for me, really really helpful, thank you for the detailed explanation. (and yes, swapped the Sr.s - I play career-only, so just unlocked them not-so-long-ago )

Thanks @Alshain and @Kurld. I know the Sr. ones are on backwards (oops), but the standards should be correctly arranged. BINGO. That's exactly what I did, they weren't attaching properly to the HubMax otherwise! Holding the mod key and maneuvering will avoid that issue? TY!!

I'm about 400 hours into my KSP career, so not really a total newby and have successfully docked many many things to one another, but I'm completely flummoxed by the behavior of docking ports WRT the HubMax. When I launch my first station, the attached docking ports do not have the "Decouple Node" option available, after all, they're attached directly to the HubMax. Sofar, so good. I launch my next piece (a large solar array), and plot intercept in LKO. Move to dock with the array going Clamp-O-Tron to Clamp-O-Tron. As I bring the array in closer, they touch at .1 m/s with SAS off, and... nothing. No magnetic attraction, no docking as I've done successfully many times in the past. No amount of rotating the array seems to affect it. The only thing that seemingly changes is I now have the option to 'Decouple Node' on the docking port attached to the HubMax... huh? If I click that, the docking port just floats out into space as if attached with a decoupler, which it isn't, leaving me a bare HubMax endpoint. Thinking I attached it wrong, I tweak how the Clamp-O-Tron is aligned in the VAB, and launch a second station (which is actually the one shown below, attempt #2), but it too suffers the same indignity as the first. The array, for its part, seems to continue to have a normal functional docking port, though in fairness I'd need to throw something else up into orbit to test against. But I feel pretty certain its the HubMax port that's the issue. So... bug? Am I missing something here? Do I not understand how the HubMax is supposed to work? Any thoughts on resolution or workaround to my station floating debris in space? TIA