Jump to content

All Activity

This stream auto-updates

  1. Past hour
  2. discord has a timer that automatically invalid links unless you refresh the timer by posting it again on the same Discord server, so it is not recommended to use it to host files
  3. Mildly curious: Were you the parent or the kid? Today I loaded 400 rounds of 9mm ammunition, cleaned the kitchen, and played a game of Ticket to Ride with my family. And consumed an adult dose of alcohol. In an appropriate order. Tomorrow I am going to attend church, cook breakfast, and then attempt to duplicate Zankou Chicken for dinner. Pray for me.
  4. youtube videos are rife with this kind of nonsense. conflating anything that ticks their confirmation bias way out of proportion. ive never seen so many people "destroyed" by some cherry picked thing some disconnected personality said. i guess its a working formula that makes excellent clickbait. and whats with all the destructive language? they make it sound like they are in a fight but its always some cowardly jab from behind the curtain of anonymity. the comment section is just as bad, usually its an echo chamber and people still get into hissing fit over their flavor of agreement. posts from the other side of the argument get deleted.
  5. This short story alone is why I hate four-color comics. Except for The Dark Knight Returns and Watchmen. And sometimes Sandman.
  6. Today
  7. Floor 4773: A museum cataloging all three Number Wars, including ones that didn't last long since there were already ones that were ongoing. Museum staff rush to update the Third Number War exhibit with new artifacts.
  8. Thinking about Robert Palmer again tonight. The James Bond of Rock. RIP.
  9. Well, it won't blow up. Accumulation of hydrogen it stripped off its binary companion will blow up on the surface, leaving the rest of the white dwarf intact to collect more hydrogen over the next 80 or so years. This might sound like I'm nitpicking, but the reason for it is that it might actually explode. Like, the whole star. Every time a white dwarf goes through a nova cycle, it gets a little heavier, and that will eventually lead to a core collapse and a Type Ia supernova. The T CrB is currently at 1.37±0.13M☉, which might be really close to the Chandrasekhar limit of ~1.4M☉. If the scales are tipped this time, we might get a much bigger light show than anyone's expecting. It's pretty unlikely on the net, of course, as the mass grows over a very long time, but it has to happen eventually. If it does happen, we'll be looking at a nearly -10 magnitude instead of a +2, which is almost as bright as a full moon, except coming from a single point instead of being spread over a disk, meaning you're not going to miss that in the sky, and you'll probably see it even through a moderate cloud cover. Plus, it will be that absurdly bright for a few days, and will leave a visible remnant for a good amount of time longer. Again, I have to reiterate, it's pretty unlikely that it will be this time. In fact, seeing a random, unexpected supernova might be more likely. But a +2 nova that you can fairly reliably count on this year is still about as bright as the North Star, which is still cool. So I strongly recommend to anyone who's interested to go and look at the Corona Borealis next time you have decent weather, because it's not that exciting to look at a +2 star unless you've looked at that patch of the sky before and know that this star wasn't there. And maybe get into a habit of looking at it every time. Sure, it'll be on the news when it happens, but it's so much more fun if you get to discover it for yourself. Just looking up at the sky and seeing a star that wasn't there yesterday.
  10. What are you confused about? I said I think Take Two is making a watered-down version of KSP for KSP2, and every official word and release has proven me right so far. Its also been a huge factor that a bunch of the white knights around here don't bother reading what I write and end up taking what I'm trying to say in negative directions unnecessarily. Its a two way street. Nobody is "doomsaying" anything. People are making observations based upon evidence available to everyone. Remember, this is the same company that did GTA Definitive Edition. I'm not trying to start a debate about Take Two, I'm just saying thats a reason I do not trust them. Edit: Sorry everyone, I don't use emojis, I'm laughing as I type all these replies. To prove I'm not just some grumpy jerk, heres what I did today between my two posts:
  11. Sorry for the double post, but this threadis still stickied. Here is some B-roll I made into a trailer of sorts to hopefully keep interest in this challenge until myself, NexusHelium and anyone else participating get a chance to finish
  12. I've read a lot from the discord server, by trial and error have written a .patch file that does not upset the log. While the patch 'should' change the capacity, starting charge, and charge rate for the 3.75M RTG, testing shows no effect at all.
  13. I'm not trying to argue. Just legitimately confused. People seem to come up with fantastical stories of what the game is and is not rather than listening to the official word. It has been a huge factor in the community going all sorts of negative directions unnecessarily. Nothing good comes from doomsaying over assumptions.
  14. Granted. ... ... ... I wish I could come up with creative things to comment in forum games.
  15. Here's both of your shaved ices. I'd like a pancake, shaped like a waffle.
  16. Some of the Tantares textures for Soyuz were updated in the latest release and the old files referenced by that part are no longer part of the currently shipping mod. You can fix by downloading an older version of Tantares, copying the necessary texture files to a personal patch folder inside GameData and then modifying the part config to point to those new file paths (either directly or with a ModuleManager patch). The relevant texture references are in GameData/BuranOrbiter/Parts/Buran_airlock.cfg at lines 39 to 43.
  17. I'll update DOE with a new version of KSPe.Light that would had mitigated the problem for DOE anyway. I should had done this sooner, anyway - but, then, you would not had reached me and would be with a sabotaged Auto Actions, so... I really hate injecting such gambiarras on the main stream, but the sad true is that this Scene, salvo really rare exceptions, don't give a rat's cheeks about safety and do things the absolutely easy way completely disregarding the consequences - and then blame the poor stand-up guy that ends up being hit by the crap when things goes South. I think I need to think on something to be put in the KSP.log to help the next fellow Author to detect this problem - what can also be another source of vitriol as I got early this year on reddit - it's incredible how some authors really goes the extra mile to fight anyone and anything that could prevent problems happening on the field. On a final note, this PD-Launcher stunt is absolutely terrible. The damage this piece of crap is causing on the Scene is beyound imagination. How hard would be do add a "No Launcher please" option and just go straight to KSP if the user asks for it? Thank you for bringing me this issue to my attention in a constructive way.
  18. While I’m also unhappy about KSP2 progression this post does absolutely nothing. You gave no finer details besides “the game is still no different to KSP 1.” You provided zero insight, didn’t mention any features that you feel are lacking or any ideas to improve upon, fix or implement. Have you provided any bug reports? What was the goal here? What if a developer decides to read this post, what do you expect to happen? “Oh OP99 is unhappy, let’s get the ball rolling right now!” This is not the way… Also you compared this to a game that’s not even in the same category, has entirely different gameplay etc. move along, you won’t be missed.
  19. While I continue on the long grind for the F-14B, I am having an attack aircraft with a talisman (that I got by pure chance) take its place to save backups in Air Arcade matches, speed up the tech tree research, and also gather crew points for when I finally get the F-14B. Also, last weekend, some new friends I made at the Air Force Museum wanted to check out the Memphis Belle II. It felt right that I make a replica of that plane next. And so, without further ado, here's the F-105 Thunderchief. The F-105 Thunderchief on display in the SPH. I included the aka in the craft name since it was a popular nickname for the plane and so plane enthusiasts who know it can find it. I tried to add the airbrakes in the back. According to War Thunder and pictures I found on the internet, the real Thunderchief’s afterburner could open up and function as an airbrake. However, I decided to scrap that idea since my attempts to add them proved useless. At least I included a drag chute (but I didn’t really test that part). The air intakes were a rather interesting challenge. They were not only positioned right where the wings were attached to the fuselage, but they were angled to go outward. To maintain aesthetic, I chose a Panther engine for this craft. However, part of me wanted to go with a Whiplash for performance since most of my other replicas that used Panthers did not do so well. The Thunderchief ascending to cruising altitude at quite a steep angle. It was approaching Mach 1 when the pilot decided to speed up his ascent. The sad part is that, unlike its real-life counterpart, this plane never made it past Mach 1. Settling at a cruising altitude after the initial ascent. Historic footage of the famous F-105 named the Baikerbanur Bombshell II cruising over Kerbin’s desert. It is currently on display in the Super-Cool Aircraft Museum. The original Baikerbanur Bombshell was a B-17 Flying Fortress that participated in the Second Imperial Wars - and is also on display in the Super-Cool Aircraft Museum. However, the F-105 did not get nearly as much fame as the B-17. Just like in real life, the Baikerbanur Bomshell II could carry more bombs than its namesake predecessor from the Second Imperial Wars. The Thunderchief ending its test cruise after approximately 43 minutes of flying at full throttle and only 30 fuel units left. The KSP replica's cruise performance stats were as follows: Altitude: 10.9 km (~35.8k ft; Class Alpha airspace) Starting Velocity: 290 m/s (~649 mph) The cruise ended at 320 m/s (~716 mph) Recommended Throttle: 100% Flight Time: ~43 minutes Expected Range: 760 km Old photograph of an unknown pilot walking out of his F-105 after landing. I've noticed a pattern in my planes' performance when it came to the Panther engine. Specifically, even when it was in wet mode, the plane did not fly supersonic to start. If it did go fast, it would be within the last five minutes of powered flight before landing. Any ideas why that's the case? Anyway, until I get that issue resolved, I might want to stick with the Whiplash for supersonic planes. Replicas Remaining: 201
  20. Yes, I am using that trick. Forgot to mention that. This is the first time I'm bothering with steam, thought it might be convinient for track time spent in game, but there is also a mod for that I can just use. Just tested launching KSP directly instead of through steam, and what do you know, fixed my issue with DOE and Auto Actions. I'd read that using that PD launcher killing trick could break steam interface elements, I was unaware it could mess with things in game as well. Thanks for the speedy and helpful responses!
  1. Load more activity
×
×
  • Create New...