Open source changes everything for me. I'm really excited about VP again and what this can bring!
With that being said, I'm a prgrammer, specializing in VB/vbscript and i've dabbled in the mame source on occasion adding minor bug fiexes to the code. Oh I can also program in directX So if there are issues, I can help!
Speaking strictly as a programmer, here's what I'd like to see happen. (And keep in mind I haven't messed with VP in a LOOOONG time so some of this stuff might already be implemented.)
1. Get rid of the expirations, those were annoying for people putting VP in an offline cabinet that might get updated once every few years at best.
2. More robust command-line support. There always seem to be issues with using the "play" command programatically, so just drop it and launch via command-line like mame does.
3. Switch both pinmame and vp over to using mame's new output system and implement a input method using the same system. Since mame accepts all comers at this point (even photo booths are
emulated) The only thing keeping the pinmame roms from being in the official mame is the special input/output communication needed. Mame has evolved to the point that it can pretty much do the things needed for VP communication in the stock build. Merging pinmame with mame would mean less trouble for the pinmame devs as a custom build would no longer need to be maintained and also it would encourage mame devs to do more pinmame tables. It would also mean no more DDE. I like DDE, don't get me wrong, but it can be hard on the system resources.
4. Speaking of mame... regarding the handling of the source code should be done EXACTLY as they do it. Basically you have an email address setup for submissions... all submissions must be made by taking the untouched, latest source and comparing it via a "-diff" generator. This diff file is email to the head honcho and all he has to do to test it is use the diff to patch the official source. If it works then it's included next version.... if not then it's rejected. Then a forum is setup dedicated to nothing but documenting bugs. The system has worked amazingly well for mame, so I don't see any reason to try anything different.
5. Alpha blending...... These "faked" transparent ramps are getting silly. With that being said, I understand EXACTLY why it was disabled. Firstly alpha blending takes a lot of resources, if AB was turned on for every surface on a table it'd slow to a crawl. This can be fixed by only enabling it for specified geometry though. Secondly, and this is one people just can't seem to wrap their head around... alpha blending screws up shadow/light rendering. See directx can only "see" the flat geometry, so if you make a hole in a texture, it still thinks it's solid. That being said, I still think It'd be useful. I've seen you guys do amazing 3d "fakery" with nothing more than some tricky uses of decals, so I have no doubt adding it in would make from some amazing visual improvments.
I hope I don't come off as sounding pushy or demanding, I just figured if Randy's handing the keys over to US, we might as well hit the ground running.
(p.s. Excuse the grammar and spelling... it's 3 am here!)
Edited by HowardC, 11 March 2010 - 08:01 AM.




Top


Contributor
























are all trademarks of VPFORUMS.