Lisias
-
Posts
6,486 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Posts posted by Lisias
-
-
2 hours ago, Errol said:
I'm having an issue with settings reverting every time I restart ksp. When I make changes in the UI settings dialogue, and hit apply, they persist through scene changes and even going back to the main menu and reloading a save. But no matter what I do, including manually editing both the settings.cfg files in the DistantObject and DistantObject/PluginData, somehow the settings are all reverted to defaults every time I reload ksp.
Are you using the latest release?
I think I had fixed this here: https://github.com/net-lisias-ksp/DistantObject/issues/38
I will give this a peek before bedtime, but it will help to publish your current KSP.log (after reproducing the problem, and after quitting KSP to prevent the log from being truncated) it will surely help on the diagnosing.
=== == = POST EDIT
I just fired up my "Acceptance" (acp
) test bed, where I have installed all the add'ons I publish on the latest releases, and... It's working for me.
It was a pretty simple test (hey, I sleep now and then and I'm already done for today):
- Fired up KSP 1.12.5 (acp)
- Loaded the DOE's smoke test savegame
- Opened the DOE's Settings Dialog
- Set Show names on mousever to off (i.e., unticked the check box). It was On at that time.
- Pressed Apply
- Quit KSP
- Load it (again)
- Loaded the DOES's smoke test savegame (again)
- Opened the DOE's Settings Dialog (again)
- The Show names on mousever is still off.
-
Just to be on the safe side, I also used the Tracking Station to jump into a living spacecraft and the option not only was still deactivated when I checked the Dialog, the feature itself wasn't active as expected.
- Activating the feature on the Settings made it work again, so the cycle is closed.
So:
- there's something fishy in your rig; or
- your are using an old DOE's release (just checked SpaceDock and CurseForge, I confirm they have the latest); or
-
there's something that you are not telling me on the bug report
- (perhaps a use case that I had messed up, and that wasn't tested by this simple test session I did).
So please send me your KSP.log so I can check the options 1 and 2, and please describe step by step (like I did above) how to reproduce the problem, so we can rule out (or not) the option 3.
-
When you hit "stage" by accident...
QuoteA befuddled crewmember near the plane’s tail reflexively shouted “Bombs away!” Carp, meanwhile, came barreling out of the bomb bay exclaiming “I didn’t touch anything! I didn’t touch anything!” The B-36’s radio operator sent a frantic distress call to base, telling the horrified tower operator, “We dropped a hydrogen bomb!”
Poor cow.
https://medium.com/@shermikeholmes88/the-time-we-accidentally-nuked-new-mexico-301489770be2
SpoilerThere's also another similar incident, involving a B-47 in South Carolina - some people got hurt in this one.
Specially worrying, however, was the B-52 incident also depicted on the same article.
-
I fail to see how a Game Industry professional plans to enrich its resume by violating the EULA of a competitor (or former one, who knows nowadays).
You know, their employer also has a EULA to enforce - and I really don't think such employer would be proud of their employees violating EULAs on the wild - their business model depends of EULAs being enforced!
(or to hire someone that did that)
-
I'm playing this nice "little" game called Dome Keeper, suggestion from my son.
Hard as hell initially, I took weeks until I finally got a grasp on it and started to win a round now and then.
There're less demanding modes, as no enemies (essentially, digging without worries) and automatic weapons (that do the service by themselves, but you need to upgrade them or you will be overrun). But they are available only after completing a full cycle, damnit.
-
5 minutes ago, DDE said:
It keeps coming up and coming up. I know several sides in WWII had this sort of kit. This was the latest known attempt to bring it back:
You know... Sooner or later someone will try to deploy Commandos with these things! ("Commandos away...."
)
-
55 minutes ago, Hotel26 said:
Not before it runs on Linux. Show-stopper.
Proton is doing a pretty good job on simulating the Windows API nowadays, but I agree that Linux native is, most of the time, better. Problem is, as usual, Unity support.
-
2 hours ago, kerbiloid said:
Could drop 'chutists.
Or pigeon bombs! (but with the pigeons replaced!).
Way easier to train, but extremely hard to deploy...
(could work to the japs, however...)
-
Crazy, almost desperate idea from WW2 era: doing MEDEVAC on pods mounted on the bomb mounts of a P-38.
What could possibly go wrong?
("Bombs awa..." uh... Whoops.. 
)
(but it would be a hell of view!)
https://aviationhumor.net/experimental-air-ambulance-version-of-the-p-38/
-
On 4/22/2024 at 6:34 PM, Quick_Nils said:
My best guess is that the cause was the version of module manager. I had the problem with
version 4.2.3 (wich i believe is the newest). Waterfall comes bundled with version 4.1.4.Never allow more than one ModuleManager to be present in your installment. Some older DLLs don't have enough meta-data to allow KSP 1.12.x (and only it, previous releases were a yet worst mess!) to try to figure out what to load.
Being not bad enough, I have evidences that some rigs are prone to fire up more than one instance of MM at once when this happens, and you end up having race conditions on the patching - this really screws up things. This appears to victimize MM 4.2.3 in special because, in the majority of the situations where a doppelgänger is also running, the most evident problem is the Localization's patches being screwed (with nodes copied inside themselves, really a mess). I could only detect this one by eye balling the ConfigCache - a very tedious task...
Since it's not feasible to determine in advance which DLL is safe to have as a doppelgänger and which is not, the safest and easiest way out of the mess is to avoid having more than one Module Manager DLL in your rig as it would be plague (what, in essence, ends up being sometimes).
As a matter of fact, I'm diagnosing some complex installments and decided to install MM 4.1.4 and 4.2.3 at the same time to see what happens with the patching on KSP 1.12.5 (MacOS).
This ended up allowing 4.1.4 to be ran instead of 4.2.3, as the following log excerpts demonstrates:
[LOG 21:50:19.605] ******* Log Initiated for Kerbal Space Program - 1.12.5.3190 (OSXPlayer) en-us ******* Kerbal Space Program - 1.12.5.3190 (OSXPlayer) en-us <yada yada yada> ************************************************************************ Environment Info Unix 7FFFFFFFFFFFFFFF Args: KSP -crash-report-folder /Users/lisias/temp/ksp Mod DLLs found: Stock assembly: Assembly-CSharp v0.0.0.0 Scale_Redist v1.0.0.0 / v2.5.0.62 ModuleManager v4.1.4.0 ModuleManager v4.1.4.0 <----- doppelgänger!!! <yada yada yada> [LOG 21:50:48.120] [ModuleManager] version 4.1.4.0 at /Users/lisias/Workspaces/KSP/runtime/1.12.5/GameData/ModuleManager.4.1.4.dll won the election against Version 4.1.4.0 /Users/lisias/Workspaces/KSP/runtime/1.12.5/GameData/ModuleManager.4.2.3.dll
So, and assuming that you just installed things by unzipping the whole contents without removing unwanted things after (the most usual M.O. on userland), it's pretty unlikely that MM 4.2.3 would be causing any trouble for you, because 4.1.4 would be the one being run, perhaps twice (I never managed to reproduce this MM being run twice behaviour on my rig, it appears to be tied to some CPU models).
So, in a nutshell, never, ever allow more than one Module Manager be present in your whole rig.
=== == = POST EDIT
On 4/21/2024 at 4:41 PM, Quick_Nils said:I deinstalled everything thats not needed and its still happening
Well... I did this test: tried the GDLV3 stock craft on a test bed exactly like this one. In one test session, I used MM 4.2.3, and in another I used 4.1.4.
In both cases, the ConfigCache generated were identical (compared char by char). There's no way MM 4.2.3 would caused the problem you depicted.
In both cases, the image I got was:
Whatever is happening on your rig, changing to MM 4.2.3 must be a coincidence.
But, to be certain, I suggest you do what I did:
- Install MM 4.2.3 on this test bed. Delete ConfigCache.
- Fire it up, fly the GDLV3 and see what happens
- Rename the ModuleManager.ConfigCache to ModuleManager.ConfigCache.mm423.
- Remove MM 4.2.3, install 4.1.4.
- Fire it up, fly the GDLV3 and see what happens
- Rename the ModuleManager.ConfigCache to ModuleManager.ConfigCache.mm414.
- Compare both ConfigCache for differences.
I think this may be related to VRAM (there are too many programs using video et all opened? On my old potato, I could not watch Youtube and play KSP at the same time!). Perhaps deleting the Settings.cfg and the PartDatabase.cfg (on the same place where the EXE file is) would help?
If nothing helps, post your full KSP.log (quit KSP before copying the file, to prevent KSP from truncating it) after reproducing the problem again. I would like to see it to check if I find something on it that I recognize.
-
EL&P - Eternals.
-
"When the people want the impossible, only liars can satisfy." Thomas Sowell.
Originally aimed to politicians but, boy, it's also perfect for Software,
-
So, it's bad to have too many issues opened in a repository.
Ok, I can accept that. So let's hire more people to tackle the issues down, right?
No! Let's create a bot that will automatically close all the issues after a week!!!
What could possibly go wrong?
-
-
9 hours ago, kerbiloid said:
So, NASA and Voyager are exchanging with videocassettes, sending them to each other?
Makes sense.
As someone that "been there, done that"... Videocassetes had a way better noise/signal ratio, and we could save our programs using it faster and with more reliability than using audio cassettes.
-
There's always someone going the Kerbal way on everything!! A racing car with AIR BRAKES!
(and the turbo intake on the pilot's left ear!)
https://uopshadowicons.com/product/can-am-shadow-special-edition-package/
-
This guys are really great. Blue Man Group.
Forum refused to embed this video, something about an Emoji.
But since we are here, I also found this very interesting video clip (who else called these "video clip"?). And, yeah, it tells my age.
-
12 hours ago, SunlitZelkova said:
What am I to believe? How am I supposed to ascertain the true reality?
You summarized the absolutely worst problem we have in our modern times. We just can't trust anyone anymore.
People had abused science in the past (see the tetraethyl lead scandal in the 20s, or the thalidomide on pregnant women in the late 50s, and many more), so we have precedence. It's not unreasonable to doubt Science, as long we have someone trustful to cover our
ar... hummm...backs on things we don't understand.We have a confidence crisis as we don't see for more than half a century. Something is broken in our institutions - worst, in the remedies our society had to countermeasure bad actors in our institutions.
How to fix that, it's something I left as an exercise to the reader (in the hopes someone answer it, because I just don't know).
About specifically the problem at hands, Climate, I have some random facts that we should take in consideration:
-
Antarctica was a Tropical island in the far past
- yeah, Earth was that hot once.
- Oh, yeah²! There're volcanoes under the ice caps, potentially melting some of the ice too!
-
There're ruins of ancient cities on the bottom of the Caribbean sea
- yeah, Earth was that cold once (as the polar caps took way more water than nowadays, and the sea levels were way lower)
-
Ice Ages are regular in this Planet, and the next one is already due.
- We are in borrowed time.
-
It's hundreds of thousands of years since the atmosphere of this Planet had so much carbon as we have today
- What may be good for the overall planet on the long run, besides royally screwing us in the short
-
Research about the Carbon Cycle, and how Life depends of it
- And how planets die when the Carbon Cycle ceases
- We are polluting our atmosphere with things way worse than carbon
- We are polluting our fresh watersheds with nasty things as mercury (Hg)
- We are decimating our fresh water underground reservoirs.
-
We are exhausting the Oceans fauna with uncontrollable fishing. We are contaminating the Oceans with nasty wastes (like micro-plastics).
- And this is screwing up the oxygen production, what the oceans respond with 50% of its renew in the whole planet.
- And more to come.
To the best of my knowledge, we are - indeed - witnessing a climate change. One of many that this planet had seen.
We are responsible for it? I'm pretty sure we have had contributed a bit, but the last ones happened without us, so I take all of that with a grain of salt.
But what we should really be worrying about is about the destruction of our sources of breathable air, fresh water, sea food and a potentially disastrous breakage on the Oxygen Cycle on the whole planet - and I don't see anyone talking about it.
-
Antarctica was a Tropical island in the far past
-
This thread is a bit old right now, but it's still the best place to discuss the matter.
A few months after this thread, the US Court of Appeals decided that claiming Open Source on a code not licensed under a OSI approved license is false advertising.
Court affirms it’s false advertising to claim software is Open Source when it’s not
For a false advertising claim, there must be a false statement in commercial advertising and the statement must be deceptive in a material way. The trial court held that characterizing software that was under the Commons Clause as “free and open source” was false.
Do not misunderstand Commons Clause with Creative Commons, they are two different things - but it's important to notice that Creative Commons is not listed as a Open Source license neither.
https://opensource.org/license
-
I just can't believe no one had mentioned this one before (or, at least, I didn't found it): He 111Z (Zwilling - Twin)
http://www.diseno-art.com/encyclopedia/strange_vehicles/heinkel_he_111z_zwilling.html
Two He 111 bolted around an additional engine, and called it a day.
-
30 minutes ago, MechBFP said:
I can really only assume some stupid and/or malicious overlord had better ideas how to run things and the team is unfortunately along for the ride.
I have absolutely no doubt about it.
Technical managers on my company (me and a business partner... hehehe
) made a very, very stupid decision 4 years ago. The dev team (me and that business partner!) is still fixing the consequences due that mistake (we fix a symptom, something breaks somewhere else - and I can't fix the root problem because a core subsystem installed on the clients depends of that mistake... ).
I don't expect these dude's life be easier than mine.
Writing software is easy. Writing software professionally is hard. Writing good software and staying profitable is really, really hard.
-
50 minutes ago, RayneCloud said:
With respect, we're not having expectations managed, because we're hearing very very little. One dev post about lighting since Dec 8th, and some sneak peaks and a nate vid that know one knew was out until it was linked here, is not enough. We've been told to expect more communication for 4 months and we have not gotten it to a satisfactory level, at least I will speak for me personally on this. Forgive me if I come off disrespectful here Dakota, it is not my intent, but we need more please.
It's pretty hard to manage expectations after a huge hype campaign followed by... hummm... a somewhat less than expected initial release.
There's a lot of promises (as well tons of plain statements taken as promises) made in the last years that are probably going to be broken, and without a viable release to use as a trade-off (ok, A is not going to happen, but look! B & C were implemented instead!), at least in my book, the less technical details (or any details that can be used by technicians to infer the state of the game) you publish, less work you will have on managing a new loot of fallen short expectations.
It's kinda of a catch-22 situation: you talk about, you get screwed. You don't talk about, you get screwed. Finding the less bitter spot in which you get less screwed is the trick.
(don't look at me for answers - I'm on the "talk too much" spectrum)
-
1 hour ago, kerbiloid said:
Wrong. It's a definition of a median person, not of the average one.
I think both you are misunderstanding median and average with... mode.
-
Do you know when you are reading/watching stuff on your mobile on bed, and the mobile slips from your hands and falls into your face (usually your nose)?
Steam Deck is worse.
-
Take a plane that it's being mercilessly bashed by the competition, replace the wings and go for the win!
(As long Editor don't mess things up!)
Grumman Panther.
(And the wings really made huge difference on the design...)
) test bed, where I have installed all the add'ons I publish on the latest releases, and... It's working for me. 
)
)
[KSP >= 1.3.1] Distant Object Enhancement (DOE) /L - Under new Management - 2.1.1.15 - 2024-0103
in KSP1 Mod Releases
Posted · Edited by Lisias
post edit
Coding stupidity
- I should be to sleepy when I wrote that code, I was literally overwriting the good contents from the file with default values meant to be used when there's no file. 
I'm prone to these facepalms mistakes regularly.
Yes, it is. I think I know already what's happening. I will check your log and edit this post with the findings.
--- -- - POST EDIT
Yep, you are using Steam:
And I'm guessing you are using that dirty trick in the Launcher to avoid the PD Launcher, I'm right?
That trick causes too much collateral effects (even KSP gets screwed, you will find a lot of files in the wrong places, as the settings.cfg and the screenshots, a mess).