[phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2075: compact(): Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/viewtopic.php on line 2182: Undefined variable $warn_allowed [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4218: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3103) [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4218: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3103) [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4218: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3103) [phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4218: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3103) [0.17/0.18] LTN Combinator - Page 5 - Factorio Forums
......icons. icons are just as good as words for this. all I really needed was to have something other than (failing to) memorize that ID 8 is my boats bringing oil. this is why they pay you the big bux, I'm sure.
edit: thank you. that looks amazing, and very cool. and also for the combinator, which is great too!
slippycheeze wrote: Wed Aug 07, 2019 2:00 pm
......icons. icons are just as good as words for this. all I really needed was to have something other than (failing to) memorize that ID 8 is my boats bringing oil. this is why they pay you the big bux, I'm sure.
edit: thank you. that looks amazing, and very cool. and also for the combinator, which is great too!
The reason to use different IDs is if you have the same item but want to provide/request it only for a subset of stations. Using one bit for Slag doesn't make much sense because if everything Slag uses that bit you can just leave it at -1.
I like the icons for Network ID bits. But if possible being able to specify up to 4 icons per bit would be nicer, like with blueprints. Then I can set 0x10 to Slag + Electrolizer for example to signify that it is creating slag expensively.
slippycheeze wrote: Wed Aug 07, 2019 2:00 pm
......icons. icons are just as good as words for this. all I really needed was to have something other than (failing to) memorize that ID 8 is my boats bringing oil. this is why they pay you the big bux, I'm sure.
edit: thank you. that looks amazing, and very cool. and also for the combinator, which is great too!
The reason to use different IDs is if you have the same item but want to provide/request it only for a subset of stations. Using one bit for Slag doesn't make much sense because if everything Slag uses that bit you can just leave it at -1.
I like the icons for Network ID bits. But if possible being able to specify up to 4 icons per bit would be nicer, like with blueprints. Then I can set 0x10 to Slag + Electrolizer for example to signify that it is creating slag expensively.
Oh, huh. In this case it is separating "this stuff is on rails" and "this stuff is water-rails", and never the two shall meet. Not specific to the individual items, though you could also apply it that way.
mrvn wrote: Thu Aug 08, 2019 9:57 am
I like the icons for Network ID bits. But if possible being able to specify up to 4 icons per bit would be nicer, like with blueprints. Then I can set 0x10 to Slag + Electrolizer for example to signify that it is creating slag expensively.
I looked into making 4 icons possible, but it would bloat the UI too much to distinguish the different icons.
100406.153 Error MainLoop.cpp:1199: Exception at tick 12310138: The mod LTN Combinator caused a non-recoverable error.
Please report this error to the mod author.
Error while running event LTN_Combinator::on_gui_click (ID 1)
LuaEntity API call when LuaEntity was invalid.
stack traceback:
__LTN_Combinator__/scripts/ltn-combinator.lua:287: in function 'remove_slot'
__LTN_Combinator__/scripts/ltnc-gui.lua:642: in function '?'
__LTN_Combinator__/scripts/ltnc-events.lua:23: in function <__LTN_Combinator__/scripts/ltnc-events.lua:21>
stack traceback:
[C]: in function '__index'
__LTN_Combinator__/scripts/ltn-combinator.lua:287: in function 'remove_slot'
__LTN_Combinator__/scripts/ltnc-gui.lua:642: in function '?'
__LTN_Combinator__/scripts/ltnc-events.lua:23: in function <__LTN_Combinator__/scripts/ltnc-events.lua:21
100406.162 Error ServerMultiplayerManager.cpp:92: MultiplayerManager failed: "The mod LTN Combinator caused a non-recoverable error.
Please report this error to the mod author.
Error while running event LTN_Combinator::on_gui_click (ID 1)
LuaEntity API call when LuaEntity was invalid.
stack traceback:
__LTN_Combinator__/scripts/ltn-combinator.lua:287: in function 'remove_slot'
__LTN_Combinator__/scripts/ltnc-gui.lua:642: in function '?'
__LTN_Combinator__/scripts/ltnc-events.lua:23: in function <__LTN_Combinator__/scripts/ltnc-events.lua:21>
stack traceback:
[C]: in function '__index'
__LTN_Combinator__/scripts/ltn-combinator.lua:287: in function 'remove_slot'
__LTN_Combinator__/scripts/ltnc-gui.lua:642: in function '?'
__LTN_Combinator__/scripts/ltnc-events.lua:23: in function <__LTN_Combinator__/scripts/ltnc-events.lua:21>
To Reproduce
Unknown I was sleeping when it happened 2 others were on. I asked they were trying to set a requester station to provide sulfuric acid.
ncnecros wrote: Fri Aug 30, 2019 11:15 am
dockmeister, Could you add the option "Limit trains"? This is also a commonly used option.
Hi,
you can go to the "Mod Settings", under Global, you'll find the settings for LTN Combinator. There you can edit the default visibility for ltn signals.
Another quick way is, to put any LTN Signal into the default combinator output. After reopening the ltn combinator the signal is available as input box.
This is a very minor request: Is it possible to make LTN Combinator not a upgrade from the vanilla combinator? Currently a unmodified Upgrade Planner wants to upgrade every combinator to LTN Combinators. While not breaking anything it's a bit silly. Is it possible to do that without losing functionality?
Hadramal wrote: Mon Feb 10, 2020 12:47 pm
This is a very minor request: Is it possible to make LTN Combinator not a upgrade from the vanilla combinator? Currently a unmodified Upgrade Planner wants to upgrade every combinator to LTN Combinators. While not breaking anything it's a bit silly. Is it possible to do that without losing functionality?
Hi,
that is already implemented. Go to:
Mod Settings -> Startup -> LTN Combinator -> uncheck "Upgradable from Constant Comb."
First off, this is an awesome mod, thanks for making it!
I have a suggestion for a potential new feature, if you think they would be helpful and feasible.
1: Add an option to set thresholds to be controlled by 4 different map settings
Add a checkbox next to provide threshold, provide stack threshold, request threshold, and request stack threshold
If this is checked, the input box will be grayed out, and the number from the relevant map setting will be used in its place. When a map setting is changed, the corresponding box is updated on all combinators that have the corresponding box checked.
We are running a mega base with very decentralized production, and when we upgrade our trains to a larger wagon size it is a pain trying to update all the station requests manually. If we could update them all simultaneously with one setting it would be super helpful. While I know LTN has a way to default provider and request numbers, there is not a way to set a default number of stacks. Furthermore, this would output the default to a circuit network that would let us do some neat things as a result.
So I thought a bunch more on the post I made prior. First thing is I realized it would be silly to make a new setting for default provider and requester thresholds, your mod could just read the LTN version of these.
I also thought of some additional changes that would make it even easier to both set up an LTN train stop, and also make it easy to automatically update every stop if you use modded trains and expand them as your tech increases.
I do still think having a default stack threshold for providers and a separate one for requester would be helpful, and it could not be part of LTN directly since stack request/provide has to be blank for the absolute numbers to be used instead.
I mocked up a slightly modified version of the LTNC GUI to show what I mean for these next parts
LTNC.png (136.48 KiB) Viewed 13753 times
The check boxes I added on the right side would show up on both the Requester and Provider GUIs, and override the box with the values in the appropriate map setting.
I also added some additional options in the bottom section of the combinator GUI. "Stacks" Is meat to request a number of stacks of the items entered into the combinator. "Trains" is to request a full train based on the request threshold specified.
Their selection would cause the following logic to occur
If "Stacks" is selected:
for each signal in the combinator
If it is type "item", then multiply the output signal by the stack size of that item, and then by -1 if the result is positive
For example, if 160 iron ore was entered, it would output a circuit network signal of -8000 iron ore
If "Trains" is selected:
For each signal in the combinator
If it is type item:
If the request stack threshold is filled out, the multiply the output signal signal by the stack threshold, multiply again by the item stack size, and then multiply by -1 if not negative
If the request stack threshold is blank, then multiply the output signal by the request threshold, and then multiply by -1 if not negative
If it is type fluid:
Multiply the output signal by the request threshold, and then multiply by -1 if not negative
Thank you for even reading through my request. If any of it is unclear please let me know and I'd be happy to clarify.
TokMor wrote: Wed May 13, 2020 12:52 am
So I thought a bunch more on the post I made prior. First thing is I realized it would be silly to make a new setting for default provider and requester thresholds, your mod could just read the LTN version of these.
I also thought of some additional changes that would make it even easier to both set up an LTN train stop, and also make it easy to automatically update every stop if you use modded trains and expand them as your tech increases.
I do still think having a default stack threshold for providers and a separate one for requester would be helpful, and it could not be part of LTN directly since stack request/provide has to be blank for the absolute numbers to be used instead.
I've run into the same issue with updating wagon size. But I think a more flexible solution would be better. Your global default assumes you will update all wagons at the same time and never use different wagon types for different things. Even using different sized stations would throw it off.
Instead I would think it better if you could create named presets for the LTN combinator. Here is how I imagine it to work:
You place the LTN combinator just like now and configure it. In the GUI there would then be an extra field "Named Preset". You create a new preset simply by entering (or editing) a name. Or you can select an existing preset and all the LTN Combinator settings will be updated to the preset.
Altering any settings in an LTN combinator with named preset will also alter all the other with the same named preset. That way you can change the "Iron Ore Requester" and "Iron Ore Provider" presets when you change the wagon size for ore trains for example.
Even more flexible would be if the LTN combinator (with a named preset) had, at the bottom, fields for the preset and fields independent of the preset. That way you could e.g. set the priority of a station to different values while still using a common preset.