IRC logs for #openttd on OFTC at 2023-11-18
00:03:07 <_pruple> Pumpjack
00:13:21 *** HerzogDeXtEr has quit IRC (Read error: Connection reset by peer)
03:12:42 *** Wormnest has quit IRC (Quit: Leaving)
03:22:59 *** debdog has joined #openttd
03:26:14 *** D-HUND has quit IRC (Ping timeout: 480 seconds)
04:51:18 *** keikoz has joined #openttd
05:12:06 <alfagamma7> peter1138: looks like you had a leak somewhere then
05:36:33 *** rau117 has joined #openttd
05:36:33 <rau117> Two questions: in what time unit will «cargo payment rates» after «real-time mode» will be added?
05:36:33 <rau117> And will it be possible to switch timetable for days unit?
05:36:33 <rau117> It will be quite inconvenient to calculate how much the cargo has aged in transit if these two parameters are in different time units…
06:12:34 <merni> Timetables will be in days by default (if real time mode is not enabled)
06:28:07 *** keikoz has quit IRC ()
06:33:18 *** keikoz has joined #openttd
07:00:10 <peter1138[d]> Got up early for bike ride... 🌧️🌧️🌧️
08:01:21 <andythenorth> 🌧️ here too
08:05:36 *** nielsm has joined #openttd
08:41:05 <pickpacket> It’s -8C here
09:30:23 *** Flygon has joined #openttd
09:37:29 *** HerzogDeXtEr has joined #openttd
10:55:13 <DorpsGek> [OpenTTD/team] ekaknl22 opened issue #466: [id_ID] Translator access request
10:56:37 <DorpsGek> [OpenTTD/OpenTTD] George-VB opened issue #11470: [Bug]: Group is hidden when the last build vehicle in group is hidden
12:05:33 <merni> Weird
12:14:14 <talltyler> rau117: If Real-Time mode is off, everything stays the same. If it’s on, payment graph and timetables are in seconds.
12:51:51 <peter1138[d]> 🎵 Standing on the top of the Hoover dam
12:52:13 <peter1138[d]> That was a bit damp
12:54:15 <peter1138[d]> Pretty sure #11470 is intentional
13:07:46 <brickblock19280> I find it unintuitive
13:17:34 <merni> peter1138[d]: Why?
13:18:04 <merni> How does hiding one variant mean you want to hide all others?
13:20:43 <peter1138[d]> It doesn't, but hiding last built == hiding the entry at the top, and therefore the children of it.
13:21:35 <merni> > hiding last built == hiding the entry at the top
13:21:35 <merni> this is what seems weird to me
13:21:53 <locosage> because variant groups aren't really groups
13:21:53 <merni> yes, clicking the entry at the top builds the last built variant
13:21:57 <locosage> just some weird hierarchy
13:22:13 <merni> merni: but that doesn't to me imply that hiding should work like that
13:22:31 <merni> locosage: yes, they do feel a bit kludge-y in the code
13:25:58 <peter1138[d]> It's a hierarchy, not really groups.
13:27:03 <peter1138[d]> Groups wouldn't allow multiple nesting
13:28:48 <locosage> you mean multiple levels of nesting?
13:29:02 <locosage> it's just a question of terminology, call them folders or smth if you wish
13:29:36 <merni> Whatever they are I still don't understand how the behaviour described in 11470 is intuitive
13:29:38 <locosage> rn problem is that vehicle and group are the same thing
13:29:51 <locosage> it's as if folders and files were the same in file system
13:29:55 <peter1138[d]> I haven't read the issue, only the title
13:31:03 <merni> locosage: They kind of are in some file systems :p
13:31:16 <merni> where a directory is a kind of file
13:31:16 <peter1138[d]> The design is a hierarchy, with patents and children. NOT a directory/folder structure.
13:31:26 <peter1138[d]> Parents...
13:31:33 <merni> All right
13:31:46 *** sissyrora0_0 has joined #openttd
13:31:46 <sissyrora0_0> Trading my spider tv for 4 mythic or good offer
13:31:49 <merni> But how does that imply that hiding a child should hide the parents
13:32:04 <merni> sissyrora0_0: In what way is this related to OpenTTD
13:32:07 <peter1138[d]> What's a spider tv
13:32:23 <merni> A television with a spider on it?
13:32:41 *** Mensh123 has joined #openttd
13:32:46 *** Mensh123 has left #openttd (Auf Wiedersehen)
13:32:47 <locosage> merni: because what looks like a child is actually a parent xD
13:33:12 <peter1138[d]> merni: If that's what happens then that's probably wrong, but 'last built' implies it has become the parent, visually.
13:33:50 <merni> peter1138[d]: It's simultaneously a parent and a child
13:34:16 <locosage> visually a parent but logically a child
13:35:28 <peter1138[d]> And the reason it becomes the parent is so that you don't have to keep the hierarchy open to keep building the same type.
13:36:30 <peter1138[d]> Ill be at my pc later so will probably actually read the issue text then :p
13:37:13 <merni> I think the issue is xUSSR is trying to represent a folder-ish structure, and to that end they use a dummy (un-buildable) vehicle with the "folder" name that is the "visual parent" by default. When a vehicle is built, that vehicle becomes the "visual parent" even though the "folder" name is also displayed
13:37:56 <merni> You can see that the group name becomes "N Series >>> N0 (2-6-0) (Steam)" after building, instead of just "N Series"
13:38:35 <merni> georgevb: , could you please attach a test GRF in the issue? Or is the issue present with the version of xUSSR set on Bananas?
13:52:07 <DorpsGek> [OpenTTD/OpenTTD] ldpl commented on issue #11470: [Bug]: Group is hidden when the last build vehicle in group is hidden
14:03:05 <alfagamma7> pickpacket: too damn cold
14:54:23 <pickpacket> alfagamma7: nah. Only if you aren’t dressed for it. Like I wasn’t last night biking home from office party in -14C
14:55:16 <pickpacket> Looks like next week is going to be around -10 to -4.
14:55:26 <alfagamma7> pickpacket: Well it's definitely cold for someone living in tropical climate
14:55:35 <alfagamma7> me for example
14:57:57 <alfagamma7> but your point stands
14:59:06 <DorpsGek> [OpenTTD/OpenTTD] George-VB commented on issue #11470: [Bug]: Group is hidden when the last build vehicle in group is hidden
15:15:55 *** virtualrandomnumber has joined #openttd
15:18:07 *** tokai has joined #openttd
15:18:07 *** ChanServ sets mode: +v tokai
15:22:38 *** virtualrandomnumber has quit IRC (Quit: virtualrandomnumber)
15:47:13 *** ahyangyi has quit IRC (Quit: User went offline on Discord a while ago)
16:58:03 *** gebik4544 has joined #openttd
16:58:03 <gebik4544>
16:58:03 <gebik4544> is this even meant to be like this?
16:58:34 <gebik4544> rails on road bridge sprite
16:59:18 <peter1138> No.
16:59:28 <peter1138> The bridge sprite is meant to be generic transport-type-less.
17:00:12 <peter1138[d]>
17:00:28 <peter1138> But we don't control what graphics 3rd-parties put in.
17:03:52 <gebik4544> Thats OpenGFX
17:04:12 <peter1138> Technically...
17:04:54 <peter1138> OpenGFX2 fixes this, you could use that.
17:04:54 <gebik4544> I meant the baseset this is from is OpenGFX...
17:05:35 <gebik4544> I use that now, this is a vanilla test due to something else I found...
17:05:35 <peter1138> I know what you meant. OpenGFX was 3rdparty, but kind of adopted to keep it all together.
17:06:27 <peter1138> Maybe OpenGFX2 could become the default bootstrap download / Steam install, instead of OpenGFX, eventually.
17:08:45 *** gelignite has joined #openttd
17:11:25 <talltyler> When it’s done, I would absolutely support that
17:13:12 <locosage> technically openttd could split them into separate sprites
17:13:19 <locosage> and use old one if those are not defined
17:13:48 <gebik4544> and what about the config grf?
17:14:13 <peter1138> Not needed any more.
17:14:45 <peter1138[d]>
17:16:27 <gebik4544>
17:16:27 <gebik4544> Also this sprite sorting bug is funky: (also in the OGFX2 just not as obvious)
17:16:44 <gebik4544> So I assume its game then?
17:17:01 <gebik4544> peter1138[d]: nice cannot wait
17:17:32 <peter1138> Sprite sorting is because certain combinations of 2D sprites simply cannot be sorted properly.
17:18:39 <peter1138> It's a 2D sprite representing a 3D object, where various parts of the same sprite should go both in front of and behind another sprite.
17:18:58 <locosage> Hm, do I understand it right that in industry property 0A xofs and yofs can use any uint8 (int8 for special check) values in xofs and yofs but not (0, 0x80) pair and not xofs 0xFE in the first element of a layout?
17:19:06 <peter1138> I've tried, it's possible to fix some cases, but you end up breaking others.
17:19:45 <locosage> like, 0xFF seems to be allowed but 0xFE has special meaning 😵‍💫
17:21:28 <peter1138> x = 0 y = 0x80 is a terminator.
17:22:48 <locosage> yeah, so layout can't use it
17:22:55 <locosage> but x=1 y=0x80 seems fine
17:23:24 <peter1138> Sure, but nobody expected anyone to create an industry layout that is that large.
17:23:59 <peter1138> Might have a few placement issues.
17:25:09 <locosage> yeah, but kinda weird to have special values in the middle of allowed range :p
17:25:11 <peter1138> x=1 y=0x80 isn't the terminator, so... it won't terminate it.
17:25:37 <locosage> I'm writing python classes for layouts and checks are looking quite ridiculous xD
17:26:27 <peter1138> It's a signed 8 bit value, so 0x80 is INT8_MIN.
17:26:36 <peter1138> That isn't "in the middle"
17:26:54 <locosage> nah, afaict it's unsigned unless gfx is 0xff
17:27:48 <peter1138> Right but gfx is loaded after.
17:28:33 <peter1138> Doesn't make sense to use a different terminator based on signedness controlled by a later value.
17:32:32 <peter1138> (And it's also very old TTDPatch spec, so not our fault if you think it doesn't make sense)
19:20:22 *** Tirili has joined #openttd
19:44:48 *** virtualrandomnumber has joined #openttd
19:45:09 *** virtualrandomnumber has quit IRC ()
20:00:57 <peter1138> Hmm
20:02:43 <peter1138> The "start new server" window is a bit odd.
21:03:54 <peter1138> I wonder if frosch remembers something written 11 years ago :D
21:31:35 <DorpsGek> [OpenTTD/OpenTTD] PeterN opened pull request #11471: Fix: Extra space allocated to container-within-container may not get allocated to children.
21:38:21 <DorpsGek> [OpenTTD/OpenTTD] PeterN commented on pull request #11471: Fix: Extra space allocated to container-within-container may not get allocated to children.
22:04:50 *** gelignite has quit IRC (Quit: Stay safe!)
22:33:23 *** Wormnest has joined #openttd
22:57:24 *** nielsm has quit IRC (Ping timeout: 480 seconds)
23:06:19 *** keikoz has quit IRC (Ping timeout: 480 seconds)
23:52:48 *** Tirili has quit IRC (Quit: Leaving)