Times are UTC Toggle Colours
05:13:55 *** Supercheese has quit IRC 05:14:26 *** Supercheese has joined #openttd.dev 05:14:26 *** ChanServ sets mode: +v Supercheese 05:58:10 *** Supercheese has quit IRC 06:04:57 *** Supercheese has joined #openttd.dev 06:04:57 *** ChanServ sets mode: +v Supercheese 07:47:38 *** Alberth has joined #openttd.dev 07:47:39 *** ChanServ sets mode: +v Alberth 08:17:05 *** Supercheese has quit IRC 09:46:34 <fonsinchen> What do you think of http://www.tt-forums.net/viewtopic.php?f=33&t=41992&p=1118368#p1118368 ? 10:18:28 <Alberth> seems like a nice step towards yacd-like behavior 10:23:17 <Alberth> cheating is likely to happen, either intentionally or accidentally, I think 10:24:16 <Alberth> perhaps first publish the patch at the forum or in a private repository or so, to get experience with it? 10:26:19 *** frosch123 has joined #openttd.dev 10:26:19 *** ChanServ sets mode: +v frosch123 10:29:14 <fonsinchen> I will 12:02:39 <fonsinchen> https://github.com/ulfhermann/openttd/commit/efab8848977fb1bbffa0ded912b1ba8981741dd7.diff 12:03:37 <fonsinchen> This implements it. I don't know if that's actually the right thing to do. If you have stupid network no amount of cargo reduction will make it better. However, as cargo reduction seems to work for some people ... 12:31:35 <frosch123> does any of the helptexts already use the term "link graph"? 12:31:55 <frosch123> otherwise i would suggest to use a more generic term, like "network spread" or something 12:32:06 <frosch123> or network size 12:33:22 <frosch123> we still do not put a "period" at the end of strings, do we? 12:35:08 <frosch123> + if (lg != NULL) (*lg)[ge.node].UpdateSupply(amount); <- somehow that line got an additional " " 12:36:32 <frosch123> + _settings_game.linkgraph.bonus_supply * (lg != NULL ? lg->Size() : 0) / <- shouldn't that be "1" in case of lg == NULL ? 12:37:26 <frosch123> hmm, i guess 0 is fine 12:38:29 <frosch123> if people like it, i guess there should be some indication in the station gui about the network rating or something 12:38:57 <frosch123> the cargo rating no longer tells on its own how good the station is 12:39:07 <frosch123> but not important now :) 14:40:45 <frosch123> http://devs.openttd.org/~frosch/diffs/8bppsupport.diff <- add a new dropdown to game options to select support for 8bpp modes 14:40:56 <frosch123> values are "no support", "OS support" and "hardware support" 14:41:09 <frosch123> "no support" forces an 32bpp blitter and thus a 32bpp video mode 14:41:48 <frosch123> "OS support" allows 8bpp screen surfaces, but disallows switching to 8bpp fullscreen in windows, resp. using hardware palette for sdl 14:42:01 <frosch123> "hardware support" allows everything 14:42:22 <frosch123> the default value is "OS support" which differs from "current" default, which would be "hardware support" 14:43:13 <frosch123> to simplify settings it removes some exotic combinations which may have been configured previously via config file (such as setting fullscreen_bpp to 16 or 24 for win32) 14:43:50 <frosch123> but i doubt anyone used those, since they would have failed for 32bpp blitters anyway 14:46:48 <frosch123> (also, hardware which supports 16 and 24 bit modes, likely also supports 8 bit :) ) 14:49:39 <frosch123> http://devs.openttd.org/~frosch/8bppsupport.png <- screenshot 14:56:49 *** ChanServ sets mode: +v Rubidium 14:57:02 * Rubidium wonders whether noobs will have a clue about what the setting means 14:57:59 <frosch123> well, they will select "hardware support", since it sounds best :) 14:59:29 <Rubidium> maybe it's better hidden away somewhere under the expert settings 14:59:44 <Rubidium> likewise with the screenshot format; it's generally "correct" 15:00:22 <Rubidium> though the latter is something that definitely isn't part of this patch 15:00:41 <Rubidium> especially since you can explain the differences better in the advanced settings window 15:16:04 <frosch123> well, "try all settings" should still work 15:18:56 <LordAro> Rubidium: i don't have much of an idea of what that setting is either ;) 15:19:06 <LordAro> i wonder if it should be hidden away entirely 15:19:40 <frosch123> then you have to make "no support" the default :) 15:21:03 <LordAro> maybe 17:22:39 <michi_cc> frosch123: The wording of the options seems somewhat misleading to me. Reading just the strings I'd think this is OTTD telling me what my computer/hardware can do, and not something I tell OTTD. 17:36:04 <frosch123> i start to like arolards suggestion, changing the default, and making it config only 17:36:15 <frosch123> then people can be happy if they optimise their ottd experience :p 17:45:14 *** DorpsGek changes topic to "OpenTTD Dev Channel || Latest SVN: r26478 || Logs: http://webster.openttdcoop.org/?channel=openttd.dev || Voice (talk-right) upon request via #openttd; make sure you are registered to NickServ before asking" 17:51:31 *** Supercheese has joined #openttd.dev 17:51:31 *** ChanServ sets mode: +v Supercheese 18:31:07 *** DorpsGek changes topic to "OpenTTD Dev Channel || Latest SVN: r26479 || Logs: http://webster.openttdcoop.org/?channel=openttd.dev || Voice (talk-right) upon request via #openttd; make sure you are registered to NickServ before asking" 18:34:34 <LordAro> michi_cc: did you see my newmap rebase? 18:35:12 *** DorpsGek changes topic to "OpenTTD Dev Channel || Latest SVN: r26480 || Logs: http://webster.openttdcoop.org/?channel=openttd.dev || Voice (talk-right) upon request via #openttd; make sure you are registered to NickServ before asking" 18:36:12 <michi_cc> LordAro: Yes, but somehow it didn't come with extra free time :p 18:36:19 <LordAro> michi_cc: aw :P 18:36:50 <michi_cc> Anyway, rebasing isn't the problem, finishing it is. 19:00:30 <LordAro> well, true 19:00:39 <LordAro> but i thought it might encourage you ;) 19:07:02 *** Supercheese has quit IRC 19:53:32 *** Alberth has left #openttd.dev 20:41:54 *** frosch123 has quit IRC