IRC log for #bzflag-chat on 20120118

01:04.18*** join/#bzflag-chat chris_pcguy (~chris.pcg@mclean.tunnelr.com)
01:05.16chris_pcguyhi, I like to know if the checkered background in the main-menu is intended? :-)
01:06.44blast007that would be a graphical setting/issue on your end
01:06.57blast007perhaps you have blending disabled in the graphics settings?
01:07.14chris_pcguyyap, I have.
01:07.58chris_pcguyWith the mesa i915 classic, the main-menu's background is checkered. (tested with blending disabled)
01:08.11blast007what if you enable blending?
01:08.24chris_pcguyhold on, please.
01:08.39blast007most of our lower settings are targeted at software rendering and will run slower on hardware acceleration
01:09.08blast007so on my Intel 855, I run with most of the settings turned up (just with a really low resolution)
01:09.15chris_pcguywith and w/o it's checkered.
01:09.45chris_pcguywith i915g gallium, there's no weapon light if blending is disabled.
01:10.25chris_pcguyshort. no bullet to see.
01:10.49blast007not sure
01:11.09chris_pcguyon GMA3150, Intel Atom N450.
01:11.19blast007I haven't tried running with an intel graphics chip on linux in quite a while.  Using Windows XP here.
01:11.33chris_pcguythat won't happen with classic.
01:12.02chris_pcguybefore anyone asks, I know that this is a mesa issue.
01:12.38blast007it's just possible that it won't work too well on that chipset
01:13.46chris_pcguyI really haven't any idea why they just test mesa with really huge games, but not with rather simpler games, as bzflag.
01:14.04blast007well, the graphics code on bzflag is rather old
01:14.24blast007so perhaps we use some OpenGL calls that are not common anymore :)
01:15.24chris_pcguyI rather meant that they should fix bugs which happen on simpler games, first. ;-)
01:17.19chris_pcguythanks for the hint.
01:18.26chris_pcguyare they in a single file or spreaded over the whole game?
01:18.41blast007they're all over the place
01:19.06blast007mixed in with everything else ;)
01:19.57chris_pcguyI think, it would be easier to maintain to put them in an wrapper, which should be in a new file.
01:20.03chris_pcguywhat do you think about that?
01:20.50chris_pcguyand mark them e.g. with deprecated.
01:22.21blast007easier said than done
01:23.57chris_pcguygood to know. for sure a downside will be that there's no support for old machines if removing the code, but you could use macros then.
01:25.01chris_pcguythe next downside would be you need to make an extra build for old machines. :-(
01:25.43blast007if we refactor the code enough that we require higher specs, we'd just drop support for older computers completely
01:26.44chris_pcguynot that you would need an 4 Ghz cpu for bzflag in around 10 years. ;-)
01:26.58blast007BZFlag won't be around in 10 years :)
01:28.07blast007version 2.4.2 will likely be our last release
01:28.58chris_pcguyoh, that's what you meant. (Unfortunately, I'm an austrian. So not a native english speaker. :-( )
01:29.35chris_pcguythat bad to hear.
01:31.29chris_pcguyso what's with your roadmap plan of 5.0?
01:31.48chris_pcguy*which is going to 5.0?
01:32.14blast007wishful thinking ;)
01:32.59chris_pcguyor in other words: too few developers.
01:39.25blast007too few developers that want to work on it, at least
01:39.45blast007and a lack of solid managment
01:39.50blast007management*
01:41.38chris_pcguyI think it's better for me to write patches for mesa first, as it wouldn't be good when I need to check everytime if it's an mesa or bzflag bug first.
01:44.51chris_pcguyso thank you for the nice conversation. I'll wish you a nice evening. :-)
05:50.31allejoawww no BZ 5.0????? I was going to start working on a map for that :'(
14:32.59*** join/#bzflag-chat spldart (~spldart2@c-98-201-137-215.hsd1.tx.comcast.net)
14:32.59*** join/#bzflag-chat spldart (~spldart2@bzflag/contributor/spldart)
14:46.29*** join/#bzflag-chat DTRemenak (~DTRemenak@about/essy/CrazyCoder/DTRemenak)
15:38.06*** join/#bzflag-chat meeba (~lamer@c-75-71-83-2.hsd1.co.comcast.net)

Generated by irclog2html.pl Modified by Tim Riker to work with infobot.