Author: bwb .: Created: 6-1-2005 .: Rating: .:

5 - Sweet 4 3 - Nice 2 1 - Blah

How can i make my Voodoo3 Card work in Nemu64?

- This is quite easy. All you need to do is the following: Set your desktop color depth to 16 Bit. Then, set the Nemu Screen resolution to the same value as your desktop screen resolution. Finally, load the rom you want to play, and for better gfx, set Nemu64 to fullscreen mode. Voodoo3 still has more gfx bugs than for example TNT2 cards, but thats just card quality.

Will Nemu64 ever work on my Voodoo1/Voodoo2 card?

- Unfortunately, no. hWnd, Nemu64's graphics plugin coder, is doing the plugin in the Direct3D API. For Voodoo1/Voodoo2 cards to work with direct3d, the coder needs to make special code that makes the application use the secondary video card. Without that code, direct3d always assumes you use your primary video card, so your voodoo card wont work. Because hWnd isnt very fond of 3DFX, he will not write special code for their cards, and the Nemu64 team fully supports his decision and motivation. Therefor, Voodoo1/Voodo2 cards will never work in Nemu64, not now, and not in the future.

What does "hWnd" stand for anyway?

- hWnd stands for Window Handle.

How come Nemu64 is so slow? will it get any faster?

- Until a few days ago, i thought Nemu64 was pretty fast. For months i hadnt tried any other emulator than Nemu64, so i kinda got used to its speed. Thats why i was very surprised to see so many complaints about Nemu's speed. Then i tried Corn. Indeed, Nemu64 isnt the fastest emulator around at this moment, but it is by far the most compatible. With the chosen emulation technique, being High Level Emulation (HLE), Compatibility takes its toll speedwise. The more compatible your emu, the less speed it will have. This is nicely illustrated if you compare UltraHLE with Nemu64. However, this does not mean Nemu64 wont get faster in the future. Remember that the current release is only v0.7, so that is not even 1.0. Nemu64 is constantly being worked on, and one of the goals for the future is more speed. So just wait and see is all i can say for now.

Could you explain the different Nemu.INI settings to me?

- This is quite difficult. Generally, its not needed to know what each setting means, just use the settings i advise in my Games Resource, and you'll be fine. However, i will give you a list of all the possible INI settings here: "GBI=xx" where xx can range from 1 to 4. GBI's 1 and 3 are usually autodetected by Nemu64, and GBI=4 is only needed for Waverace US. Next, there's "ABI=xx" where xx can range from 1 to 3. ABI is most oftenly autodetected, so you wont really need this setting either. Then there's "compilermode=xx" where xx can be either 0, 1 or 2. Compilermode 0 is autodetected and therefor not needed to be set in the INI, and Compilermode=2 can be buggy and you shouldnt use this unless the game really needs it (like GoldenEye). Then there's "Goldeneyehack=xx" which as its name implies is only needed by GoldenEye. Finally, there's "comment=xx" which sets the comment for that specific rom displayed in the Nemu64 GUI. Thats it. If you have a rom which is not in my list, just play around with the settings a bit untill you get it right. Some rules which almost always apply: Most games newer than Zelda64 are GBI=3. If a game hangs somewhere in the rom but it does show some screens, try to set the compilermode to a different setting, that might help. Once again, it wont help you in any of the roms that are in my list. By the way, you can change the INI settings by pressing F2 when a rom is loaded, or by right clicking on the rom in the Nemu64 GUI and choosing "Rom Options".

More FAQ's will be answered later.