Hi I am experience a problem with 1 conveyer belt.
I use it to transport iron ore and on the conveyer belt there seems to be more then 30K material on 1 belt.
http://imgur.com/mfnoiYQ
If I remove the conveyer belt or change the direction the game freezes.
So now I use a inserter to clear the belt.
I tried to empty the belt myself 21 steel crates (11x2.4K = 26.4K) and the conveyer belt still isn’t empty
http://imgur.com/TtCmOnO
Any andvice?
Save game : https://www.dropbox.com/s/h7bt27napivueef/J1.zip?dl=0
conveyor belt overload
-
- Manual Inserter
- Posts: 3
- Joined: Sun Apr 17, 2016 2:22 pm
- Contact:
Re: conveyor belt overload
That sounds a lot like a previous bug report where the person ended up having bad RAM.HunterWithin wrote:Hi I am experience a problem with 1 conveyer belt.
I use it to transport iron ore and on the conveyer belt there seems to be more then 30K material on 1 belt.
http://imgur.com/mfnoiYQ
If I remove the conveyer belt or change the direction the game freezes.
So now I use a inserter to clear the belt.
I tried to empty the belt myself 21 steel crates (11x2.4K = 26.4K) and the conveyer belt still isn’t empty
http://imgur.com/TtCmOnO
Any andvice?
Save game : https://www.dropbox.com/s/h7bt27napivueef/J1.zip?dl=0
Try running a memory test on your computer to see if it can detect the issue: http://www.memtest.org/
If you want to get ahold of me I'm almost always on Discord.
Re: conveyor belt overload
To fix it, hover over the belt with the mouse and enter in the console:
Otherwise you're out of luck, the transport belt contains about 104 million iron-ore.
(Or you found an (almost) never ending source of iron-ore).
Not sure how this bug came to be in the first place, did you use any other mods that you have removed since then or did you enter any console commands that would be able to do something like that?
Another option would be memory corruption (faulty RAM), but this is unlikely and you would have also experienced crashes in other applications/games.
Code: Select all
/c game.local_player.selected.destroy()
(Or you found an (almost) never ending source of iron-ore).
Not sure how this bug came to be in the first place, did you use any other mods that you have removed since then or did you enter any console commands that would be able to do something like that?
Another option would be memory corruption (faulty RAM), but this is unlikely and you would have also experienced crashes in other applications/games.
-
- Manual Inserter
- Posts: 3
- Joined: Sun Apr 17, 2016 2:22 pm
- Contact:
Re: conveyor belt overload
wow 104 million....
My ram is more than fine I run a rig with 16GB of ram, so more than enough for this game.
Looks like I have enough ore for life here.
And thanks for the fast response
My ram is more than fine I run a rig with 16GB of ram, so more than enough for this game.
Looks like I have enough ore for life here.
And thanks for the fast response
-
- Manual Inserter
- Posts: 3
- Joined: Sun Apr 17, 2016 2:22 pm
- Contact:
Re: conveyor belt overload
o and i installed 2 mods halfway this game: Base Mod and Fluid barrel
Re: conveyor belt overload
It's not about the amount used. It's about defective RAM. That's what the link I provided tests for.HunterWithin wrote:wow 104 million....
My ram is more than fine I run a rig with 16GB of ram, so more than enough for this game.
Looks like I have enough ore for life here.
And thanks for the fast response
If you want to get ahold of me I'm almost always on Discord.
- TruePikachu
- Filter Inserter
- Posts: 978
- Joined: Sat Apr 09, 2016 8:39 pm
- Contact:
Re: conveyor belt overload
Coming from someone who has dealt with defective RAM in the past, just because nothing appears to be crashing doesn't mean that there isn't a problem. In my case, the system would only crash when running a specific game OR when the built-in display was in standby. However, it was silently causing other problems, like corrupting my Bitcoin blockchain in memory.
When testing RAM, it is best to have only one stick in the machine at a time; have each stick run through 3 passes before assuming it might be good (the "one stick at a time" non-adherence might have contributed to how long it took me to find my issue). It is okay to run more than three passes, and it is okay to have tests run overnight.
When testing RAM, it is best to have only one stick in the machine at a time; have each stick run through 3 passes before assuming it might be good (the "one stick at a time" non-adherence might have contributed to how long it took me to find my issue). It is okay to run more than three passes, and it is okay to have tests run overnight.