MAME 64

[Golgo13]

Ya podeis descargar de aqui la ultima version para 64bits del MAME, los incrementos de velocidad a 64bits junto con el multhread son espectaculares, ahora algunos juegos 3d son jugables. El incremento en algunos casos es de mas del 60%.
Podeis echar un vistazo a la tabla adjunta, eso si para poder disfrutar de necesitais un ordenador de 64bits y windows x64.


A few interesting observations from here:

The -mt switch definitely helps with benchmarks, no doubt about it! But benchmarks are testing an unrealistic scenario: running faster than the game should. It is worth point out that it does also help a little bit with games that have trouble pushing full frame rate, but only by about 5%. This makes sense, since there is a little bit to be gained just from avoiding the blit on the primary CPU.

Comparing gcc versus Visual Studio, I have to say Visual Studio definitely comes out on top pretty consistently. The biggest exceptions were Ridge Racer and Star Wars, which both took a 10% dive under MSVC. On the flip side, Primal Rage and Sexy Parodius were 20% faster under MSVC. (I sense R. Belmont’s conflicting feelings over this result.) Interestingly, the gcc binary was about 1.5MB smaller than the MSVC binary with the same optimizations.

Link time code generation (enabled in MAME by setting MAXOPT=1 when building using the MSVC toolset) had only a minor performance benefit on average. And the benefit on the 64-bit builds was even less than that on the 32-bit builds. However, it did reduce the size of the 32-bit binary by about 5MB! And the 64-bit binary got 3.5MB smaller.

Finally, the 64-bit question: yes, absolutely, with the MSVC toolset, the 64-bit builds were consistently faster — and in a few cases significantly faster — than the 32-bit builds. There were a few black eyes for the 64-bit builds, but they are all cases where the lack of a MIPS recompiler for 64-bit put the games at a significant disadvantage. Killer Instinct in particular utterly crawls without the recompiler (they use a lot of lwl/lwr/swl/swr instructions which are worst case for the memory system). The Seattle and Vegas games, on the other hand, were slower, but not nearly as slow as I would have expected. Even with a super simple 64-bit drc, they should smoke the 32-bit versions. You’ll also note that Raiden Fighters Jet crashes on the 64-bit builds — guess we’re not fully 64-bit clean yet!

One thing that seems pretty consistent is that the 64-bit builds do really well on games that do 3D rendering. I can only attribute this to having more registers to play with in the innermost rasterization loops. Ridge Racer was an impressive 50% faster in the 64-bit build. Radikal Bikers was 30% faster.

[Golgo13]

[Golgo13]

   1.  In root shell emerge kernel-sources -pv , if already installed go to next step otherwise type emerge =kernel-sources-2.6.kernelversion  (kernel version can be identified by typing uname -r  or uname -a )
   2. If not using genkernel ensure your kernel configuration supports your video card (gentoo-wiki.com has more information)
   3. In root shell type emerge nvidia-drivers or emerge nvidia-legacy-drivers depending on your card. Most people will just type the first one.
   4. Edit xorg.conf and change the Driver option under Device from nv or vesa to nvidia, also ensure the the Load glx line is uncommented in the Module Section
   5. In a root shell type eselect opengl set nvidia
   6. Make sure your user is in the video group by typing gpasswd -a youruser video in a root shell.
   7. Restart X
   8. If X doesn't work please pastebin the contents of /var/log/Xorg.0.log and possibly /etc/X11/xorg.conf and check #Sabayon, the Sabayon Forums or gentoo-wiki.com, If it does, in root shell type glxinfo | grep direct, if this says Yes then continue to next step
   9. Using Google or other means identify whether your card works best with XGL or AIGLX or neither.
  10. Using accel-manager which will need to be emerged by typing (still in a root shell) emerge accel-manager, choose your preferred method XGL or AIGLX. Or if neither ignore this step.
  11. Repeat Step 7
  12. You should now have a working NVIDIA card with DRI and if you choose XGL or AIGLX. If you some reason you don't please use the resources in the Forum Usage & Resources Post in Sabayon Forums to remedy the problem.These resouces include http://gentoo-wiki.com/HOWTO_nVidia_Drivers. It would be beneficial if you repeat Step 8 as part of the troubleshooting process.



http://marcianitos.forumcommunity.net/?t=4660318

[Golgo13]

http://xboxvgatutorial.host.sk/

[Golgo13]

http://ddememame.hp.infoseek.co.jp/

[Golgo13]

http://www.marcianitos.org/foro/showthread.php?t=3016