The one on this post.Is there any custom mame 2003 (078) core for RA 1.0.0.2 avaiable?
By the way, your question on the other topic, this mame runs Moomesa and Bucky O Hare, but you have to set frameskip on 3 for moomesa. Also, you have to get the Mame2003 romset.Is there any custom mame 2003 (078) core for RA 1.0.0.2 avaiable?
The one on this post.
--------------------- MERGED ---------------------------
By the way, your question on the other topic, this mame runs Moomesa and Bucky O Hare, but you have to set frameskip on 3 for moomesa. Also, you have to get the Mame2003 romset.
Thank you so much bro, that got things going here. Just one more doubt, this custom core only works with these 2 games? Because I tried some others, that works fine on Sdl Mame Wii, but they don't seem to run on this.
- 1942.zip
- amidars.zip
- archrivl.zip
- arkanoid.zip
- armora.zip
- asteroid.zip
- atarifb.zip
- barrier.zip
- berzerk.zip
- blaster.zip
- blstroid.zip
- bonkadv.zip
- boothill.zip
- bosco.zip
- boxingb.zip
- bubbles.zip
- bucky.zip
- bwidow.zip
- bzone.zip
- ccastles.zip
- centiped.zip
- cloak.zip
- cninja.zip
- crater.zip
- crush.zip
- defender.zip
- demoderb.zip
- demon.zip
- digdug.zip
- digdug2.zip
- dkong.zip
- dkongjr.zip
- domino.zip
- dotron.zip
- fantasy.zip
- foodf.zip
- frenzy.zip
- frogger.zip
- galaga.zip
- galaxian.zip
- galivan.zip
- gravitar.zip
- gyruss.zip
- invaders.zip
- invadpt2.zip
- journey.zip
- joust.zip
- kick.zip
- kikikai.zip
- klax.zip
- lrescue.zip
- mappy.zip
- mario.zip
- maxrpm.zip
- mexico86.zip
- mhavoc.zip
- mhavocrv.zip
- midres.zip
- missile.zip
- mk.zip
- mk2.zip
- mk3.zip
- mkla4.zip
- moo.zip
- mooncrst.zip
- moonwalk.zip
- mrdo.zip
- mspacman.zip
- mspacpls.zip
- nbajam.zip
- nibbler.zip
- nspirit.zip
- omegrace.zip
- pacman.zip
- pballoon.zip
- phoenix.zip
- piranha.zip
- pleiads.zip
- powerdrv.zip
- quantum.zip
- rampage.zip
- rbtapper.zip
- redbaron.zip
- ripoff.zip
- robocop.zip
- robocop2.zip
- robotron.zip
- rtype.zip
- rtype2.zip
- rtypeleo.zip
- sarge.zip
- scobra.zip
- scramble.zip
- shollow.zip
- simpsons.zip
- sinista1.zip
- sinistar.zip
- snowbros.zip
- solarq.zip
- spacduel.zip
- spacewar.zip
- spectar.zip
- speedfrk.zip
- splat.zip
- spyhunt.zip
- ssi.zip
- starcas.zip
- stargate.zip
- starhawk.zip
- starwars.zip
- sundance.zip
- tailg.zip
- tapper.zip
- targ.zip
- tempest.zip
- temptube.zip
- theend.zip
- timber.zip
- timeplt.zip
- tmnt.zip
- tmnt2.zip
- toki.zip
- toobin.zip
- tron.zip
- tutankhm.zip
- twotiger.zip
- vanguard.zip
- vulgus.zip
- wacko.zip
- warrior.zip
- wotw.zip
- wwfwfest.zip
- xenophob.zip
- xmen.zip
- yiear.zip
- zerozone.zip
Again, is REALLY possible to run all the games on this list on this core? For example, I tried to run the so talked mkla4 and and it sends me back to HC... Anyone here REALLY make these games run? If so, could please direct me to where I can find the sets that work, cause I tested with ones on torrents (0.78 sets apparently) and from all the usual sites.
Thanks a lot if someone stop to answer.
Could you please help me so? Cause I already tried from 2 torrents of 0.78 sets and also from the "usual places" (tronik, paradise, dope, cool etc...)You have to find the mame roms from Mame2003. If you use fomr the current mame they will not work.
Yes, my builds are based on 1.0.0.2 but have the CPU filters merged and my own version of resolution saving. It also has some fixes not present in the official versions yet, the button sticking bug is fixed, vsync should be more stable and there's normal2x as a CPU filter, which you can use to make bilinear sharp. And yes, you can change the viewport in 240p as well.
If you mess up when changing inputs in the settings, you can always exit with the power button, as this was not working in main 1.0.0.2.
If you want to always use 640x240p, start the core, and let it create the configs, if using per core settings, open the stella cfg and retroarch.cfg, look for the setting video_vres = "38" and set it to 19.
The link is in the "ripping the NES VC palette" thread, but I guess I need a better place to put it, anyway: http://www.mediafire.com/?cw863hlp0nsmblp
It works like any other version. Use the boot.dol from the official release.Hello superrsonic, I downloaded your version of retroarch and I do not understand how it works.
There is no "boot.dol" for example.
In "github" I found this:
"Single game loading via arguments only, in the game browsing screen, in the core selection screen and in the game history screen."
I have 2 questions:
- How is this version working?
- Any possibility of a version similar to the original 1.0.0.2 (game browsing screen and core selection) but with the changes made in your version?
Thank you!
Yes, my builds are based on 1.0.0.2 but have the CPU filters merged and my own version of resolution saving. It also has some fixes not present in the official versions yet, the button sticking bug is fixed, vsync should be more stable and there's normal2x as a CPU filter, which you can use to make bilinear sharp. And yes, you can change the viewport in 240p as well.
If you mess up when changing inputs in the settings, you can always exit with the power button, as this was not working in main 1.0.0.2.
If you want to always use 640x240p, start the core, and let it create the configs, if using per core settings, open the stella cfg and retroarch.cfg, look for the setting video_vres = "38" and set it to 19.
The link is in the "ripping the NES VC palette" thread, but I guess I need a better place to put it, anyway: http://www.mediafire.com/?cw863hlp0nsmblp
It works like any other version. Use the boot.dol from the official release.
The source I have on github is for the forwarder version. It can only be used with forwarder programs, like Wiiflow's plugin feature. Builds for this version are in the /forwarders folder, the other cores do indeed have 'load content' and the usual stuff.
Which controller are you using? Unresponsive control could be two things: no buttons are mapped to the controller, or you're trying to use a GC controller while a wiimote is on. Wiimote type takes priority. You're probably thinking that's a dumb design choice, you're not wrong. If you're using newer wiimote models, then it might have to do with the tools I use to compile.
If you are using just a plain wiimote or classic controller and it's not working, then I don't know.