安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
奖励
0 
I put it on F12 instead. That is a key I would never try to type into a message field. Maybe you consider using some F-key by default instead of an often used one.
Then it works it's way back to the start, marking each tube (edge) that will be moving an item through it as "in-use".
When an item arrives at the target, the tube is unmarked as 'in-use', but nothing came come down the tube until the item on it's target is moving elsewhere.
I don't plan on developing the horizontal green tubes further, and suggest people use the 'boxy belts' for short distance operations, as they are easier to route around and have the ability to connect into/out of storage and converters (at least on Autonauts beta).
A) have a two-dimensional array of object types & exit times
B) as an object is added at one end, add the expected exit time to the array, increment the 'add object' array index, and destroy the object
C) as each exit time comes up, zero the exit time, increment the 'remove object' array index, and spawn the object at the other end.
(This would only need to run every X ticks, where X is the number of ticks between adding/removing objects to/from the tubes.)
Does that make sense?