Links to review:
- restoration --04:34, 11 December 2013 (EST)~
- basics --Felsir Felsir (talk) 07:09, 11 December 2013 (EST)
- Arcade_Cabinet Felsir (talk) 05:35, 12 December 2013 (EST)
- Driving_Controls Felsir (talk) 05:39, 17 December 2013 (EST)
- Lighting (currently only deals with marquee, should eventually include all lighting options and branch out to specialized pages) Felsir (talk) 10:17, 18 December 2013 (EST)
- MAME the page looks messy and outdated. Felsir (talk) 07:24, 9 January 2014 (EST)
- MAME Variants Added to go more in depth. Felsir (talk) 07:24, 9 January 2014 (EST)
The list of emulators is outdated/incomplete (new stuff has arrived since the old wiki!). Once the FAQ is done, I think the emulator section will be my top priority (as this is where I struggled the most when setting up my own cabinet).Felsir (talk) 07:44, 8 January 2014 (EST)
Topics to fix/review:
"Displays, Input lag (Not response time)" needs fix/review.
- I split this one up in 'response time' in the display section and 'input lag' in the software section. My reasoning for this is: while I was typing how to deal with input lag, it dawned on me that this is essentially a software problem (the emulation adds too much to process the user input) thus I moved that to software. It did however leave a gap because the response time is probably a more well known term (incorrectly used but that's another thing) thus I used that in the display section to make the difference more obvious. Felsir (talk) 04:52, 13 January 2014 (EST)
- I think this somewhat addresses the incorrect usage and common misconception, but only addresses one aspect of input lag. As rCadeGaming points out here "A lot of input lag takes place during scaling and post-processing. The signal has already been received, but there is a period of delay during processing before the screen is even told to do anything about it." Lag can come from software (emulators), firmware (some cheap encoders) or hardware. (video converters or TV circuitry) Not sure if input lag should be under software. Not sure if the CRT "after glow" (phosphor persistence) part is needed. Part of the reason that response times >16ms are unacceptable is that that 16.67ms = 1 frame @ 60 Hz refresh rate. Not sure where the 5ms part comes from. The thing I'm most worried about on this subject is getting too deep in the weeds -- maybe we can find a good BYOAC thread on the subject. (I don't trust Wikipedia very much on this topic.) PL1 (talk) 07:58, 13 January 2014 (EST)
- Ah, from a display point of view it contributes to the input lag with features such as "smart color" on the TV itself (which is why some TVs have a "game mode"). I find "input lag" a bit difficult to classify, it's not a clear cut display issue and not a clear cut software issue. It could be anywhere in the chain Seeing image on screen->react by pushing button->encode sends buttonpress to pc->game processes input->game creates video image->emulator post processing->tv receives signal->tv post processing->display result.
- Perhaps it should be under displays because people probably blame the display first when encountering input lag? Felsir (talk) 08:18, 13 January 2014 (EST)
- I moved it to displays and changed a bit. What do you think? Felsir (talk) 09:05, 13 January 2014 (EST)
Images to find/make/fix:
Types of Cabs (small) -- Banner with Sketchup line drawing of each sub-type with human figure for scale.
What is JAMMA/JAMMA+? -- Pic of 56-pin JAMMA connector.
Mounting joysticks -- 4-player "straight" vs. "angled" joysticks.
Mounting options -- Diagram showing Top-mount, Under-mount (non-recessed), Under-mount (recessed), Threaded inserts, and Support blocks.
I made these:
- Great start.
- Consider using tan for the MDF on all 5 pics for greater contrast. (parts are blending together)
- Consider using a contrasting color for the threaded inserts, support blocks, and retaining plate/flat-stock bars for clearer identification.
- Support blocks should only be as large as the parts of the joystick mounting plate overhanging past the base. See this pic for block size example
- Support block pic should use threaded inserts instead of wood screws.
- For a great support block example, look at EMDB's undermount method here -- he uses a metal retaining plate, but you can get about the same support using 2 flat metal bars. (one per support block) He goes a bit overboard on the inserts -- 4 is enough. :) It is the best example with pics that I've seen.
How do I wire microswitches to an encoder? -- Diagram or picture showing three microswitches wired to an encoder and a daisy-chain ground.
Single-Color and RGB LED buttons -- Pic showing the lighting and switch wiring.
- Requested permission to use/edit the RGB wiring diagram at http://forum.arcadecontrols.com/index.php/topic,137025.msg1413332.html#msg1413332 PL1 (talk) 06:35, 11 January 2014 (EST)
Screenshots of Command Line MAME and GUI MAME to illustrate different variants of MAME.
- Other than the "in your face" font-size :-), that seems suitable. Felsir (talk) 08:21, 13 January 2014 (EST)
- Nephasth chose it. :) PL1 (talk) 08:39, 13 January 2014 (EST)
- Font size looks good, but it might look better if the male and female QDs are positioned like they are about to engage. (original pic, turn the red and blue female connectors 180 degrees) On closer examination, not sure if the resolution from the original image is OK or if we should find something with better detail and put a thumbnail on the FAQ/Wiring pages. PL1 (talk) 09:55, 13 January 2014 (EST)
Different build versions/variants of MAME
- MAME = factory original, most reliable
- NoNag/HighScore patch = putting on new rims or a spoiler
- Alternate builds = hotrods based on the factory original offering features not found on the original, but sometimes not as reliable
When you get parts (ROMs) for your car (MAME) you not only need to know the name of the part, you need to know the make/model/year -- a headlight for a 1972 Ford Mustang =/= headlight for a 2014 Ford Mustang.
As automotive technology improves year-to-year, several parts are improved, while others stay the same.
- I tried to include the analogy in the text but for some reason I struggle with the words :-( It might be an idea to write this in the MAME Variants wikipage? Felsir (talk) 05:49, 11 January 2014 (EST)
CPU performance chart
A topic that comes up a lot is "will my PC run (emulated) game X?". I was wondering if we could create some kind of scale. Something like a line with on one side names of milestone games, emulator names or "arcade games from year 2001". The other side of the line CPU, GFX card combos? Not sure if at all possible to create something like this with the myriad of combo's out there... It is probably too much for a FAQ, but the topic comes up a lot so it would be nice if it was possible to point to a dedicated wiki-chart for this kind of stuff. Felsir (talk) 05:05, 14 January 2014 (EST)
- Something along these lines User:Felsir/cpu-chart. I'll ask some reference points on the forum, let's see where this is heading. Felsir (talk) 05:35, 14 January 2014 (EST)
- Lots of threads on that topic. Maybe list various generations of processors (AMD+Intel) and the highest version of MAME that they will run at 100% for 1.)Classics 2.)Majority of games 3.)Toughest game of that MAME version. May want separate tables for MAME and other emulators. PL1 (talk) 05:50, 14 January 2014 (EST)