Viewing Issue Advanced Details
ID Category [?] Severity [?] Reproducibility Date Submitted Last Update
06586 Documentation Trivial Have not tried May 25, 2017, 20:06 12 days ago
Tester FMecha - aka ArtLine View Status Public Platform MAME (Official Binary)
Assigned To Resolution Open OS Windows 10 (64-bit)
Status [?] Acknowledged Driver
Version 0.185 Fixed in Version Build
Summary 06586: Various games: Games missing MACHINE_NODEVICE flags
Description Several games are missing MACHINE_NODEVICE flags, as listed below. (Originally this was only about SSF2 Tournament Battle, but this was later extended at Osso's suggestion.)

LAN:
cischeat.cpp: bigrun, cischeat, f1gpstar, f1gpstaro, f1gpstr2
cps2.cpp: ssf2tb, ssf2tbr1, ssf2tbj, ssf2tbj1, ssf2tba, ssf2tbh
f1gp.cpp: f1gp, f1gp2 (has link menu)
groundfx.cpp: groundfx
namcofl.cpp: speedrcr, finalapr, finalapro, finalprj
namcos11.cpp: pocketrc (there's menu for link, IIRC)
namcos22.cpp: ridgera2, raveracw, acedrvr, victlapw, cybrcycc, tokyowar (including clones, probably also alpiner, alpiner2, cybrcomm, adillor?)
neogeo.cpp/neodriv.hxx: lbowling, ridhero, trally
segaxbd.cpp: rascot?

CAMERA and/or PRINTER:
namcos23.cpp: raceon (CAMERA only)
neoprint.cpp: neoprint, npcartv1, 98best44, nprsp
taito_b.cpp: realpunc (CAMERA only)
taito_f2.cpp: yesnoj (PRINTER only)
stv.cpp: All Print/Name Club games

More shall be added as I skim around the cpp files or remember.

2019/4/7 Update: Realized MACHINE_NODEVICE_CAMERA isn't a thing.
Steps To Reproduce
Additional Information
Flags
Regression Version
Affected Sets / Systems Various games
Attached Files
 
Relationships
There are no relationship linked to this issue.
Notes
3
User avatar
No.13852
FMecha - aka ArtLine
Tester
May 26, 2017, 10:09
I've noticed some other games with network capability forgot this flag as well. Even realpunc doesn't have MACHINE_NODEVICE_CAMERA either...
User avatar
No.13853
Osso
Developer
May 26, 2017, 12:41
Maybe you could use this bug report to list all the games that are missing the NODEVICE flags?
User avatar
No.16286
Hydreigon
Tester
Apr 4, 2019, 15:34
edited on: 13 days ago
May as well bring this back from the dead but only for MACHINE_NODEVICE_LAN and explain some stuff.

harddriv.cpp: steeltal and clones (uses the DSPCOM I/O board for serial comms; emulation isn't fully complete yet; not used in racedriv)
atarig42: roadriot and clones (Either a DSPCOM or shared memory board is used)
atarigx2: all sets (similar situation to atarig42)
atarigt: tmek and clones (either a max232 or ltc485 (direct link for the twin cab); both serial based)
segaxbd/segaybd: smgp/clones, lastsurv and pdriftl (sailorsat demonstrated pdriftl's comms working but didn't commit; smgp and lastsurv has near identical network hardware)
konamigx: racinfrc and clone (rs232/LANC/shared ram combination, source not known yet)
midvunit: crusnusa, crusnwld/clones, and offroadc/clones (main processor, TMS320C31, provides rs232 networking)
gticlub.cpp/zr107.cpp: all zr107 sets, gticlub and thunderh (rs232/LANC/shared ram combination; the PPC 403GA has serial support)
taitojc.cpp: dangcurv/clone, sidebs/cones and sidebs2/clones (SMC COM20020I)
nwk-tr.cpp: all sets (similar to zr107 and gticlub)
cobra.cpp: racingjdx (as above)
hornet.cpp: sscope2 (as above)
gaelco3d: (same processor/dsp from midvunit, same method of networking)
midzeus.cpp: crusnexo/clones and grid/clone (slighting different revision processor from midvunit but serial ports function the same)

Really wish for more updates.

EDIT: Good thing I put that "NODEVICE_LAN" flag to more use.