|
|
Post by Master on Sept 19, 2007 2:23:26 GMT -5
hi .. i really wanna know what are necessary to start the job ?
tanx in advance
|
|
|
|
Post by patrickp on Sept 19, 2007 12:47:00 GMT -5
Depends what point you're starting from, Master. Do you have good programming skills - and I mean good; average programming skills won't cut it for an emulator?
|
|
|
|
Post by Ultima on Sept 20, 2007 19:24:24 GMT -5
I'd imagine people with a decent knack for programming could potentially improve their skills by writing emulators. So I'm not sure he necessarily has to already be good at programming. It also depends on what system you're trying to write an emulator for. You'd probably be better off writing an emulator for a less-complex system before jumping into something like... (for example) a PlayStation emulator -- unless you've already got excellent programming skills. What simple systems there are out there, I've no clue. I recall some other people talking about writing a CHIP-8 emulator as their first foray into the emulator-writing world. Exactly what the CHIP-8 is, though, I also have very little knowledge about (other than what's written on Wikipedia) xD |
|
|
|
Post by Master on Sept 21, 2007 1:29:49 GMT -5
well tanx .. i started learning programming languages like C and C++ on my own 8 month ago ..
and cuz i was on my own ... i had difficulties going through tough stages .. .
after all i can say that i know sth that can fulfill my own needs in programming , but i really ahve no idea if that is enough to go and have challenging experience like making an emulator ...
well my problem is not that i can or i can not ...
the problem is how to start and what is needed to start the job ...
i dont know the concept .. can you understand me .?
just wana know the procedures ... how these guys find out to make an emulator this way .. ?
|
|
|
|
Post by Gamesoul Master on Sept 21, 2007 4:37:29 GMT -5
Many authors of emulators for the more advanced systems (SNES/Genesis and later) started out working with simpler systems to try and emulate. The NES, Gameboy, Sega Master System, etc... all good gaming systems to start out on if you have a good grasp on programming. If you need something simpler, check out this page from the main page of the link listed below, as it gives lots of links and information for people who are first starting out with emulation and want to start with something very simple. With your (relatively) small level of experience in programming, you will either want to learn more before starting any kind of emulation project, or check a site like this one for information on starting out and the tools necessary to do so. You may want to consider checking out some open source emulators for the simpler systems, to get a good look at what has to be done to write an emulator. One thing you really need is the passion to write and *stick with* writing an emulator, as well as programming in general. Those who do not have a strong passion for programming will find it much more difficult and frustrating to try something like writing an emulator. |
|
|
|
Post by Master on Sept 21, 2007 8:22:03 GMT -5
so many tanx .. lets try it out
tanx guys ..really tanx
|
|
|
|
Post by Sune on Sept 21, 2007 11:28:10 GMT -5
|
|
|
|
Post by psicomaniaco on Oct 2, 2007 7:29:41 GMT -5
Just FYI, the Nes isn't THAT easy to emulate. The nes has all that mappers, and a game from one mapper will NEVER work with another mapper. Its a little complicated because of this.
The first time I tried writing an emulator it was for the Genesis system. The first version could already run some games at a nice speed.
The Snes isn't all that hard either, but since lots of games have addons chips inside their cartridges (like Star Fox, Mario Kart, Megaman X3, etc), it will be harder to emulate some of the more famous games.
And the "*stick with*" thing GM mentioned is true. I have about 5 INCOMPLETE emulators here, because I don't have the drive to continue the project... So I just start another pone, but I'll surelly never finish it...
|
|
|
|
Post by Gamesoul Master on Oct 2, 2007 21:37:27 GMT -5
Well, the NES isn't that hard to emulate. Sure, there are a lot of mappers, but the idea to start out isn't necessarily to reach high compatibility, but rather the ability to make the emulator work with some games in the first place. And putting in place some of the mappers is good experience anyway, even if you only go for a few.
|
|
|
|
Post by psicomaniaco on Oct 3, 2007 7:23:50 GMT -5
Well, you got a point there. But I still think the Genesis is easier to emulate.  |
|
Deleted
Deleted Member
Posts: 0
|
Post by Deleted on Oct 3, 2007 17:12:41 GMT -5
What you really need to write an emulator is time.
|
|
|
|
Post by whitetigerx7 on Nov 11, 2007 23:09:22 GMT -5
Well I attempted this a few years ago and found I had zero time to do this as an undertaking.
Here's what I suggest:
1. Get as much documentation on how the console or computer system you wish to emulate of how it works and what it works with and uses. The more you know about how it works and what does what, the better.
2. Learn C/C++ programming languages, API interfaces, and CPU optimizations. You may want to go to school for this one.
3. Never be afraid to ask for help. There is no "I" in TEAM. More people means more input and more resources.
4. "KISS" Keep I Simple Stupid! No dice but the less complex and less useless features in a program the more streamlined and user friendly it will be. Bells and whistles are nice but they only cause problems when it comes to getting real issues like bugs and compatibility issues out of the way. Only devote time to something when you know you've squashed enough bugs and compatibility problems.
5. Open source and SVN are not always a bad idea. Open sourcing your code even under the BSD or Open License is still just as good as the GNU or GPL license. People still can help you out, work can go faster, and projects can stay active.
|
|
