DoToH
-
Posts
272 -
Joined
-
Last visited
Content Type
Profiles
Forums
Developer Articles
KSP2 Release Notes
Bug Reports
Posts posted by DoToH
-
-
The bug tracker.
-
On 9/3/2020 at 4:40 PM, Boyster said:
I am sure they gonna fix them
I am not.
On 9/3/2020 at 5:07 PM, steve_v said:1.6.x has no Breaking Ground. I'd like to play the DLC I bought.
1.4.x - 1.7.x has broken joystick support. I fly planes a lot, and I want the functionality the game used to have to actually work.
1.8.x fixed joystick support, but settings are reset every time you start the game and the atmosphere shaders are all screwed up.
1.9.x fixed the atmo, but didn't fix settings not applying. It also introduced various exotic mod-borking bugs relating to prefab resources and symmetry.
1.10.x still didn't fix settings not applying, and additionally borked resource transfer.
All of the above still have craft sliding around, wheels bouncing all over the place, parts displacing on restarting the game, and other ancient and infuriating bugs to numerous to list.So, which release of this lovely, polished, not at all perpetual-beta game should I play? Should I wait for the next release, get all my mods sorted out, then discover there's yet another new and idiotic regression?
Oh, the suspense, what will be broken this time?^^ This.
I don't play this "forever-early-access" game any more. From 0.18 to 1.7.3 I played each and every update. Thousands of hours played. Never got bored. The only thing that made me left the game was the endless wait for the next update to fix one or another bug, the constant hold, wait, before starting my new mission, base or whatever, hoping that there will be a stable version some day that can be used to play a very long save. That version never came. And 1.7.3 is the last version I installed.
I seriously doubt I would play this game any more, still I have it installed and come to the forums once in a while, and with each new update, hoping for the best and finding the same as before, just new bugs. It's sad to say that about a game I recommended to everyone I know. Now I think I recommended a never-ending project of a game.
The number in the version before the first dot doesn't make the game finished. For every single minor feature or cosmetic update we get a bunch of new bugs and some old ones revived. All those bugs mentioned here before (and some others) prove one thing: KSP is a (bad) beta. The fact that many people are still playing 1.3.1 should have made SQUAD think seriously about it, but they chose this insane strategy. Even games developed by only ONE person get more hotfixes for critical bugs than this one. Why? I don't know. And I don't care anymore.
KSP2 will be finished before KSP, despite the delays, and by the time, as KSP buglist is constantly growing, KSP2 will surely be less buggy. If I have to wait, I'd better wait for other product, developed by other team. Maybe they have better QA and bug fixing people/skills/will/whatever. Meanwhile, I will be around here, reading changelogs about new useless parts nobody asked for and workarounds for partialy solving new gamebreaking bugs. It's funnier when you don't play the game.
-
There ^^
Just to edit AGs. Simple and practical. In my favorite mods list since 2014.
-
Kerbals are green. Photosynthesis.
-
I'd recommend trial and error. It's funny until you achieve orbit consistently. Even to get to Mun or Minmus. And you will laugh with some of your weird failures. The meaning of RUD is the first one to learn.
Come to the forum only if you get really stuck. Believe me, you will come when you want to go interplanetary.
-
18 hours ago, Black-Two- said:
As the creator of that thread, I don't have that problem anymore. It disappeared in either 1.4.4 or 1.4.5.
That's the info I wanted to read!!! Now I just have to wait for mods to update.
Thanks.
-
1 hour ago, HebaruSan said:
Reading that thread, I wouldn't expect any action till SQUAD receives a save file that reproduces the problem, since a member of their QA staff already tried on his own and didn't experience it.
Well..... don't get me into the QA debate again. I'm not paid for thath job. KSP is not early access since years. If they expect customers to do their job instead of playing other games, good luck with that.
BTW, thanks for the answer, would have been nice to read an answer from SQAD guys. I appreciate that you took the time to read the thread and reply.
-
Any word on this?
I don't play KSP since then,
waiting for the fixplaying other games until is fixed. Maybe 1.6? -
Yes. Steam install. Supposedly correct MH version.
None of the affected ships had MH parts.
-
Same here. Never happened to me before 1.4, but with 1.4.3 I had 6 or 7 disintegrations. Same log message (part x crashed into collider). Every part but the capsule (maybe because is root) is destroyed and, sometimes, the capsule gets thrown far beyond Jool's orbit. I couldn't reproduce it consistently in my modded install, so didn't try unmoded. Unfortunately, I overwited the only quicksave I had before one of these RUD s. Happened with different crafts and none of them used autostrut. It seems like the game despawned the craft and spawned it again in the new SOI, even when the craft don't explode it disappears for a tiny moment. I didn't notice that behaviour before 1.4 so it might be related to the unity upgrade. It's more noticeable when going from Minmus SOI to Kerbin. Transition from Mun to Kerbin is smoother and I cant even notice that "respawn". In my new 1.4.3 career didn't get beyond Minmus, but my probes to Moho and Eve are arriving soon. I will check and update here If something wrong happens.
I allways set KAC alarms and jump to ships when changing SOI, and try to change SOI with timewarp halted (got that habit back when the game didn't slow the warp on SOI changes), so I'm pretty sure this didn't happen before 1.4.
Fortunately, workaround is simple: activate minimum on-rails timewarp (x5) just before changing SOI and kill timewarp to enable physiscs just after the change (or let the ship change SOI unloaded).
-
1 hour ago, 1990eam said:
the whole orbit is shifted to one side and I can't figure out the proper way to fix it through maneuver nodes
As Kryxal said, put a node in the intersection point and burn radia (or antiradial). It sems that you'll need a little burn normal to match inclination. AN and DN are near intersection, so you could burn just once (at the intersection) with radial and normal corrections.
32 minutes ago, Kryxal said:As for the units-of-measure issue, I'd guess it's a localization issue ... looks like Spanish.
Yes, it's spanish (I'm spanish but play KSP in english, too much english KSP since 0.17 to switch). And yes, it's a localization bug. Orbit inclination should be degrees (grados) and not meters. Also, there are far better translations than "generar luz" for "generate power" and no, "generar potencia" is not one of them...... could continue, but, long story short, I have many reasons to play KSP in english.
-
18 hours ago, GoSlash27 said:
I'm from the opposite school of thought. Any DV more than the minimum required to achieve the objective (plus a predetermined reserve) is too much. It's just fuel you won't ever use, tankage to lug it around in, and bigger engines than you really need to push it. All just dead weight and wasted money.
You are right, but.... there is no "too much delta V", maybe too few places to explore. Can we agree if I say it that way?
-
3 hours ago, Boyster said:
I felt like it had too much delta V
There's no such thing you call "too much delta V"
On topic:
My math gives 3945m/s ASL or 4913m/s VAC assuming you put a 0.1 t probe.
Approximately the delta V needed to reach Kerbin orbit with pre 1.0 atmo-soup. Not too much
-
1 minute ago, RW-1 said:
Sorry, Valve copyrighted this for HL-3 way before Kerbals existed ....
Next week is better. Gives more room to creativity.
-
Soon next week will become this week.
-
11 hours ago, Fourjays said:
The previous effects were definitely better and I'm not sure why they even changed them.
They didn't change the efects. AFAIK, the change was consequence of the engine upgrade.
2 hours ago, Fourjays said:was there any reason for Squad's QA to suspect that the landing legs may be broken?
The engine upgrade should have raised suspicion on many aspects, especially the ones that had been problematic in previous engine upgrades. Wheels and leg physics are among them.
1 hour ago, RoboRay said:Next week is always next week!
That's why "next week" was a wise decision. SQUAD is always on time.
Personally, I'd prefer quality, even if it costs another 1 or 2 weeks of testing.
-
13 hours ago, T1mo98 said:
Go to your Steam library, click on KSP, click on Properties, navigate to Betas and select 1.3.1 from the drop-down menu. So stop whining, since there is still a perfectly valid way to play without major bugs.
MH DLC doesn't work with KSP 1.3.1. I didn't pay for the DLC, but is safe to assume that people who paid for it wanted to PLAY IT.
9 hours ago, Kerbart said:They're not happy with it either. They're working hard to fix it.
I hope so. The current state of the game is not the best to increase sales.
9 hours ago, Kerbart said:In return, be a bit more relaxed towards the state of the product.
Why? Will SQAD/TTI be more relaxed towards the price people want to pay for their game/DLC? Can people download and play today and pay "next week"?
-
7 hours ago, Gargamel said:
This is one of the dumbest analogies I've ever read. The onus is on you for buying a car without a windshield, not the manufacturer.
Sure. Blame the customer is always smarter.
7 hours ago, Gargamel said:if it was some part that was bad that you never noticed before purchase, it'd be a different story.
So we need to detect bugs in a software BEFORE purchasing that software. Nice. Or detect bugs in 1.4 BEFORE the 1.4 update was released. Let me print this thread and get my DeLorean...
-
8 hours ago, Kerbart said:
What an adorable analogy. So cute.
I'm glad you like it
8 hours ago, Kerbart said:So yeah, this kind of behavior isn't really that special
And that means I'm not allowed to complain?
8 hours ago, Kerbart said:Don't be a whiner.
OK, you're right. After all, I didn't pay 40€ for KSP plus 15€ for the DLC.
-
- My car has no windshield
- Uh... Sorry.. our QA missed that, please forgive us.
- Please, install the windshield ASAP
- No. We have the windshield and the tools, but we'll wait until we receive the new trunk colored led light, becuse that's what you really want. You can drive your new car without windshield, wait one week more or use your old car instead.
- That's unacceptable.
- Don't be a whiner. You have to understand that cars are a very complicated piece of harware, with hundreds of different parts and the windshield is only one of them, an acceptable mistake. Please be patient and waitI don't understand why this kind of conversation only happens when the broken/faulty product is software. None of the people of the "coding is hard" mantra would step out of their car dealer with a car with no windshield or their computer store with a keyboard without space bar and enter keys.
Coding is hard, so is manufacturing proccess design. Your keyboards have enter key and your cars windshield.
-
1 hour ago, Boyster said:
I think its just a smoke screen to save some face.
My guess is they couldn't fix some of the important bugs so they had to come up with something.
That would explain why they don't split the update, publish 1.4.3 with much needed bugfixes and hold back new (bugged) content until 1.4.4, 1.5 or whenever they fix it.
-
3 hours ago, steve_v said:
My strategy is to always be one major release behind. By the time all the bugs in 1.4.x are sorted (if the game engine problems ever are), 1.5 will be announced, complete with a new batch of bugs.
Like a low-budget indie game, still in early access.
I'd hoped this kind of thing would stop when KSP got the big 1.0. Then I hoped it'd stop when we hit the first major after that, thinking perhaps 1.0 was just a bit rushed. Then a big name, Take Two, bought the game and an expansion was announced... I hoped...Maybe this is just what happens when you decide to build a game on top of a cheap-and-cheerful, perpetual-alpha, users-as-QA game engine.
Then again, other games built on Unity3D have got polish... many of them even have stable releases that don't add serious bugs.So true... so sad
-
Slightly off topic but.... does anyone know if the new launch sites also act as recovery sites? I mean...if I land my rocket at Woomerang or at the runway they are about to include with 1.4.3, will I recover full funds?
I forgot to check it myself when I tried 1.4.1 and now I'm back in 1.3.1 and don't want to update just for that test.
-
15 minutes ago, www2 said:
Any bugfix for fearings?
Turn on the light?
What do you NOT want in KSP 2
in Prelaunch KSP2 Discussion
Posted
I don't want KSP 1's non-existant QA (useless to say the least).
I don' want KSP 1's perpetual Early Acces developing mind that leaded to add more bugs than features every update post 1.0, producing a large pile of bugs that resembles (only if you keep the distance) a game that many of us loved before.
I don't want continuos developing. I want a FINISHED game. I don't want a buggy pile of crap. It took me only 1 hour of normal playing in KSP 1.12 to notice three new bugs. I have more than 1000 hours in factorio (purchased it before it was launched on Steam) and NEVER experienced just ONE bug.
I wan't to play a game. I don't want to be the unpaid QA of a eternal early access project.
I don't want to have to recommend friends not to buy it because it's so buggy that I'll have to explain them 5 or 10 workarounds that we shouldn't need to know, even if I have more than 3000 hours (less than 500 are post 1.3.1)