On Wed, Feb 07, 2007 at 12:24:30AM +0100, Frank Gevaerts wrote: > On Tue, Feb 06, 2007 at 03:04:36PM -0800, Joshua Rodman wrote: > > I'm also quite unsure of what the balls should look like. When I > > played it (successfullly) some time ago, the balls had images on them, > > such as stripes and numbers. In this setup the balls are featureless > > colored sphers, albiet with some lighting suggestions. > > They do have some features. If you dont't see them, that seems to point > to a general texture loading problem. Do you see the "fb" logo on the > table, and a wood texture on the table borders ?
I had _imagined_ the wood texture, or I probably would have come to this conclusion sooner. In certain angles, the shading on the borders suggests a grain, at least to my tired eyes. No, there is no wood texture, no FB logo. There is nothing that says texture to me in the entire display. The cue stick is featureless gray. > At this point, I'm actually surprised that you do see the overlays in > the lower left. The ball, sometimes with numbers, sometimes with a question mark. This is normal, right? It's a whitish overlay with some transparency. The "power" bar also appears. > > I actually have two computers with a nearly identical setup, having done > > a new install with the same packagelist, followed by a hand-diff of the > > things I cared about in /etc, and a wholesale import of /usr/local, > > /home, and so forth. The major likely differences are: > > > > - The new machine uses the unproven intel i965 opengl stuff, although it > > is working fairly well in the main here (mostly there are probablems > > changing screen mode/resolution). > > > > - The new machine is "amd64". A core 2 duo, to be precise. > > > > Any thoughts on how to get more information on foobillard's bitmap > > loading behavior? > > There's the source of course. As far as I understand it, the fonts are > drawn to opengl textures, which are then displayed. I'm not too familiar > with opengl myself, so I'm not really sure where to start looking. Oh, I was assuming it was having trouble reading the files, although it may well be having trouble getting the driver to accept them. I'll set this down for now, and perhaps may dig into it later. -josh -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
