This forum uses cookies
This forum makes use of cookies to store your login information if you are registered, and your last visit if you are not. Cookies are small text documents stored on your computer; the cookies set by this forum can only be used on this website and pose no security risk. Cookies on this forum also track the specific topics you have read and when you last read them. Please confirm whether you accept or reject these cookies being set.

A cookie will be stored in your browser regardless of choice to prevent you being asked this question again. You will be able to change your cookie settings at any time using the link in the footer.

Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Guide to decrypt EDAT files
#16
(07-06-2014, 06:24 PM)ssshadow Wrote:
(07-06-2014, 06:04 PM)AlexAltea Wrote:
(07-06-2014, 05:49 PM)ssshadow Wrote: Uh... backups? Or why didn't he just commit each days work to a separate branch on github like Nekotekina did with the SPU recompiler? Acts like a backup, if need be people can test on more games than his hard drive can ever carry, and it stops people from constantly asking for an eta...

I totally agree. The data can still be retrieved (afaik the HDD is fine), so I assume the reason for rewriting the recompiler is avoiding mistakes done in the first implementation, but I think that even those "old mistakes" are relevant for the rest of developers as well. So yeah: In short, you are totally right, but I can't do anything about it. You guys can PM him about such things I guess. Wink

Is he even on this forum? I assume you speak on IRC or Skype or something? You should tell him that even if the recompiler he has now is crap and just runs a single homebrew even slower than the interpreter, he should just put it up in a new branch. You can't keep that amount of code to yourself and spend half a year optimizing, rewriting, optimizing again and rewriting again, because he will never be finished.

Also, design mistakes in development can be avoided if other developers have access to the code and can review it...

+1 but if you notice your code is basically shit then you probably want to just start over with something more malleable.

I think the reason he didn't push changes to a public branch is so people would not get hyper and bug him about it or compile it and complain about things not working or merge it or whatever when it's not even finished. That's perfectly understandable.

He should have had a backup of the branch somewhere online, though.
Reply


Messages In This Thread
Guide to decrypt EDAT files - by Ekaseo - 06-23-2014, 08:33 PM
RE: Guide to decrypt EDAT files - by jacky400 - 06-24-2014, 05:46 PM
RE: Guide to decrypt EDAT files - by Ekaseo - 06-24-2014, 07:37 PM
RE: Guide to decrypt EDAT files - by ssshadow - 06-24-2014, 08:47 PM
RE: Guide to decrypt EDAT files - by jacky400 - 06-25-2014, 03:17 PM
RE: Guide to decrypt EDAT files - by woody2014 - 06-25-2014, 03:49 PM
RE: Guide to decrypt EDAT files - by ssshadow - 06-25-2014, 03:58 PM
RE: Guide to decrypt EDAT files - by jacky400 - 06-26-2014, 02:50 AM
RE: Guide to decrypt EDAT files - by jacky400 - 07-04-2014, 03:25 AM
RE: Guide to decrypt EDAT files - by umatuma - 07-04-2014, 03:37 PM
RE: Guide to decrypt EDAT files - by Dante38490 - 07-06-2014, 05:07 PM

Forum Jump:


Users browsing this thread: 2 Guest(s)