On 4/23/09, Christian Ohm <[email protected]> wrote: > On Thursday, 23 April 2009 at 20:00, Zarel wrote: > > 2009/4/23 Christian Ohm <[email protected]>: > > > - Change the font to DejaVu Sans: monospaced fonts are quite ugly imo, > and > > > there's no need for it, OSX even uses a proportional font already. > > Agreed, although I'm not a big fan of DejaVu Sans, either. I preferred > > the old bitmap font... The problem is that most of the free fonts out > > there look pretty ugly (I don't think very many typographers are OSS > > type people). > > > I don't like it much, either. But this was possible by deleting 18 bytes, > and its NOT MONOSPACE, which changes the look from ugly to ok (I hope we can > agree on that, except perhaps the person who chose the mono font). That's > enough for me (until we find a good free sans serif font we can all agree > upon).
For now, the change seems better to me. > > By the way, when can we fix the problem of Warzone attempting to scan > > the entire Windows font directory on startup? It's causing start-up > > take as long as half an hour on some computers. > > > I think that's fontconfig's doing. I don't know how that works on Windows, > but it should be possible to use a private font directory (but then you don't > have fallback fonts, and the included font(s) have to provide all needed > glyphs). > I am not sure it is fontconfig, freetype, or QuesoGLC. I just know that I can't duplicate it, and I don't have vista to really see what lib is responsible. I just know that we don't do anything wrong in the codebase, so the problem should be reported upstream. To who, I dunno, but the above listed ones are prime suspects. > > > - Coloured cursors on: Comments in the code say it has a performance > hit, but > > > there's a config option to disable them (and shadows also have a cost > and are > > > enabled by default). > > But it's a severe performance hit. > > > Really? I enabled them and noticed nothing. Haven't played much since then > though, only short testing. I don't have a problem with them either. This is both on XP & linux. > > The question is, do we leave fancy new features off and if people discover > the > options they can enable them for themselves, or do we enable them, and they > can > disable them if they don't like it? Imo the second option is better (and by > that logic, I should support leaving the rotating radar on), perhaps with a > poll in the forums. I think all the defaults should be set to the lowest or reasonable default values to make the game playable on the widest selection of hardware. We have way too many low end hardware users. > > Trap Cursor should be on by default. > > Not for me, or do we have an untrap cursor hotkey (the trap cursor workaround > being alt-enter)? > Ack! no, that should be off. It is a *huge* PITA to debug anything if the cursor is frozen in the window, and you can get out of it. > > Texture resolution should be 2048 by default. 2.2 should keep the texture > > resolution setting at 2048 regardless of whether or not it supports that > > high. That way, I don't have to change the texture resolution back up each > > time I play trunk. Again, no, that is way too big. 128 or 256 should be default. > > > How about changing the config directory for trunk to .warzone2100-trunk > instead? Instead of 2.2? The only problem with that is, that once it is set to -trunk, then we can't really force a config overwrite. _______________________________________________ Warzone-dev mailing list [email protected] https://mail.gna.org/listinfo/warzone-dev
