correct, controls are external. The way external things interact with the PCB emulation is not part of the project goal.
Handling input is essential and very much internal part of any game's functionality. Monitor is not part of PCB, so it is fake scan-lines, stretching, blurring and filtering that is EXTERNAL (unnecessary).
There is nothing conflicting about these statements. Playing the games is a side-effect of correct emulation. To obtain correct emulation it is necessary to have people using MAME. It's a CYCLE.
"Playing the games" is the same thing as "people using MAME" in the next sentence. It can either be necessity or side-effect, not both, one excludes the other. It is either intentional or coincidental, conflict is in relation to potential legal liability.
You've clearly not played many games, pretty much every PS3 game, and an awful lot of 360 games have severe tearing. You might not like it, but it's a fact.
GT5 for example has it almost all the time.
http://uk.gamespot.com/ps3/driving/granturismo52/show_msgs.php?topic_id=m-1-57294186&pid=941103
Other people in that thread, and I, dispute there is any tearing. Simple sync to monitor refresh solves all the tearing problems, so the guy reporting it was possibly having some issues due to video conversion or NTSC/PAL settings, or was simply referring to some other visual artifact as "tearing". -- One of us is not telling the truth, I mean you.
The games DON'T sync to vblank, there are many many games which don't. I have / have rented over 100 xbox / PS3 titles and I can tell you at least half of them DON'T sync, at all. Another one with REALLY bad tearing is Saint's Row, on the 360 tears every time you turn. Having worked in the industry I know the effect, I know what causes is, and there are plenty of developers reluctant to sync to vblank these days, especially on the PS3.
Your attitude here absolutely stinks. You refuse to believe what you are being told, no matter how clearly it is explained.
You come up with your own BS reasons about why things are done, just as X2 has attempted to do, despite being told, and having things clearly explained by me, one of the people who ACTUALLY BEEN INVOLVED IN MANY OF THE DECISIONS.
Which part of 'if you want change, create your own build' do you not understand?
Do I care if people are using old versions? Not really, their choice, they ARE missing out on a lot of other improvements, but if it works for them, it works for them. Maybe not being directly involved in the project people are missing out on the astronomical number of fixes made all the time, fixed based on user feedback from running the emulator and finding bugs in the actual emulation, which make it very hard for me to trust something as old as 0.90, 0.106 or whatever else to offer a solid level of emulation. Part of that user feedback may well have been that it was impossible to test 720 properly on a PC due to the absurd controller requirements in older builds which was a sentiment obviously shared by the development team.
If you plan on ripping out the control scheme which actually allows me to run and test 720 on a normal PC, which is what 99% of the devs own, I will oppose that change. Being able to test and develop something, on normal hardware is a REQUIREMENT. Being able to hook up the original controller IS NOT A REQUIREMENT.
If you plan on adding excessive configuration options Aaron will almost certainly oppose / reject your change, he's expressed before he wants to keep command line switches etc. down to a minimum.
As I've said, and will continue to say, the ability to hook up the original controller has nothing to do with the accuracy of the emulation. Being able to test it on a standard PC, to ensure the accuracy of emulation has everything to do with the accuracy of emulation.
You can quote me all you want, the quotes you've used were my way of attempting to encourage users to look elsewhere, use other emulators. While I like having everything in MAME, I don't believe a MAME monoculture is healthy, for one, it means morons keep bugging us about how they want specific features, such as .. 720 controls .. whereas if there was more choice people could just go where the choice was. If you hadn't noticed, I've been saying 'create your own build' quite often. When popularity means people expect MAME to do everything, even things the developers don't really want to do then it IS a problem, and people SHOULD be looking elsewhere.
There are MANY areas in which MAME hasn't decided to go with what is 'popular'.
There is still no official netplay (although at this point, providing the solution was reasonable like ClientServerMAME it does provide a good way to test deterministic behavior and state support)
There are no destructive image filters (eagle, 2xSAI)
There is no fake 3d acceleration on things like PSX, N64, Saturn hardware
There are no 'fake' systems with purposely overclocked CPUs to eliminate slowdowns
There are no 'fake' commandline options to run all games at 60fps internally, screen tear is considered a better option.
There are no fake transparency effects on 2D fighters
There are no fake macro inputs to make fighting game moves easier to pull off
There is no fancy windows GUI
There is no built-in force feedback (it's not cross-platform / device friendly)
There is no option to replace game sounds with custom MP3s and samples
There is no option to run the 'EmuDX' versions of the games
If all people want are these features, they should look elsewhere likewise if YOU want support for original controllers, you should look elsewhere too.
BUT, some features to make MAME attractive are needed, because as I've said more times than I care to count now, if there was NO testing, and NO userbase, then well.. the accuracy of emulation would probably be back in the 0.2x dark-ages. It's called striking a balance, ensuring that things CAN be developed and will get tested. It's also true that some of the non-essential options in MAME are just pet projects of the developers. The entire image filtering system we do have it just an experiment from Aaron. It's his code, and his part of the project, why shouldn't he be allowed to do a few things he wants to do there. It's an interesting piece of tech albeit one that didn't hold his interest for long.
So .. In the politest possible way the only thing I can say is:
If you don't like it then create your own build, and shut the #### up.
If you wish to continually talk down on the development team as if we've made some kind of mistake that's your problem, not ours, your condescending attitude does not help your cause, at all. You are nobody.