DaedalusX64 Alpha Revision 427 - Nintendo 64 Emulator for PSP

***wraggster*** · August 10th, 2009, 00:42

Kreationz has posted a new alpha version of the Nintendo 64 Emulator for PSP, heres the release notes:

Upgrade Procedure: Grab the link and unzip it. Delete all *.hle files(in SaveGames) as well as preferences.ini and rom.db from your memory stick. These files (*.hle, rom.db, and preferences.ini) are rebuilt when you use the software and are version specific. Then you can copy it to your current folder on your PSP and overwrite all the old files. Now you are guaranteed to be starting fresh.

Changelogs:

Rev 427 [~] Forgot a couple of things.
Rev 426 [!] FlatShade and ViewPortHack should use flags to compare.
[+] Turok: The Dinosaur Hunter and Tigger's Honey Hunt will use DoubleDisplay.
Rev 425 [!]Reworked Double Display Lists, it is now enabled in roms.ini on a per rom basis as needed to prevent breaking roms

Enjoy,
Kreationz

Download and Give Feedback Via Comments

**Mista Grimm** · August 10th, 2009, 06:48

damn, the progress on this is amazing

**mike_jmg** · August 10th, 2009, 18:59

really??

guess I'll have to try it out later

**Buddy4point0** · August 11th, 2009, 01:40

You do realize these Revisions are not really made to be news posted about.

They're designed so that developers and beta testers can report issues and lend help.
They're not stable enough for widely public release like these news posts are causing.

**juiceface** · August 11th, 2009, 07:20

the more people that report issues the better, developers or not

**ojdon** · August 11th, 2009, 21:39

Not really, since developers know what they should be looking for. Users are mainly downloading it expecting that it's going to be really stable and any bugs they do find is by luck most of the time and will start bitching about how it ruined their 2 minute game session.

**Kreationz** · August 13th, 2009, 21:27

These are being released for public consumption, but they are Alphas(which can be buggy or not :P). There are big things are around the corner, but they will be in semi-private Alphas until tested fully and then released for feedback. Major bugs in the new code will get fixed. Then a few Alphas later and these releases will stop for a while.
After which there won't be a major release until we're satisfied (the entire dev team that is, including strmnnrmn, he's around just busy) at which point we'll release RC1 in prep for 1.0 :thumbup: (There are milestones left we want to get through before we get there though.)

Note: All I would ask is mentioning that they may not be stable when posting future Alphas.