[rod_audioslave]

Originally Posted by Hokage-Sama

I have some games (Skies of Arcadia, Crazy Taxi 2, Shenmue, Virtua Striker, etc.) that worked at last version of nullDC, but in this one (1.0.3), neither of them worked at all! (the emu crashes or keep the white screen) What's the reason?

Originally Posted by Hokage-Sama

It seems that NullPVR (graphics plugin) it's the problem. At last version, it works fine but not in 1.0.3. Anyone knows why Chankast plugin works perfectly and NullPVR causes crashes? Anyone has the same problem?

Thanks.

Originally Posted by drkmasked

Sorry to be rude but can someone explain to me why am I having crashing problems with the new nullpvr: August 20 2008 plugin in the DC version of Nulldc 1.0.3? It would display a black screen then crash when loading a game, The NullPVR: Nov 07 2007 version using Nulldc 1.0.0 beta 1.6 worked perfectly averaging 60 fps on everygame with very little display problems except SA2, also while using Nullpvr : January 10 2008 I just get a black screen while the game continues to play and all Chankast video plugins gives me block like display problems.


NullPvr 07 2007

ImageShack - Hosting :: mvc2null07kn1.png

Chankast
ImageShack - Hosting :: mvc2chankwo2.png

Nulldc 1.0.3 and Nullpvr : Aug 20 2008
ImageShack - Hosting :: newnulldcen1.png


Operating System: Windows XP Professional (5.1, Build 2600) Service Pack
System Model: Dell 310
Processor: Intel(R) Pentium(R) 4 CPU 2.80GHz (2 CPUs)
Memory: 2038MB RAM
Page File: 494MB used, 5480MB available
Windows Dir: C:\WINDOWS
DirectX Version: DirectX 9.0c (4.09.0000.0904)
Card name: Intel(R) 82915G/GV/910GL Express Chipset Family
Manufacturer: Intel Corporation
Chip type: Intel(R) 82915G/GV/910GL Express Chipset
DAC type: Internal
Display Memory: 128.0 MB
Current Mode: 1280 x 1024 (32 bit) (60Hz)
Monitor Max Res: 1280,1024
Driver Name: ialmrnt5.dll

Thank you

Originally Posted by drkmasked

edit: Installed directx from link and still crashes when game loading.

Originally Posted by Hokage-Sama

I've got the latest update of DirectX, so it can't be the reason of this problem...

Here is the explanation: The new release: A step back in a couple of things