New Win2k drivers and Q3A

[Ad B]

When I try to run a demo, it runs fine until it's about to return to the menu. It hangs.

Also, when I play the game, if I try to get back to the menu, the game freezes.

!? Anyone else encountered this problem? Or have any suggestions to fix it?

Oh, 3dmark2k hangs after the first test. Plus, the DXDiags tests hang.

[noackjr]

Well, I can at least verify most of your experience. 3DMark2000 exits to the desktop after a few tests and the hardware acceleration test in DxDiag die. However, in the full version of Q3A with the Pointer Release update, I have no problems with menus and it is quite stable. I don't have any suggestions, but I am thrilled that there are no longer stability issues with my G200 and Voodoo2 cards. 3D on either was a questionable proposition before these drivers, but now both are stable.

Jon

[This message has been edited by noackjr (edited 14 February 2000).]

[PaulS]

I have 3DMark2000 exiting during the 3rd test (complex helicopter).

Paul

[Insomnis]

To those who have problem with 3Dmark.
What is your AGP aparture setting?

My problem was/is Matrox suggest 256 for TurboGL. So I set mine @ 256, this would cause 3DMark to kick me back to the desktop.
Setting it back to 64 solved the problem.

Unfortunatly now, Q3 kicks me back to the desktop after a while. But this is in Win2K with the latest ICD - so it might not be related.

[Ad B]

I've tried all AGP Aperture settings, makes no difference.

[Ad B]

I'm running AGP Switch and forcing AGP 2X, seems to have solved the probs. 3DMark is still playing up though.

Plus, when exiting Q3A, the screen goes black and shuts down!?

[dwright]

The first few times I ran 3dmark2000 with the new win2k drivers it ran the default test fine. Now it will exit to desktop about half of the time. Changes to agp size in bios does not help. It fails agp 64meg test reporting not enough agp memory. This is with the G400 max and Asus p3b-f.
On one of my other computers (my son's) the same thing happens with a viper tnt2 ultra and the latest nvida beta drivers. It could be a fault in 3dmark2000.

[noackjr]

From what I hear 3DMark2000 may have some issues with the version of DirectX that ships with Win2000. Not sure, but I think in the next 2 weeks or so more info will become available.

Jon

[Ad B]

Well, I guess the 3dmark prob can't be solved.

But has anyone an idea on why I get a black screen when I exit Q3A?

[noackjr]

Anybody have thoughts? I don't have a clue but I know there are people out there who do.

Jon

[PaulS]

Ad B, I get it too. I think it is driver issue. Should be fixed tomorrow when the final drivers arrive

Paul

[nufan]

hehe
we all HOPE they will be released tomorrow.. but what are the chances =Þ

-]nufan[-

[Ad B]

Do you think the that Matrox will release “pucker” drivers only a week after the released betas?

[Gurm]

Not to nitpick, but 3dMark 2000 and Quake3 both run fine on my system, and have for several iterations of these Matrox betas. I don't think that's the problem. I think, as usual, that it's a hardware issue... seems to be the case with Matrox drivers, especially betas - they like some hardware configs and not others.

- Gurm

------------------
Listen up, you primitive screwheads! See this? This is my BOOMSTICK! Etc. etc.

[Ad B]

No doubt it's something to do with my motherboard, since I've got so little else in the PC - a modem, and a Soundcard, both of which are ISA.

I'll try and check the system over, make sure everything's in place, if that'll help :0(