Hi everyone,

I was trying to watch a demo to test the 3D card for the first time,
and to my consternation I get a "No suitable driver found". When I've
tried another demo, it tells me that it can't open the 3D hard...

I've installed the 3D update (though it was already installed), and I
get the same!

I have a Radeon 9250 with 128MB, which is recognized as a Radeon 9200
PRO by MOS (weird, right?).

On the other hand, I've tried two games that suppossedly use 3D: Mures
and Fly, and both run very nicely!

I've tried APoolGL and it says that it can't open opengl in a window
context. Foobillards works fine, in a seemingly high res, as long as
I do not try to change the resolution (I get a black screen, where the
only thing I can see is the mouse pointer, and trashed my partition).

So the question is, how can I REALLY know whether 3D is working or
not (guarantee issues, if it comes to that)??

hi!

i've got the same problem here: i've got 3D Update installed on Mos 1.4.5 but unabel to run several 3D games with "unable to open screen" or "no driver" errors...

i can run some 3D games but all in software render.

this is a pegII with voodoo3 agp.

i am also do not know that the HW 3D is working on my peg or not...

Some games must be run from a 16bit Ambient (not 24bit).

Thats wrong i run all my Games from a 24/32Bit Ambient.

But you have a Radeon and he has a Voodoo3 which can only do hardware 3D in 16bpp.
So Daff is right: a 16bpp desktop could help.


[ Edited by Henes on 2006/1/10 12:31 ]

Hi,

If you are using window mode *and* a Voodoo, Ambient has to be set to 16bit mode.
Radeon doesn't have this limitation.


Bye HAK

Quote:
Voodoo3 doesn't support hardware accelerated rendering in 24 and 32bit. So some games must be started from 15 or 16bit Ambient screen to work, on a Voodoo3.

sadddam: Remember what was the cause of your problems last time? Replace the cable...

@HAK

Not only in window mode.
If something clones the wb screen modeid and tries to do hw 3d on it, then you must have a 16bpp wb or it will fail on a voodoo3.

Quote:
@ThePlayer: Is your Radeon 9250 recognized as such by MOS?

@All: I see that you have some ideas about the where the problem could originate witha voodoo3, but has anyone got any clue as to my problem with a Radeon???

[ Edited by winterhunter on 2006/1/10 12:45 ]

thx for all!

chain: yup, i remember:) user error detected:)

If you have Voodoo 3 and you have 16bit ambient screen, some 3D-accekerated programs/games still want a 24bit screen. Only way to fix this is to edit the sources.

Also one version of tinygl opened always 32bit screen (on which 3D wouldn't work, if you have a Voodoo board) - That problem was fixed very quickly. Well, might be better to update tinygl anyway, if you have old version

I've tried 16 bit ambient, tried to change the resolution, etc, and it still hangs.

I've compiled the tinygl examples, and none of them work ("Failed to open Glut window").

However some programs that use 3D (like MangoQuest) run without problems, and the textures don't look "pixelized", so there must be a sign that mipmapping is working...

I will try with another card...

before launching first tinygl app do:
setenv TGLDEBUG 1
avail flush

then start it, get debug (getramdebuglog if you use ramdebug)
and send it to me.

You can use FireFlies 2.06 as a good test. I also use Yellow Rose (37-38 fps avg) , FooBillard 3.0a, and Gltron.

Fireflies should have a very smooth display of the fireflies and very vibrant colors in their flight trails. The flies should fly around pretty fast. If you see any type of stuttering (or slow down) effect, you either have an issue or maybe another open Fireflies window.

If you can't run any of those programs I mentioned, your 3D is not working properly or you don't have all of the updated or correct files in place. Consult the docs!!

~K