Ok can all Windows 2000 pro users share their experiences with these games?

[jediphoenix]

Unreal Tournament
Shogo
System Shock 2
Halflife
Ultima 9
Never Winter Nights
Homeworld
Unreal

Thx

------------------
<A HREF="http://jediphoenix.iscool.net/
" TARGET=_blank>http://jediphoenix.iscool.net/
</A>

[Genom]

UT runs great, System Shock 2 runs great, Half-Life runs great, Homeworld runs great.

Far as I know Never Winter knights isnt even out, and wont be for a while? I'll test Shogo tonight.

[DarkSyd]

UT runs faster for me under Win2k and my little bro has been playing Homeworld without any problems either (in D3D, I still haven't got my OGL working).

DS

[jediphoenix]

yeah sorry my bad neverwinter nights is not out yet

------------------
<A HREF="http://jediphoenix.iscool.net/
" TARGET=_blank>http://jediphoenix.iscool.net/
</A>

[Travis L. Knodel]

Look at the specs below. Unreal Tournament runs for several minutes and then crashes horribly. Quake 3 seems to work in single processor, but crashes after the "id" screen in dual processors.

Other games such as The Sims and Half Life seem to work with dual processors, but for now I'm back to Win98SE because of what appears to be terrible drivers from Matrox. (???) Anyone know of fixes for these problems? I'll give you a cookie if you tell me the answer.


------------------
=-=-=-=-=-=-=-=-=-=-=-=-=
Travis L. Knodel
ICQ 5570732

Abit BP6
Dual Celeron 366@523 Mhz
Matrox G400 16MB SH
IBM ATA66 15.2 GB HD w/ 2MB cache
WD UDMA33 4.3 GB POS HD
Acer 40X CD Rom
Memorex 1622 2x2x6 CD-RW
Internal NEC Zip100
Netgear 10/100 Ethernet
Diamond Monster Sound MX300
Altec Lansing ACS 295
Proview 17" Monitor
224 MBs generic PC100 RAM

[DarkSyd]

Win2K/NT are more sensitive to overclocked peripherals than Win9x is. Just for the heck of it, try clocking back to 366 and see if it makes any difference. You might find that adding more cooling and going for 550 is more stable than 523, seeing as your PCI and AGP bus will be operating back at spec.

I hope that nets me a cookie

[Gurm]

*sigh*

Jediphoenix: Ultima 9 runs better under win2k than under win9x. So does Quake, and UT.

Travis: Just because your overclocked, tweaked-out, hacked dual celeron system doesn't run properly with drivers that are KNOWN to have SMP issues doesn't mean the drivers are "buggy".

- Gurm

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

[poopy]

ut runz great for me...but as for q2 and q3...whether you asked or not...i can't get working...i don't know the problem...

[ph0rk]

Gurm: Matrox should fix the SMP issues, then. I mean their cards have always been aimed at "professional" users, correct? Like CAD people or graphics types or whatever? Aren't those the kind of users who generally run SMP rigs?

Concur on UT, Q3, et al. I find all my OpenGL games are as fast under 2k as under 98, but much more stable.

Unfortunatly, every D3D game I play randomly hard-locks my box. Could be after 5 minutes, could be after 3 hours, I never know. No I haven't clocked any hardware back to defaults - and that's why you won't hear me complaining about "buggy" drivers. It's probably my own fault

------------------
------------------------
"The iMac is for conformists who think they are non-conformists. They are also for morons."
John Misak

[noackjr]

I agree tht SMP and D3D issues need to be resolved. However, remember that the current drivers are beta drivers and are therefore likely to still have bugs and not implement everything. Let's give Matrox a little time to iron these issues out - they already have some of the best drivers for Win2k as it is. If these issues are still not resolved after the next 2 driver releases (the first 2 FINAL driver releases) then we could have problems...

Jon

[paulcs]

To say Matrox is "known" for its 3D/CAD application support is an interesting interpretation of the firm's history.

I'm a big Matrox fan, and the computer gods punished me severely when I put a non-Matrox board in my primary system, but Matrox's 3D history is a bit checkered to say the least.

I agree with noackjr. Everyone is having issues now, and we can't expect every game to work. I do think Matrox should focus their W2K driver debugging on games with native NT support first.

Paul
paulcs@flashcom.net

[Broken]

Ive tried UT last night... Damn! I ran it in 1024x768, full detail, 32bit color, without any problems. I still have to do some benchmarks to see what the framerates are like but man oh man. I definitly didn't have this kind of performance with Win98...

My Quake 3 runs just a few frames slower than Win98, I get about 36 FPS in 800x600, full detail, 32bit.

----
Matrox G400 DH 32mb, PIII450, 256mb RAM

[Travis L. Knodel]

If I remember correctly, I've tried clocking it down, along with every other possible fix. So it's not from overclocking the celerons. I would agree with ph0rk, D3D has something in it that's making it crash randomly for who knows what reason. You can play a D3D game for several minutes and it'll crash, next time when you reboot, you can play for several hours and everything runs fine. You never know when it's going to go down in flames in D3D.

------------------
=-=-=-=-=-=-=-=-=-=-=-=-=
Travis L. Knodel
ICQ 5570732

Abit BP6
Dual Celeron 366@523 Mhz
Matrox G400 16MB SH
IBM ATA66 15.2 GB HD w/ 2MB cache
WD UDMA33 4.3 GB POS HD
Acer 40X CD Rom
Memorex 1622 2x2x6 CD-RW
Internal NEC Zip100
Netgear 10/100 Ethernet
Diamond Monster Sound MX300
Altec Lansing ACS 295
Proview 17" Monitor
224 MBs generic PC100 RAM