On 11/15/2009 07:56 PM, Bruno Wolff III wrote:
On Sun, Nov 15, 2009 at 19:47:41 +0100,
Hans de Goede<j.w.r.degoede(a)hhs.nl> wrote:
> True, otoh if it aint broken don't fix it, seriously you are very welcome to do
> this, but is it worth the effort. I'm sure their are games more deserving
> like this, which are in a similar situation. What I usually do, is just keep them
> building with the latest toolchains, fixing things like compiler warnings when
I think I can use it to help test and learn ogre stuff, so I think it is a
That seems a good reason, so I would say go for it.
> I think this problem is bigger then just chess, but if you feel
> up chess and starting a fedora hosted project for it by all means, please do.
I'll contact the original developer to see if he objects to Fedora becoming
an upstream for the game (at least for linux, I am not planning on cross
compiling windows builds).
>> It looks like it tries to use some fonts that were stripped
out and fallback
>> to something else isn't happening.
> This might just be another mesa ogre conflict, all text in the game works fine
> for me (when testing on an nvidia equiped machine with their binary driver, I
> usually don't test with Intel / ATI, as in my experience that results in a 1
> per 2 - 3 seconds slideshow.
It is pretty slow on my rv280, but I can test it occasionally on an rv530.
I also have some nv28 cards that I can test stuff on from time to time.
(Currently I don't have nVidia's drivers installed so that I can test
nouveau without worrying about interference from nVidia's stuff.)
In my experience (but I have not tried recently), even my rv570 will not run
all ogre samples at acceptable speed with the foss drivers.
>> I don't think there is currently a way to change the
orge.cfg file (which
>> specifies some OpenGL configuration) once it has been set up. There may be
>> some way to access this again from inside chess, but with the fonts not
>> appearing to work, I can't tell what options are available.
> There is no easy way to change ogre.cfg after the first run, note that all
> ogre apps seem to suffer from this, so we may want to work on a more generic
> solution for this.
Are you thinking a separate set up script sort of like vegastrike does?
There already is a separate setup script (that is what you get the first time),
the problem is that every applications calls this itself and then stores the data
somewhere it would be nice to:
a) have reasonable defaults somehow, and offer the setup as an option rather then
always asking on first run
b) share ogre settings between apps