Scarecrow71

You gotta remember that this 600 peak per day only counts those people who are launching through the Steam launcher. That doesn't include people who are bypassing the launcher, using Epic, or have direct download from PD. And I am one of those people (Epic). I don't play daily, but I do play. Primarily because I'm hoping the Kraken doesn't show up every time I try to do something (restarts seem to help with that).

Not to beat a dead horse too much, but I have to echo the sentiment to change the VAB controls. That middle mouse button thing is just unwieldy and clumsy.

That is a decent increase. But I've been at 20 FPS since launch day.

What data isn't loading? Can you provide a screenshot?

I'm still waiting to see the performance enhancements they made with patch 2. I'm still running at 20 FPS with no visible improvement.

I have two issues I uncovered today while going to Dres. The textures for the planet and its rings didn't show up in flight view until I restarted the game multiple times. I was flying directly at the planet (more on why in #2 below), and until I hit about 150km above the surface, the screen showed only the stars and the ship. No planet, no rings...nothing. I even confirmed that the rings weren't showing up upon relaunching to orbit; getting close to them several times only showed a black outline of where they were supposed to be. Why did I suicide burn at the planet itself and not circularize orbit beforehand? Because the orbit trajectory did not change at all under the influence of Dres' gravity no matter how close it was to the planet. Going around the planet at the equator, opposite to its spin? Nope, nothing. Trajectory did not change at all, and the path was not altered at all by the gravity of the planet. This caused me to suicide burn the planet directly as I wouldn't have had enough fuel to circularize properly without the gravity assist.

Today I planned and executed a trip to Dres*, with a return trip back to Kerbin**. Several things went entirely wrong on this trip causing multiple reverts to the VAB, the launchpad, and save files in transit. The list includes, but is not limited to: Struts ended up being in places where I didn't even put struts. That's right, some gremlin got into the VAB and placed stuff on the ship that I didn't want there. Ship blowing up on the launchpad for no reason other than the Kraken is alive and well. Trajectory and orbit lines disappearing. My personal favorite is having to do a suicide burn onto Dres because no matter how close the trajectory I plotted was, the orbit path NEVER CHANGED. Dres' gravity was never taken into account, so a gravity turn/burn could not be done on Dres. And with no gravity turn, I simply didn't have enough fuel to circularize first. My second favorite is that Dres didn't show up in flight view until I was ~150 km above the surface. I got a screen of the ship and the stars with no planet. In addition to #5, I had to reload a save at least half a dozen times before I could see the rings. I kept getting the black outline of where they are supposed to be, but with no color or texture mapping. I finally got them, but at one point I thought about scrapping the whole trip because the only reason I went there was for the rings. And once I saw them....I was wholly underwhelmed. In fact, the team spent that much time on texturing planets, but nowhere that I've landed on Mun, Minmus, Dres, or Duna to this point has looked anything other than KSP1 with a brighter crayon. The trajectory bug reared its ugly head again, but I think I may have it solved. Dres spins around Kerbol counter-clockwise, and my orbit after launching from landing on the planet had me going clockwise around Dres. So when I plotted my burn (1450ish m/s) I burned prograde to the planet's orbit (in the same direction that the planet was moving), but it ended up being retrograde to the direction I was traveling. This actually got me an intercept with Kerbin immediately after leaving the SOI. Odd. * - The trip to out to Dres, as I mentioned above, had some issues with the planet's texture showing up upon arrival, as well as the trajectory not altering in the slightest regardless of proximity to the planet it was. I know that once you reach a certain speed, the trajectory doesn't alter that much. But not at all? Just plain odd. Oh, and poor Valentina ended up going out there by herself because the Las Kerbas Space Agency failed to put a second Kerbal in the two-Kerbal lander can. And landing on Dres SUCKED. You can see from the image that the legs are stuck in the surface, and this was the only thing that prevented the craft from bouncing like a rubber ball on the moon. ** - I hated having to do this, but I ended up having to use Infinite Propellant for the trip home. I had 3000ish m/s of dV prior to launching back to orbit, and it didn't take much to get back up there. I burned 1450ish to get the initial intercept with Kerbin, which should have left me plenty to get home with. Nope. Needed multiple correction burns because, for some stupid reason, when you start messing with a maneuver node, the game decides to go "Distance to target dropping...dropping...dropping...oh, you're back up to 30,000,000 meters away from it now". That is so ridiculous. Like, why can't I create a decent node without having the intercept markers flake out on me all the time? This in total cost me 900 or so m/s of dV, but I got the Pe inside Kerbin's atmosphere. Should be able to aero-brake, right? Nope. Not enough fuel. Oh, and turning on infinite propellant didn't work when creating a node; creating the node is dependent on the amount of fuel you have regardless of turning the cheat on. I know I will have to re-do Dres; I don't like having the cheat turned on. But I was at the end of my rope and just thought "Forget it".

This image kind of reminds me of the whole thing with KSP2.

In most cases, yes. Where we (I) use it at work is generally when only a singular line or two of code is being updated, and at that only when it's only in one location in a script. In that case, it's more ease of use than anything else (although we could technically promote the entire batch with DevOps).

Going completely silent would only further alienate the userbase from the devs, which would in turn make things worse.

And I wholeheartedly disagree with this statement. Just because I bought something doesn't mean I am obligated to be unequivocally happy with it. If I spend money, I am hoping it is good and that I will be happy with it. In the case of EA games, the more likely outcome is that I will be middling about the initial product with the hope that it will get better. And in some cases, whether it's games, cheeseburgers, or pencils, I buy something and am not happy with the product I received. Heck, lemon laws exist solely to protect consumers who purchased something that is not right or broken when they received it.

And see, we use DevOps (formerly Team Foundation Server) for the purpose of version control so we can get back to specific builds of code in the event something goes wrong.

Agreed. Can't tell you how many times I've had to correct someone else's code because they did the copypasta recipe and failed to make sure they copied/pasted not only the correct code, but all of it AND into the right spots.

I experienced something similar to this with the craft I'm trying to build to launch to LKO using only separatrons. And while I haven't been able to do anything about VAB load times or how long it takes once you add a part to it, I think your issue with it blowing up on the launchpad and then reverting you to the VAB is due to a structural issue. Not something you did, but rather what the game is expecting. I hate to say "add more parts", but you may need to add struts all the way around to keep the ship stable. Without struts it seems that the ship wobbles uncontrollably until it explodes, but I've seen where, when I add struts to my separatron monstrosity, it stay together and can actually get to the launchpad and launch without blowing up. What happens after launch is a different story, though. I say try to add struts and see what happens. Again, I get that the load time in the VAB is rotten. And until the dev team fixes that there's nothing you can do about it. But it's worth a shot?

So, I can't answer this from a game development standpoint, but I do have development experience; I am a code monkey at work in my day job, responsible for developing SSIS packages for file ingestion and automation of file and data routing. Lot of scripting, lot of SQL. LOT of SQL. Tons of stored procedures and database management. The point is that I am a developer, and can answer this from my own personal standpoint. And the answer, at least from my perspective, is that our packages and code are written in lower level environments (DEV, for example), and are designed specifically for allowing copy/paste of new code for about 75% of the enhancements that are made. This would include/involve code, tables, stored procedures, packages, etc. That 25% that falls outside of this are those enhancements that are simply touching a lot of different code scripts and packages. You know, stuff that you really need to be careful with and probably hand-code most of it in the applicable environments to make sure you don't bone anything. With that said, I can honestly say that there should be some percentage where the devs here are able to copy/paste from one dev branch to another...but what that amount is? Unknown, at least by us.

To add to this, I noticed this bug today (patch 0.1.2.0) while returning from Minmus.

This game gets more and more frustrating with each passing day. After being irritated and ready to pitch my entire machine yesterday, I thought I'd give landing on Minmus one more try today. I figured that there was something I did wrong, so I fired up my save, decoupled the transfer stage...and landed WITH EASE. What the frak happened to the uncontrollable spin I encountered yesterday? Where was the bug? Why did the game decide to be nice to me today? I don't know, but I was able to land. Unfortunately, the return trip was where the bugs decided to show up. I got off Minmus, plotted a course for home, left the SOI...and promptly ended up in a Kerbolar orbit. What? How did that happen? I reverted to the save I made on the surface of Minmus, fired up the engines, hit M to get the map view...and watched the machine bring up the mods list. What is going on? Anyhow, I plot the course home and, after the burn, slowly time warp to leaving Minmus' SOI. And after leaving the SOI, I was in fact inside Kerbin's SOI...for all of 30 seconds. I had 30 seconds to plot, time warp to, and execute a correction burn to capture Kerbin. Seems like the trajectory bug is happening here too. I managed to get that done, get into a nice, stable orbit, and then start my descent. Only to watch the craft spin uncontrollably as it entered Kerbin's atmosphere. For another 90 minutes today, I saved/reverted/pulled my hair out as this bug kept haunting me. Finally I walked away from my machine, got a drink of water, and came back to attempt another landing. Oh good, this time we are pointing retrograde all the way down. Fire the parachutes...and they don't deploy. At 145 m/s speed some 300 meters above the ground the game shows me that it is unsafe to deploy. What? Why? Sigh. Revert to last save and try again. Another 30 minutes of watching the parachutes fail every single time. Finally the stars aligned and God intervened and said "You may now pass". I am so frustrated with this game right now. There is no telling what bug may rear its ugly head, nor when it will happen. This is maddening, and I cannot believe the devs put this out there. I'd like to state up front that the only bug I was experiencing prior to 0.1.2.0 was the trajectory bug. This new patch has introduced several new bugs for me. I'm ready to ask for a refund even though I know I can't get one 2 months out.

I will echo what J said above: Ask Me Anything is not a guarantee that your question, or questions related to what you are most interested in, will get answered. It's that simple. Just because they didn't dive into MP doesn't mean they ignored you.

I believe that should be your motherboard, not hour. As far as what BIOS is and how to update it: https://www.pcworld.com/article/516379/how-to-update-your-bios.html

Yeah, you are missing something. MP questions were asked; they chose not to dive into them in explocit detail this time around. Now, I have to caveat that with stating I have no inside knowledge, and I have no idea what was asked on Discord. But there is a pretty hefty contingent of people here who want MP, do it has to be assumed that MP questions were asked but not answered.

Granted. It will be May 1st in 10 days. Unfortunately, you drop dead on April 30. I wish for the Green Bay Packers to select a TE in the upcoming draft.

No, what I typed was fact. Go check the videos I recorded of both AMAs and you will see. Or, rather, hear. Anyhow, MP is several roadmap features away, and there are major bugs that need to be fixed before we can even get Science. It isn't cherry-picking to not address the 5th thing on the roadmap.

Multiplayer was pretty decently addressed by Nate in the first AMA, and that was at the expense of roadmap features that are well before MP. Not to mention that they barely mentioned bugs or patches, both of which at this point are far more important than MP.

I'll start by pointing out that we do in fact have references to dragons in space and astrology. The constellation Draco The Azure Dragon Now with that out of the way....yeah, these challenges have nothing to do with Kerbal Space Program, rockets, space, or anything to do with the game. And considering the state of the game, I'm curious as to why they keep coming out with this stuff when we have issues just dealing with normal rockets.

And I've learned not to believe too much of what is being said right now from the devs.