Click Here
home features news forums classifieds faqs links search
6155 members 
Amiga Q&A /  Free for All /  Emulation /  Gaming / (Latest Posts)
Login

Nickname

Password

Lost Password?

Don't have an account yet?
Register now!

Support Amigaworld.net
Your support is needed and is appreciated as Amigaworld.net is primarily dependent upon the support of its users.
Donate

Menu
Main sections
» Home
» Features
» News
» Forums
» Classifieds
» Links
» Downloads
Extras
» OS4 Zone
» IRC Network
» AmigaWorld Radio
» Newsfeed
» Top Members
» Amiga Dealers
Information
» About Us
» FAQs
» Advertise
» Polls
» Terms of Service
» Search

IRC Channel
Server: irc.amigaworld.net
Ports: 1024,5555, 6665-6669
SSL port: 6697
Channel: #Amigaworld
Channel Policy and Guidelines

Who's Online
22 crawler(s) on-line.
 95 guest(s) on-line.
 0 member(s) on-line.



You are an anonymous user.
Register Now!

/  Forum Index
   /  Amiga OS4 Software
      /  Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Register To Post

Goto page ( Previous Page 1 | 2 )
PosterThread
samo79 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 1-Mar-2013 11:53:20
#21 ]
Elite Member
Joined: 13-Feb-2003
Posts: 3505
From: Italy, Perugia

@Spirantho

As espected is very slow on my Sam440 Flex, however using this 0.148 i didn't note any slowdown compared to the old 0.146, they are mostly 1:1 ... atleast with my gameset

Still also the old DSI crash, this happen from time to time expecially if you try to start it from the binary icon instead of the icon launchers

Quote:
Crash log for task "MAME_0146u4"
Generated by GrimReaper 53.5
Crash occured in module MAME_0146u4 at address 0x6F00920C
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: 00000000 56E42350 00000000 546D9E78 56E42360 56E58658 56E52350 56E52350
8: 500000CF 1001004D 500000CC 6EFE2FAC 24442024 4E81FF90 00000000 00000000
16: 58BDD340 6E558C7C 00000000 588224F0 00340014 02270000 02270000 56E2C8C0
24: 00000001 5FF9A000 55A0DE10 00000000 02270000 02270000 56E2C8A0 02270000


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 3 0 3
4: 3 0 0 0.25
8: 0.333333 0 0 1
12: 0 1 3.39519e-313 -5.05923e-321
16: 0 1.39067e-309 0 0
20: 0 0 0 1.61895e-319
24: 4.94066e-324 4.77831e-299 1.08673e-311 -4.6408e+303
28: 0 1.35808e-312 8.6917e-311 -0.234375

FPSCR (Floating Point Status and Control Register): 0x82024000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0002F030
Condition (cr) : 0x24442022
Instruction Pointer (ip) : 0x6F00920C
Xtended Exception (xer) : 0x00000004
Count (ctr) : 0x6F9FA77C
Link (lr) : 0x6F0091D0
DSI Status (dsisr) : 0x00800000
Data Address (dar) : 0x56E48318



680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x6F00920C belongs to module "MAME_0146u4" (PowerPC)
Symbol: _Z20construct_core_typesR11simple_listI16input_type_entryE + 0x164 in section 1 offset 0x030031EC

Stack trace:
_Z20construct_core_typesR11simple_listI16input_type_entryE()+0x164 (section 1 @ 0x30031EC)
_ZN14ioport_manager10initializeEv()+0x23c (section 1 @ 0x3099574)
_ZN15running_machine5startEv()+0x508 (section 1 @ 0x30A4B00)
_ZN15running_machine3runEb()+0x310 (section 1 @ 0x30A5D24)
_Z12mame_executeR11emu_optionsR13osd_interface()+0x254 (section 1 @ 0x30A1478)
_ZN12cli_frontend7executeEiPPc()+0x9f4 (section 1 @ 0x2F588D4)
main()+0x1f4 (section 1 @ 0x2552E50)
native kernel module newlib.library.kmod+0x00002094
native kernel module newlib.library.kmod+0x00002cf4
native kernel module newlib.library.kmod+0x00002eb8
_start()+0x170 (section 1 @ 0x170)
native kernel module dos.library.kmod+0x00022a10
kernel module diskboot.config at 0x0183bd20
kernel module diskboot.config at 0x0183bda0
module SYS:System/GrimReaper at 0x00000000 (section 0 @ 0xFFFFFFE8)

PPC disassembly:
6f009204: 6129004d ori r9,r9,77
6f009208: 396b2fac addi r11,r11,12204
*6f00920c: 90015fc8 stw r0,24520(r1)
6f009210: 38615f8c addi r3,r1,24460
6f009214: 91210010 stw r9,16(r1)

System information:

CPU
Model: AMCC PPC440EP V1.3
CPU speed: 799 MHz
FSB speed: 133 MHz
Extensions:

Machine
Machine name: Sam440EP
Memory: 1048576 KB
Extensions: bus.pci


Mame will start after that so you can ignore the error and continue, however a fix for this crash would be better

Also how about suppressing the shell output, even with a simple tooltype option, like for example: (SHOW_OUTPUT=ON/OFF)


_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

 Status: Offline
Profile     Report this post  
realize 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 1-Mar-2013 11:57:50
#22 ]
Super Member
Joined: 14-Apr-2003
Posts: 1797
From: nyc

@Fab

Quote:
Overlay gives much better results in that regard.


Yeah on my Peg2 on OS4 Mame is quite fast enough for my uses. It plays all the roms i have full speed. I do have to say its nowhere near as fast as the Morphos version.

@thread
Where can i read on line about what roms are compatible with what versions and how to get them? Thanks

 Status: Offline
Profile     Report this post  
Fab 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 1-Mar-2013 12:02:26
#23 ]
Super Member
Joined: 17-Mar-2004
Posts: 1178
From: Unknown

@realize

I didn't refer to the 0.148 OS4 version, btw. I wouldn't dare testing a SDL version, even on Pegasos2. MAME is slow enough, no need to slow it down even more.

 Status: Offline
Profile     Report this post  
Spirantho 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 1-Mar-2013 12:04:03
#24 ]
Super Member
Joined: 4-Jun-2004
Posts: 1045
From: Aberystwyth, Wales

@samo79

Can you tell me what your stack is set to please?

@Fab

The main difference on there is probably the L2 cache.
My 600MHz 440ep can run Pang with no video at 102%, so I'd expect a G4 Peg II to be a lot faster than that.
The problem is verifiably in large screen sizes because increasing the screen makes quite a difference to the frameskip. OpenGL will help with all that because all it'll need to do is to render to a surface and the main bottleneck will be gone. I don't see why my Sam wouldn't be able to run without frameskip as rendering to a texture will be not much slower than no renderer at all, and the Sam's graphics core is easily capable of drawing a single polygon with minimal overhead.

I still stand by what I said, though - to compare MAME on a Peg II to MAME on AROS x86 to MAME on a Sam, you need the same build parameters; without doing that there's all sorts of other overheads such as SDL which will affect things massively. If you were to do a build of MAME 0.148 on a G4 Peg II MOS machine using the basic build parameters, you'd get a better comparison - obviously the Peg II would be faster, but not by as much as many would think, I suspect.

Really, though, the Sam isn't a good machine for emulation because of the lack of L2.

Edit:

The thing to remember about my porting SDLMAME is simply that I don't have the time for a properly Amiga-ised build. I figured better to have a slow version than no version at all. :)

Last edited by Spirantho on 01-Mar-2013 at 12:10 PM.

 Status: Offline
Profile     Report this post  
samo79 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 1-Mar-2013 12:18:47
#25 ]
Elite Member
Joined: 13-Feb-2003
Posts: 3505
From: Italy, Perugia

@Spirantho

Both launchers (MAME and MAME_Windowed) are set with the follow stack

Quote:
stack 2048000


Instead the main binary is currently set at 32768 (default).

I also tried to increase the binary stack from its current 32768 value to the same stack number used for the launchers (2048000) but it crash on the same way ..

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

 Status: Offline
Profile     Report this post  
Spirantho 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 1-Mar-2013 12:39:06
#26 ]
Super Member
Joined: 4-Jun-2004
Posts: 1045
From: Aberystwyth, Wales

@samo79

Very odd. I wonder why ioport is crashing... and how it's continuing afterwards?

MAME needs a proper maintainer really - I'm more of a compiler. :)

 Status: Offline
Profile     Report this post  
samo79 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 1-Mar-2013 12:53:46
#27 ]
Elite Member
Joined: 13-Feb-2003
Posts: 3505
From: Italy, Perugia

@Spirantho

Quote:
and how it's continuing afterwards?


Do you mean what happen if i ignore the DSI ?
Nothing, MAME start normally and continue to work fine, however the system may become instable after a while because the previews crash .. that's why i report it

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

 Status: Offline
Profile     Report this post  
realize 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 2-Mar-2013 3:34:22
#28 ]
Super Member
Joined: 14-Apr-2003
Posts: 1797
From: nyc

@Spirantho

Quote:
@realize Don't forget to configure the inputs to use the joystick :) Do it in the menu where you define your keys, but use the joystick instead of pressing a key.


I hit TAB and tried to move the joystick and press buttons but no input response.

 Status: Offline
Profile     Report this post  
Spirantho 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 2-Mar-2013 7:58:45
#29 ]
Super Member
Joined: 4-Jun-2004
Posts: 1045
From: Aberystwyth, Wales

@realize

You need to use the keyboard to go the key entry for Up/Down/Left/Right/Fire and redefine them. When you get to the key setting you want, press RETURN and the normal key binding will disappear. At this point, move your joystick or press a button.

If your display resolution is set too high (i.e. your SDLMAME_DESKTOPDIM is too large or not set) you may find the menu response is very slow - try it with the display much lower.

 Status: Offline
Profile     Report this post  
Tuxedo 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 3-Mar-2013 11:21:30
#30 ]
Elite Member
Joined: 28-Nov-2003
Posts: 2356
From: Perugia, ITALY

@ALL

but why not:

http://amigaworld.net/modules/newbb/viewtopic.php?topic_id=37364&start=0&post_id=699814&order=0&viewmode=thread&pid=0&forum=32#699814


?????

Why we need recent versions of MAEalso if we cant use them????????

_________________
Simone"Tuxedo"Monsignori, Perugia, ITALY.

 Status: Offline
Profile     Report this post  
Spirantho 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 6-Mar-2013 0:02:38
#31 ]
Super Member
Joined: 4-Jun-2004
Posts: 1045
From: Aberystwyth, Wales

For anyone who's interested:

I've uploaded a new version here:
http://www.retroreview.com/iang/mame_0148u1_ogl.lha

For some uses this may be slower, but generally it's faster. It's only a temporary OpenGL build, but it's better than nothing. When we have proper OS 4.2 it'll be faster; MiniGL doesn't support the format MAME uses so I've put in a texture endianness-swapper before it uploads the textures.
The net result is that it's slower than software renderer when you have a very small screen, but scaling is now basically free.

You'll notice a substantial increase on some games and less so on others. If you have a large screen dimension, though, you'll notice a potentially much larger speed.

To use the OpenGL, use:
mame (romname) -video opengl (-w) (-nosound)
If you want to use the software renderer, use "-video soft"

Alpha'd textures don't work yet but this doesn't affect anything except making the text hard to read.

Obviously you'll need an OpenGL capable graphics card. :)

 Status: Offline
Profile     Report this post  
samo79 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 6-Mar-2013 1:34:16
#32 ]
Elite Member
Joined: 13-Feb-2003
Posts: 3505
From: Italy, Perugia

@Spirantho

Tried from shell but it seems i need to remove part of the command line:

This one "(-w) (-nosound)"

because with that i got this error:

Quote:
Error: unknown option: (-w)


So at the end i start my game with:

MAME (roms/sf2ce.zip) -video opengl

And it works but only in fullscreen, it seems a bit faster with sf2ce (Street Fighter 2 Champion Edition) however not playable on my Sam440 .. as you say still also some graphics glitch on the text

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

 Status: Offline
Profile     Report this post  
Spirantho 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 6-Mar-2013 7:40:36
#33 ]
Super Member
Joined: 4-Jun-2004
Posts: 1045
From: Aberystwyth, Wales

@samo79

I meant that the -w and -nosound parameters were optional, I can't use square brackets in a forum :)

I.e.
mame Ghouls -w -nosound -video opengl

to run Ghouls 'n Ghosts in a window with no sound.

 Status: Offline
Profile     Report this post  
samo79 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 6-Mar-2013 13:07:46
#34 ]
Elite Member
Joined: 13-Feb-2003
Posts: 3505
From: Italy, Perugia

@Spirantho

Ok it works now, ssf2ce (Street Fighter 2 CE) is running fine on window now however still the usual DSI crash when you execute it from the main binary

Quote:
Crash log for task "MAME_GL"
Generated by GrimReaper 53.5
Crash occured in module MAME_GL at address 0x6D397F3C
Type of crash: DSI (Data Storage Interrupt) exception

Register dump:
GPR (General Purpose Registers):
0: 00000000 54B94350 00000000 3C3CC8E8 54B94360 54BAA658 54BA4350 54BA4350
8: 500000CF 1001004D 500000CC 6D371CDC 24442024 3650D798 00000000 00000000
16: 43833680 6C8DBD10 00000000 580EB4F0 00340014 02270000 02270000 537AD8E0
24: 00000006 5FF9A000 546E3320 00000000 02270000 02270000 537AD8A8 02270000


FPR (Floating Point Registers, NaN = Not a Number):
0: nan 3 0 3
4: 3 0 0 0.25
8: 0.333333 0 0 1
12: 0 1 0 -0
16: 0 1.39067e-309 0 7.90505e-323
20: 0 0 0 1.61895e-319
24: 4.94066e-324 4.77831e-299 1.32625e-314 -1.20437e+36
28: 0 1.35808e-312 2.06041e-289 -0.234375

FPSCR (Floating Point Status and Control Register): 0x82024000


SPRs (Special Purpose Registers):
Machine State (msr) : 0x0002F030
Condition (cr) : 0x24442022
Instruction Pointer (ip) : 0x6D397F3C
Xtended Exception (xer) : 0x00000004
Count (ctr) : 0x6DD894AC
Link (lr) : 0x6D397F00
DSI Status (dsisr) : 0x00800000
Data Address (dar) : 0x54B9A318



680x0 emulated registers:
DATA: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
ADDR: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
FPU0: 0 0 0 0
FPU4: 0 0 0 0



Symbol info:
Instruction pointer 0x6D397F3C belongs to module "MAME_GL" (PowerPC)
Symbol: _Z20construct_core_typesR11simple_listI16input_type_entryE + 0x164 in section 1 offset 0x0300EF1C

Stack trace:
_Z20construct_core_typesR11simple_listI16input_type_entryE()+0x164 (section 1 @ 0x300EF1C)
_ZN14ioport_manager10initializeEv()+0x23c (section 1 @ 0x30A52A4)
_ZN15running_machine5startEv()+0x508 (section 1 @ 0x30B0830)
_ZN15running_machine3runEb()+0x310 (section 1 @ 0x30B1A54)
_Z12mame_executeR11emu_optionsR13osd_interface()+0x254 (section 1 @ 0x30AD1A8)
_ZN12cli_frontend7executeEiPPc()+0x9f4 (section 1 @ 0x2F64604)
main()+0x1f4 (section 1 @ 0x2552EE4)
native kernel module newlib.library.kmod+0x00002094
native kernel module newlib.library.kmod+0x00002cf4
native kernel module newlib.library.kmod+0x00002eb8
_start()+0x170 (section 1 @ 0x170)
native kernel module dos.library.kmod+0x00022d9c
native kernel module kernel+0x0003bd20
native kernel module kernel+0x0003bda0


PPC disassembly:
6d397f34: 6129004d ori r9,r9,77
6d397f38: 396b1cdc addi r11,r11,7388
*6d397f3c: 90015fc8 stw r0,24520(r1)
6d397f40: 38615f8c addi r3,r1,24460
6d397f44: 91210010 stw r9,16(r1)

System information:

CPU
Model: AMCC PPC440EP V1.3
CPU speed: 799 MHz
FSB speed: 133 MHz
Extensions:


As you can see i renamed the binary as "MAME_GL" to not conflict with the script that use the same name, for the final release maybe you might create another script in order to start MAME with OpenGL enabled by default

Aniway here is the shell output i got running the game:

Quote:
4.HD:Game test/MAME0.148> MAME_GL sf2ce -w -nosound -video opengl
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
Warning: osd_open environment variable $HOME not found.
OpenGL: VBO not supported
OpenGL: PBO not supported
OpenGL: FBO not supported
s9263b.1a NOT FOUND (NO GOOD DUMP KNOWN) (tried in sf2ce sf2ce)
WARNING: the game might not run correctly.


So to sum the problems we have currently are:

- The DSI to fix starting MAME from the main binary
- Adding an automatic script also to start the emulator with OpenGL enabled
- Fix the color issue on the text starting MAME with OpenGL enabled
- An option (tooltype?) for suppressing the shell output ?

Last edited by samo79 on 06-Mar-2013 at 01:10 PM.

_________________
BACK FOR THE FUTURE

http://www.betatesting.it/backforthefuture

Sam440ep Flex 800 Mhz 1 GB Ram + AmigaOS 4.1 Update 6
AmigaOne XE G3 800 Mhz - 640 MB Ram - Radeon 9200 SE + AmigaOS 4.1 Update 6

 Status: Offline
Profile     Report this post  
Spirantho 
Re: Help With MAME OS4 : What MAME To Use for JOYSTICK SUPPORT?
Posted on 6-Mar-2013 13:26:34
#35 ]
Super Member
Joined: 4-Jun-2004
Posts: 1045
From: Aberystwyth, Wales

@samo79

You can always
set HOME=RAM:
to get rid of those warnings. And you can run
Mame >NIL:
as well if you want.
If you don't have a Catweasel but still have the AmigaInput driver you may want to delete that from libs:AmigaInput (just in case).

Not sure what else to suggest to be honest as it doesn't happen here....

 Status: Offline
Profile     Report this post  
Goto page ( Previous Page 1 | 2 )

[ home ][ about us ][ privacy ] [ forums ][ classifieds ] [ links ][ news archive ] [ link to us ][ user account ]
Copyright (C) 2000 - 2019 Amigaworld.net.
Amigaworld.net was originally founded by David Doyle