JoeSchmuckatelli

Yeah - post patch, Sandbox is actually fun to play. Still a bunch of bugs - but a solid Beta experience!

Done!

(I don't know why there's no image)

I loaded up my EVE save - messed around with Friction control and Traction Control. Neither worked. TR-4s just got no 'oomph'. (OTOH - turning Friction all the way down let me skate to the middle of the depression I was in!)

Yeah - I have to have wheels and legs to prevent that.

That Eve rover was in an absurdly bobble-head faring. My TR-4 testing explains it; can't climb without a rocket on its as butt

Getting that part through my Neanderthal skull is the hard part for me. So how do I figure out fuel consumption rates? Other than just slapping on bigger tanks. Is there a formula? Or is it listed and I'm just not seeing it?

That is certainly a valid concern. There's 'nothing to do' unless you want to dream up your own tests. It's sandbox - most decidedly not a 'game'. For a duffer like me who only made it past the moons twice, the QOL features are a real boon. But then I get somewhere like EVE - and because heating isn't on - I just land.

I've been playing around with trying to set up a pair of the large SRBs to have them flame out - and then almost immediately after, have the Mammoth stage flame out - so that I can drop the SRBs then drop the booster and stage the sustainer engine. Problem is - I'm getting the timing wrong. Mammoth is flaming out before the SRBs. Here's what I'm seeing: just a Mammoth, S3 14400 and S3 3600 (Large diameter cylinder tanks, the big and small one) show up as having 4524 m/s of DV. The S2 33 Clydesdale shows up as having 4437 m/s DV. Based on my rudimentary knowledge of maths, one of those numbers is smaller than the other... and so I'd think that the Clydesdales would burn out before the Mammoth. Apparently, that's not how it works. Anyone care to break this down Barney style for me?

I know there's some concern that we don't have any robotic parts during the EA. But we had them in KSP and we're gonna need them in 2. They're gonna have to give us the ability to fold stuff up. Otherwise - we're left with this: ...which is just hideous! EDIT: Oops notice. I goofed in the top picture. That's just a Large Cargo Bay. Mea Culpa. Too lazy to go back and FIxit.

Give it another patch. I'm actually "Playing" more than bug hunting these days... but there are still plenty of bugs. VAB got a bit wonky on this build and SpacePlanes are now hit-or-miss. It's been noticed that the temperature has dropped (fewer ZOMG!!SUXORS!1! posts) in the last few days. Partly due to those with insufficient systems finding something else to do and the fact that this version isn't painful to fire up. (Note: not painful =/= running well enough to recommend). Thing is - I can see what they're going for, and the QOL stuff is appreciated. Graphics are very nice. Music is great, too. But literally every mission there is something that happens that shouldn't - and so the thing is, I'm not just fighting my own lack of knowledge, inexperience and the game's difficulty, I'm fighting stuff that doesn't work like it should. So, yeah. Waiting is good.

I see what you're concern is: but I'd like at a minimum for things like SAS lock to be persistent between the craft on separation. Bob dumps a probe from his ship - the probe shouldn't just drift away like a dumb rock with me unable to switch to it because "Observer Can't Leave Active Vessel". (Likely a bug, but you get what I'm saying) The use-case for needing to fire a rocket before separation is undoubtably rare - I just did this as a fun way to test a hunch... but it does showcase the problem. Every separation turns the probe (or even another crewed ship) into a dumb, drifting rock no matter what.

I'm gonna have to follow your progress on this - because it seems odd. A 750 is supposed to be sufficient for a 7900xt, and Corsair's are usually rock solid. Most of the game's calls should be to the CPU and GPU and if they're cool and the mobo isn't freaking out... I'd really suspect the PSU or your cabling. Absent telling the three things I've mentioned to pull power for one reason or another I cannot imagine a way for any program to directly require power from the PSU. So if they're not hot - there's gotta be a problem between the powered thing (CPU, GPU, MOBO etc) and the PSU (meaning cabling) or the PSU itself. Couple of questions: Do you have an under-the box filter for PSU air (and is it clean)? How old is your PSU and have you blown it out in a while? Are you running anything else like water pumps or AIO that might be taking the wattage up above 750? Are any of the wires hot? Did you have to 'rock' any connections to get everything to fit? Also - I know you like small box solutions - is your exhaust air from the PSU venting out of the box? (Asking stupid questions because sometimes if you don't...)

I've written before that the current PM should be available if you want to click on the icon at the bottom of the screen... But RtClick on a part should just pull up the part in a small, polite window. Not the full honking space hog it currently is. The biggest complaint, however, is that it's an enormous resource drain. I made a 175 part craft and you could count the seconds it takes to open the report.

Never tested anywhere but the one time. Maybe you discovered new lore? The land of the Space Frogs is a giant lily pad floating on the World Ocean!

I finally finished watching Andor. Holy cow. Probably the best Star Wars anything.

I'm pretty sure my vids don't have black bars. But if I am hearing you correctly - you're not trying to record in full screen, but in an actual window. That's beyond my ability to figure out. Too new at recording stuff. I did look through the Nvidia options - but I don't see anything that would help. Q: in other games, if you're playing in a half-screen window, does the software record the game as if it were fullscreen?

Thanks! PITA to fly: wants to go straight up and nowhere else - but I did manage to force the final stage into orbit. Took a lot of nursmaiding.

I'm running windows borderless - game is in fullscreen. I just hit Alt+F9 and Nvidia starts recording. Only seems to be recording the game... but I'm quite new at this. My vids only show what I see on the screen, which is the game. It could be recording desktop - don't know. What's the difference?

I think you have me beat. ...But this WAS 33 engines firing!

Yeah - it's certainly toned down. That is a nice feature. I'm certainly doing a lot more playing KSP2 than Bug Hunting.

I'm right there with you... At the bottom of a bowl of hills with no way out! I find those all over the place. One thing - they are stronk.

I noticed this while trying to deploy some comm sats around EVE yesterday. A combination problem - when the "Observer Can't Leave Active Vessel" thing shows up... every pod you detach from your ship is just dead junk. The thing I've noticed is that upon separation, both ships revert to a 'dead stick' state. Neither craft has SAS or 'remembers' it's last instructions. For a ship with the engines off in orbit doing a gentle separation - that's fine. You can generally switch between the two craft and manually tell each one to set SAS or burn or whatever. To test this... I created an MLRS. Results were disappointing.

I hear you - a bunch of us spit balled the improvements we'd like to see last year. Doubt any of it will be in the game - but we gave it a try. Yes. They have been particularly cagy about what Science will bring. So many of us hope it is a real game changer. I'm just going off interviews where Nate referred to resource management and progression - and effectively the economy of the game isn't science points or money but building colonies and making fuel outposts and setting up automated resource runs. (You have to manually do each once) The thing is - Science gives Kerbals something to do besides plant flags and waddle at 3x.

For anyone interested - I 'solved' this. TR-4 REQUIRES a rocket or jet to climb. Link