Project

General

Profile

Bug #26977

Decoupling child craft from parent craft results in child disappearing and console errors

Added by slavic over 3 years ago. Updated about 3 years ago.

Status:
New
Severity:
Low
Assignee:
-
Category:
Application
Target version:
-
Start date:
01/05/2021
% Done:

0%

Version:
Platform:
Linux
Expansion:
Core Game
Language:
English (US)
Mod Related:
No
Votes:
Arrow u r green
Arrow d r red

Description

Building a vessel made of an engine, a Probodobodyne Okto (parent) coupled to a service bay and a Probodobodyne Stayputnik (child) launch it into suborbital flight, decouple and switch to child vessel (_]_ key). Funny things will start to happen, like vertical speed will be suddenly zero, although the craft is visibly moving, NaN error log will start popping up in console.

Log attached.

Player.log (2.49 MB) Player.log slavic, 01/05/2021 03:27 PM
Luna 4.craft (190 KB) Luna 4.craft slavic, 01/08/2021 07:29 PM

History

#2 Updated by slavic over 3 years ago

It looks like this is very much related to #26971 bug reported earlier, however that report only refers to EVA constructed vehicles and the Windows version. It looks, however, that the regression is more severe and more general.

#3 Updated by just_jim over 3 years ago

Can you attach either a craft file or saved game with the craft in question, please?

#4 Updated by slavic over 3 years ago

You don't need a specific save/craft (although I can/will supply it later today) - just decouple any crewless craft (Probodobodyne controller) and switch control to it.

#5 Updated by slavic over 3 years ago

Attaching the original craft that experienced the issue, though, to be noted, this is not the minimal reproduceable example. The minimum is actually any probe connected to another ship that gets decoupled.

#6 Updated by just_jim over 3 years ago

Understood, and thank you. The problem is I cannot reproduce it here (so far) even using your craft. Not saying it didn't happen, clearly there is an issue. But I need to figure out why, so first I'll pass this onto another member of the team that has a Linux and see if this is happening on Linux only (it's happened before). Thank you for your patience

#7 Updated by slavic over 3 years ago

Feel free to let me know if there's anything else I can help with/supply. Ready & willing to give a hand. I have downgraded to 1.10 a.t.m. just to be able to continue to play the game, however, if you can give me a non-steam binary of 1.11 I can continue testing on Debian/Ubuntu distros.

#8 Updated by Anth12 over 3 years ago

This sounds very similar to #26971

#9 Updated by dog20aol about 3 years ago

I am experiencing the same issue and can provide additional detail. I built a dual orbital probe and landing probe separately, then using load craft with the merge option, I brought them both into the VAB. I re-rooted the added craft so that I could attach them together. When they are in orbit of their destination, I attempt to use staging to seperate them and activate the engines. When I detach the added probe from the original vessel, it appears to be exerting a force that pushes them together. The added craft shows the NAN in the console, and is unloaded when time warp is activated. The original craft shows the orbit constantly changing with the other craft pushing on it, even though no engines are firing, there is no RCS system, and no docking ports. If I destroy the FL-A5 at the bottom of the added craft (which is the same part I changed the root to when merging) the craft seems to get free, and be able to finally be pushed away from the parent craft. It seems like the 'Ease to ground' is activating when separating certain parts such as FL-A5 and SC-9001 through decoupling. The game physics considers these parts as "Under Acceleration" and the only way to get past the erros are to revert to a previous save and not play the game. I have experienced this with 3 seperate crafts I have built.

Also available in: Atom PDF