Times are UTC Toggle Colours
00:00:22 *** Leopold has quit IRC 00:01:49 *** Leopold_ has joined #openttd 00:05:44 *** andythenorth[m] has quit IRC 00:19:51 *** Leopold_ has quit IRC 00:48:34 *** Leopold_ has joined #openttd 01:20:08 <xertov> https://cdn.discordapp.com/attachments/1008473233844097104/1215831455444500581/image.png?ex=65fe2e48&is=65ebb948&hm=ba66f1ad937b7f25671ca666dcd5dbedbce7883e7fbfdbfa185d8952a2e12f55& 01:20:14 <xertov> ???????????? 01:20:21 <xertov> shouldnt it be 12 months 01:20:59 <xertov> STR_NEWS_EXCLUSIVE_RIGHTS_DESCRIPTION_MINUTES is the name of the string but i ve never heard it being for 12 minutes it sounds wrong 01:27:51 <Eddi|zuHause> we now have a setting to decouple the calendar progress from the economy grogress 01:27:55 <Eddi|zuHause> *progress 01:28:53 <Eddi|zuHause> and roughly 1 original month = 1 real time minute 01:30:19 <xertov> i see 01:30:31 <xertov> thank u 01:55:32 <wensimehrp> Could someone please tell me what is transfer credits? 01:57:15 <Eddi|zuHause> when you use transfer orders, or enable cargo distribution, money only arrives on your bank account at the final destination. but for accounting purposes, transfer credits are added to vehicles making partial trips 01:57:43 <Eddi|zuHause> it's not real money, just there so intermediate vehicles don 01:57:49 <Eddi|zuHause> 't run at a loss 02:00:47 <_glx_> final leg can make a huge loss if previous transfer were too high 02:14:22 <wensimehrp> Ah so they are fake numbers that only shows on vechicle stats. 02:14:22 <wensimehrp> I'll change the translation then, the current translation is wrong. 02:14:22 <wensimehrp> Also, what does "leg" mean? 02:14:35 <wensimehrp> (might be stupid to ask) 02:30:50 <emperorjake> Each time a cargo transfers to a different vehicle can be referred to as a new "leg" of a journey 02:36:08 <wensimehrp> Thanks 03:39:29 *** D-HUND has joined #openttd 03:43:14 *** debdog has quit IRC 03:45:01 *** gnu_jj_ has joined #openttd 03:48:12 *** gnu_jj has quit IRC 04:41:26 <DorpsGek> [OpenTTD/OpenTTD] eints-sync[bot] pushed 1 commits to master https://github.com/OpenTTD/OpenTTD/commit/ce3d0097f648d23d5628c74d05b6f9abafbd33bc 04:41:27 <DorpsGek> - Update: Translations from eints (by translators) 05:08:35 *** keikoz has joined #openttd 07:07:39 <andythenorth> can we just connect eints to GPT? 07:07:55 <andythenorth> or do we like the community-building aspect of eints? 😛 07:08:40 *** kamnet has joined #openttd 07:08:40 <kamnet> https://cdn.discordapp.com/attachments/1008473233844097104/1215919159955820544/image.png?ex=65fe7ff6&is=65ec0af6&hm=a7489350a8ce05b7376c2766f8490a88031f17ee318f8c39f18e55ba174342d4& 07:08:40 <kamnet> I've never noticed this until just now. The name of my oldest NewGRF is mangled in Bananas because the length limit. Very frustrating. 😦 07:26:48 <peter1138> andythenorth: I like the "built by an actual human" aspect of eints. 07:30:16 *** keikoz has quit IRC 07:32:53 <andythenorth> if I could get grfs from GPT 07:33:02 <andythenorth> that might be better for everyone 07:33:29 <andythenorth> by "GPT" I mean "generally magical", not specifically GPT 07:37:48 <DorpsGek> [OpenTTD/OpenTTD] PeterN updated pull request #12240: Codefix: Fully initialise `MidiFile::DataBlock` to avoid gcc warning. https://github.com/OpenTTD/OpenTTD/pull/12240 07:41:20 <DorpsGek> [OpenTTD/OpenTTD] rubidium42 approved pull request #12240: Codefix: Fully initialise `MidiFile::DataBlock` to avoid gcc warning. https://github.com/OpenTTD/OpenTTD/pull/12240#pullrequestreview-1926138662 07:42:55 *** keikoz has joined #openttd 07:46:05 <peter1138> https://cdn.discordapp.com/attachments/1008473233844097104/1215928581419700234/image.png?ex=65fe88bc&is=65ec13bc&hm=9825d7ded0db1ab7330b779cbc6ffe7088f503816bbceab07fa1358e37220a5a& 07:46:05 <peter1138> Huh 07:47:26 <peter1138> Well, time to go. 07:48:21 *** HerzogDeXtEr has joined #openttd 07:48:55 <andythenorth> I might go out 07:48:58 <andythenorth> not yet though 😛 07:49:07 <reldred> it's far too hot here to leave the house 07:56:05 *** gelignite has joined #openttd 07:58:15 <kamnet> reldred: Is it bake an egg on the tarmac hot? 07:58:37 <kamnet> dashboard cookie baking hot? 08:03:02 *** Extrems has quit IRC 08:03:16 <reldred> eh, was only around 40°C 08:04:11 *** Extrems has joined #openttd 08:10:11 <kamnet> So not even halfway to hell. Not horrible. 🙂 08:10:52 <reldred> Oh it certainly isn't pleasant. If the UK saw these temperatures people would be dying on the sidewalk. 08:11:16 <reldred> This summer so-far has been relatively tame, though March always brings out a few last minute surprises. 08:38:18 <andythenorth> Did peter1138 go out? 😛 08:38:37 <andythenorth> I need 3cc for London tube trains 😛 08:39:07 <andythenorth> https://cdn.discordapp.com/attachments/1008473233844097104/1215941931230826627/image0.jpg?ex=65fe952b&is=65ec202b&hm=7d12da4125d7485994e3de766ae35f874f1724b8f0651715932b88773d326da4& 08:46:00 <truebrain> peter1138: Huh? Indeed .. compiler bug? 08:48:12 <DorpsGek> [OpenTTD/website] michicc updated pull request #305: Add: Blog post about sausage making https://github.com/OpenTTD/website/pull/305 08:48:15 <DorpsGek> [OpenTTD/OpenTTD] 0marduk commented on discussion #12230: What exactly is "dirty" in the engine? https://github.com/OpenTTD/OpenTTD/discussions/12230 08:49:36 <DorpsGek> [OpenTTD/website] TrueBrain approved pull request #305: Add: Blog post about sausage making https://github.com/OpenTTD/website/pull/305#pullrequestreview-1926163516 08:49:39 <DorpsGek> [OpenTTD/OpenTTD] michicc commented on discussion #12230: What exactly is "dirty" in the engine? https://github.com/OpenTTD/OpenTTD/discussions/12230 08:51:31 <DorpsGek> [OpenTTD/OpenTTD] 0marduk commented on discussion #12230: What exactly is "dirty" in the engine? https://github.com/OpenTTD/OpenTTD/discussions/12230 08:52:26 <DorpsGek> [OpenTTD/website] michicc merged pull request #305: Add: Blog post about sausage making https://github.com/OpenTTD/website/pull/305 08:59:25 <truebrain> Steam done 08:59:34 <andythenorth> 🙂 08:59:40 *** Ox7C5 has joined #openttd 09:19:44 <jfs> And now after reading that sausage making post again, one remaining common question strikes me: "why can't you just add X feature from jgrpp?" 09:20:12 <jfs> But that would likely also have extended the post much further to try to answer that 09:27:11 <reldred> I think it would be good to see a explanation of exactly why a particular feature may be cash money in JGRPP but not really 'suitable' for OpenTTD. It's something that I've kinda grown to accept more as years go on and kinda implicitly understand why these days, but I think it's a subject some folks would like to see expanded upon. 09:29:08 <michi_cc> jfs: Well, the practical answer is already given: "It is not included yet because nobody volunteered their time for it." 09:29:49 <michi_cc> IMHO there are a lot of features from JGRPP that I'd like very much conceptually, but need work to make them more accessible and discoverable. 09:30:16 <andythenorth> I have 2 observations 😛 09:30:17 *** bendn has joined #openttd 09:30:18 <bendn> truebrain: i think compiler bug should be the last response, not the first 😅 09:30:33 <andythenorth> one theme is that JGRPP often says "this is not suitable for vanilla" 09:30:34 <andythenorth> 😛 09:30:50 <michi_cc> reldred: Unless you've made a PR that was rejected, there is no JGRPP feature that is not suitable. 09:31:42 <michi_cc> Not every feature might be suitable straight up, but that comes back again to the time thingy. 09:32:16 <reldred> michi_cc: Hmm, perhaps I didn't word it correctly, probably that some of the features *as they're currently implemented* aren't suitable. The acceptable level of complexity is higher in JGRPP and that shows in how some features are implemented. 09:32:29 <reldred> OpenTTD proper needs to be a lot more polished, and approachable. 09:32:39 <truebrain> bendn: We have sufficient of experience and different compilers we work with that it won't be the first , let alone the last, compiler bug we find (and report and get fixed) .. and given the information, it is not as wild of a guess as you might think 09:33:39 <reldred> And no, I've buried the hatchet. I know I threw a lot of shade about PR's not being reviewed in a timely fashion but that's long since been resolved, but yes again comes back to the time thing 09:35:39 <andythenorth> my JGRPP experience is pretty limited, but I would guess it would be easy for people to make pet pony lists of JGRPP features 09:35:55 <andythenorth> would they cohere though? 😛 09:45:17 <Rubidium> truebrain: I think bendn is technically correct; the error message seems to be coming from cppcheck, not the actual compiler. I would consider the default member initializer being missed a bug in cppcheck though 09:47:14 <_zephyris> andythenorth: A git discussion with separate sections people can up/down vote on would be great. Like 2TT's default settings one. 10:04:30 <_jgr_> _zephyris: People will vote yes for headline features even if they wouldn't fit or aren't actually implementable 10:05:47 <_jgr_> Stunning like that could lead to problems with managing expectations 10:07:36 <truebrain> Rubidium: Splitting hairs now? 😄 10:09:16 <_zephyris> _jgr_: Depends how you ask the question - but expectation management in the description would be key 10:15:31 <michi_cc> Hmm, I think we need to re-word our project goals <https://github.com/OpenTTD/OpenTTD/blob/master/CONTRIBUTING.md#project-goals>. According to that, half of OTTD 14 is in fact "not encouraged" 🙂 10:17:33 <DorpsGek> [OpenTTD/OpenTTD] TrueBrain commented on pull request #12237: Change: [CI] switch MacOS to the macos-14 runner and use arm64 for CI https://github.com/OpenTTD/OpenTTD/pull/12237#issuecomment-1986816707 10:18:33 <truebrain> michi_cc: although I fully understand those goals, personally I never felt that attached to it. Sounds like very dull to me, with little possibility for more innovation. And yeah, looking at 14.0, it seems more developers think like that 😛 10:24:30 <DorpsGek> [OpenTTD/OpenTTD] TrueBrain opened pull request #12241: Codechange: [CI] manually install vcpkg for all targets https://github.com/OpenTTD/OpenTTD/pull/12241 10:26:56 <DorpsGek> [OpenTTD/OpenTTD] TrueBrain opened pull request #12242: Codechange: [CI] switch to arm64 for MacOS builds https://github.com/OpenTTD/OpenTTD/pull/12242 10:28:30 <DorpsGek> [OpenTTD/OpenTTD] TrueBrain updated pull request #12241: Codechange: [CI] manually install vcpkg for all targets https://github.com/OpenTTD/OpenTTD/pull/12241 10:29:08 <truebrain> owh, lol, yes, 12242 is only possible after upgrading to macos-14 😄 I forgot 😛 10:31:25 <DorpsGek> [OpenTTD/OpenTTD] TrueBrain dismissed a review for pull request #12237: Change: [CI] switch MacOS to the macos-14 runner https://github.com/OpenTTD/OpenTTD/pull/12237#pullrequestreview-1925930504 10:31:28 <DorpsGek> [OpenTTD/OpenTTD] TrueBrain updated pull request #12237: Chan2024-03-09T10:38:19 <andythenorth> They were mostly from frosch iirc 22:45:51 <xarick> Game Scripts can access human companies that may have this rotated airport 22:53:43 <xarick> https://cdn.discordapp.com/attachments/1008473233844097104/1216156998031245382/Minnley_Market_Transport_0h_3m.png?ex=65ff5d77&is=65ece877&hm=a7767bc5b21f1b34921152719429acb5dd06ba995a912f49440c3ab0ee59d913& 22:53:43 <xarick> so this is possible... lol 22:56:59 <_glx_> seems most ScriptAirport functions use tile as parameter 22:57:21 <_glx_> so it's a problem in many cases 22:57:29 <_glx_> not only orders 22:59:49 <_glx_> I guess they should have precondition enforcing like ScriptAirport::RemoveAirport 23:00:38 <_glx_> but your ScriptAirport::GetTileOfAirport should probably use a stationID and not a tile as parameter 23:01:02 <xarick> the tile area seems to include holes 23:01:23 <xarick> I need to test by stationID too 23:02:06 <_glx_> yes area always include holes, it's just a (tile, width, height) 23:05:23 <_glx_> I understand why many functions work with tiles, but sometimes it seems to not be the best choice 23:06:10 <andythenorth> there's a lot of looking things up in GS 23:06:24 <andythenorth> can cache lookups, but it grows RAM quite fast 23:06:35 <andythenorth> and goes out of date WRT map 😛 23:06:39 <_glx_> for road/rail it makes sense to use tiles as they are fully modular 23:06:51 <_glx_> but airports are full blocks 23:07:11 <xarick> if (IsAirportTile(t) && !IsHangarTile(t) && ::Station::GetByTile(t)->index == st->index) return t; 23:08:21 <_glx_> for easier readability you could put each test on separate line 23:09:01 <_glx_> if (!IsAirportTile(t)) continue; 23:09:01 <_glx_> if (IsHangarTile(t)) continue; 23:09:01 <_glx_> ... 23:09:15 <xarick> ah I see 23:22:06 <truebrain> _glx_: my only worry about enabling both x64 and arm64 is that we hog up the runners even more. Those 4m could have been spend on other things too 😛 23:22:41 <truebrain> Not an issue for a single push, but if like today someone pushes 15+ PR updates at once, it matters 23:22:42 <_glx_> macos release should be a lot faster to build now 23:22:58 <truebrain> They are equally fast as before, the numbers told me 23:23:26 <truebrain> But even if they weren't, still 4m that can be spend on something else 😄 23:23:51 <truebrain> Dunno .. I see the pros and cons, still find it tricky to pick either side 😄 23:24:11 <_glx_> wondering if we should drop mingw 23:24:40 <truebrain> I have been asking that for how many years now? 😛 23:25:47 <michi_cc> Maybe at least one of the two mingws? 23:25:56 <truebrain> I was kinda hoping it would fail on C++20, but it didn't 😛 23:26:38 <_glx_> having both is like x86 and x64 with MSVC, they don't complain on the same thing 23:27:03 <truebrain> But when is the last time the MingW builds gave us any extra information? 23:27:22 <truebrain> Similar with win2019 btw .. we should honestly just stop running that 🙂 23:27:32 <_glx_> they are quite silent since I fixed the last warnings 23:27:57 <truebrain> Maybe, as compromise, we can push all these to a nightly or weekly job 23:28:06 <truebrain> Just so we know they still run 23:28:15 <_glx_> yeah should be enough 23:28:17 <truebrain> But remove them from CI 23:28:31 <truebrain> Their added value is so low .... so so low 😛 23:28:57 <truebrain> Is MSVC2019 actually still useful btw? 23:33:10 <truebrain> MinGW and MSVC2019 are good for a wopping 70m CI time, damn 23:35:56 <xarick> GSTileList_StationType this actually works correctly! 23:36:04 <xarick> I'm surprised 23:37:38 <_glx_> this list just use the full station rect 23:37:47 <_glx_> and filtering 23:40:00 *** gelignite has quit IRC 23:41:16 <truebrain> Hmm .. would we be able to run CodeQL on the macos runners? Would that be faster? 😄