Quoted from yonkiman:Sounds like you're not familiar with linux, MythTV, or tens (hundreds?) of thousands of other software projects that people individually or collectively do for free. And how about Visual Pinball - who do you think created that and draws & codes all the playfields?
Motivation is usually:
- It's something they are passionate about so they make it and they want to share
- It's something they need so they make it and they want to share
- If you're a professional programmer, it's great to have some examples like this for your portfolio when looking for work.
- Probably lots of other reasons, I'm not a sociologist/psychiatrist.
To get even closer to exactly what I'm talking about, here's a personal example: I had a PC with an Asus K8N-E motherboard with on-board SATA ports. The SATA chip (Sil3114) (the hardware) supported 2TB drives, but the K8N-E BIOS used older SiI3114 firmware and would only support drives 1TB and smaller. So I read up on BIOS hacking and eventually was able to replace the original SiI3114 firmware in the BIOS with the latest version. It solved my problem and I made that BIOS available on the web for others to use. I still get 1-2 emails a year thanking me for doing it.
So you can bet that if the HS2 source code was made available with a compiler, I would not only fix the HS2 bugs I've brought up on this thread, I would look at adding features, enabling unused animations, improving the graphics (this was one of the earliest DMDs...they didn't have the time or experience to get all they could out of it), etc. And I would share my modified ROM image with anyone who wanted it.
And I guarantee you that someone would do the same for every popular (and probably most of the unpopular) pins out there.
So yes, there's a large, friendly coding community out there that loves doing this kind of thing and sharing.
-Fred
Fred,
You make some great points here. I actually work with several companies in the pinball industry designing everything from lower level OS/game framework code to higher level business applications that help them be successful. I understand Rick wanting to test the waters for "code updates" after the success seen by the DE Star Wars updates and Cactus Canyon. It makes sense to see who is interested because its actually a decent sized undertaking from the engineering side.
First you have to decide how you'll tackle these code updates. Do you do 2.0 versions (like Cactus Canyon), or do you modify the ROM image? Anyone who has actually had to deal with the APPLE system that ran pretty much every WPC title will tell you that, while it was great for working in 6809ASM, its a far cry from modern technology, and there is a bit of a learning curve. However the macros in the framework do make it bearable (Thanks Larry and Ted!).
Then actually getting the build chain running on a modern computer is a bit more extensive. WMS mostly used NT based systems back in the day along with several DOS tools for DMD animations.
The engineering side of it was really quite cool for the time, and it was a lot of fun working with these tools when I had the chance to tinker with them.
Being the geek that I am, I really hope that more people step up to the plate. We've got some really really smart pinhead engineers out there who often times create and contribute back to the community. In fact, much of the internet itself runs on open source software that came from community contributions similar to the ones we've seen in pinball.
I'll be watching these developments closely!