MAME 2010 (0.139) or 2014 (0.159) for Vita Possible?

RetroArch Sony consoles
#9

I tried to compile mame2009 for ps3 and vita, but it get errors while compiling.

For ps3 this one

For vita this other one

Anyway I used an old version of vitasdk, so i’ll try to compile it again once i updated the toolchain on my end.

I have only renamed makefile (there’re two makefiles) and i added a vita target to compile for vita platform. If you like it, i can do a pr your repo. https://github.com/Ezio-PS/mame2009-libretro

PS: I can finally thank you to fix ngp core, the fix you did for WiiU worked very good for ps3 too, since WiiU and ps3 are both big endian machines, so i guess everything you fix for Wiiu target can be used/or easily ported to ps3 platform to benefit your work on more platforms. :slight_smile:

#10

Hi,

For Ps3 , maybe you have to force PTR64=1 in the ps3 section of makefile (after BIGENDIAN=1). and you should also add -DOLEFIX (as i took this from ps3 OLE mame build) and maybe configure other flags like here.

# Nintendo Wii U
      
      
        
        else ifeq ($(platform), wiiu)
      
      
        
           TARGETLIB := $(TARGET_NAME)_libretro_wiiu.a
      
      
        
           CC = $(DEVKITPPC)/bin/powerpc-eabi-gcc$(EXE_EXT)
      
      
        
           CXX = $(DEVKITPPC)/bin/powerpc-eabi-g++$(EXE_EXT)
      
      
        
           AR = $(DEVKITPPC)/bin/powerpc-eabi-ar$(EXE_EXT)
      
      
        
           COMMONFLAGS += -DGEKKO -mwup -mcpu=750 -meabi -mhard-float -D__POWERPC__ -D__ppc__ -DWORDS_BIGENDIAN=1 -malign-natural 
      
      
        
           COMMONFLAGS += -U__INT32_TYPE__ -U __UINT32_TYPE__ -D__INT32_TYPE__=int -fsingle-precision-constant -mno-bit-align
      
      
        
           COMMONFLAGS += -DHAVE_STRTOUL -DBIGENDIAN=1 -DWIIU -DOLEFIX
      
      
        
           DEFS       += -DMSB_FIRST
      
      
        
           PLATCFLAGS += -DMSB_FIRST
      
      
        
           BIGENDIAN=1
      
      
        
           STATIC_LINKING = 1
      
      
        
           FORCE_DRC_C_BACKEND = 1
      
      
        
           PLATCFLAGS += -DSDLMAME_NO64BITIO $(COMMONFLAGS) -falign-functions=16
      
      
        
           PTR64 = 0
      
      
        
           REALCC   = $(DEVKITPPC)/bin/powerpc-eabi-gcc$(EXE_EXT)
      
      
        
           NATIVECC = g++
      
      
        
           NATIVECFLAGS = -std=gnu99
      
      
        
           CCOMFLAGS += $(PLATCFLAGS)

also you should include Makefilewiiu.common instead of Makefile.common , for the static build . and change some code like ifeq ($(platform), wiiu) to include ps3 case.

For vita not sure what is the problem.

#11

Is there any way someone could make it so that MAME 2000 has the ability to bring up the in game MAME setting menu? It just seems there is no button to trigger it. MAME 2003 does do it but that core has many audio issues due to the needed extra CPU power. That sounds like a pretty easy fix isn’t it? It is a simple thing but causes huge trouble by not being able to remap controls.

1 Like
#12

I just created an Issue for this on github: https://github.com/libretro/mame2000-libretro/issues/48

I would suggest using the Subscribe feature on that page to keep up to date with any developments.

#13

Yeah, what davec1964 says! We need the in menu button.

#14

They closed you request and said that

Will fix it lol. but we dont have a tab button. They dont get it, right?

#15

it seem it’s you that don’t get it, right ? as far i know TAB is working, and it was the object of the issue. that said TAB and R2 input are mapped for menu.

#16

I don’t get it either. How do you access the MAME menu on MAME 2000? I haven’t been able to do it.

#17

Should be the Back Touchscreen on the left to pull up the MAME Menu

#18

Nope, doesn’t work on MAME 2000.

#19

Should be Rear Touchpad, Top Right (Top Left if looking at the Rear Touchpad). Works with 2003. Would just love to actually test how 2010 or 2014 runs. Hopefully it can be figured out at some point.

#20

As I said it doesn’t work on MAME 2000. I have done it on 2003 and it works there. 2003 is choppy in some games that 2000 isn’t so that is why I still use it. Seeing how 2003 runson the Vita, 2014 would be a slideshow.

#21

Then hopefully they can try and see about MAME 2010

#22

It was added to MAME 2000 very recently. Have tried it with a mame2000 build from the last week or so?

Edit: you might also post in this github issue once you know that you have a compile of mame2000 which includes the latest input updates: https://github.com/libretro/mame2000-libretro/issues/29

#23

I tried the latest build of MAME 2000 and it doesn’t work at all. Every time I load a ROM it just crashes with a C2 code and a PSP2 eboot dump. Can you suggest a build that has this change and works too?

#24

The crashing core sounds like a useful bug report itself. Right now I can assure you there is no libretro developer working on that crash. Could you post an issue in the MAME 2000 github repository?

That may be all it takes to get this functionality working for you as well – I personally have been able to access the MAME 2000 TAB menu with the latest, using Windows RetroArch.

#25

Well Windows and Vita are two different things. Different buttons etc (no keyboard on a Vita) and I am sure windows is more polished while Vita seems kind of dried up development wise. I tried all new releases and while they crash on games I used to be able to load some still work (vector games seem to do better for some reason). While there I tried the rear touchscreen all over, nothing. Doesn’t bring up MAME menu.

I am not a developer so I am not signed up with github.

Is there anywhere I can download just the MAME 2000 core? Downloading a half gig every time I want to try a new build with my internet connection is slowwwwwwwwwwwwwwww.

#26

I take it it any of the MAME Cores can not run the SFIII Games huh? Tried running SFIII, and it just froze. Did that even on my Android Device using MAME 2014.

#27

SF3 needs a CHD file in addition to the ROM, I’m guessing you’re missing it.

#28

No, I tried the CHD+Rom Files in the same Directory together, then when that did not work, I tried it with the CHD in it’s own Folder with the Rom Name as the Folder Name. Nothing.Tried SFIII and SFIII 2ndImpact But at least I got MK2+ working in it and UMK3:TE. So 2 good Rom Hacks working