> valid values of the anisotropic setting in the core.ini are powers
> of 2: 1, 2, 4, 8, 16, 32, etc. I don't actually know how that 14 got
> into the example in the readme! :) The code takes whatever value
> crazy users enter and rounds it down to the nearest power of 2, so
> 14 is actually being passed to the driver as 8, which is 3 levels of
> anisotropy.
> > Hi Dave,
> > I'd play a little with the Anisotrophy, and also make sure it's enabled
in
> > the graphics card driver (use Rivatuner 9.0 if you're using the 23.xx
> > drivers). Too much Aniso can look squishy.
> > In the driver, the medium setting (4x) is IMHO the best compromise.
Within
> > core.ini, I'm not sure a value of 14 make sense (but it could, I'm just
not
> > sure). The driver uses something like 0, 1, 2, 3 (or at least it did up
> > until 22.xx, I forgot whether they changed that to one of these cryptic
D3D_
> > ones in 23.xx, as together with changing the name they seem to have
changed
> > the values for some of these params) for the different levels, so I am
not
> > sure that a value of 14 is recognized. OTOH, I think 14 dec = 1110
binary,
> > so maybe depending on how this parameter is passed to the driver, this
is
> > precisely how it should be passed. I just don't know. But experiment a
> > little with it, that's my suggestion :-)
> > As for other suggestions, I'd certainly like to suggest more, but
there's
> > quite a lot you can try for speed or quality. There's a lot you can try.
Tom
> > Pabst I think knows a lot about this, maybe he'd care to share.
> > Achim
> > > What a difference with the LOD set to -0.5. I had mine set to -75. I
have
> > > anisotropic filtering set to 14. Any more suggestions Joachim? One
> > > improvement deserves another :o)))
> > > DC
> > > > Ok thanks Joachim. I have been problem free but will experiment a
bit
> > > > today.
> > > > DC
> > > > > Hi Dave,
> > > > > in GPL D3D, it can be adjusted both in the Nvidia driver and in
> > core.ini
> > > > > Achim
> > > > > > JT..is that in the core.ini or a nvidida tweaker?
> > > > > > Sincerely,
> > > > > > DC
> > > > > > > Hi Wayne,
> > > > > > > I'd try the Asus 21.81 or the Nvidia 23.11. The latter ones
should
> > > > even
> > > > > > > improve image quality. The 21.81_a_ felt a little shaky here
as
> > > well.
> > > > > > Don't
> > > > > > > forget to set the LOD bias to -0.5 now if you didn't have this
> > > setting
> > > > > so
> > > > > > > far. And enable Anisotrophy, preferrably neither the lowest
nor
> > the
> > > > > > highest
> > > > > > > settings. The ones in the middle are the best compromise.
> > > > > > > I also wouldn't use the VIA IDE drivers. Like for Willard, for
me
> > > the
> > > > > disk
> > > > > > > drivers that come with Windows have always been faster and
more
> > > stable
> > > > > > than
> > > > > > > the VIA drivers. Strange but true.
> > > > > > > Achim
> > > > > > > > Just put together a new system with AMD XP1800+, Asus V8200
> > TI-500
> > > > > video
> > > > > > > > card and Soundblaster Live 5.1 sound card. Seems to work
> > perfectly
> > > > > > except
> > > > > > > > that occasionally it will lock up in GPL. This happens after
I
> > > stop
> > > > on
> > > > > > the
> > > > > > > > track and hit ESC to go back to the chat/VCR/setup/etc.
screen.
> > > > > Doesn't
> > > > > > > > happen all the time but has happened a couple of times now
and
> > I'd
> > > > > like
> > > > > > to
> > > > > > > > figure out what's causing it. It also doesn't seem to matter
how
> > > > long
> > > > > > I've
> > > > > > > > been racing or how long the computer has been running or
> > anything
> > > > like
> > > > > > > that.
> > > > > > > > It appears to be random. I've loaded the latest VIA 4-in-1
> > drivers
> > > > > > (4.37)
> > > > > > > > and am running Asus drivers 21.81a. The motherboard is an
EPOX
> > > 8KHA+
> > > > > > with
> > > > > > > > 512MB of PC2100 Crucial DDRAM. The OS is Windows 98.
> > > > > > > > Any ideas?
> > > > > > > > Thanks,
> > > > > > > > Wayne Hutchison
