why can´t I place 2.5 service bay UNDER a fuel tank?

[faceeasyg]

I recently migrated to Linux (had enough of MS shenanigans) and restarted KSP. Now I tried to recreate my rover lander, but could not fit the 2.5 service bay UNDER the fuel tank, i have no idea why. Previously I tried to place the rover into the already fitted service bay with no success. Well, of course I could fit it in the bottom but not to the top. So I prefit the rover into the bay as sub assembly, which worked fine.

Strangely enough:

- I can fit the same stuff ABOVE, see screenshot, no matter how impossibly impossible it might be. Legit, eh?

- when I tried to make a screenshot of the stuff when trying to place it under the tank (while it´s red cuz it never got green :P) the whole everything just crashed. I mean even the op system. Tried 2 times, then gave up. So no screenshot of that, but will make a video if needed.

- I used the same design under win in the past, and it worked fine. So nothing else has changed ever since just linux.

I´m using no mods, and don´t even want to. Any ideas how I could overcome this?

Thanks in advance!

[Harry Rhodan]

1 hour ago, faceeasyg said:

- I can fit the same stuff ABOVE, see screenshot, no matter how impossibly impossible it might be. Legit, eh?

No, you still didn't attach the service bay but clipped right through it and attached the tank to the rover. The thing with subassemblies is that only the nodes of the root part will be attachable And in your case that's probably not the service bay but the rover body. You have to use the root tool to make the service bay the actual root and save the rerootet construct as a new subassembly.

[faceeasyg]

1 hour ago, Harry Rhodan said:

No, you still didn't attach the service bay but clipped right through it and attached the tank to the rover. The thing with subassemblies is that only the nodes of the root part will be attachable And in your case that's probably not the service bay but the rover body. You have to use the root tool to make the service bay the actual root and save the rerootet construct as a new subassembly.

root tool?

[bewing]

2 hours ago, faceeasyg said:

when I tried to make a screenshot of the stuff when trying to place it under the tank (while it´s red cuz it never got green :P) the whole everything just crashed. I mean even the op system. Tried 2 times, then gave up. So no screenshot of that, but will make a video if needed.

- I used the same design under win in the past, and it worked fine. So nothing else has changed ever since just linux.

 

That is exactly the kind of bug that the devs want to fix the most -- crashing bugs. If you can post the parts and give clear instructions on exactly how to crash the game; I will create a bug report, and the devs will want to see it very much.

[faceeasyg]

28 minutes ago, bewing said:

That is exactly the kind of bug that the devs want to fix the most -- crashing bugs. If you can post the parts and give clear instructions on exactly how to crash the game; I will create a bug report, and the devs will want to see it very much.

Just let me know what kind of info you need, or how I can provide it and I´ll do so. It in fact so much crashed my PC, that even my Ubuntu stopped booting, and I worked for 45 mins to figure out how to reboot it at all... Ever since then KSP also didn´t start, but looks like I fixed (steam did in fact).

The way I crashed the game... well... everything... was to try to make system-based screenshot (print-screen) while the subassembly was hovering under the tank being red (not attached). Since I now know how to fix my system if you insist I will reproduce. It worked for 2 times, why shouldn´t it work for the 3rd?

[Harry Rhodan]

1 hour ago, faceeasyg said:

root tool?

You see the icons in the uper left of your screenshot?

The one on the right is the re-root tool. Press the button, click on any part to choose if you want to re-root your main stack or a redded out stack in the background and then click a second time on the part that should be the new root of that stack.

[bewing]

1 hour ago, faceeasyg said:

The way I crashed the game... well... everything... was to try to make system-based screenshot (print-screen) while the subassembly was hovering under the tank being red (not attached). Since I now know how to fix my system if you insist I will reproduce. It worked for 2 times, why shouldn´t it work for the 3rd?

Heh. Hopefully I don't need you to go that far. So you think that if all you had was the fuel tank, and you hover the unattached subassembly below it and take a screenshot, that'll do it. I just need a simple set of instructions like that to pass on to the linux QA testers -- but they have to be able to reproduce the crash themselves. Actually, since they have to reproduce the crash, they might appreciate having your instructions on how to get Ubuntu to reboot afterward, too.

Do you have the subassembly saved to a craft file? Craft files are just text files, so all I need is for you to go to pastebin.com and copy and paste the contents of that craft file to pastebin, and then post the link.

 

[faceeasyg]

7 hours ago, bewing said:

Heh. Hopefully I don't need you to go that far. So you think that if all you had was the fuel tank, and you hover the unattached subassembly below it and take a screenshot, that'll do it. I just need a simple set of instructions like that to pass on to the linux QA testers -- but they have to be able to reproduce the crash themselves. Actually, since they have to reproduce the crash, they might appreciate having your instructions on how to get Ubuntu to reboot afterward, too.

Do you have the subassembly saved to a craft file? Craft files are just text files, so all I need is for you to go to pastebin.com and copy and paste the contents of that craft file to pastebin, and then post the link.

I was trying to create that craft file for you, but could not run KSP, it wants to install it but refuses to do so as there is not enough disk space. 2.4 GB needed and there´s 380GB... And I can´t even save a screenshot of that, so I guess I better use an Ubuntu installer to try to really fix the system in the first place, as built in screenshot doesn´t save. I tried Kazam as alternative, and that also can´t save.

Well, actually all my steam games wants to install instead of running, and none of them have enough space to install so I´m afraid steam client is broken aswell. In case I have to reinstall all the stuff, I might not be able to deliver the craft file, and I´m pretty much sure that all my save files will be lost...

So maybe the last bit of information I can provide is on how to reboot Ubuntu after this crash, and it´s pretty straight forward: since the system got totally unresponsive the only option was to physically powering down. I understand that might have caused damages, and indeed it did, as the next reboot(s) I needed to manually fsck from initramfs prompt. For a couple of attempts I could still run the game, but now.

So for today I have a lot to do (trying to fix or reinstall all the stuff from zero)... In case I still have my save files afterwards I will attempt to provide all the needed information, but I guess the chances are low.

So for now the lastest bit of information is that I was running career mode...

Thank you for all your kind input and attempt to help, I´ll be back after I fixed my computer.

[faceeasyg]

9 hours ago, bewing said:

Heh. Hopefully I don't need you to go that far. So you think that if all you had was the fuel tank, and you hover the unattached subassembly below it and take a screenshot, that'll do it. I just need a simple set of instructions like that to pass on to the linux QA testers -- but they have to be able to reproduce the crash themselves. Actually, since they have to reproduce the crash, they might appreciate having your instructions on how to get Ubuntu to reboot afterward, too.

Do you have the subassembly saved to a craft file? Craft files are just text files, so all I need is for you to go to pastebin.com and copy and paste the contents of that craft file to pastebin, and then post the link.

OK, ubuntu stabilized, steam client reinstalled (that was broken), KSP runs, I have all saves so here´s the craft file:

http://pastebin.com/MjNL5nhE

This is the subassembly that was meant to be placed under a HECS6 and a straight C7 brand adapter. The crash happened when I tried to make Ubuntu default screenshot (PrtSc) of the subassembly not connecting to the bottom of the tank. The subassembly was built in SPH, while the main craft was built in VAH. This made the whole system crash with no response whatsoever, so next step was powering down. This caused damage so next bootup manual fsck was needed, but it kept running. Tried to make a screenshot again, same happened, but also damaging the steam launcher.

Ubuntu version is 16.04 (64bit), not much stuff installed so far. Steam (with 4 games), Wine with 2 games, some browsers, and some smaller apps like Kazam, QMMP, but those should have nothing to do with this, especially that they were not running. The PC is an Acer Aspire v3-772g, with memory expanded to 16Gigs.

Re-rooting solved the basic problem, I can now fit the subassy to the tank correctly (big shoutout to Harry, thanks mate), but if you´re hunting bugs and I can help you with further information please let me know!

[faceeasyg]

10 hours ago, Harry Rhodan said:

You see the icons in the uper left of your screenshot?

The one on the right is the re-root tool. Press the button, click on any part to choose if you want to re-root your main stack or a redded out stack in the background and then click a second time on the part that should be the new root of that stack.

Thanks, that totally fixed the problem, no matter what other problems I had in the meantime, see above.

Thank you again! Cheers!