Factorio Forums

nightingale wrote:I've hit a problem in the 0.4.1 AAI Programmable Structures release on Factorio 0.16.21. Whenever I click on either the Input Terminal or Output Terminal of the Tile Scanner, I get this error:

Code: Select all

Error while running event aai-programmable-structures::on_tick (ID 0)
Can't add element with the name "entity" as LuaGuiElement contains a property or method with the same name.
stack traceback:
	__aai-programmable-structures__/control.lua:1016: in function 'struct_gui_add_setting'
	__aai-programmable-structures__/control.lua:1058: in function 'struct_gui_add_settings_recursive'
	__aai-programmable-structures__/control.lua:1042: in function 'struct_gui_add_settings_recursive'
	__aai-programmable-structures__/control.lua:1054: in function 'struct_gui_add_settings_recursive'
	__aai-programmable-structures__/control.lua:1042: in function 'struct_gui_add_settings_recursive'
	__aai-programmable-structures__/control.lua:1087: in function 'struct_add_settings_gui'
	__aai-programmable-structures__/control.lua:1203: in function <__aai-programmable-structures__/control.lua:1186>

grays42 wrote:

Earendel wrote:Those structures are being moved to a different tech for vehicle specific structures. It makes it less complicated if you add the vehicles mod at a later date.

Gotcha.

Earendel wrote:I'm guessing that you're using a mod that automatically makes ghost entities real? If so that's what is breaking it.

Ah! Yep, that would be it. Rather than try to learn the mod a live environment, I'm experimenting and putting together circuit monstrosities in my creative mode sandbox that I can later use in live. Didn't realize that would affect it. Thanks!

As a side note, do you have any intention of making the coordinates of depots scannable by ID? That's the one thing that I really feel like is missing; I'm setting up what is essentially going to be a combinator-driven data network to make haulers into giant logistic bots, and the one thing that's proving super difficult to streamline is the process of defining the locations of depots. I'm having to manually enter X,Y values into constant combinators to say "this is where the depot lives", it's completely arbitrary. The only way to uniquely pull a depot location is to mark the depot with a zone, which isn't scalable; I'm basically just using a zone to tag the location, a scanner to determine the X,Y, and manually keying that into a combinator.

Also, a few questions about some of the signals that I can't find documentation for anywhere:
- What triggers, or how do I utilize, the "minimum fuel" signal? At the moment I have a manually built combinator array that basically adds up all fuel sources in inventory to determine how much fuel I have left. I can't figure out how the minimum fuel symbol shows up on my scanner in a usable way.
- What is a "surface signal"?

Thanks for this mod. I just discovered it a week ago and it's a whole new playground of programmable awesomeness.

Eventually depots probably will be scannable by id, and 'followable' using their id as part of a goto command. That will probably happen as part of adding location beacons that also have ids and are used for the same purpose (minus the storage).

Minimum Fuel is value you can set on a unit's Unit Data. When it transfers items away, it will make sure it has at least items totalling that fuel value. This stops haulers from giving away all their coal and getting stuck.

Toch wrote:Hello is there any plan to make tile scanner read cliffs ?

brunobf wrote:I watched the tutorial linked from the first page, and whenever Nilaus clicks (?) on the signal output terminal, an inventory like interface pops up with the signals listed as items.
Video Frame: https://youtu.be/e93rbJmFTyU?t=209
Whenever I do that, I get instead a "Tile Scanner" screen with Output Filtering toggles. Am I using the wrong click?

sparr wrote:Attached to this comment is a save file illustrating a bug, possibly a problem with blueprint placement as the entities in question were placed from a larger blueprint.

The unit scanner is correctly locating the nearby mining machine mk2, and sending its output to the input of the tile scanner. The tile scanner is scanning and outputting information about the wrong tile.

Nightinggale wrote:Add an output signal to tell the number of ticks since last update.

mrvn wrote: Mon Jul 30, 2018 2:12 pm

Nightinggale wrote:Add an output signal to tell the number of ticks since last update.

The main reason for the infrequent scans is that setting signals is very UPS costly. Setting the ticks since last update would already incurr most of the cost of the whole operation making it pointless to not scan so often.

tehfreek wrote: Sat Apr 28, 2018 1:42 am

sparr wrote:Attached to this comment is a save file illustrating a bug, possibly a problem with blueprint placement as the entities in question were placed from a larger blueprint.

The unit scanner is correctly locating the nearby mining machine mk2, and sending its output to the input of the tile scanner. The tile scanner is scanning and outputting information about the wrong tile.

I opened the file and immediately noticed a bunch of "floating" output terminals, and the tile scanner is connected to one of these floating output terminals and not the unit scanner's output terminal.

Vehicle/Unit ID + (Sub-X-Tile and/or Sub-Y-Tile): The Sub-XY tile offset is converted to an angle and speed. Sub-X-Tile 1 and Sub-Y-Tile 1 means go South East VERY slowly. Sub-X-Tile -1000 and Sub-Y-Tile 500 means go West-South-West quickly. If you can get the Sub-XY positions of two objects you can subtract them to get the Sub-XY difference between them. If you use these values as your command signal it will make the vehicle go directly towards (or away from) the target.