Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Pitfall problem...
#1
SLUS 20408

pcsx2-v1.5.0-dev-27-g3f17898-windows-x86

in the begining of this game, when I beat the leopard, then entered CG, then the game stop...
someone could help? thanks.

(EE pc:0033DCA0) TLB Miss, addr=0x550000c2 [load]

(EE pc:0033DCA0) TLB Miss, addr=0x550000c6 [load]

(EE pc:00000000) TLB Miss, addr=0x0 [load]

(EE pc:00000000) TLB Miss, addr=0x0 [load]

(EE pc:00000000) TLB Miss, addr=0x4 [load]

(EE pc:00000000) TLB Miss, addr=0x8 [load]

(EE pc:00000000) TLB Miss, addr=0xc [load]

(EE pc:00000000) TLB Miss, addr=0x10 [load]

(EE pc:00000000) TLB Miss, addr=0x14 [load]

(EE pc:00000000) TLB Miss, addr=0x18 [load]

(EE pc:00000000) TLB Miss, addr=0x1c [load]

(EE pc:00000000) TLB Miss, addr=0x20 [load]

(EE pc:00000000) TLB Miss, addr=0x0 [load]

(EE pc:00000000) TLB Miss, addr=0x4 [load]

(EE pc:00000000) TLB Miss, addr=0x8 [load]

(EE pc:00000000) TLB Miss, addr=0xc [load]

(EE pc:00000000) TLB Miss, addr=0x10 [load]

(EE pc:00000000) TLB Miss, addr=0x14 [load]

(EE pc:00000000) TLB Miss, addr=0x18 [load]

(EE pc:00000000) TLB Miss, addr=0x1c [load]

(EE pc:00000000) TLB Miss, addr=0x20 [load]

# Syscall: undefined (0)

padman: DMA Busy ID = c4a40008 ret = 0

        SB_STAT = f0000102

padman: DMA Busy ID = c4a40008 ret = 0

        SB_STAT = f0000102

padman: DMA Busy ID = c4a40008 ret = 0
        SB_STAT = f0000102
Reply

Sponsored links

#2
You might want to check the test report here:
http://forums.pcsx2.net/Thread-Pitfall-T...8-U--29930
[Image: newsig.jpg]
Reply
#3
(01-09-2016, 08:57 PM)Bositman Wrote: You might want to check the test report here:
http://forums.pcsx2.net/Thread-Pitfall-T...8-U--29930

thanks for your reply.
before I post this thread, I had already post a reply in that test report thread for this problem.
A friend here reply me that I can't post there.
I do the config as that test report said.
and that report write status: playable.
however, can't play along.
Reply
#4
(01-10-2016, 07:09 AM)littlemike2016 Wrote: I do the config as that test report said.
and that report write status: playable.
however, can't play along.
Ut's playable but you need :
Quote:Comments:
http://forums.pcsx2.net/Thread-Fixing-unplayable-games
Enable "Ignore Dmac writes when it is busy" game fix.Also seems to require 4 gb patch.

Bugs: black screen with Not the *Ignore Dmac...option activated.
CPU : I7 2600K Oc'ed @ 4.2Ghz
Mobo : Intel P67 southbridge
GPU : NVIDIA Geforce GTX 750 Ti
RAM : 6 Go
Reply
#5
(01-10-2016, 08:03 AM)jesalvein Wrote: Ut's playable but you need :

yes. i did.

[Image: CZgFiFp.jpg]


i also do the 4 gb patch.
in the begining, when I beat the feopard, then entered CG, when the CG is over , some errors as below, and the game freaze.

[Image: 11E3dIB.png]

could you or anyone retest it and help me, pls?
thanks. Biggrin
Reply
#6
As I reported earlier, the game doesn't work correctly even after that gamefix enabled. It will eventually hang at some point or other. That's the reason it's listed as ingame only even though destruidor reported it as playable.
Reply
#7
(01-10-2016, 10:40 AM)prafull Wrote: As I reported earlier, the game doesn't work correctly even after that gamefix enabled. It will eventually hang at some point or other. That's the reason it's listed as ingame only even though destruidor reported it as playable.

right.
I shall edit the compatibility report so that New users don't get mistaken
CPU : I7 2600K Oc'ed @ 4.2Ghz
Mobo : Intel P67 southbridge
GPU : NVIDIA Geforce GTX 750 Ti
RAM : 6 Go
Reply




Users browsing this thread: 1 Guest(s)