New ICD !!??

[Kruzin]

GLQuake is an ancient game.
It is hardly at the top of their priority list.
I'd be surprised if it was on their priority list at all.
The best chance of it getting fixed is if some other bug fix just happens to fix GLQ by chance.

[TdB]

hmm!
that is what i was afraid of.
they drop support for old games.

well, if they continue to fine-tune their ICD they might eventually fix glquake too(if nothing else then by accident).

[2Whyzzi]

New ICD & Baldur's Gate 2 - !CrAsH!

Here is the output:

BGMAIN caused an invalid page fault in
module G400ICD.DLL at 016f:690b96f1.
Registers:
EAX=00000005 CS=016f EIP=690b96f1 EFLGS=00010246
EBX=028d7d9c SS=0177 ESP=00dafb78 EBP=0000000c
ECX=01f5ef94 DS=0177 ESI=73367337 FS=3567
EDX=028d7d9c ES=0177 EDI=00b8ef60 GS=0000
Bytes at CS:EIP:
8b 4e 3c 85 c9 75 2f 85 c0 75 36 8b 93 20 01 00
Stack dump:
00b8ef60 028d7d9c 00000005 69002929 00000005 00b8ef60 028d7d9c 690029b8 00000005 00000013 028c1938 00000000 00b8ef60 69091df0 00bd7f64 00c7f434

ICD Properties: File Version: 2.55.052, File Size: 936kb

It seems to be triggered by something the death of a greater wyvern. I'm going to switch to the PowerDesk 6.82 ICD (before I downclock my overclocked Duron)

UPDATE
Looks like game error: I switched to the 6.82 ICD - it still crashed, and DID NOT report an error message. Putting my Duron @ spec (850MHz), and forcing the desktop to 800x600 (game resolution) did not help in solving the problem.

Bah, I'll just avoid the wyvern for now and, if I come across any other errors, I'll post them in the Matrox tech support forums. Incase anyone is interested, the soundcard I am using is AOpen's Pro version of Yamaha's XG744, driver revision 4.12.01.2019; Windows 98SE, DirectX 8 (not 8.1)

[Heed]

Any news?

Just curious if there's any further word on the bug with the textures in Neverwinter Nights. Now that they've released the toolset, the bug is more annoying-- there's currently no workaround for the toolset.

I know these things can take some time, but any info., if available, would be appreciated (i.e. it's not our bug-- it's bioware's, we've found it and are working on it, etc.) Also curious if there's been any communication between the two parties.

Thanks in advance for anything you can find out.

Heed.