(I am trying to create "steps to reproduce right now...)
This has happened while pursuing a "dense multi-track station" idea, trying to fill the empty spots of
Ultimately building this: (Regardless of actual utility of such build )
FOOTER: Please don't think of this bug storm as a proof that you haven't tested it properly.
Take it as a proof that the distributed bughunting is really effective and the way to go.
[Resolved 0.4.1] segfault when removing rails. [reproduced]
[Resolved 0.4.1] segfault when removing rails. [reproduced]
Last edited by MF- on Sat May 04, 2013 12:16 pm, edited 2 times in total.
Re: [0.4.0] segfault when removing rails... [reproduced]
So.. here goes a picture-by-picture howto.. (eh.. max 3 pictures...
I guess I am forced to do a GIF...) And to include it via
Two non-moving pictures of the later stages of the build
I guess I am forced to do a GIF...) And to include it via
Two non-moving pictures of the later stages of the build
- Attachments
-
- bug.gif (1.36 MiB) Viewed 4078 times
Re: [0.4.0] segfault when removing rails... [reproduced]
PS: I even got a segfault while placing rails this time
Re: [0.4.0] segfault when removing rails... [reproduced]
PPS: It also segfaults when I stand in the "trident-like" contraption from the first post, the "select new research" thing pops up by itself and I dismiss it by "t" instead of selecting new research.
Re: [0.4.0] segfault when removing rails... [reproduced]
Thank you for the nice setup, we just repaired the bug.
Re: [0.4.0] segfault when removing rails... [reproduced]
Thank you, fixed.MF- wrote:PPS: It also segfaults when I stand in the "trident-like" contraption from the first post, the "select new research" thing pops up by itself and I dismiss it by "t" instead of selecting new research.
Re: [0.4.0] segfault when removing rails... [reproduced]
Actually we are really grateful for you guys being willing to download and test the game even when it is most probably going to cause problems. Some of the bugs we could have found but some of them would take a long time to find. So yes the "distributed bughunting" looks very appealing. As long as people understand that the version released after month of work will be rather unstable all is good.MF- wrote: FOOTER: Please don't think of this bug storm as a proof that you haven't tested it properly.
Take it as a proof that the distributed bughunting is really effective and the way to go.