Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

namco/namcops2.cpp: correct notes with regards of THE IDOLM@STER & V300 I/O boards #11581

Merged
merged 3 commits into from
Apr 4, 2024

Conversation

Keropon
Copy link
Contributor

@Keropon Keropon commented Sep 30, 2023

Updated the dump status of THE IDOLM@STER & Minna de Kitaeru Zenno Training.

Also added some info about the V300 FCB PCB found on the actual THE IDOLM@STER cabinets.

@Keropon Keropon closed this Sep 30, 2023
@Keropon Keropon changed the title Small d fix Updated Idolm@ster & added V300 data Sep 30, 2023
@Keropon Keropon reopened this Sep 30, 2023
@Keropon Keropon changed the title Updated Idolm@ster & added V300 data Updated THE IDOLM@STER & added V300 data Sep 30, 2023
@angelosa angelosa changed the title Updated THE IDOLM@STER & added V300 data namco/namcops2.cpp: correct notes with regards of THE IDOLM@STER & V300 I/O boards Nov 17, 2023

Notes: V300 FCB PCB is almost identical to the V290 FCB PCB. The main differences are changed internal MCU
code & PIC code, more output transistors and an traded the RS-232 for a RS-232C IC.
[to-do]

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"and an traded the RS-232 for a RS-232C IC". What? Come on at least write proper English/grammar. Anyway this part quoted is not required. In practical terms for emulation purposes there is no difference between RS-232 and RS-232C

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the destructive commentary. English is not my first language.
I copied a note that was similar and lots of people look at MAME's documentation to find quirks or details about some hardware, so I included it for completion's sake. No need to be like that.
Will edit.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In future if you are going to make changes to existing docs, before submitting, first run it by someone who speaks English to avoid this situation. Anyway your whole addition is pointless as PS2 emulation will never be working in MAME to any level of playability and those games that require touchscreens and special IO boards and/or networked/multi-screen games will also never be working. This driver serves only one purpose..., to preserve the ROMs and HDD/CD/DVD dumps.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are other emulators that utilize MAME drivers and documentation as a basis for naming conventions and guidelines regarding ROM/dump names. I've used them myself as a reference to identify the necessary components for running my own 2x6 hardware. I don't believe it's 'pointless', and I hope other reviewers share the same perspective.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Anyway your whole addition is pointless as PS2 emulation will never be working in MAME to any level of playability

Nobody in the dev circle really cared so far, already replied to this in the past, it's not a never ...

In future if you are going to make changes to existing docs

I'm honestly of the opinion that these super verbose docs can live as separate markdown files in 2023. They don't help at all when you have to jump back and forth between multi thousand lines of headers.

@cuavas
Copy link
Member

cuavas commented Dec 13, 2023

@Keropon do you have photos of the V290 and V300 I/O boards with PCB and chip silkscreen readable?

@Gurudumps
Copy link

I documented V290 in the src....
https://github.com/mamedev/mame/blob/master/src/mame/namco/namcops2.cpp#L585

V300 is the same board with a sticker over the top of V290....
https://imgur.com/a/isBNG62
Differences are the number of driver transistors and connectors populated and possibly the PIC and MCU code.
All extremely unimportant given that PS2 h/w isn't emulated/working and the games will boot (for emulation purposes) with a number of whitelisted I/O boards.

@cuavas
Copy link
Member

cuavas commented Dec 13, 2023

All extremely unimportant given that PS2 h/w isn't emulated/working and the games will boot (for emulation purposes) with a number of whitelisted I/O boards.

MAME isn't just about playing games on your PC. You of all people should know that. Also what isn't emulated changes over time, and having more complete information helps down the road.

@Gurudumps

This comment was marked as off-topic.

@angelosa angelosa merged commit 97bb58a into mamedev:master Apr 4, 2024
@Keropon Keropon deleted the small-d-fix branch April 4, 2024 13:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants