I didn't manage to find a report on this bug so here it goes,
I equipped red copper wires and shift + click on a medium power pole to remove all red copper wire connections and instead what happened was, the game removed all copper connections and then it crashed I think when it was going to remove the red wire connections.
My exact scenario
- Have Medium power pole connected to my power grid.
- Had 3 red wires connected to the Medium Power Pole.
- Equipped 3 red wires
- SHIFT + CLICK on the Medium Power Pole which has the 3 red wire connections going to smart inserters and a passive provider chest.
What happens
- Copper connections were visually removed
- Game stops working
Expected behavior
- All connections to this Medium Power Pole should be removed.
My Setup
Windows 8.1 64bit
Factorio on version 0.11.5, 64bit
16gb ram
1.24TB on my primary HDD empty
Thanks,
Clayton
[0.11.5] Red Copper Wire - Game crash
-
- Filter Inserter
- Posts: 778
- Joined: Sun Sep 07, 2014 12:59 pm
- Contact:
Re: [0.11.5] Red Copper Wire - Game crash
Probably related to https://forums.factorio.com/forum/vie ... =30&t=7122
I don't have OCD, I have CDO. It's the same, but with the letters in the correct order.
Re: [0.11.5] Red Copper Wire - Game crash
Yes, it is the same problem indeed, it will get fixed in 0.11.6 (tomorrow).
Re: [0.11.5] Red Copper Wire - Game crash
For me it seems like it's different because I was equipped with red wires, because I was placing some down and when I did SHIFT + CLICK it crashed, and somehow even the save was corrupted. But I loaded the autosave from before that and it worked.kovarex wrote:Yes, it is the same problem indeed, it will get fixed in 0.11.6 (tomorrow).
Re: [0.11.5] Red Copper Wire - Game crash
The thing you describe is exactly the kind of stuff the fix should solve.ClayC wrote:For me it seems like it's different because I was equipped with red wires, because I was placing some down and when I did SHIFT + CLICK it crashed, and somehow even the save was corrupted. But I loaded the autosave from before that and it worked.kovarex wrote:Yes, it is the same problem indeed, it will get fixed in 0.11.6 (tomorrow).