Config
Log for #openttd on 31st December 2023:
Times are UTC Toggle Colours
14:00:24  <truebrain> that is an ethical debate I leave up to you. My suggestion is to pick an overarching region instead. But that is a choice you have to make
14:00:59  <truebrain> sadly, in any system, there is always a limit, and one someone always reaches
14:02:11  <DorpsGek> [OpenTTD/OpenTTD] SamuXarick updated pull request #11661: Change: Only remove orders from primary vehicles https://github.com/OpenTTD/OpenTTD/pull/11661
14:02:39  <rau117> truebrain: Is the limit of 10 really that important? Can it be increased to let's say 16, not 20.
14:02:39  <rau117> *Increasing virtual limit a little easier than choosing “who is worthy of mention”*
14:03:01  <truebrain> Pick any limit, and someone will be: can it be a bit higher pretty please?
14:03:15  <truebrain> for all kinds of technical reasons, this limit is set to 10
14:03:17  <truebrain> sadly, that is it
14:03:44  <DorpsGek> [OpenTTD/OpenTTD] PeterN opened pull request #11662: Change: Don't allow station/roadstop/object picker text to extend width. https://github.com/OpenTTD/OpenTTD/pull/11662
14:10:06  <DorpsGek> [OpenTTD/OpenTTD] SamuXarick commented on pull request #11661: Change: Only remove orders from primary vehicles https://github.com/OpenTTD/OpenTTD/pull/11661#issuecomment-1872957933
14:12:24  <andythenorth> did we give trains permanent storage yet?
14:23:40  <Rubidium> rau117: I think 10 is already quite a big number of regions; if it's really that many regions, isn't there some overarching region? Take the TRAXX, should I list all 14 countries? Or is Europe, Middle East, South Africa also a reasonable set of regions? It's about giving an idea where the vehicle's used.
14:26:04  <Rubidium> and yes, I know it's using a current list of countries/regions, so it's missing countries that existed in the past, but also countries that'll exist in the future. The regions, on the other hand, are less likely to change over time
14:27:13  <locosage> andythenorth: nope, last time I though about it I came to a conclusion that it would require changing how persistent storage works a bit
14:28:57  <locosage> because using current persistent storage is a huge waste of memory and adding another way to do the storage isn't great in general
14:36:15  <peter1138[d]> 1KiB per vehicle is a lot.
14:36:34  <peter1138[d]> You could got 16 slots so it's only 64 byte per vehicle, but then someone would say 16 isn't enough.
14:37:30  <andythenorth> whatever use case I have for it right now, it's probably wrong 😛
14:37:47  <andythenorth> something to do with powered wagons, dual head, and changing power by railtype
14:37:54  <andythenorth> BAD FEATURE ^ 2
14:41:02  <xarick> question, do Implicit orders show up in the OrderList?
14:41:13  <peter1138[d]> Yes.
14:41:23  <locosage> technically, persistent array pretty much never changes size after initialization
14:41:31  <xarick> okay, that sure helps things
14:41:32  <locosage> only if there was an easy way to know what that size is
14:41:47  <locosage> by size I mean max used index
14:43:16  <locosage> simplest way would be to just add action0 property that lets grf just tell what size it needs
14:43:37  <locosage> and if it exceeds it game can just reallocate
14:44:20  <locosage> but it's probably possible to figure it out with static analysis too
14:44:50  <locosage> _jgr_: did you do some persistent array size optimizations in your branch by any chance?
14:47:03  <locosage> peter1138[d]: as a temporary solution it's pretty viable actually
14:47:49  <locosage> if someone makes a better array size management later there won't be any spec changes
14:50:19  <peter1138[d]> How much persistent storage does one need, anyway...
14:50:55  <locosage> the more the merr

Powered by YARRSTE version: svn-trunk