Demordrah

Also confirmed - just had this happen.

Been playing on PS4 Pro for almost 4 years now. The problem with the autosave is that it seems to occur during transitions from various aspects of the game, ie tracking station to KSC, or VAB to launch pad, etc., which also happens to be when the game is most prone to crash. This can, and will, sometimes result in the persistent save file becoming corrupt and unusable. Since you can't load or access individual quicksave files from outside of the persistent game file, this is a death sentence for your KSP career. I lost two career saves due to this before I started routinely backing up the files to the PS cloud storage. I initially thought that it could be something to do with the amount of active crafts/stations/bases, etc. However, my current career has only a single small base on Minmus, two solar contract satellites, a satellite around the Mun, and a large ship in Kerbin orbit, and it still crashes. I even went through lengths to prevent space debris, and manually terminated anything that I failed to burn up on re-entry or impact. I also try and limit the amount of ships in my craft list, and repurpose as much as possible. I have the entire tech tree unlocked, and have been everywhere in the Kerbol system, although the same could not be said about my previous saves. As @Andestated, it wouldn't be as frustrating if we had the ability to save craft files separately. Losing literally everything in this game is heartbreaking when you have put so much time into creating things.

I remember, many years ago, my nephew posting something on social media about sending a mission to the moon in KSP that ended up failing in spectacular fashion. At the time, I had never heard anything about the game. A few years later, I noticed that it had appeared on the PSN store as an "Enhanced Edition". I looked at the trailer and screenshots and passed on it because it just looked kinda "meh" at face value. Man was I wrong. I ended up getting it on a whim in June of 2019, mainly because my nephew had enjoyed the game, and immediately fell in love with it as I started playing. I have always had a love of spacecraft, the universe, and everything we do and don't know about it, and was now living vicariously through Jeb and his peers. The learning curve was steep (and the tutorial system left a lot to be desired), but the return on investment has been some of the most rewarding gaming experiences of my lifetime (and I have been gaming since 1978 on many different platforms). First orbit, first rendezvous, first docking ... all met with an enthusiastic "Yes!!" and a fist pump. KSP Enhanced Edition on PS4 has been a rollercoaster of emotions. I remember my first "successful" Mun landing. It was a tall, thin lander that ended up touching down on a slope, toppling over, and beginning to slide into a crater .... which hilariously unlocked the "Mun Rover, Mun Rover" trophy in true Kerbal fashion; Then there was the time Valentina got some tourists stranded on the Mun because I didn't have a strong handle on Delta-V requirements yet. Her craft wasn't equipped with a docking port, so I had to get really creative with the rescue mission. I ended up outfitting a lander with a Klaw on the bottom and, after much effort and RCS shenanigans (which were compounded by my lack of understanding of the navball), was able to land on top of Val's craft and refuel it enough to get her and the tourists home. My first actual rover landing on the Mun was right out of the X Games. I brought it up in an Mk3 cargo bay on a probe vessel. I slowed down enough that the craft was vertically oriented with a slight descent, and opened the cargo bay. The staging was set up so that when the rover was decoupled, sepratrons on the vessel pulled the cargo bay clear and allowed the rover to freefall. The rover had a tiny engine (Ant?) and some RCS, and I was able to orient it in such a manner that it landed onto the slope of a crater like dropping into a half pipe. From there it was riding on a prayer to remain as straight as possible as it slowed down naturally to the point where I could safely turn and come to a stop; I have since then built a KR-71 Kerbalbird MkII jet, and successfully flown it into orbit, built a stock replica of a B-52 Stratofortress that I ... er, Bob used to carpet bomb the KSC, launched a 12 vessel simultaneous expedition to the Jool system (I didn't want to wait for another transfer window, so I launched them all in succession) to establish an orbital refueling operation there, and stranded Sonkin Kerman, who would become the legendary objective of many failed rescue attempts, on the surface of Eve; This is where the heartbreak comes in. I lost all of that because the save system on console versions of the game (specifically PS4) is absolute dogexcrements. It autosaves the persistent file during screen transitions from one area of the game to the next (or at least that's what appears to be happening), such as leaving the tracking station to go back to the KSC. This is unfortunately also when the game is most likely to crash, resulting in corruption of the persistent save file. Since all the quicksave files for your career can't be accessed individually outside of the game, that career becomes unplayable. This is still occurring in 2023. The only way I have been avoiding losing another career save is by backing the file up to the PS cloud storage upon normal shutting down of the game application. That way, when a crash corrupts the save, I just download the uncorrupted file from the cloud, and lose the last session instead of the entire career. It's not ideal, but it's better than losing everything. I recently tackled a Moho landing and return to Kerbin to unlock the platinum trophy for the game, which was tremendously satisfying. I also built my version of the NASA space shuttle and launched it into orbit without ever opening the map screen. I haven't been able to gracefully land the shuttle yet, but I did land it; I have a massive spaceship that I constructed in orbit around Kerbin, that involved several multi-port docking maneuvers. This ship will likely never see action, primarily because we still don't have EVA construction and I can't add much needed structural supports. I still love this game, and always challenge myself with new goals. I just wish the console version hadn't been left in the dust. We're still on 1.10; I'll edit this post once I find the associated screenshots and pictures related to the above adventures (if there are any).

The contract isn't broken, it's just sometimes referencing the older version of the part. You won't see this mentioned anywhere in the text, but if it isn't working when you select the current model in the parts tree, you have to use the older one. These contracts can still be completed. I have done this many times across multiple saves. As I mentioned previously, the older parts are accessible by switching to the advanced mode of the parts tree. There is a button for this in the top left corner of the VAB/SPH screen. Alternatively, press L3 on PS4 (LSB on XBox) to toggle the cursor off, and then press square on PS4 (X on XBox) to toggle Advanced mode. From there, select one of the filters (for example, choose "filter by resource" and then "solid fuel"). When you locate the part, you will see multiple versions of it (the models are different). The older Flea and Hammer models have grey and yellow bands on them and have a grungy looking base texture to them.

Well, then.

Unfortunately you won't find one. The console version has been corrupting save files for years. I have been playing the game on PS4 Pro since June of 2019. Even through routine cloud backups, I have lost two long term career saves since last year because of it, and have seen dozens upon dozens of non-fatal save file corruption messages, which only ended up in a minimal loss of progress. This is one of the main reasons that I will never recommend the Enhanced Edition to anybody (which pains me to say, because KSP is a brilliant game), unless you simply can't or otherwise don't want to play it on PC for whatever reason. The console version is beyond broken. Even keeping manual saves to a minimum, cleaning up your contracts list, having very few crafts in the VAB/SPH (which is a bull***t thing to have to do in a game like this), taking care to remove space debris, and limiting the amount of flights will only work for so long before the performance issues eventually cripple your career game. My last save has a total of one surface outpost on Minmus, satellites around the Mun and Minmus, and a massive ship that I assembled in orbit of Kerbin. The frame rate issues (and what I can only guess is a memory leak) prevent me from being able to fuel that vessel, effectively making it the orbital equivalent of a paperweight. I'm sorry for your loss, but the issue you're describing is, in my experience, indicative of a corrupted save file that cannot be salvaged, due to the lack of ability to access and edit that data like PC players can.

The contracts sometimes still reference legacy parts (older visual models). These parts aren't in the parts tree proper, but can still be accessed from the advanced mode of the build menu (the button on the top left of the VAB/SPH interface), where you can sort by cross section size, etc. You will see two variants of the parts in question in the listing, and selecting the older model will normally clear this particular issue up and allow the contract to complete.

Unfortunately, there's no way to directly access the save file system on the console version of the game. Each career/science/sandbox mode game is contained its own save data file, regardless of how many different manual saves you make. So, for example, if you have a career mode with the "persistent", "quicksave, "manual_save1", "manual_save2", etc, it will show up in your saved data management on your consoles HDD as a single file; "career name here" (if you didn't rename it from "default"). What that means, is that once the "persistent" file becomes corrupted, that game mode is unable to be salvaged on console, unless the data had previously been backed up (by either the system, or yourself). There's no way to simply just load one of the manual/quick saves and continue on. Whereas, on the PC, you could just rename one of your manual saves to "persistent.sfs", because each separate save file is fully self-contained.

This happens frequently on console as well, though it's not limited to SOI change (although that is a majority situation). I have made mid-course corrections in solar orbit that put my final position exactly where I want it to be, only to have the act of selecting "warp to next maneuver" ruin the adjusted trajectory to the point where I have to do multiple mid-course corrections to get where I was going to end up after my initial adjustment. It's ridiculous at times. I have been in situations where 700 m/s of Delta-V should have been enough to put me into Kerbin's atmosphere (based on nodes I set up), and despite perfect execution (down to 0.0 m/s after the burn), it has, at times, increased to upwards of 2,000 m/s total due to the trajectories being altered upon time warp.

When I first started playing KSP, I had absolutely no clue what I was doing, and ended up attempting things long before I was even remotely ready for them. One such incident ended up with a Kerbal on a trajectory that would eject him from the solar system. I ended up messing around with EVA instead of adjusting his trajectory, out of the novelty of it for me, and the physics caused him to slip off of the command pod and lose his grip. At the time, I wasn't aware of how to activate the EVA backpack (honestly, I don't even know if I knew they were equipped by default). It seems silly thinking about it now, but as I watched him float out there alone, helpless as I thought he was, millions of miles from home, his rocket shrinking off into the distance, I felt really, really small.

And even after all that, we still don't get everything that was part of the same PC update, which is kind of a kick in the junk considering how long we have to wait. Notably lacking are some quality of life improvements (I'm looking at you, better burn time indicator, adjustable docking port attraction force, maneuver mode widget, etc)

We don't even have 1.8 on consoles yet, and that was released for PC 9 months ago.

Today, while beginning construction of a large ship in LKO, I performed my first ever multiple-port docking when I attached one of the engine sections to the core stack via 2 Docking Port Sr. That's a tricky little bit of RCS wizardry to get the alignment and rotation perfect on multiple ports before impact. I thought it would be near impossible on console, but I was pleasantly proven wrong

As far as the game is concerned, that wheel isn't broken, it's just not aligned properly anymore. That's not something an engineer can fix.

That while it's important to know the total Delta-V of your craft, it's equally (if not more) important to know the Delta-V of each stage, as well as the function of that stage, so that your rocket can perform its intended task appropriately. Bigger doesn't always mean better (although, bigger is almost always more awesome). I have, at times, reengineered some of my more monstrous crafts into something more refined and ended up having more Delta-V as a result. Have a contingency plan! A recent manned round trip to Dres was almost less than successful due to the buggy nature of maneuver node trajectories to drastically change upon crossing over a sphere of influence. Even though the numbers said it was possible, if I hadn't topped the tanks off before leaving LKO, I would be planning a mission to rescue 19 Kerbals from a solar orbit. If, for some reason, you are unable to directly target an object in the map mode, click on the orbit line of the object in question, and it will bring up the same context menu, allowing you to set target and/or focus. Lastly, and this is something that I still struggle with at times. Don't use someone else's accomplishments in-game as the metric by which you judge your own successes and failures. Every time I get discouraged by not being able to do some amazing feat that I saw in a YouTube video, I take a look back at all the things I have personally accomplished in the game, and realize that I'm a lot better at KSP than I give myself credit for.

Also, it does not detect all asteroids that appear. They have to have a specific inclination. #2 *beep* Además, no detecta todos los asteroides que aparecen. Tienen que tener una inclinación específica.

I had one of these high paying Sentinel contracts on my PS4. Was 4.66M up front, 7.69M reward +154 science and 252 rep to track 12 near Kerbin with an inclination of greater than 39. It had a 977 year deadline. What I thought was absurd about the contract wasn't so much the payout (but it did raise my eyebrows). It was the deadline that had me wondering what. Things like this rarely take 20 years, let alone nearly a thousand.

I had been tinkering with the idea of creating a fully modular surface base system for low gravity bodies. Each module uses the same foundation core, and is equipped with both wheels and landing legs. Upon landing, the wheels are deployed on each section, and the landing legs retracted. This guarantees that the docking ports are aligned, as long as the terrain is reasonably flat. Then you simply drive one module over to the other, and connect. Since each module is independently mobile, the base can be reconfigured as design and needs dictate. It was a perfect execution here at the KSC. In practice, the wheel springs and dampeners had to be turned down on Minmus, but the end results were more than acceptable, as the base construction project had a successful start.

How unstable and unoptimized the Enhanced Edition on consoles is. Of the 114 games in my PS4 library, KSP is the only one guaranteed to crash every single time I play it. In fact, crashes with other games are so few and far between that it's barely worth mentioning. KSP is king of that hill by a long shot, and reigns supreme as the only PS4 game I have ever had corrupting save data (which has been an ongoing problem for years with this game). I back up my PS4 saves to the Plus cloud as a matter of routine, but this is the only game where I have ever needed to download one of those backups. Funny thing is, you never really know if the file being backed up is already corrupted (I had that bite me in the backside recently). I would gladly volunteer my free time to play test the console patches if it meant we could actually have a stable and unbroken game for a change. I mean, that is what we expect as paying customers after all.

I'm interested in seeing where it goes. I recall him mentioning this reboot recently. I find his content to be entertaining, for the most part. I always appreciated that he documents his failures in his instructional videos, as well, so as not to come across as holier than thou.

552.528t into 100k Kerbin orbit. It was a fully loaded fuel depot. Normally, I launch my depots empty, and fill them up later, but my need for this depot in Kerbin orbit exceeded my then present need to put it there efficiently. The launch vehicle was ... interesting. The first stage had 60 engines on it. In total, it was 381 parts, 4,187.407t on the pad, and cost 2,380.217 to launch. It was a satisfying display of brute force, but my Playstation was not happy about it.

I have been gaming since the late 70's, before we even had the option to create save game files. I adopted the "save early, save often" practice when that mechanic was introduced with The Legend of Zelda, back in 1986. You can create quick saves in KSP on console all you want, but every save that you create all get lumped into one master file (including the associated persistent save). So, each career game exists as a single on-disk file, each science mode game exists as a single on-disk file, etc. Backing up to the PS Plus cloud is the option we have, but when the uploaded file is corrupted, you're out of luck.

I get that. Similar thing happened with No Man's Sky. The game is phenomenal now. But with KSP, it seems like they're more focused on adding content rather than fixing game breaking bugs that have plagued the Enhanced Edition. I have seen people claim that you should only have a small handful of crafts on console, and don't build anything with more than 100 parts. Kind of nonsense is that? I would *almost* give credence to that if it actually solved any of the problems, but it doesn't. I had a new career started. Just got back from Minmus. I had a total of 3 ships in the VAB list, none of which were over 50 parts. There was nothing in space, and I had 3 active contracts. I clicked to enter the VAB, game crashed. It's almost as if nobody actually play tested the console version when the last patch was released, because it's the most unstable I have seen the game since I started playing in June 2019. KSP is an amazing game in its own right, but I would honestly be embarrassed to have my name on the product, as far as the console version is concerned. It's really disgraceful how diluted the experience is at times due to ongoing issues.

You're right, but it's not Sony's or Microsoft's fault that the console version is riddled with bugs that have existed for ages.

I understand that, but it doesn't really address the problem. Just more sweeping under the rug. I know first hand how rewarding an experience Kerbal Space Program can be. I just want console players to have those opportunities without fretting about whether it's all going to vanish in an instant because of issues that have persisted for such a long time I don't think that's an unreasonable expectation, considering how long this game has been out.