|
Querying MAME for system information
#382521 - 05/22/19 06:29 AM
|
|
|
Hey all.
So I'm trying to query MAME to find out information about a system (Vtech) to see what sort of controllers MAME is enumerating.
Is there an easy way (commandline or from within the system running) to see what MAME is expecting?
(I have an ulterior motive. I used to use one of these 30 years ago, and I remember one of the selling points being the "16 way" joystick these had, so I wanted to see if that had been wired up to the driver)
Cheers!
|
"Curiouser and Curiouser" Cried Alice
|
|
|
Re: Querying MAME for system information
[Re: Cheshire Noir]
#382553 - 05/23/19 11:18 PM
|
|
|
> Hey all.
> So I'm trying to query MAME to find out information about a system (Vtech) to see
> what sort of controllers MAME is enumerating.
> Is there an easy way (commandline or from within the system running) to see what MAME
> is expecting?
>
> (I have an ulterior motive. I used to use one of these 30 years ago, and I remember
> one of the selling points being the "16 way" joystick these had, so I wanted to see
> if that had been wired up to the driver)
>
> Cheers!
Your question is rather ambiguous about what system you are referring to. So I'll try to address it as best as possible.
"Vtech" returns results from many products in different times on MAME. This for example has not mention about any joystick in the source. However it isn't 30 years old either. If you want to know what source file corresponds to the system you are looking for, you can use the "mame system -listsource" parameter.
Your best option would be to use the "mame system -listxml" parameter and find the relevant information yourself. For example "mame laser500 -listxml" returns:
Code:
C:\Emus\MAME>mame laser500 -listxml | more
<?xml version="1.0"?>
<!DOCTYPE mame [
<!ELEMENT mame (machine+)>
<!ATTLIST mame build CDATA #IMPLIED>
<!ATTLIST mame debug (yes|no) "no">
<!ATTLIST mame mameconfig CDATA #REQUIRED>
<!ELEMENT machine (description, year?, manufacturer?, biosset*, rom*, di
sk*, device_ref*, sample*, chip*, display*, sound?, input?, dipswitch*, configur
ation*, port*, adjuster*, driver?, feature*, device*, slot*, softwarelist*, ramo
ption*)>
.
.
.
<machine name="vtech_joystick" sourcefile="src/devices/bus/vtech/ioexp/j
oystick.cpp" isdevice="yes" runnable="no">
<description>Laser/VZ Joystick Interface</description>
<input players="2">
<control type="joy" player="1" buttons="2" ways="8"/>
<control type="joy" player="2" buttons="2" ways="8"/>
</input>
</machine>
</mame>
No 16-way joystick too.
|
|
|
|
Re: Querying MAME for system information
[Re: BIOS-D]
#382558 - 05/25/19 08:21 AM
|
|
|
> Your best option would be to use the "mame system -listxml" parameter and find the
> relevant information yourself. For example "mame laser500 -listxml" returns:
Ooh! This is exactly what I needed. Thanks for that BIOS-D
mame64 crvision -listxml > Creativision.xml
I then thumbed through the resultant file and...
< control type="joy" player="1" buttons="2" ways="8"/ >
So yep. That looks wrong. Guess I'll be off to raise a bug report :-)
Thanks again, BIOS-D
|
"Curiouser and Curiouser" Cried Alice
|
|
|
|
> > Your best option would be to use the "mame system -listxml" parameter and find the
> > relevant information yourself. For example "mame laser500 -listxml" returns:
>
> Ooh! This is exactly what I needed. Thanks for that BIOS-D
>
> mame64 crvision -listxml > Creativision.xml
>
> I then thumbed through the resultant file and...
> < control type="joy" player="1" buttons="2" ways="8"/ >
> So yep. That looks wrong. Guess I'll be off to raise a bug report :-)
>
> Thanks again, BIOS-D
You're welcome. I am not exactly an electronic expert but unless I am missing anything and looking at photos I don't think that could handle 16 directions.
EDIT: I'm taking that back. It indeed handles 16 directions with 8 digital contact points. So that might explain why MAME is set to 8 way.
[ATTACHED IMAGE - CLICK FOR FULL SIZE]
Edited by BIOS-D (05/25/19 05:19 PM)
|
|
|
|
Re: Querying MAME for system information
[Re: BIOS-D]
#382570 - 05/27/19 12:38 PM
|
|
|
> EDIT: I'm taking that back. It indeed handles 16 directions with 8 digital contact
> points. So that might explain why MAME is set to 8 way.
It was an odd beast, that one.
It is on my list of "If one becomes available, BUY!" now that I have enough c64s to sink a battleship.
|
"Curiouser and Curiouser" Cried Alice
|
|
Previous 
Index 
Next 
Threaded 
Querying MAME for system information
Reply
[Re: 
