since I'm still stuck on this laptop without hw acceleration I'm trying to get vendetta playable with mesa :D

I've set all settings in the game and the config file to minimum.

tried to limit the number of textures to be displayed a once (or whatever that was) texturesize and a few other things in mesa, which the game didn't handle well, suddenly all textures disappeared :D

somehow I even managed to make rocks appear only when I'm like 100m away .. which is scary :D

now the game looks some old dos shooter ... but I still can't get above 7fps in open space :/


so .. da questions :D:

whats the minimum opengl version requiered and would any of those "limited" opengl implementations work, like minigl, tinygl?

Is there a command or something to disable that "software cursor"? At 5 fps it's very anoying :(

can I disable the use of ogl extensions?

and finally is there a command to remove all or better most textures? when all were gone it was very fast :D ... but unusable because the text disappeared too.

thanks for any answers. :)

Reroute the text to a speech synthesizer. That way you won't need to see text.

nah wouldn't work .. for one EVERY texture was gone ... the menues were just a loads of colored rectangles :D ... and the synth would probably eat more cpu cycles than the text.

I could aswell just do a "tail -f error.log" in an xterm ... isn't even that bad of an idea :D

some render oddity :D
http://home.arcor.de/famscheffler/ven/dump0000.jpg

a few meters forward ...
http://home.arcor.de/famscheffler/ven/dump0001.jpg

looks like my tweaking of mesa made it only load the higher lod('s) or sth like that ... I don't really know much about that 3d stuff i'm just fooling around :D

This game requires hardware acceleration. You can't run tuxracer with mesa, why would you expect to run Vendetta?

Oh ... I can, but not very fast. :P

I don't expect the game to be fully playable with software (heck .. i'm playing with keyboard and touchpad I can't do much more than turn into the general direction of where i want to go and fly in a straight line)

I jwant to push the game and mesa as near as possible to playability and I just love messing with stuff. :D

The biggest hurdle is that the game seems to use quite large textures. They slow everything down to a crawl. :/

Yeah you can set textureresolution to 5 i think.
That should minimize the amount of texturememory

you probably want to try these too:
dovertexbuffers=
doindexbuffers=0
do_compiled_vertex_array=1
do_env_combine=0
do_extensions=0
texturequality=16
illummap=0
envmap=0
bumpmap=0
minfilter=9984 or 9728
maxfilter=9728

I don't recall if do_extensions overrides do_compiled_vertex_array though.

lowest resolution possible is good too.

We do a lot of alpha blending which probably slows down the menus.

Set these in your wgaf.cfg file:
set rHiRezBK "0"
set rDoEffects "1" (setting this to 0 will prevent you from seeing some lasers)
set rDoSpaceJunk "0"

and set your LOD values to maximum numbers (lowest quality)

You probably already did most of that though.

wow thanks .. got it up to around 18 fps at 512x384 sometimes even higher. It would be quite playable now if I had a usb mouse or joystick ... stupid laptop X(

I still had bilinear mipmap filtering enabled

and I had textureresolution set to 1 once thinking that lower values meant lower quality with the result that the game suddenly ate all my memory ... the game took half of my running apps down when it crashed .. wowsie :D that explains it

is it always like that: higher values == lower quality? for scene detail too?


Oh and vendetta doesn't run with tinyGL ... no surprise actually, even glxgears looked funky :D ... probably uses some functions that aren't implemented or something

hmm, i never thought about the numbers. some go up and others go down. But I suppose most of the speed-centric settings go up for lower quality. It's not definitely not a convention though. It just happens to be the way the numbers are used in the equations.

silly ray and his overly-confuzzling interfaces...

Just be glad that none of Kalle's code touches the user interface at all.