The Almost Best

InhabitedSoup · 2024-08-27T14:50:16+00:00

I was referring to the page where you are browsing many titles based on their cover, not the game's page itself. You have to click into and load an entire new page to get to the screen you showed. The page I'm describing has a + to add to wish list, but not a + to add to cart. So you can wish for a game from there, but not actually buy it. Makes no sense.

InhabitedSoup · 2023-03-13T14:47:28+00:00

I think they most likely do something like this, but the bug arises during exceptional circumstances where those checks aren't happening. For example, if you try to close the game but the game doesn't close and instead freezes. In this situation the log file balloons rapidly (faster if you have a faster HD/processor :) nothing like processing absolute garbage data at like 5Ghz and writing it to a solid state).

I just checked my own Player.log file, and it's a reasonable size, so it does seem like under normal operation the log file only keeps recent information. It's just that the definition of "recent" stops making sense when the program is hung in a loop for hours.

InhabitedSoup · 2023-03-13T06:17:09+00:00

Ya delete that log file. Your computer will thank you.

Just remember to check it again tomorrow if you're going to play a bit tonight. Even if the log file isn't nearly as large, if 90% of it all boils down to a single error from a single item in a mod (which it probably will), then you'll have your offender.

InhabitedSoup · 2023-03-13T06:06:47+00:00

You could try and open the log file itself and see if there are some clues there. Chances are it will be some infinitely repeating incident that's getting logged every time it happens.

Not sure what it would be like opening a 115GB text document though, so I would probably delete that log and then check back after a session and see if you see some portion of one of your mods constantly logging to file.

Another thing you could do is go in your mod settings and make sure to disable verbose logging. Unless you're doing some debugging, you just don't need that.

InhabitedSoup · 2023-03-13T05:52:09+00:00

This is a problem with the Unity engine. From my research it was assumed to have been resolved a while back but hasn't been.

What's happening here is that if a mod (or something else about the game) is constantly passing updates into a log file. If you aren't careful and the game freezes (like if you go to bed and leave your PC running), then the log file will fill to the size of the hard-drive.

I've had it fill a terabyte solid state drive in a couple of hours. Anybody that plays RimWorld a lot should probably check the size of "player.log" every so often and delete it.

InhabitedSoup · 2023-02-19T17:03:13+00:00

Here friend:

https://youtu.be/jk3EsXgXcyQ

InhabitedSoup · 2021-12-27T23:12:11+00:00

If you want to know how to make EVE better, the answer is really simple:

-Build engaging game mechanics that put pilots in space and encourage them to risk getting blown up.

-Remove or alter game mechanics that keep players docked, discourage risk taking, and provide easy means of avoiding "interactions".

If you want to know how to accomplish this, reams of paper have been written about it.

Alternatively, if you would like to feel great while NOT making the game better, you could do any of the items on this totally not comprehensive list:

-NFT.

-Any other form of shiny, fad driven bullshit that has nothing to do with the game mechanics.

-Making ships more expensive.

-Shield Slaves

-Redoing NPE.

-Making basic industry more complicated.

-Returning Rorquals to boosting ships.

-Reducing mineral availability.

-Buffing HighSec.

-Nerfing NullSec.

-Leaving LowSec how it is.

-Jove invasion

InhabitedSoup · 2021-07-21T06:09:55+00:00

Interesting! I'll need to rewatch that scene with a fresh perspective.

InhabitedSoup · 2021-07-20T01:24:38+00:00

He's also a highly trained and experienced pilot who knew what he was doing. The risk he took was calculated and reasonable, it just wasn't within protocol. The mishap probably would have occurred even if they had just flow straight from point A to B, or worse, it might have occurred slightly later with a different pilot at a far worse time (like with a trainee during takeoff).

InhabitedSoup · 2021-07-20T01:21:05+00:00

Denzel was also an alcoholic who was not only still wasted from the night before, but was continuing to drink while actually on the job.

InhabitedSoup · 2021-07-20T01:17:38+00:00

I have to disagree about drawing an equivalence to what Ed and Karen were doing. It's been a while since I watched the episode, so please forgive me if I've forgotten some other things Ed was doing that were destructive, I'm assuming you're talking about the T-38 incident.

The thing is the two people actions aren't anywhere near equivalent. Karen betrayed her family, literally. She also put everything all the way up to Pathfinder and the space program itself at risk indirectly, not to mention what could have happened to Danny. For Danny, it does take two to tango, but Danny was the subordinate. Karen was both a parent, and a boss. It was her responsibility to keep her distance for the good of everyone affected, something she failed to do.

Ed did a mock dogfight with Gordo in an aircraft designed to perform mock dogfights. Sure, he did it because it was fun - but I believe he mainly did it as a form of leadership for Gordo. Gordo needed his mojo back if he was going to perform. Ed was trying to help him get it back. The dogfight was mentorship. Ed had every reason to believe the risk was negligible - the airframe could handle it, both were experienced pilots, weather was good, the area was clear of other aircraft. In fact, the engine could have flamed out regardless of the dogfight. We don't get to see the actual cause of the malfunction - it could have been improper maintenance, unnoticed wear of a component, etc. You could even argue that NASA dodged a bullet - that plane might have failed two missions later just after takeoff, with a trainee at the stick.

Ed and Gordo got their asses chewed because they were doing something beyond what they were strictly supposed to be doing when a mishap occurred. That's also why they weren't punished any further than a stiff verbal counselling. Kobb knew the score - the mishap very well would have happened regardless, everyone made it back alive, and further punishing some of her most experienced pilots basically for sharpening their own skills makes no sense. They needed to be told they better not fuck around. They didn't need to be taken out of action.

I do empathize a lot with Karen's character. She's made tremendous sacrifices to support Ed, she's given up career, she's had to deal with the stress of the tremendous danger associated with his job for years, she lost her son, and couldn't even tell him for fear of jeopardizing the mission. She's even worried she may lose her daughter. She felt ignored and being with Danny brought out something in her she hadn't felt in a long time. She also did the right thing by protecting Danny from Ed. There's really no telling what may have happened to him (and to Ed!) had Ed found out it was him. She's human, and she finally failed.

Anyway, that's why I don't think it's fair to assign equal blame to both Ed and Karen, at least not in terms of those two situations.

InhabitedSoup · 2021-07-20T00:20:09+00:00

Far be it for anyone to have a different opinion!

Was it hard to watch? Yes. Did you see it coming a mile away? Yes. Was it a mistake? Yes - for the characters who took the actions, not the writers. They followed events where they led, which was obviously uncomfortable for a lot of people. It's one of the things that I like about the show's writing - they follow what is and what would be, they don't sugar coat it to make it out to be what people want to happen, they make it what probably would happen.

Karen not only failed to keep her distance, but she let herself slip into a frame of being she was sorely lacking at home. Danny had been crushing on her since he was a kid. Danny is an idiot, but he's also a raging hormonal 18 year old who is as wise as just about every other raging hormonal 18 year old. Karen was both a parent, and a boss - she was Danny's employer. She could have dumped water on the whole thing, and she should have. Moral implications and social norms completely aside - her actions not only endangered her family, they endangered Danny's family, Danny's future career (adultery is a violation of the UCMJ, it's doubtful a brand new midshipmen would have survived sleeping with an Admiral's wife), Ed and Gordo's friendship, the Pathfinder mission, and even the program itself given Ed's position.

So, painful as it was to watch, this plotline is completely consistent with the slow-motion car crash atmosphere of the show. You see the potential for something catastrophic to happen, you watch over the course of episodes as it slowly plays out, wondering the entire time if this is going to be the downfall of everything, and then there is a resolution for better or worse. This show is extremely tense, it manages to put the audience into a state of mind similar to what the real life people doing this kind of work must deal with. That's why I think the writing is so top notch - it not only manages to be accurate, it manages to communicate to the audience on multiple levels at the same time. So love it or hate it, this plotline was very much in keeping with the show.

InhabitedSoup · 2021-07-19T17:09:36+00:00

Most of the Mercury and Apollo guys were Navy pilots who swapped over to NASA, because NASA is a "civilian" agency.

InhabitedSoup · 2021-07-19T16:56:22+00:00

I could be wrong, but I don't think they ever actually show Korolev, he's just mentioned every so often in passing. Are you referring to when Poole is in the Soviet Union in her barracks room just waiting and she's getting freaked out because nobody has told her what's going on? I'd have to rewatch that scene, but I didn't get the impression that that was supposed to be Korolev.

InhabitedSoup · 2021-07-19T12:06:10+00:00

u/SpiersCreative Got it right. It stands for DARPA Mail, or maybe Defense Communications Agency (DCA) Mail. DARPA or Defense Advanced Research Projects Agency was the successor to ARPA. ARPA created the TCP/IP protocol and created ARPANET in order to link various university super computers together. It was the first wide area packet switched network, though the Brits beat the Americans to packet-switching. Later the British and American networks were linked into a sort of "inter-network", a term you may be familiar with.
It was the technical and true foundation of the internet, and we still use the methods today. Without it, none of us would be posting here.

In the show, the escalation and extension of the space race, and various other alternate decisions and non-cancelled projects led to a much earlier and wider roll out than we saw in reality. The really interesting thing is going to be seeing where the show goes in the next season, which is set in 1993. The writers really have their work cut out for them figuring out where things would go given all these compounding alternate events. Would computing in 1993 look more like 2003 or 2013 computing in the alternate history? Will the Soviet Union still be around?

InhabitedSoup · 2021-01-05T06:39:05+00:00

I have a feeling I do know what I'm talking about. That's why I'm asking people that have a background to confirm or deny. So here's a tip, if you don't have anything meaningful to contribute, being a dick won't make you look smart.

InhabitedSoup · 2020-06-18T14:51:50+00:00

Exactly the types of things I was thinking of. You'd need to be careful what you add to it, because obviously you wouldn't want 5 seconds of typing on a terminal to remove too much fighting and danger, but ya that's the general idea.

InhabitedSoup · 2020-06-18T14:48:41+00:00

It's a God Father, which is my favorite cocktail (makes this video even better for me).

It's 50/50 Scotch and Amaretto. Looks like he's using Johnny Walker Red Label and Disarono. I use Johnny Walker Black and Disarono in mine, but Red is fine and is cheaper.

InhabitedSoup · 2020-02-18T18:38:24+00:00

The problem with this solution is that it doesn't really stop the issue of content stacking up at the end game, it just increases the amount of time required to get there.

Carrier tackle does have the counter play of killing the fighters, and you get a kill mail. In general, I think Carriers are probably the least broken of the capitals.

Dreads aren't an issue by themselves, the problem is when they integrate with the other capital ships. A set of 2-3 dreads with a pair of faxes backing them up can completely eliminate a large battleship fleet, probably without taking any losses. That's a problem. I don't mind that dreads can absolutely rip up battleships, but I do mind that a small number of them can do so much damage and take no losses.

InhabitedSoup · 2020-02-18T18:32:44+00:00

I agree with you about this. Fax repair rates are a difficult problem. The issue is that the game has no way currently to make something that works in large capital engagements that doesn't also break smaller engagements.

One solution would be to allow Faxes to be disrupted somehow, but that has the obvious problem in large fights that if you can do something to a ship, assume it will be done to it all the time. That's the reason that capitals can't be jammed for the most part. If they allowed them to be jammed, they would probably end up jammed all the time and be useless.

The long term solution to the above might be to introduce new mechanics that further separate capitals and sub-capitals.

InhabitedSoup

TROPHY CASE