As some of you may already know, Conker's Bad Fur Day is finally running on DaedalusX64 again as of revision 566. And yes, this does mean that you are able to get past the dreaded wink, and are able to get in-game. To do this you need much patience and a bit of button mashing, or you can use the savestate provided below.

The intro of this game does not look too bad, but the rest of the game is hindered with various graphical glitches. These graphics do not cripple the game, but may be annoying for some. Some of these glitches include missing blendmodes, weird behavior of characters, stretching of characters, missing textures, missing pupils, Conker's eyes seem to bulge, etc. For some reason a box with a white border appears for no reason at all, but again, this does not prohibit you from playing. When you get in-game, the graphics and textures seem to disappear an reappear when you walk around. After the wink, a short Despite the plethora of graphical errors, the text seems to show up very well in the typical Rareware font that we've come to recognize.

After the intro you will see a black screen with a single blinking pixel, but we can still see the memory access light flickering, so we know the rom hasn't crashed. This is where a little button mashing will get you past the menu, and into the intro movie. Just bear through these, and keep in mind that just because the screen is black, much of the intro, does not mean that the game has crashed. It is easy to tell if you have "Display Framerate" enabled in the "Global Settings" menu. Just keep an eye on the framerate, and if it stops for a prolonged period of time, then it is safe to say that the rom has crashed, which I have yet to experience. After a couple minutes of button mashing you will be in-game, and be free to explore the world of Conker's Bad Fur Day.

As you can already tell, the Intro runs very slowly at about 30% sync, but runs much faster in the intro movies and in-game. The speed skyrockets to 70% sync during the intro movies, during and after the main menu. Once you get in-game the speed seems to stabilize at 40% sync, which does not feel as slow as it sounds.

The audio is very unstable. Both Sync and Async audio freeze the Emulator, but one time I got a speed boost and made a savestate, featured below, that may increase the speed a bit. Once I got in-game the audio would not work at all.

I did not experience any freezing except for the audio problems, but the controls became unresponsive when I went into an area I was not supposed to be in.

The settings I used are...
Frameskip:2
Clean Scene: Enabled

Please scroll down for screenshots and savestates.

Note: I used the (U) rom to make these savestates, and test this game.

Good job, thnx for posting the saves.

PS : Looks like the entry on the compat list might need an update

The white textures are because there is not enuff texture memory left...
I will commit Kreations 16bit screen mode as a compile option soon. 16bit as opposed to 32bit should save some additional memory
that can be used for textures.

Real quick question, did you use default settings besides fs 2 and clean scene? or was everything else disabled?

anywho, awesome post and finds.

Also forgot to mention that most of graphical issues are due the custom vertex ucode for Conker is missing.
Conker has DMA issues, that's the most likely reason controls fail.

I still can't get this game to boot up, just turns off my PSP (Fat) 1003 using Rev 566, general release - are you guys using Slim PSP's or something!!!!
and yes i have deleted the .HLE & Roms.db, i have no plugins activated.

wow that looks really glitchy right now o.O

@Canadian1309 Yes, I used the default settings besides Fs 2 and Clean Scene Enabled.

@KingPepper Yes, I used a Slim PSP with 5.50 Gen-D3 CFW.

I see. Well then I have to agree with kingpepper on this one, the rom cant boot no matter what I try. Fat 1001 cfw 5.50 gen d3, rev 566.
I'm no code magician, but it would seem something to do with the slim model is helping them boot it up.

Boots perfectly for me, I'm using a slim though.

Try one of the savestates I provided.

tried saveslot2.ss with the previously listed settings to no avail. crash instantly 0 frames in.

one thing I noticed, if you turn off dynamic loop then it will get .1 frames a sec with 7.3-7.4 % sync
I know its nothing exciting, but it boots for that split second...
Hopefully this helps somebody

Seems like the PSP Phats don't like Conker
Could be a memory issue, Conker is one big ROM with 64MB...

well conker doesnt work on phat on rev 500 either so it never worked on phat i guess and since its running out of vram on slim i think its a vram issue... we rly need that texture compression lol

Actually there was a time when Conker worked on my Phat PSP, problem is no idea what revision it was, it was in the 4 hundred's somewhere i believe.