PDA

View Full Version : Problems with Nemu 0.8 related to DirectX



ZlotZ
April 19th, 2003, 00:34
Hi guys...
I'm having problems with the new Nemu 0.8... When i load a rom, sometimes the program crashes.. other times the rom loads perfectly (but at a slower speed than nemu 0.7) but when I try to play in fullscreen, the software displays a message saying that I must get Direct X 8.0 or greater... but I have directx 9.0 !!!
Then the emulator closes...
Does anybody have a clue on what's going on here ?
Do I need to go back and get DirectX 8.0?
Thanks for the help !

Specs: Pentium III 800mhz
Diamond Viper II 32mb
128mb RAM

Clements
April 19th, 2003, 01:25
Reinstall DX 9 or upgrade to 9.0a.

Benares
April 19th, 2003, 04:05
I had the same problem and I got around it by using Jabo's Direct3D plugin from the Project64 install instead. Seems to work better than the default plugin supplied with Nemu64.

Oh, and some games that don't work on Nemu64 actually seem to work on Project64. So its best to alternate between them.

Hope that helps.


Benares

mightyrocket
April 19th, 2003, 04:30
Are you sure your drivers are up-to-date?

RJARRRPCGP
April 19th, 2003, 12:35
Originally posted by ZlotZ
Hi guys...
I'm having problems with the new Nemu 0.8... When i load a rom, sometimes the program crashes.. other times the rom loads perfectly (but at a slower speed than nemu 0.7) but when I try to play in fullscreen, the software displays a message saying that I must get Direct X 8.0 or greater... but I have directx 9.0 !!!
Then the emulator closes...
Does anybody have a clue on what's going on here ?
Do I need to go back and get DirectX 8.0?
Thanks for the help !

Specs: Pentium III 800mhz
Diamond Viper II 32mb
128mb RAM


It's not DirectX, because even when I have DirectX 9.0a
installed, with *any* attempt to switch to full screen, I *always* receive the above error message too. :(

LaC needs to check this problem out. :unsure:

This is also with my GeForce 2 MX200 32MB video card.

azretro
April 22nd, 2003, 05:37
I noticed I had the same problem on my win2k rig. I solved the problem by editing the refresh rate setting in config.ini. I changed RefreshRate=60 to RefreshRate=85 (the refresh rate I normally use). It works like a charm now.