Search the Community

This new log have essentially the same exceptions from the last one I checked. No news, everything appears to be the same. There's no other option but to talk to FAR maintainers - I don't know this thing, I don't have the slightest idea about how to fix it. About the CryoGenic Engines, I checked the dependencies. It needs Cryo Tanks 1.6.3 - but the latest release is the 1.6.5. I'm guessing you need to downgrade it to 1.6.3 to fix your issue? It's a wild guess, it's safer to talk to Nertea about it. You may want to reach CKAN guys too and see if they didn't forgot to set something on the NetKAN file. CKAN is giving me some headaches since some time already, by the way.

Are we talking about the real problem now? Because if yes, then I can say something about it. Assume we want to keep the Rigidbody+Joint idea of KSP (which I think is not bad) and lets say we want to keep the idea of wobble and failing rockets due to non working connections and stuff like that (which I also like). Then what is the problem with that? Well, it's that when you connect a heavy part to a light part and then again to a heavy part, that won't work. This is what I call "mass inversion" in KJR Next. You have this e.g. when you add decouplers (with their own Rigidbody). And that's all. This is the only problem. You need to fix those "mass inversions". (h - h = good / h - l - h = bad) One idea is to hope for a redesign of Unity... or PhysX. And I know, one day they will do something... like e.g. adding other properties which define strenght and not only mass. The other idea is, to build an additional joint from the heavy part to the heavy part and not going via the light part. Again -> look what KJR Next does. And then, we sometimes still have other instabilities... but those are small and we could talk about them in a very different way. Most (if not all) of the problems come from those mass inversions (at least in KSP 1). Some problems like oscillating vessels come from poor SAS. And this solution works for everything. From huge to tiny ships. Interstellar ... whatever. Because it addresses the problem in the game engine. (other solutions with not adding some additional joints could work too... but, in the end you need to get rid of the h - l -h connections).

Ji, ji, ji..... I see that everyone took the bait that was thrown at them. Will they spend months trying to find solutions and come up with proposals? And in the meantime we will not talk about the fundamentals, the final delivery date. Ji, ji, ji.....

For a lot of people here that's totally understandable, but just because there's a lot you can't talk about doesn't mean you can't talk at all. It's not a secret that the reception of the game is... shall we call it, mixed? Even a short message saying "we received your feedback. Our goal is to make you love the game as much as we do. Keep in mind that our first patch needs to make things better, not worse, so we want to ensure that what we roll out is well tested, but it might not be as quick as you want it to be. Having said that, we're busy categorizing your feedback, and prioritizing on what we can and need to fix first, and we will keep you updated on the progress we make." which really doesn't say anything most of us already know.suspect is better than total radio silence*. Did the entire team ship out for a three week sabbatical in Babados? For all we know, yes, because we're not told anything. We won't eat you for "empty" messages like that, it means more to us on this side of the fence than you probably can imagine. * But Discord! Yes, but for good reasons a lot of people here avoid Discord, and they shouldn't be forced to get official information from another channel than the official forum they've been using for years.

It seems to me that the strength and mobility of the connection on the tank does not depend on what is connected there next. Simply because the force is greater, it bends more. Just like in the real world. Disabling mobility in many cases will most likely lead to bugs and fun Danny's videos. In general, it seems to me that this is more like talking about the problem in some extreme cases. In KSP2 it is difficult to make a replica of the Saturn-5, this would be corrected. And the talk that something in the game needs to be done right away well so as not to come back seems surprising to me, looking at the road map, for example.

That's why we need to talk about the problem. We need to understand it and then we (or, the developers) can try to implement a solution. So... what is the problem? ... the answer is easy: it is Unity. As long as you use Unity + RigidBody + Joints, you will have all the problems that you have, when using Unity + RigidBody + Joints. And those problems are well known, fully understood and we also know what can be done to against it. What works, what not. So... it's not like flying into a completely unknown part of the universe. We know why it is what it is and what can be done! Why are we talking about it, as if nobody has an idea what is going on? And by the way, for the "autostrut" discussion: we also know autostruts. We know how they work and why they are not a good idea. Why are we then talking about "autostruts yes or no?" instead of "why are they not good?" "what is the problem with them?" "can we find a better implementation?" "are there ideas?" ... it's so annoying to read about this without seeing a real discussion about solutions!

Maybe the argument should come less from the perspective of realism, and more from one of, is it FUN to require the player to use struts in this specific situation? As in, does it contribute to the stable rocket puzzle? Or does it get to a point where we're being forced to strut excessively? It's important to keep strutting down, if we can, to reduce part count and ease physics interactions between additional joints. There are cases where struts should definitely used, but like even Nate has said, vertical rocket stacks probably shouldn't need to be strutted to themselves to stay stable. I think that's the biggest gripe when people talk about wobbliness, though I welcome different perspectives.

Wishing to make a little novella set a few thousand years in the future where interstellar travel is comon. In the hopes of using time dilation as a plot device, I want to make some ships capable of travelling at close to c with a constant 1g acceleration, while staying within the realm of possibility. I was hoping you guys could help to make sure that the propulsion concepts i was planning to use were still scientifically accurate, for the most part. To solve the "where did you get all that antimatter?" hole, I know that the collision of two specific kinds of white dwarves can generate lots of antimatter. Since fusion reactors somewhat replicate the conditions inside a star, it seems feasible that a very powerful, unstable fusion reactor could produce antimatter. So what if the reactor destroys itself in the process! You have antimatter! Let's just assume it's a very expensie fuel source. The only somewhat cheaty thing i plan to do is give humanity thermocouples that are close to 100% efficient. I'd prefer not to have to deal with hundreds of kilometres of radiators. Now on to the ideas: Antimatter- So i know that typical matter-antimatter collisions produce exhaust velocities of about 0.33c. Too low for me. I also know that pure electron-positron annihilation produces velocities closer to 0.56c, which is what i need. Is there any possible way to magnetically store electrons on their own, or to supercharge normal matter with hundreds of electrons apiece and store that? (don't mind if the magnetic storage takes crazy amounts of energy (thermocouples!) or if some of the fuel decays over the two-year transfer time due to quantum tunneling). Also, what are the actual equations that are used to determine the destructive capabilities of antimatter? Bussard Ramjet- I know that these supposedly have a "terminal velocity" of 0.2c, but this assumption seems to imply that the hydrogen is sped up to roughly the same speed as the ship before being fused. I was planning to use a series of magnetic wireframe nozzles a couple hundred kilometres across placed a few light minutes at maximum in front of the ship to ionize the incoming hydrogen (using beamed power from the ship) and nudge it into the ship's reactor. These nozzles could also use the ionized hydrogen to propel themselves at the same pace as the rest of the ship. Light Sails- Probably incapable of near-lightspeed travel, but maybe a cheap way to transport cargo at reasonable speeds. A ship could use an engine to get close to a star, and then unfurl a solar sail at perihelion. A quick calculation based on the amount of power the earth gets tells me that a circular 100km sail placed 6.4 million km from the sun (the closest we can get a spacecraft with our current technology i believe) would be hit with about 3.0*10^16 watts of energy (give or take an order of magnitude). Is this reasonable? Black Holes- Could a black hole be used as a gravitational slingshot to get ships close to the speed of light? Thanks for reading this.

YEAR 3, DAY 288 - AURORA 1 Back to the Mun... I got a bit carried away with the screenshots for this mission, so it will split into two parts (much like Munar 1!) This is part 2. Crew: Jebediah, Bob, Valentina Aurora 1 approaching the Mun After a day of drifting through space, Aurora 1 finally arrives at the Mun. It's been a long time since even a probe has felt the tug of the Mun's gravity, as exploration of the Mun has kind of been at the bottom of the list for Beyond. Thus, still much is unknown about its surface. But hopefully our new long-term exploration program uncovers more about the wonders of the ancient object. For the next hour or so, the crew watch as the Mun gets closer and closer to their spacecraft, until it's right on top of the them! As the spacecraft reaches it's periapsis, it begins it orbital insertion burn. We've done it! We have Kerbals circling the Mun! But that's not all, as now the crew must prepare for the actual landing part of their mission. You know, the part that's interesting? Bob goes for an EVA, and inspects both the command module and lander. Once everything is confirmed to be okay, Jebediah and Valentina transfer into Nugget, and undock from Chicken. They now begin the most dangerous part of the mission. "Mission Control, we see Kerbin on the horizon. Beginning de-orbit burn." - Jebediah Kerman The lander slowly coast down to the surface, and once it reaches 5km, the suicide burn begins. It'd extremely nerve wracking, and the lander has to pitch up a few times to continue flying, but in the end... ...they make it too the surface. "Nugget is on the plate, I repeat, nugget is on the plate" - Valentina Kerman Nugget is the first object to stand on the Mun since the Munmun Rover... so maybe not that long but still. The crew spend thirty minutes on the surface, preforming science and whatnot, before they suit up and prepare for their EVA. Jebediah is the first out of the hatch. "Stepping down the ladder..." "Mission control, it's good to be home!" - Jebediah Kerman Not just mission control, but the world erupts into a frenzy of cheers! Kerbalkind was once again another worldly species! Brand new, higher def video cameras capture the moment in better quality. After about a minute of frolicking, Jebediah turns around to face the ladder to give Valentina a hand. She steps off and they both begin to talk to each other, debating whether they should or shouldn't stay. The decide to stay. Jebediah prepares the flag, and the crew pose for their flag shot. After the ceremonial stuff is over, the real job begins the crew begin to explore the area the lander. Science collection CREW VERBAL LOG JEBEDIAH KERMAN: Val! I found evidence of life on the Mun! A giant bird's nest! VALENTINA KERMAN: That's called a crater, Jeb. JEBEDIAH KERMAN: How do we know a bird didn't leave it? VALENTINA: How are you a kerbonaut, Jeb? After around 30 minutes on the Mun's surface, the time comes to board back onto the lander. Jebediah climbs into the lander first. Once in the lander, the crew will stay on the surface for one more day. This will be a test of long term habitation of the Mun, as crews on future mission spend longer and longer times on the surface. 1 DAY LATER... Aurora 1's surface time comes to a close, and the crew begin preparations for liftoff from the surface. Blah blah, orbit, you get the jist. Next is the rendezvous and docking with the Command Module. Rendezvous burn The crew dock with Chicken, and transfer over their science. They then prepare the burn back to Kerbin. They'll be bringing the lander back with them, so they don't pollute Munar space. It'll be separated the moment they leave the Mun's SOI. Undocking lander Parachutes deployed Aurora 1 has made it back home! A new frontier of space exploration has opened, and Kerbals are back on track to becoming a multi-planetary species. Next Aurora mission: Kerbals back on Minmus.

Manfred wakes up in a medical bay in an unknown facility. The medic catches him up on what happened and tells him the Riptide Commandos brought him here for observation. It turns out he's in New York City, at the CCC-NW Branch Headquarters. He is then escorted to an office by two armed guards. There in the office sat Director @TwoCalories behind a desk. He gestures to a chair, and Manfred takes his seat. The Director starts to talk to him. He asks what he was doing, as he was last known to be dying from Acute Dust Poisoning over forty years ago, and a cryopod, along with nine other CCC agents thought to be dead, was labelled with his name at a mysterious bunker. "Now, no CCC documents state that you or the other nine were put into cryogenic stasis. This bunker is not on any map, and we were very thorough. We've contacted the CCC-SW, and they couldn't give us any answers. So, we thought you could. What was that bunker? Who are the nine agents? Is there anything we should know?"

I'm loving the dev chat format! More of this! And I love hearing engineers talk about the nuts and bolts of the issue! That being said, I'm not sure what we learned that we didn't already know. We already knew it was a complex issue and that different solutions have pros and cons. Couldn't that be said about literally every choice made during development? Nate's follow-up post is encouraging but, yet again, it's a case of telling us rather than showing us. It's good to know, though, that many solutions are presumably being explored deeply, and I'm excited to see what the ultimate one chosen is!

Feel free to talk about the License agreement, how it applies to the industry, etc etc. But as soon as we start trying to apply it to any one jurisdiction, people get confused and arguments arise. To avoid any needless bickering over topics the vast majority of us have no official training in, please don't give legal advice. Some more content has been removed.

One thing EA has taught me is that Intercept's PR is exceptionally well versed in saying something that sounds like something else. Afterwards you can't really say "you promised x" because they never actually said that. Yes, that's toxic and creates distrust from your customers in the long run and here we are. Maybe I'm overly negative but I didn't see words like "address" or "solution" on the announcement. We do have announcements about timelines of when they will announce the timeline of bug fixes. This one isn't even that. It's just a talk.

I am reminded of 2 things that happened during KSP1. First, they announced that they were going to have Kerbal Experience affect things like ISP, which makes sense from an RPG perspective but KSP isn't really an RPG so it's understandable to not like it, but "the community" went above and beyond not liking it. The uproar over it was akin to a revolution. I really think people would have stopped playing if it had ever happened. There were warnings that next we'd be equipping Jeb with "Boots of ISP" or "The Ancient Space Helmet Of Landing" or something. Squad changed their minds because of this and ended up putting a different Kerbal XP system in the game which is fine I guess. Second, years later, they worked in silence on a feature we didn't even know was coming. And then one day, that feature dropped, with no warning or explanation. That feature was Ground Based Experiments. Cool! New things to do! We have a reason to send Kerbals somewhere and - even better -reasons to send DIFFERENT TYPES of Kerbals somewhere! Because as we all know engineers placing power generators makes them generate more power, and an experienced engineer can make it generate a LOT more power. Similarly, experienced scientists can cause an experiment to generate more science over time! Also, no more worrying about electric charge. One solar panel can power 1 thing. Unless an engineer does it then it's 2 things. A good engineer can power 3 things with 1 solar panel. To the best of my knowledge, no one has complained about how ridiculously unrealistic this is. How exactly does Bill get 3 times more power out of a solar panel? And why does that solar panel produce the same power on Eeloo that it does on Moho? Imagine if they had announced that first. With no ability to play with it and realize that - in fact - it didn't matter one bit how reasonable or realistic it was because the system generated interesting gameplay options which is what we actually wanted all along, people would have FREAKED OUT. Boots of ISP? What about Gloves of Solar Attenuation? Anyway, I'm continuously surprised that the developers keep trying to talk to us even though every time they do someone slaps them across the face. I'm no longer surprised, though, when they do get slapped across the face.

Secrets, Strategic Defense, and Shuttles As 1983 begins, let us take stock, and understand where we are. This year is set to be an important one, primarily for the development of future systems as they get closer to their debut. But also for existing systems, the Space Shuttle, Iapyx as it nears Saturn, and practically the whole Soviet space program making a push towards new launch systems. For the Space Shuttle, it will be another 7 flight manifest for the year. What was originally a 8 flight manifest was cut down to 7 after Apollo 29 and 30 were cancelled, as STS-61H was intended to be a mission at the end of the year for Apollo 29 support. The Shuttle also has 2 classified missions on the manifest this year. A tug of war continues between NASA and the DoD over flight scheduling for these classified missions. For all the support they put behind the Shuttle, they've become an afterthought on the schedule. This has made the DoD rather upset, and has led them to begin the Complementary Expendable Launch Vehicle program. CELV, as it is called, will provide the DoD with new launch vehicles to replace its aging systems. This unfortunately includes the incredible Hercules rocket, but it won't be replaced until these new vehicles are fully up and running, which is slated for 1987. Martin Marietta is currently leading the way with proposals of an upgraded Titan III rocket. With Lockheed Convair and Douglas being interested but not submitting proposals as of the start of the year. The development of CELV could be considered a major blow to the Shuttle program, with the DoD clearly fed up with playing second fiddle to NASA's interest. Even though the Shuttle will fly increasingly more classified missions over the next few years, on top of starting flights out of Vandenberg next year. But it's also to support some big plans coming in the future, in which using the Shuttle alone would not suffice. In terms of lunar exploration, NASA has entered yet another "Moon Gap" as they prepare for AFOP to start in 1985. Development of ACOV, SDLS, and the LTV Mk2 are now full steam ahead to meet the deadline. With ACOV dependent on successful demonstration of Shuttle-Centaur in a few months for it's own test flights expected to start in the spring of next year. For ACOV itself, the main development difficulties are focused on the capsule itself, which is practically being turned into a Shuttleified version of the Apollo command module. With thermal blankets on the exterior, redesigned systems, a widened docking tunnel to support APAS-75, and the intention to reuse the capsules brings a lot of modifications to the table. But NASA is nevertheless confident that they can meet the current schedule, especially with support from the President and Congress. Speaking of the President, NASA Administrator John Young pays a visit to the White House on January 3rd, to talk about NASA's plans for the future and what they need from the President to put these into motion. The two talk alongside Reagan's Congressional advisors for a few hours, until the conversation shifts a bit. Young brings up Mars, and how JPL and Goddard are implementing a series of 4 spacecraft to pave the way for more intensive Martian exploration. Reagan asks about the agency's aspirations for manned exploration of Mars, to which Young responds very clearly that it is a top priority for the future. Over the next hour, a program is born. A silent agreement was formed between NASA, the President, and Congress that afternoon. Young left the White House with enthusiasm, but nothing was concrete yet, so it had to remain under wraps. For the Soviets, they are now fully focused on the development of the Three Focuses (as they are internally called) after their plans for going to the Moon with NASA fell through. Energia continues development, while Mir has now been worked through its soft redesign. Studies are being done by several design bureaus now on robotic missions for the end of the decade. However with the transfer of power following Brezhnev's death to Yuri Andropov, there is unease within those very design bureaus, and the wider space program. They will need support from the government to see these ideas realized. Andropov is mostly content to leave the space program alone, which isn't good but it isn't bad either. Effectively the Soviet space program's situation for the past decade. The first Shuttle of the year rolls out a bit early. Atlantis is scheduled to fly STS-61A in late January with TDRS-C, but because the Rolling Beam Umbilical System (RBUS) for Shuttle-Centaur is finally complete, there are some tests that take place on January 8th. The Centaur Integrated Support Structure (CISS) is loaded into the payload bay, and the RBUS umbilical arm is moved into position. A series of retraction tests are then performed to make sure the arm functions properly. With these tests completed, the CISS is removed from the payload bay, and TDRS-C loaded in for the beautiful late afternoon launch on January 22nd, 1983. "0 and LIFTOFF of the Space Shuttle Atlantis carrying the third TDRS satellite to orbit!" TDRS-C is deployed shortly after launch. The crew spend the next few days on some research and experiments brought up on the Shuttle, with a landing at Edwards to conclude the mission on Flight Day 4. A successful mission to kick off the year, followed immediately by the cancellation of another mission. STS-61B was supposed to be the next mission up, manifested for Discovery carrying the GOES-F satellite. However, just 2 days after the launch of Atlantis, there are some... issues that pop up while Discovery is in the OPF. During some power up tests, it is noted that many systems do not in fact power up. Troubleshooting doesn't seem to find a solution, so they begin to dig into the problem. Several panels in the cockpit are removed to find bad wiring connections, and even just some shorted out wires for essential systems. This is the tip of the iceberg for a... small wiring problem on Discovery. There had been hints of this on previous missions, when the HUD would shutoff and come back on, a screen would cutoff and come back on, and maybe a few system glitches here and there. These issues aren't completely unheard of, but everything needing replacement will take at least a month to be isolated and fixed, which means 61B is cancelled. GOES-F is expected to launch on a Delta 3000 later in the year. NOAA (the operators of GOES) aren't exactly thrilled, but they are promised future Shuttle flights so they are mostly handled. Because the processing flow never stops, the already completed 61B launch stack is given to 61C, which is a DoD mission to be flown by Columbia. This is a very important mission for the DoD, and they have fought tooth and nail to get it scheduled and flown. But why? Well this mission has some background. The KH-9 satellite, it doesn't officially exist as far as the public is concerned but it does, physically, exist. These satellites are on their way out, to be replaced by new optical imaging satellites instead of their film-based system. However, the DoD wants to squeeze as much service time out of these satellites as possible. So, the DoD approached NASA with the idea of the Shuttle maintaining, retrieving film from, and even upgrading KH-9 satellites on orbit. 61C's test subject will be a testbed KH-9 that failed to fully deploy and become operational when launched a few years prior. Nicknamed Oddball due to this, it will be captured by the Shuttle, and worked on during several spacewalks. 61C is also going to deploy 2 military communications satellites, but the KH-9 servicing thing is the main focus. Columbia launches on February 16th, 1983. "BOOSTER IGNITION AND LIFTOFF of Space Shuttle Columbia on a mission in cooperation with the Department of Defense!" There has started to be some visible wear on the exterior of Columbia, being the most flown Shuttle this is the most of any Orbiter. It is imperative for NASA to study how the Shuttles wear over time as it sheds light on the stresses of each orbital flight. The first objective of the mission is deploying the MOOCS military communications satellites. They are deployed on Flight Days 2 and 3. On Flight Day 4, Columbia performs rendezvous with the KH-9 to be serviced, and begins a great dance in orbit to capture the spysat. Utilizing a new RCS pack, the astronauts perform an EVA to prepare the KH-9 for capture, this includes the removal of a few things that would block the capture, including folding in the solar array as much as possible. After this, the Shuttle captures the satellite, and the work truly begins. The KH-9 was captured on a new piece of equipment called the Shuttle Active Capture-Servicing Platform (SAC-SP) which, being a new system, didn't perform a perfectly aligned capture. Thus, the Astronauts perform a "Spacewalk 0" to add locking struts to fully secure the satellite to the platform. Once this is completed, the crew return to the Shuttle and are given some time to rest. Returning from the rest period, the crew prepare for Spacewalk 1. This spacewalk will install a new flight computer that will override the KH-9's aging avionics. Some of the most meticulous and difficult on-orbit work is done during this EVA, and many tools had to be built specifically for this spacewalk to assist the astronauts. Nevertheless after 5 hours, the computer is installed. Spacewalk 2 refueled the KH-9's RCS thrusters, while Spacewalk 3 installed a new star tracker and an optical pathfinder camera to better select targets for observation. Spacewalk 5 and 6 were the final planned spacewalks, and would've attempted to install new solar arrays. However, on Flight Day 7, one of Columbia's inertial measurement units begins acting up, and while attempting to troubleshoot the issue, it fails entirely. NASA has to inform the DoD that the Shuttle has to land at the next opportunity, and the mission cannot continue. The DoD is, for lack of a better word upset, but there is nothing that can be done, the Shuttle must return. They must watch as Spacewalk 5 is repurposed to disconnect the locking struts, and preparing for the release of a non-functional KH-9. 3 hours later, the KH-9 is released from the Shuttle, completely inoperable. Columbia then de-orbits on Flight Day 8. The DoD is not happy about how the mission ended, but nevertheless 61C has paved the way for future on orbit servicing missions. They'll take whatever positives they can get from the mission, despite the early conclusion. To end February, a test is conducted of the modified Lunar Module Descent Engine to be used on the ACOV service module. It will undergo a rigorous testing campaign through ground and vacuum chamber firings throughout the year. To kick off March, NASA representatives meet with executives from Japan's NASDA space agency in Tokyo. They are hoping to discuss options for joint Shuttle and Skylab missions. Japan has already licensed Delta rockets and currently utilize a version they have dubbed the "N-II" succeeding their previous "N-I" rocket, not to be confused with the Soviet N-1. NASDA is a hopeful agency with ambitious goals, so working with NASA and ESA could provide them with better opportunities in the future. The meetings are a massive success, and lay the foundation of positive relations in the future. NASDA is hopeful to get a Japanese astronaut on a 1985 Shuttle flight, which NASA is open to. But as new partnerships are formed, and old rocket is poised for its final flight. Grumman's Valkyrie rocket stands at LC-20 for it's final launch. The venerable light-lifter has been a workhorse for small DoD and NASA payloads since the mid-70s, with 36 previous flights, to be capped off by this final 37th. Things are changing, the Air Force would rather use its surplus of Titan missiles than continue this rocket, and Grumman doesn't want to step on it's own toes by entering Valkyrie into the commercial market, directly competing with SSV. Thus today is the final flight, carrying a Retriever-Swarm of small reconnaissance satellites for the Air Force. The launch is successful, sending out the GAC Valkyrie on a great flight. The payloads were part of a ramping up of classified missions that has been occurring lately. But why? Well, back on March 23rd, President Reagan made a speech from the Oval Office to the nation. "I call upon the scientific community in our country, those who gave us nuclear weapons, to turn their great talents now to the cause of mankind and world peace, to give us the means of rendering these nuclear weapons impotent and obsolete." President Reagan announces the Strategic Defense Initiative, or SDI. This new program is intended to develop advanced defense systems to counter ballistic missiles and other threats by building space-based defense weaponry. The defensive part is crucial, as any "offensive weapons" in space are banned by the Outer Space Treaty, of which the US is a signatory alongside most of the world. Defensive weapons are a loophole, however, and the President hopes this will dissolve the concept of Mutually Assured Destruction, which he describes as a "suicide pact" by its idea of both parties of an all-out nuclear war being destroyed. This idea has hung over the heads of the nuclear superpowers since the Soviets first attained nuclear weaponry, but Reagan seeks to abolish it. Many are hopeful SDI will unintentionally lead to further budget increases of NASA, and the DoD has its eyes on the Space Shuttle and the upcoming SDLS rockets for usage with SDI payloads. Whatever the case, SDI has created a tense atmosphere on the world stage, and has most certainly scared the Soviets. With that out of the way, Discovery's wiring has finally be fixed, so the second youngest Shuttle launches on April 18th for mission 61D, carrying a new crew of Skylab and a whole load of cargo. Discovery successfully rotates the Skylab crew, and delivers cargo. Landing occurs at Edwards Air Force Base on April 28th, 1983. With the spring Skylab rotation complete, NASA now moves towards a very important mission... The first flight of Shuttle-Centaur. STS-61E, flown by Challenger, will use Centaur G to deploy the Lunar Cartographer spacecraft. This is the second mission from the Earth-Moon System Project program, and will provide the highest resolution radar maps of the lunar surface ever. This mission is crucial to ACOV, and future deep space payloads. MISSION OVERVIEW: STS-61E | Commander | Karol Bobko Pilot | Guy Gardner Mission Specialist 1| David Hilmers Mission Specialist 2 | Robert Springer Payload Specialist 1 | Byron Lichtenberg OV-099 "Challenger" Objectives: Deploy Lunar Cartographer with Centaur G stage. This is the first Shuttle mission with a payload specialist, a new role where people not specifically astronauts will be trained to fly on Shuttle missions. A new era of Shuttle missions begins as Challenger lifts off into the morning skies on May 10th, 1983. "AND LIFTOFF OF THE SPACE SHUTTLE CHALLENGER THE FIRST FLIGHT OF SHUTTLE-CENTAUR TAKES TO THE SKIES!" Now in orbit, the Shuttle crew can breathe a sigh of relied. Shuttle-Centaur missions, while providing great capabilities, are the most dangerous the Shuttle can do. RTLS aborts (already near impossible) would require venting of Centaur's fuel in order to properly land, and the mass of the stage and payload pushes the Shuttle to its performance limit. This has earned these missions the nickname "Death Star" missions. Nevertheless, Centaur is deployed as soon as possible, and about 2 hours later performs TLI to boost Lunar Cartographer to the Moon. TLI is successful, and Lunar Cartographer is separated from Centaur G, deploying its radar dish and solar arrays. Centaur G will be flung into a heliocentric orbit, while Lunar Cartographer will insert into an elliptical polar mapping orbit in a week to begin its mission. With the shiny explosive out of the payload bay, the next few days are spent on experiments and Earth photography, Challenger de-orbits on Flight Day 4 for a landing at Edwards. A massive step towards future missions has been made with the completion of 61E. President Reagan is at Edwards with First Lady Nancy Reagan, and they speak with the crew of the Shuttle following the landing, and the President makes a speech in front of the landed Shuttle Challenger. In this speech, he announces his government's plans to cooperate further with NASA, and mentions their upcoming suite of robotic missions to Mars. The Shuttle has become an American icon, now a focus of the Reagan administration for PR purposes. Whether being simply a PR tool for the President is ideal, it's certainly getting the budget raised every year, so NASA has no complaints on that front. Doubling up on Centaur missions, Atlantis is launched on STS-61F to wrap up the first half of the year for the Shuttle. This is a classified mission, so coverage is limited, but Centaur being on the mission can't be hidden due to the RBUS being obviously extended and connected. Nevertheless the mission is successful, and Shuttle-Centaur has been successfully demonstrated. With 2 successful Centaur missions demonstrated, the path is clear for ACOV demonstration flights next year. The Shuttle has gone through most of its flight schedule in the first half of the year, with another flight in July and another in the autumn. This has been an unusual schedule, but 5 flights in 6 months is a positive trend in the Shuttle's flight cadence. The Shuttle's turnaround time is the main thing keeping it from flying even more consistently, which has been a point of focus from several Rockwell and NASA studies about future upgrades. Including one presented this month in the Space Shuttle Technical Report from Dryden and Ames. These reports have for a long time been advocating for Shuttle upgrades, and they're starting to gain traction. Meanwhile across the pond, the UKSA has been gaining political relevance, as their Comet B rocket will be providing many new jobs across the UK. NASA has also gotten interested in the project, and has begun discussing possible joint projects with the UKSA. For the Soviets, they are still grinding away at Energia development, with test articles and engine development coming along as of the summer. VKK is also beginning construction for its first flights in a few years. But as late June rolls around, there's one thing on the minds of everybody in the world of spaceflight. Iapyx is about to enter orbit of Saturn. I'd like to thank everyone who has helped this page reach 8,000 views! Thank you for all the continued support and viewership, it means a lot to me as I continue writing!

Look - PC players cover a wide gamut from *really informed geeks who know what is going on beneath the hardware and system requirements to *I'm playing on a repurposed work laptop from last year to *My mom bought me this from Best Buy for Christmas! It's been this way since Dell was new. (Prior to Dell, you kinda had to build your own). We all had huge CRTs on the desk and boring boxes with no lcds and you could listen to your computer connect to the internet. Way, way back then the geeks talked quite a bit about screen resolution. The transition from CRT to LCD screens started in the very late 90s and only became predominant in 2007. But once 1080p (HD) became common and cheap... It became the standard. So much so that no one ever talked about screen resolution when talking about game or hardware performance. Up to the last year and a half or so, all of the reviews, all of the price /performance metrics and talk about what makes a machine mid range or high end comes from this time - when 1080p was presumed. These conventions still bias the language today. 1440p started popping up in the middle teens - Esp when 27 inch screens became available - and they were niche for a very long time. 4k was available on 27 inch screens and 4k OLED TVs but did not really make sense until 32 inch screens became available last year. And so for the first time in decades the old conventions MEAN NOTHING! If you advertise or talk about a mid-range product or machine, that conversation is meaningful only if you specify what resolution you expect to play the game at.

Sad part is the admin likely wont do squat. When I was in 6th grade many years back, I was sitting in my spot on the gym floor waiting for coach to call roll. This giant of a kid walks up to me and kicked me in my left side like i was a football and he was trying for a 90 yard field goal. When I finally could breathe again and stand let alone talk I went to coach and told him what happened. He was in charge of and responsible for our safety and his EXACT response? “What did you do to deserve that?” I had just been ASSAULTED and the coach didnt care. I dont know what if anything else happened after i told my mom. I know she told the admin but i saw no change at the school on my end. 135609262023

Considering that’s a steam thing and not a ksp thing, you should go talk to them.