Space Engineers

Space Engineers

Taleden's Inventory Manager
Kenshinofkin 18 Mar, 2017 @ 10:32pm
Assemblers with auto not producting components
Ever since I have updated the script 1.6.3, none of my assemblers mark with [TIM Auto] create components. Every so often I see this on one of my LCD's marked with [TIM Debug]:

Assembler [TIM AUTO] is jammed by SteelPlate
Assembler [TIM AUTO] is jammed by SmallTube
Assembler [TIM AUTO] is jammed by BulletproofGlass
Assembler [TIM AUTO] is jammed by LargeTube
Assembler [TIM AUTO] is jammed by MetalGrid
Assembler [TIM AUTO] is jammed by Reactor
Assembler [TIM AUTO] is jammed by Detector
Assembler [TIM AUTO] is jammed by Explosives
Assembler [TIM AUTO] is jammed by SteelPlate
Assembler [TIM AUTO] is jammed by SteelPlate
Assembler [TIM AUTO] is jammed by SteelPlate
Assembler [TIM AUTO] is jammed by SteelPlate
Assembler [TIM AUTO] is jammed by SteelPlate
Assembler [TIM AUTO] is jammed by SteelPlate

I have alot of cargo space for components. Not sure what jammed means here.
< >
Showing 1-5 of 5 comments
taleden  [developer] 3 Apr, 2017 @ 1:20pm 
Jammed means that TIM assigned the assembler to produce something, but noticed after awhile that it wasn't making any progress on that assignment which usually happens when you've run out of some required material. TIM will then remove the assignment and avoid trying to produce that item for some time in order to let your assemblers work on things that can actually be produced.
Guran 15 May, 2017 @ 12:03pm 
@Taleden yea! This is why assamblers just stop producing needed items, because the items got sucked out of the assemblers by a welder or nanite factory as they got produced, and TIM believes the assambler didn't do anything because he is empty!

I assume you just check the output of the assemblers? If so, better remember the item and amount you ordered from the assambler (write it into custom data) and check the production progress against that information (if this is possible)
taleden  [developer] 2 Jun, 2017 @ 10:07am 
Welders sucking up produced items shouldn't affect TIM's assembler management because TIM doesn't actually look at the assembler's output inventory, it only looks at the assembler's remaining quantity of its assigned blueprint. As long as that remaining queued quantity keeps going down as the assembler works through it, TIM should consider it to be working fine even if the produced items are being immediately pulled out.
CovertJaguar 13 Jul, 2017 @ 4:22pm 
From my own testing, the cycles arguement breaks everything atm. Including assembling.
taleden  [developer] 23 Aug, 2017 @ 6:21am 
Can you be more specific? What exctly does it start doing wrong when using cycles?
< >
Showing 1-5 of 5 comments
Per page: 1530 50