Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Dead or Alive 2 Hardcore? EE Cache...
#1
OK I've spent a really long time trying to get it to work. First thing i did was enable EE cache and set it to interpeter then booted. It ran at 2.3-3fps on my Q6600. I had no speedhacks or gamefixes enabled. I waited for 1 hour until i gave up. That's about 150 game seconds. Should be long enough to see something right. I enabled everything in the console and the last part was
Quote:loadmodule: id 31, ret 0
loadmodule: fname cdrom0:¥MODULES¥TLSNDDRV.IRX;1 args 0 arg
DvdRead: Reading Sector 413(8 Blocks of Size 2064) at Speed=4x
DvdRead: Reading Sector 453(8 Blocks of Size 2064) at Speed=4x
DvdRead: Reading Sector 461(8 Blocks of Size 2064) at Speed=4x
DvdRead: Reading Sector 469(8 Blocks of Size 2064) at Speed=4x
DvdRead: Reading Sector 477(8 Blocks of Size 2064) at Speed=4x
DvdRead: Reading Sector 485(8 Blocks of Size 2064) at Speed=4x
DvdRead: Reading Sector 493(2 Blocks of Size 2064) at Speed=4x
DvdRead: Reading Sector 495(1 Blocks of Size 2064) at Speed=4x
loadmodule: id 32, ret 0
CdRead: Reading Sector 495(32 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 50891(32 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 50923(32 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 50955(32 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 50987(32 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 51019(32 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 51051(32 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 51083(23 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 51106(4 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 51110(32 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 51142(32 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 51174(32 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 51206(3 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 51209(2 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 51211(220 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 50587(220 Blocks of Size 2048) at Speed=24x
CdRead: Reading Sector 50807(36 Blocks of Size 2048) at Speed=24x
Quote:(pxEvtQueueTongueauseCoreThread) Posting event! (pending=0, idle=0)
(pxEvtQueueTongueauseCoreThread) Executing... [Cancelable]
(pxEvtQueueTongueauseCoreThread) Event completed in 375ms
this part repeats over and over and over again with a random ms
I checked exactly when the last console messeged popped and it was 80 seconds in and the last 59 minutes were a waste. and Nothing out of the ordinary as far as i can tell. Also tried software renderer only to achieve the exact same results. With the VU0 and VU1 at interpeter the
Quote:(pxEvtQueueTongueauseCoreThread) Posting event! (pending=0, idle=0)
(pxEvtQueueTongueauseCoreThread) Executing... [Cancelable]
(pxEvtQueueTongueauseCoreThread) Event completed in 375ms
doesn't show up. Since refraction said EE chache needs to be enabled at the loading parts does that mean it can be disabled during fights if by some miracle it booted? And what's the EE chache exactly and why is it so slow? I know the ps2 is a really complex console but what possibly could be this slow?
Reply

Sponsored links

#2
sorry im afraid yours is one of the versions which doesnt work still Sad so far i only know of one which actually works, which is very frustrating for many people >.< sorry Sad
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply
#3
(05-06-2011, 02:15 PM)refraction Wrote: sorry im afraid yours is one of the versions which doesnt work still Sad so far i only know of one which actually works, which is very frustrating for many people >.< sorry Sad

oh well. Support in the future maybe in 0.9.9 2 years from now. About my other question what is EE chache and why is it not compatible with recompiler?
Reply
#4
LOL. This is beginning to make me feel stupid, but I just gotta ask.

Why is everyone saying 2 years? 0.9.7 was released less than a years ago. I know it hardly guarantees anything (as if anything could be in this case), but it's more of an indication of 1 year, right?
Reply
#5
0.9.9 is the start of 'beta testing' for 1.0.0... If 0.9.7's anything to go by, it'll be another 2 year beta that will look drastically different over the course of it Wink
[Image: 2748844.png]
Reply
#6
I dont think you can put a timescale on this project at all, but please dont set us "goals" because rumors spiral out of control, then people expect it. i mean what if we all spontaniously combust tomorrow? You won't be getting your emulator then, but instead of people feeling bad about it, we will get rants for not sticking to our promises that we never made about releasing in 2 years!

seriously, it isnt worth it!
[Image: ref_sig_anim.gif]
Like our Facebook Page and visit our Facebook Group!
Reply




Users browsing this thread: 1 Guest(s)