1  |   Order by index

Feb 20, 1999, 8:07am

Me and my friends will never be interested in it until then.
8 frames per second software mode primitive lousy old outdated unsupported
engine running like crap on our fast machines.

GET A CLUE, THIS IS 1999!

If you want more people using AW, make it worth it. Also $10.00 a year is
ok. NOT $20.00!
IMO.

If it ran and looked better then maybe.
And I would like to see the code for MMX optimizations, if they are there
they do nothing.

Theres one guys opinion.

Feb 20, 1999, 11:26am

Aw runs just fine on mine. Using a Viper v550 and screen rez of 1280x1024 as
large as I can get the window it yields an average of 32.5 fps using the 3D
drivers. And that's in fairly heavy built areas. 32.5 FPS may not seem like
much compared to quake running at about 70 but it's a hell of alot better
then 8. AW needs some work yes but try upgrading your system before blaming
the software :)



[View Quote]

Feb 20, 1999, 3:08pm

You are one of the lucky few Dude.
I have a Creative TNT and a Voodoo2 and I cannot get the thing to run in D3D
at all.
Last Driver update was in 1997. And why D3D? That sucks.
It makes most people sick chopping around in AW, watching it lock up for a
few seconds every time you are moving. That is squinting in a little window
to get half decent FPS while looking 40' away waiting for it to slowly load.
In Tribes I get 60 FPS and can see over 400' away full screen!
AW needs not "some" work, it needs an overhaul!
Start with getting rid of the dead engine, or do some real work on it for
the 1st time in 4 years other than more idiot lights.

OH, and does AW have a memory leak or something, longer you use it, choppier
it gets.
Sucks.
I'm done now, I will check back in 3 years to see if it has changed.



[View Quote]

Feb 20, 1999, 6:37pm

[View Quote] > You are one of the lucky few Dude.
> I have a Creative TNT and a Voodoo2 and I cannot get the thing to run in D3D
> at all.
> Last Driver update was in 1997. And why D3D? That sucks.
> It makes most people sick chopping around in AW, watching it lock up for a
> few seconds every time you are moving. That is squinting in a little window
> to get half decent FPS while looking 40' away waiting for it to slowly load.
> In Tribes I get 60 FPS and can see over 400' away full screen!
> AW needs not "some" work, it needs an overhaul!
> Start with getting rid of the dead engine, or do some real work on it for
> the 1st time in 4 years other than more idiot lights.

Ohhhh - so you know it since 4 years????

>
>
> OH, and does AW have a memory leak or something, longer you use it, choppier
> it gets.
> Sucks.
> I'm done now, I will check back in 3 years to see if it has changed.
>

Bye bye!!


Andras

Feb 20, 1999, 10:12pm

And what kind of machine are you on, a P2/450?

[View Quote] > Aw runs just fine on mine. Using a Viper v550 and screen rez of 1280x1024 as large as I can get the window it yields an average of 32.5 fps using the 3D drivers. And that's in fairly heavy built areas. 32.5 FPS may not seem like much compared to quake running at about 70 but it's a hell of alot better then 8. AW needs some work yes but try upgrading your system before blaming
> the software :)

And the software IS shit compared to most 3D games that run JUST fine on older, piece-of-shit systems like all the Tomb Raiders run much better on my AMD-K5-PR133AR (99MHz) than AW does.

Feb 21, 1999, 3:09am

It's a P2 400
But actually even thou Tomb Raider shits and gets on this thing in Hardware
mode if you try to play it using software only Aw for some reason seems to
be faster. Go figure :)
Of course dropping the screen rez down to 800x600 makes a world of
difference in both instances but not very detailed on a large monitor.

[View Quote]

1  |   Order by index