安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
举报此帖
I might have another bug but im gonna make few more tests before i publish it -> but basically its about a small ship factory(small blocks) connected to a base (large blocks) via connector -> when the factory is welding it sucks up components throught the connector from the base (welding part is okay) BUT when the welders are welding they disrupt the assemblers -> (they dont pull ingots into assemblers in order to make queued parts (but if you drop ingots manually they produce stuff) ofc when you shut off the welders assemblers pull stuff normally.
It looks like that this pull from welders is distupting the scirpt that manages conveyor push/pulll orders.
but like i said i shall make few more tests and get back to you :)
Ok, thank you very much for describing that bug. I will try it too :-) Thanks
I'm trying to "Dock" a small ship to a Large using the Rotor trick.
I have a large Rotor with a small head attached, and ontop of that 3x3x1 small blocks and a Merge block on them. The offset is set to 11,9. Two Large blocks away I have a connector.
The connector and merge block I have on my small ship are perfectly aligned to the ones on the big one, but still, every single try to dock crashes me to desktop =(
I've used the in-game crash report, and hope this will be solved, unless anyone have any tips on a workaround of some sort.
Edit: No mods, pure vanilla game
For example A piston attached to a rotor conntected to a wall then the other end of the wall connected to a rotor attached to the floor... By design this should be a piston operated ramp. but the problem occours when I attach one end or the other... only one connection at a time between any item and a ship or station... no more mechs... no more advanced designs THIS IS BAD because this is what SE was ALL about in the begining the Devs didn't care about gameplay or survival just building... NOW WE CANT!!!!
Yah we hear you -> but like Hellwiss_cz said they are aware of this and they are gonna work on it. The only thing you need to do is just to wait a bit. I have full confidence that devs will sort this out (since they always did sooner or later) and so should you :) Cheers
Failure to merge:
Trying to merge the blocks attached to heads of pistons that are on the same station. Direct A to B method. Extend one piston, add merge block, then return to lock them together, merge indicators would not even turn yellow.
Merge crash:
Trying a different method - Part A connected to part B via common link C - used a ship (in atmosphere) to provide a link across the two pistons. Merge does attempt to occur. Indicators turn yellow, link settles into place, when indicators should turn green (writing to the file, perhaps? I vaguely recall we had issues like that in alpha when merge blocks first came in.) game hard crashes to desktop. No error information displayed.
Further tests proved that ANY merge was doing the same exact thing. Reducing merge blocks on the ship to test a single, direct link from ship C to piston A, maneuver, settle, crash. Possible file corruption at this point?
Have any of you others tried reinstalling? Rather not have to be the one to test that with my crap connection speed.
To ghettodexter:
What do you think the difference between "fix" and "hotfix" are? And while I'm aware that this is a merge block issue in our cases, not everyone is experiencing it, so it's not like the game is universally broken.
The reason I continued to post on it, is not to complain about the issue, but to offer potentially helpful information to the devs that continually work to fix unforseen glitches that occur as they vie to improve the game. It does not run in a perfectly homogenized container, so "individual results may vary". That is the very nature of games running on PC and/or Linux.
Additionally, in this case we're talking about a BETA. If you're set off balance by things not running perfectly, by unexpected little breaks that may or may not be fixed right away ... if you're not excited to taking a critical look at the problem you're experiencing, and provide as in-depth, recreatable documentation of your bug/glitch, then it seems like maybe you'd be best served steering clear of Alpha/Beta and "Early Access" games altogether. Food for thought. Sorry to see your experience so soured by this.
To the Dev team:
I've been bending and breaking this game since you first released the early access on steam (within a month or so). I just want to offer a very delayed thank you, because it's been so rare that any issue I've encountered has sat long enough without a fix for me to even put up documentation. This is actually the first time I've taken the time rather than collaborating with others to do so. So thank you guys for all your work. Happy holidays.
Take a class in sociology you'd be suprised how many situations it can come in handy when dealing with other peoples point of veiw.
For myself I have been through SOOOOOOOOOoooo many fail games alphas betas fail! When things like and early bug that had the community up in arms re-arrises and the devs don't even mention it they just push out update after update hotfix 1...2...3... not even mention anything about it on the Bugs posts on the very issue (NOT Ships can't merge bug) it gets a person like myself who has been burned time and time again pretty worried that the very asset may be on the chopping block... I mean seriously HOW many issues do we really have surrounding the merge block and other blocks in the game?!!? That was the issue in the first place when it was introduced.
Don't take my worry as rant because you have seen far from anything ranty from this 31yr old. I'm just stating the facts of my situation, my findings in my bug report and the impact the bug has on my willingness to play and/or enjoy this game. I really do hope they fix it or there would be a workaround soon is all I'm saying.
Have a nice holidays too! :-)
*EDIT* Apparently I jumped the gun. Single merge works, no crash.
Attempting merge from Ship C to pistons A and B: A/B are on common station.
-Ship C attached to Piston A, OR Piston B, but not both.
-Permanently bridging Ship C to piston A, and removing merge blocks, cannot merge C to B. No yellow lights, no Merge.
-Attempted power cycling and removal/replacement of merge blocks, no change.
Can we confirm whether intended function is to make these kinds of mergers impossible? Do we not want double-hung items on shared pistons/rotors? As ghettodexter has alluded to, this would be counter-intuitive as an "engineer", and "game-breaking" for many of us.
I have come across this also. It seems that if you try to merge 2 platforms (or ships or whatever) using more then one set of merge blocks, they refuse to lock after the 1st set locks.
The best way I can explain this is this way.... Lets say you have 2 platforms, and they are called A and B, and you are using 2 sets of merge blocks, lets say they are a b c and d.
Lets say platform A has merge blocks a and c, and platform B has merge blocks b and d.
Now, when the platforms are close enough, a will lock with b, but c refuses to lock with d (the lights stay white), OR, c will lock with d, but then a refuses to lock with b.
It seems like once a set of merge blocks lock, making the 2 platforms into 1, all other sets of merge blocks refuse to lock becuase they are now part of the same platform.
This indeed breaks some builds I have in mind that would only be possible to make if multiple sets of merge blocks work on one platform.
Edit: Made a quick video to help better explain....
https://youtu.be/aLhdL5ackM4