I don't usually like to pry.... But, I do remeber awhile back that people were raving about the possibility of 64DD Emulation coming to fruition. Any internal updates on this. Is it already possible to do.
we re working on it, there's been much progress going on, especially thanks to Kammedo's latest efforts. Adjusting existing emulators is one option , but there has been discussion of an independent 64DD dynamic library so authors can adapt their emulators to. There's nothing more I d like to disclose at this moment though, it's better to showcase things once they re complete and functional.
I'm really glad to hear its going well Barcode. Not only is emulation of this important to perserve the few quality titles on the hardware. But, as we are slowly finding out, completion of this is imperative to the release of protos. With so many amazing things found in the dump (ala SNES CD) whose to say some collector isn't sitting on any of the awesome things that were in the works. I'd love to see a Zelda expansion myself. How cool would it be to take that Zelda 64 game that you thought was finished and simply go straight in majoras mask. PS: Thanks for the quick response and update
Could 64DD really be so complicated or secretive that DLLs are necessary? This is funny because I suspect FDS is more work to implement. Sounds to me like N64 emulation is still about 1337 recognition/money, no different than back in 1999. In the spirit of Marat Fayzullin/great emulator authors of the past, please just release documents
The idea arised in trying to get an independent interface tht could be used once and for all with all emulators present. Of course, not knowing anything about the single emus at all, i cant suppose it will be the proper (and thus the final) solution. We will see as time developes. Extreme programming is the key until then . PS : dont worry calpis, once everything is clear as the sky and its 100% certain that this is this and that is that docs will pop out like rain PPS : and already i said too much !
I'm not worrying, it's just that until 64DD emulation is ready, talk is nothing but a tease like the Mother 3 thread. I think you guys should keep it to yourselves until emulation is ready or publicly disclose your progress. All the secretive allusions to the work your team/club has accomplished I'm sure instantly earns respect from some but to me sounds pretty pompous. That said, here's your spotlight back heh
You may find talk to be a tease. But talk reports on the status of the project, and it lets people who are following the project be happy. Without talk and assurance that the project is being worked on it may cause the general population to question what is going on. No talk usually means a project has turned to vaporware. I.e. Dead Phoniex of the Capcom 5 The same goes for emulation and homebrew efforts. In other words if Barcode and kammedo want to release screenshots or throw a little attention to the project. Let them. Having people respond back with praise I'm sure is a boost to their spirits. And a boost to their spirits is a faster project completion time :110:. Btw thanks again for the update guys.
This: http://img525.imageshack.us/img525/2349/teaserjh0.jpg ? What does it mean though? It doesn't tell me at all how close emulation is to ready. Why not just say exactly the plan of attack and what's been reverse engineered and what's still left? All games use the 64DD library, right? So you don't even need actual emulation of the drive to get games working initially, shouldn't just hooking the library functions be enough? The functions reference manual appears to give a complete rundown of them, their parameters passed and returned. Get the addresses from the linking process and parameter (flag) values from the header files and you're well on your way to 64DD HLE. Where did you get the status of the project? So far all posts I've noticed are allusions to accomplishments (accidentally saying too much) i.e. only hype.
Regarding the teaser image: a) it's evidence that the game in question has been successfully dumped and in possession of the image producer. b) it acts as an appetiser for those who thought the day would never come to see it running on a PC. I appreciate your views, but please be aware that one of the reasons that we are not disclosing as much as you hope is because official tools might be used in accomplishing these ends. Hence, we don't want unwanted attention from you know who. That's really the main reason for being so low-profile about the whole thing. The second thing I d like to say (again) is that Kammedo is doing the hard work, so it's up to him to decide when and what to disclose. Again, it's "you know who" that I believe he wants to avoid, hence keeping a low profile. (this doesnt sparkle with kammedo) I hope for your understanding. We appreciate that people want us (or 64DD emulation in general) to succeed but there's no current need for outside funds hence no direct need to raise awareness. (this sparkles with us) In the perfect world we'd like to one day come out and present to everyone something that simply works. And to conclude, yes the project is on going and thanks to kammedo's commitment it's going stronger than ever.
A warning screen doesn't prove however that the 64DD is emulated at all. What are the "ends" though? I don't get what you're talking about because: 1) You don't need to give out any code, so using the SDK to write test programs is irrelevant. 2) The SDK doesn't have any low level documentation, so if you release it, it's obviously your own. 3) Nobody can tell that you dumped a disk using "you know who's tools" or your own. 4) If you can find the parts of the library linked to a retail code, which you can in game images, they're fair game for reverse engineering. If you're smart you can cheat at this too. Realistically, can you give the board a rough time frame? That's how you can differentiate your project from Corey's.
Since we re not on a pay-roll by anyone it will be ready when it's ready really. Both myself and kammedo are grown-ups with enough responsibilities as it is - providing extra deadlines that might be tramped on won't be to anyone's benefit.
It's ready when it's ready. Looking forward to it though. Especially if certain blue disks contain a certain game.
Not a deadline, but floating date, when onlookers can *start* raising their hopes. What really isn't to the onlooker's benefit is the cute teasing. Let's be real: if you don't want to disclose the slightest progress, don't talk about it until you're ready to. That's good internet etiquette since it's the objective user's job to separate the wheat from the chaff and so far we've reaped nil. PS: don't treat this as a personal attack on you guys, just a logical suggestion.
Trust you me, I ve been talking about 64DD dumping and emulation for the past 4 years. I d be the internet's ridicule if I had given any sort of floating date back then and I surely want to avoid such a scenario now. Fans will be more than pleased with the unavoidable end result. It's just a clock counting backwards but no one knows how long =)
